Forum Discussion

Mark_Sleeper's avatar
Mark_Sleeper
Level 3
13 years ago
Solved

Netbackup - multiple bpcd & vnetd in chkconfig

I'm running NB 6.5.6 on Redhat 5.

When I look at sysconfig for the bpcd and vnetd I see something like this on almost all of my clients (also linux, RHEL5 & 6):

chkconfig --list |grep bpcd
        bpcd:           on
        bpcd.04-26-12.12:08:06: on

chkconfig --list |grep vnetd
        vnetd:          on
        vnetd.04-26-12.12:08:06:        on

 

Does anyone know what the 2nd process is with the date stamp?  I'm guessing it's from a NB upgrade because it doesn't appear on new system builds. It's not causing any problems as far as I can tell but if it's not necessary I'd like to turn it off.

 

BTW, there is only one bpcd and vnetd process actually running:

ps -ef |grep bpcd
root     10202 18080  0 08:55 pts/0    00:00:00 grep bpcd

ps -ef |grep vnetd
root     10337 18080  0 09:00 pts/0    00:00:00 grep vnetd

 

Thanks for your time,

Mark Sleeper

7.1.x and Earlier
Backup and Recovery
Basics
NetBackup
  • Anonymous's avatar
    Anonymous
    13 years ago

    Your right its from the upgrade. I get them on client upgrades (SUSE). You can turn them off  or remove them entirely and leave the un-dated one.

     

    If you look in /usr/openv/.phistory file you may well see what is happening during the upgrade and the creation of these entries.

4 Replies

  • Anonymous's avatar
    Anonymous
    13 years ago

    Your right its from the upgrade. I get them on client upgrades (SUSE). You can turn them off  or remove them entirely and leave the un-dated one.

     

    If you look in /usr/openv/.phistory file you may well see what is happening during the upgrade and the creation of these entries.

  • CRZ's avatar
    CRZ
    Level 6
    13 years ago

    BTW, there is only one bpcd and vnetd process actually running:

    ps -ef |grep bpcd
    root     10202 18080  0 08:55 pts/0    00:00:00 grep bpcd

    ps -ef |grep vnetd
    root     10337 18080  0 09:00 pts/0    00:00:00 grep vnetd

    There are NONE running - you're only grep'ing your grep command :)

    In 6.x, they shouldn't show as running daemons (this changes in 7.x somewhere) but you would see their ports (13720,13782) open in the output of a command line `netstat -an`.

    But I digress.  :)  I think you've nailed it - someone probably upgraded to 6.5.6 back around noon on 4/26 and a diff was created for the previous service which you really shouldn't need, assuming everything is working as intended right now.  Do whatever Stuart says.  :)

  • Mark_Sleeper's avatar
    Mark_Sleeper
    Level 3
    13 years ago

    HA!  You're right!

    I was in such a hurry to ask the question I wasn't looking at the output very closely.

     

    I have chkconfig'd them off and removed them from xinetd.

     

    Thank you all for your help,

    Mark

  • Marianne's avatar
    Marianne
    Level 6
    13 years ago

    Mark, please mark the post that has helped you most as Solution?

    Suggestion: start planning upgrade of your environment to 7.x as 6.x is approaching EOSL....

    See CRZ's 'featured' post:

    https://www-secure.symantec.com/connect/forums/be-aware-netbackup-6x-end-support-life-fast-approaching