An attempt to update action packs through the "Action Pack" menu under "Administration" in ROC fails with a "connection refused" error. The following messages are found in the update-service.log file:
INFO (PollUpdate.java:554) - Error: Connection refused
ERROR (MessageHelper.java:42) - Fail to download file ftp://ftp.ca.com/pub/dpm/ReleaseAutomationActions/ActionPacks//pkgList.xml
The following are likely causes for the "connection refused" error:
The following tests will help identify which cause is at play. First, to check for any possible network-related cause:
If any or all of the above tests fail, this likely means a network issue is preventing Release Automation from contacting the FTP site in order to retrieve action pack updates.
Next, check if the update service is running and if the "\uploadActions" folder is empty:
Lastly, verify the NAC can connect to the repository. The NAC updates the repository as a result of the update process, so if it cannot access the repository, it may throw a "connection refused error". To check if this is the case:
If the above test in JMX fails, the nolio_dm_all.log file will record two error messages: "sync action packages error" and "Failed to find the repository details. Please check nolio-repo.properties file and repository hostname." This indicates a failure connecting to the repository.
If the cause is determined to be due to a network communication issue:
If the cause is due to the "uploadActions" folder still having content:
If the the cause is due to NAC being unable to access the repository: