Troubleshooting Installation Errors with CA XCOM for Linux.

Document ID : KB000009497
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

If transfers fail going to XCOM on Linux after a new install, or a loopback transfer fails, run these tests to find out where the problem lies.

Environment:
Linux
Instructions:
    • Verify that the xcomadm group was properly created before the installation.
    • Check that the ports are listening:
       ~> netstat -an|grep 804tcp        0      0 0.0.0.0:8044            0.0.0.0:*               LISTENtcp        0      0 0.0.0.0:8045            0.0.0.0:*               LISTENtcp        0      0 :::8046                 :::*                    LISTENtcp        0      0 :::8047                 :::*                    LISTEN 
      that is with IPV4 and IPV6.

NOTE: The XCOM Linux product does not directly listen on a port, it relies on INETD/XINETD to listen on the port and start XCOM when a connection comes into the port.

  • If that is OK, check that (x)inted is starting xcomtcp. It's easiest to use telnet to do this as this gives you enough time for the verification:

    ~> telnet 127.0.0.1 8044 &

    ...
    Connected to 127.0.0.1.
     ~> ps -ef|grep xcomroot     15503  4364  0 08:38 ?        00:00:00 xcomtcp REMOTE 0spohe01  15505 15474  0 08:39 pts/2    00:00:00 grep xcomroot     23604     1  0 Jun04 ?        00:00:00 /usr/sbin/xcomd [1]+  Stopped                 telnet 127.0.0.1 8044~> kill %1~> ps -ef|grep xcomuser001  15507 15474  0 08:39 pts/2    00:00:00 grep xcomroot     23604     1  0 Jun04 ?        00:00:00 /usr/sbin/xcomd[1]+  Terminated              telnet 127.0.0.1 8044~>
  • Look for a /tmp/.it file:
    ~> ls -lart /tmp|tail -4-rw-r--r--  1 user001 users       930 2009-08-06 08:22 test.as4-rw-r--r--  1 user001 users   2031550 2009-08-06 08:50 xcomg0K9nn-rw-r--r--  1 root    xcomadm   62684 2009-08-20 08:39 .itdrwxrwxrwt 18 root    root       3352 2009-08-20 08:39 .~>
  • If you do not have the xcomtcp process or the /tmp/.it file, it's most likely a firewall or (x)inetd config problem.

     

Additional Information:

If everything looks fine, contact CA Support and send them the .it trace file for review.