Page 1 of 1
unix agent 6.2.01.200 become unavailable
Posted: 18 Jun 2008 9:14
by philmalmaison
does anybody have this king of message, remaining from a agent unavailable
proclog message :
TCP_COMM::connect: OS_SOCKET_connect Socket Error - 146
thanks in advance
Philmalmaison
Posted: 18 Jun 2008 12:30
by fyot
Hi Philmalmaison,
You try to use a bad TCP port to connect your agent.
You must verify some information on your agent :
-Authorized CTM Server (verify if your CTM server could be ping)
-TCP port (and firewall parameters)
Do same verification on your server to connect your agent.
- If you define special TCP port for your agent don't forget to modify
- AGENT PORT for that agent on your Control-M Server.
- Verify CONVERSION parameters (must be 06 to 6.2.01)
Posted: 18 Jun 2008 2:48
by philmalmaison
thanks for your help Franck, i think i found the pb.
i have 9 agents on the same machine, but a mistake was made in port number.
As controlm give dynamically the 3 number after the AGCMNDATA, it take +1 +2 +3 and i have some of the other agent taking the predecessor port number +1, so the port looks busy some times for the second one if first one using the number for TRACKER/AG_COMM or AT_COMM
regards
Merci A+