Procedure to start 'bpcd' in standalone mode if it does not respond to connection attempts.

Page 1 of 4

Document ID: 256685

http://support.veritas.com/docs/256685
E-Mail this document to a colleague

Procedure to start 'bpcd' in standalone mode if it does not respond to connection

attempts.

Details:
Sometimes it happens that bpcd appears to be 'listening' but does not respond to
connection attempts.
The netstat -a command shows bpcd listening:

netstat -a | grep bpcd

*.bpcd *.* 0 0 24576
0 LISTEN

But bpcd does not respond to connection attempts, and there is no log produced in the
bpcd log directory.

This could be because of some problem with the OS or the inetd process. This may
occur when there is a security wrapper in the inetd.conf configuration file. This is an OS
problem to be solved by the system administrator. For a quick fix they can remove the
security wrapper for bpcd, if they are using one.

Check the /etc/inetd.conf file. You might see a line for bpcd that looks something like:

bpcd stream tcp nowait root

/usr/local/sbin/tcpd /usr/openv/netbackup/bin/bpcd

Comment out the line with the 'wrapper' and add the line as configured by NetBackup:

# bpcd stream tcp nowait root

/usr/local/sbin/tcpd /usr/openv/netbackup/bin/bpcd
bpcd stream tcp nowait root
/usr/openv/netbackup/bin/bpcd bpcd

Stop all the VERITAS NetBackup (tm) processes:

/usr/openv/netbackup/bin/goodies/bp.kill_all

Re-read the inetd.conf file:

file://H:\study\netbackup\Upload_site_done\done\New Folder\Procedure to start 'bpcd'.htm 7/6/2010

Procedure to start 'bpcd' in standalone mode if it does not respond to connection attempts. Page 2 of 4

ps -ef | grep inetd

kill -HUP {inetd_pid}

Restart NetBackup. Try to connect to the bpcd daemon, or try a backup.

telnet {hostname} bpcd

If the connection to bpcd still cannot be established (or there is no security wrapper), the
bpcd process can be run in 'standalone' mode as a workaround.

You might not be able to start the bpcd process because it cannot bind to port 13782. In
that case, you will get a message:

bpcd -standalone
bind(13782) failed: 125

The following steps will allow bpcd to be started in standalone mode.

Edit the /etc/inetd.conf file by commenting out the bpcd line:

# bpcd stream tcp nowait root

/usr/openv/netbackup/bin/bpcd bpcd

Stop all the NetBackup processes:

/usr/openv/netbackup/bin/goodies/bp.kill_all

Re-read the inetd.conf file:

ps -ef | grep inetd

kill -HUP {inetd_pid}

Now bpcd will not be listening. You will be able to start it in standalone mode with:

bpcd -standalone

Restart NetBackup. Try to connect to the bpcd daemon, or try a backup.

telnet {hostname} bpcd

The system administrator will have to fix the inetd function for a permanent fix. But this
will get backups running.

file://H:\study\netbackup\Upload_site_done\done\New Folder\Procedure to start 'bpcd'.htm 7/6/2010

Procedure to start 'bpcd' in standalone mode if it does not respond to connection attempts. Page 3 of 4

Products Applied:
NetBackup BusinesServer 3.3, 3.4, 3.4.1,
4.5, 4.5 (FP3), 4.5 (FP4), 4.5 (MP1), 4.5
(MP2), 4.5 (MP3), 4.5 (MP4)
NetBackup DataCenter 3.4, 3.4.1, 4.0 V,
4.5, 4.5 (FP3), 4.5 (FP4), 4.5 (MP1), 4.5
(MP2), 4.5 (MP3), 4.5 (MP4)
NetBackup v3.2 and prior (UNIX Platforms)
3.1.1, 3.2

Last Updated: June 24 2003 07:06 AM GMT

Expires on: 365 days from publish date
Subscribe to receive critical updates
about this document
Subjects:
NetBackup BusinesServer
Operating System: Configuration
NetBackup DataCenter
Operating System: Configuration
NetBackup v3.2 and prior (UNIX Platforms)
Operating System: Configuration
Solaris
Application: Configuration, How To
Equipment: Configuration

Languages:
English (US)

Operating Systems:
Solaris
2.6, 7.0 (32-bit), 8.0 (32-bit), 9.0 (32-bit)

Symantec World Headquarters:

20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com/,
Tech Support Web: http://entsupport.symantec.com/,
E-Mail Support:
http://seer.entsupport.symantec.com/email_forms,

file://H:\study\netbackup\Upload_site_done\done\New Folder\Procedure to start 'bpcd'.htm 7/6/2010

Procedure to start 'bpcd' in standalone mode if it does not respond to connection attempts. Page 4 of 4

FTP: ftp://ftp.entsupport.symantec.com/ or
ftp://ftp.entsupport.symantec.com/

THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY
OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC
SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT
APPLY.

file://H:\study\netbackup\Upload_site_done\done\New Folder\Procedure to start 'bpcd'.htm 7/6/2010