Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Troubleshooting

Troubleshooting

Update domain errors

Update domain errors

Consider the following troubleshooting tips when you update a
CDI-PC
domain:
When you initiate an update of a CDI-PC domain running as a Windows service, the domain starts in the process mode instead of the service mode.
Reason
: In JDK 9 and later releases, the
java.endorsed.dirs
system property is no longer available.
CDI-PC April 2025
has upgraded its JDK version to 11. The
java.endorsed.dirs
JVM property is part of the registry in a Windows CDI-PC domain configured to start as a service. This specific registry entry was created while creating the domain and was not modified during the update from the CDI-PC service page (DMS).
Solution
:
  1. After the domain is updated successfully, use the following command to stop the Informatica CDI-PC service on the target Windows system where you want to start the domain as a Windows service.
    INFA_HOME/tomcat/bin/infaservice.bat shutdown
  2. Run the following command to remove the Informatica CDI-PC service:
    INFA_HOME/tomcat/bin/infaservice.bat remove "InformaticaCDI-PC"
  3. Run the following command to reinstall the Informatica CDI-PC service:
    INFA_HOME/tomcat/bin/infaservice.bat install "InformaticaCDI-PC" "Informatica CDI-PC"
Error: No such file or directory error is being logged during
wait_for_node_shutdown
command
After you register a multi-node CDI-PC domain and perform an update operation, the update is successful. However, the taskoutput.log file contains the following error:
2024-07-30 15:39:53.692 INFO: [cf-task-pool-5][commandframework.TaskExecutor] [reqid:6E8WC6ayXzuix6r8vls2ac] [DML_20003] Subtask ID [wait_for_node_shutdown] started. 2024-07-30 15:39:53.692 ERROR: [cf-task-pool-1][commandframework.TaskExecutor] [reqid:6E8WC6ayXzuix6r8vls2ac] [DML_30001] Command [/data/Informatica/cdipc/202410_update_hardening/master/Informatica/platform/home/isp/bin/plugins/ms/clientgateway/msgateway.sh stopservice] failed. Error: [Cannot run program "/data/Informatica/cdipc/202410_update_hardening/master/Informatica/platform/home/isp/bin/plugins/ms/clientgateway/msgateway.sh": error=2, No such file or directory] 2024-07-30 15:39:53.693 INFO: [cf-task-pool-5][commandframework.TaskExecutor] [reqid:6E8WC6ayXzuix6r8vls2ac] [DML_30003] Node service operation [shutdownAndWait] started. 2024-07-30 15:39:53.695 ERROR: [cf-task-pool-1][commandframework.TaskExecutor] [reqid:6E8WC6ayXzuix6r8vls2ac] [DML_30001] Command [/data/Informatica/cdipc/202410_update_hardening/master/Informatica/platform/home/isp/bin/plugins/wfs/cmdgw/wfsgw.sh stopservice] failed. Error: [Cannot run program "/data/Informatica/cdipc/202410_update_hardening/master/Informatica/platform/home/isp/bin/plugins/wfs/cmdgw/wfsgw.sh": error=2, No such file or directory] 2024-07-30 15:39:53.695 INFO: [cf-task-pool-1][commandframework.TaskExecutor] [reqid:6E8WC6ayXzuix6r8vls2ac] [DML_20005] Subtask ID [stop_gateway_services] succeeded.
You can ignore this error.
Error:
The request failed because of error [Connection refused (Connection refused)]. Please ensure the requested host and port are proper and the process is running on the requested port.
This error appears when update fails because you couldn't connect to the
CDI-PC
domain.
Updating the
CDI-PC
domain fails because of one of the following reasons:
  • The
    CDI-PC
    domain is unavailable before the Listener service starts. Restart the
    CDI-PC
    domain and retry the update process manually.
  • There is no communication between
    Informatica Intelligent Cloud Services
    and the
    CDI-PC
    domain. Resolve the network issues and retry the update process manually.
  • CDI-PC
    domain node is unavailable. Restart the node and retry the update process manually.
For more error details, see the
Domain Management App
log file.
Error:
/export/home/ispqa/<user_name>/Node1/Informatica/platform/sys/apps/listener/202308/dmlistenerlauncher.sh (Permission denied)
This error appears when update fails in the Initialize stage because the
dmlistenerlauncher
script doesn't have correct permissions to run the script.
Solution
: Assign
execute (755)
permission to the
dmlistenerlauncher
script and retry the update process manually. For more error details, see the CloudConnect log file.
Error:
INFO: [
][commandframework.TaskExecutor] [reqId=85e0157411a142139df8330009883ca1] [DML_30051] Required disk space [10,000MB]. Available disk space [1,788MB]. 2023-05-09 15:36:32.079 ERROR: [cf-task-pool-1][commandframework.TaskExecutor] [reqId=85e0157411a142139df8330009883ca1] [DML_30052] Required disk space is unavailable.
This error appears when update fails because the required amount of disk space is not available on the node.
Solution
: Create the required amount of disk space (a minimum of 10 GB) and retry the update. For more error details, see the taskoutput log file.
Error:
[DML_20010] Task [Downloading patch] failed on node [node01] in host]. Please check the Listener logs of the node [node01] for more details. For more details, view the LISTENER logs in listener. <System log directory>/listener/DMLTaskOutputError in taskoutput log
This error appears when update fails because the
CDI-PC
binaries are not available in the Secure Agent.
Solution
: Make sure that the Secure Agent contains the appropriate binaries. For more error details, see the taskoutput log file.
Error:
[pool-3-thread-2][commandframework.TaskExecutor] [reqId=deee669b67064b07979e742c4cd17842] [DMU_10009] Can't download the file. ERROR: [Connection reset]
This error appears when update fails because you can't connect to a
CDI-PC
domain.
Solution
: Resolve the connectivity issue between the
CDI-PC
domain host and Secure Agent host. For more error details, see the taskoutput log file.
Error:
Regarding 2023-06-14 12:31:10.520 ERROR: [cf-task-pool-4][commandframework.TaskExecutor] [reqId=46ef9dcbdf5740e09c895c4fc7cff614] [DML_30065] Unexpected file found in extracted installer directory. 2023-06-14 12:31:10.520 WARN: [cf-task-pool-4][commandframework.TaskExecutor] [reqId=46ef9dcbdf5740e09c895c4fc7cff614] [DML_20004] Subtask ID [verify_integrity] failed.
This error appears when update fails as the installer script is corrupted.
Solution
: Retry the update process manually. For more error details, see the taskoutput log file.
Error:
INFO: [cf-task-pool-1][commandframework.TaskExecutor] [reqId=a23da466d220418eb626f01a97eac904] [DML_30051] Required disk space [4,000MB]. Available disk space [27MB]. 2023-05-29 13:25:33.774 ERROR: [cf-task-pool-1][commandframework.TaskExecutor] [reqId=a23da466d220418eb626f01a97eac904] [DML_30052] Required disk space is unavailable.
This error appears when update fails in Pre-update stage because the required amount of disk space is not available on the host.
Solution
: Minimum of 4GB disk space is required for the update to run successfully. Create the required amount of disk space and retry the update. For more error details, see the taskoutput log file.
Error:
[/export/home/prodxuser/build189/Node1/Informatica/platform/sys/data/downloads (Permission denied)]
This error appears when update fails in Download stage because the downloads folder doesn't have appropriate privileges.
Assign correct permissions to the downloads folder and retry the update process manually. For more error details, see the taskoutput log file.
Error:
INFO: [cf-task-pool-1][commandframework.TaskExecutor] [reqId=a23da466d220418eb626f01a97eac904] [DML_30051] Required disk space [4,000MB]. Available disk space [27MB]. 2023-05-29 13:25:33.774 ERROR: [cf-task-pool-1][commandframework.TaskExecutor] [reqId=a23da466d220418eb626f01a97eac904] [DML_30052] Required disk space is unavailable.
This error appears when update fails in Updating stage because the required amount of disk space is not available on the host.
Solution
: Create the required amount of disk space and retry the update. For more error details, see the taskoutput log file.
Error:
Domain port in use
This error appears when update fails in Updating stage because the
CDI-PC
domain port is used by another process.
Solution
: Shut down any other process running on the
CDI-PC
domain port and retry the update. For more error details, see the taskoutput log file.
Error:
The request failed because of error [No trusted certificate found in the trust stores to verify the server certificate chain.]. Please ensure the Keystore and Truststore are configured correctly and the process is running on the requested port.
This error appears when update fails in Updating stage with a certificate error.
Solution
: To enable communication between the
Domain Management App
and the domain, both the truststore certificates must be shared and available. Verify that the
Domain Management App
contains the domain truststore and the domain certificates folder contains the
Domain Management App
certificate.
For more error details, see the
Domain Management App
log file.
Error:
None of the agents in the agent group can handle the request.
This error appears when update fails in Updating stage because the
Domain Management App
is not available.
Solution
: Make sure that the Secure Agent is available and running. Retry the update manually. For more error details, see the
Domain Management App
log file.
Update fails with a connection refused error when the listener is terminated during the updating stage of the master gateway node.
During a multi-node domain update, if the master gateway node listener is terminated during its update stage, the update retries but fails at initialization with a connection refused error. All retry attempts receive the same error.
Solution
: Start the master gateway node and retry update.
CDI-PC multinode update fails during the listener start stage with the following error:
[catalina-exec-1] [JWTTokenAuthenticationFilter] [reqid:5b47093f435444929c43ed628ec3c7c4] [CloudConnectCommon_10015] Failed to validate the token because of error [{*}Token is not sign by the domain{*}.]
This error appears when you use different private keys in each CDI-PC node keystore file.
Solution
: Use the same private keys in each CDI-PC node keystore file.
See Appendix A: CDI-PC domain log files for the log file paths of each component of a
CDI-PC domain
.

0 COMMENTS

We’d like to hear from you!