When we start the Linux agent, it'll show the below error and immediately shuts down. (V 21.0.5) but Informatica agent in the same machine connects to AE.
Certificate loaded from file '../../../TrustedCerts/ae_public_cert.pem'.20230314/235212.382 - U02000398 Loading certificates from the directory './security' that is specified in the parameter'AgentSecurityFolder'.\20230314/235212.382 - U02000376 Could not parse certificate './security/CALONLD055.pem'. Please make sure that the certificate is in PEM format.20230314/235212.382 - U02000377 Certificate loaded from file './security/CALONLD055.cert'.20230314/235212.382 - U02000377 Certificate loaded from file './security/CALONLD055_ca.pem'.20230314/235212.383 - U02003057 Agent process 'LISTENER0' with PID='309' is up and running.
U02000102 Error when calling the function 'listener().bind(::)', error code 'Address already in use'.20230314/235212.388 - U02003073 Agent Prozess '/home/infa/automic/ServiceManager/bin/../../Agents/unix/bin/ucxjlx6-LISTENER0-CALONLD055,PID=309' shutdown has been initiated.20230314/235212.540 - U02000017 The check interval for 'Jobs' has been set to '60' seconds.20230314/235212.540 - U02000017 The check interval for 'Server' has been set to '60' seconds.20230314/235212.540 - U02000017 The check interval for 'Reconnect' has been set to '120' seconds.20230314/235212.540 - U02000017 The check interval for 'Report' has been set to '60' seconds.20230314/235212.540 - U02000017 The check interval for 'File Event' has been set to '60' seconds.20230314/235212.540 - U02000017 The check interval for 'File Transfer Restart Point' has been set to '60' seconds.20230314/235212.540 - U02000017 The check interval for 'File Transfer Statistic' has been set to '60' seconds.20230314/235212.540 - U02000017 The check interval for 'File Transfer Report' has been set to '60' seconds.20230314/235212.540 - U02000017 The check interval for 'unused FT connection' has been set to '300' seconds.20230314/235212.540 - U02000017 The check interval for 'backend command' has been set to '600' seconds.20230314/235212.540 - U02000231 Anonymous 'Job' is allowed.20230314/235212.540 - U02000231 Anonymous 'FT' is allowed.20230314/235212.540 - U02000231 Anonymous 'File event' is allowed.20230314/235217.392 - U02000313 Communication error with partner '*IPC(LISTENER0)', error: 'WS-read/1(The WebSocket stream was gracefully closed at both endpoints)'.20230314/235217.392 - U02003058 Agent has lost connection to 'LISTENER0/PID=309' process, reason '309'.20230314/235217.393 - U02003073 Agent Prozess 'AGENT,PID=32760' shutdown has been initiated.
Off the top, it sounds like the main agent is trying to listen on a port that's already in use.
Are you specifying the same listening port for both your main agent and your informatica agent? If so, that'd be an obvious problem; they need to be distinct. If not, then it sounds like some other process on the server is trying up the port you specified for your agent.
Have you tried running your agent using a different port?
Maybe the agents use the same port for some communication, or it is also possible some other application use the port which is used by agent. To detect the cause, watch the configuration file which port settings you use. Then take a look on the shell.
ss -el | grep <Port>
Then you become a list of application allready listening to this port. If you not get not enough information, rund this command as root or with sudo.
Hope that helps
we have the same issue afer updating the AIX-Agent from 21.0.4 to 21.0.5HF1 with CAU. I think, that the Problem is the new Agent. It open a seperate Listener (is in V21.0.5 new) and this one is at the same Port as the old one. Our AIX-Admin killed the old Listener Port an than the Agent works after restart fine. Check the prosess via ps like: ps -ef | grep <here your path of Agentinstall> | grep -v grep . If you find a process like ucxja64-LISTENER0 (Example AIX), kill them and start your Agent again. Maybe Broadcom do not check after stop/killen the old Listener-Prozess that the process is really killed from the operating-system. In our case the terminating that process took over 3 seconds!
Hi Shashank and Alexander,
If you believe you encountered an issue with the product, we'll gladly review it through a Support case.