Port 10000 for RALUS goes down, but the agent is still running

[Diego81]

Hi All,

I have a problem with one of our server (RHEL 4) and Ralus.

During the backup, the agent crashes. This appens when it is trying to contact the port 10000 at the end of backup process. I've seen that the port 10000 for beremote goes down after some seconds.

This is my /etc/services entry for beremote:

[root@isisrv2 root]# more /etc/services | grep 10000
ndmp            10000/tcp                       # BackupExec RALUS

Once I start the VRTSralus.init service, I see the port listening:

[root@isisrv2 root]# netstat -anp | grep 10000
tcp        0      0 0.0.0.0:10000               0.0.0.0:*                   LISTEN      13069/beremote

[root@isisrv2 root]# nmap -sT -O localhost
10000/tcp  open        snet-sensor-mgmt

After some seconds, they disappear. I run the nmap and netstat command but I cannot see anymore the port 10000:

[root@isisrv2 root]# netstat -anp | grep 10000
[root@isisrv2 root]#

But beremote is still running:

[root@isisrv2 root]# ps -ef | grep beremote
root     13069     1  0 10:31 pts/74   00:00:00 /opt/VRTSralus/bin/beremote
root     13178 11211  0 10:34 pts/74   00:00:00 grep beremote
[root@isisrv2 root]#

This is crazy... Someone can help me???

[Diego81]

After some debug jobs, I was finally able to see an error message in the debug file:

4b54bb0 Tue Sep  2 11:44:54 2008 : Function vfmObjCtl, VxMS resolved the error code to this message:  system call failed
4b54bb0 Tue Sep  2 11:44:54 2008 :              vx_read_ext: vfmObjCtl: ret_val : 0XB
4b54bb0 Tue Sep  2 11:44:54 2008 :              vx_read_ext: vfmObjCtl: ret_val (exclude VFM_WACL): 0X0
4b54bb0 Tue Sep  2 11:44:54 2008 :              vx_read_ext: file_extstat.ext_filevers : 1
4b54bb0 Tue Sep  2 11:44:54 2008 : ====> VX_OpenObj returning 0
4b54bb0 Tue Sep  2 11:44:54 2008 : ReadObject: Beginning of EA cur_stream_len 240

No references about that on Symantec support site. Any ideas?