Troubleshooting guide

General Test and Troubleshooting Procedures
26 NetBackup Troubleshooting Guide - UNIX
◆ /etc/services (or applicable NIS file) does not have the correct bpcd entry.
The correct /etc services entry is:
bpcd 13782/tcp bpcd
◆ /etc/inetd.conf (or applicable NIS or DNS file) does not have the correct
bpcd entry. The correct /etc/inetd.conf entry is:
bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd
◆ /etc/inetd.conf was changed but was not reread. Correct this condition by
executing one of the following (whichever works):
/bin/ps -ef | grep inetd
kill -HUP the_inetd_pid
or
/bin/ps -aux | grep inetd
kill -HUP the_inetd_pid
Note On a Hewlett-Packard platform, use inetd -c to send a SIGHUP to inetd.
If the problem is with an AIX client, use SMIT to verify that the InetServ object class
has been updated with information about the bpcd process (/etc/inetd.conf and
/etc/services information).
If you modify the InetServ object class, using SMIT, the inetexp command is
automatically invoked. If you edit the InetServ object class, using an ODM editor, run
the inetexp command to export the InetServ object class to the /etc/inetd.conf
and /etc/services files. This keeps these files in sync with the InetServ object
class.
If you change the /etc/inetd.conf or /etc/services file, using SMIT, the
inetimp command automatically updates the InetServ object class. If you change
either file, run the refresh -s inetd or kill -1 InetdPID command to inform
the inetd daemon of the changes to its configuration file.
4. telnet to bpcd on the client. If it succeeds, keep the connection until after
performing step 5, then terminate it with Ctrl-c.
telnet clientname 13782
Where clientname is the name of the client as configured in the NetBackup class
configuration, /etc/hosts, and also in NIS and DNS (if applicable).
For example,
telnet ant bpcd
Trying 199.999.999.24 ...
Connected to ant.nul.nul.com.
Escape character is ‘^]’.