bprd dies and no backups run

[Navadeepan_Pill]

Hi,

We have Netbackup 5.0 running on Solaris 8 with One Master & 4 Media Servers. All are SAN Media servers.

We are facing a problem, intermittenly none of the schduled backups kicks off, no backups run. When checked, we found that bprd daemon was stopped. bprd dies automatically.

Any one faced the same problem? Pls. help

Best Regards

Navadeepan

[Stumpr2]

My first guess would be to check the memory resources.

However, I suggest creating the debug folder and checking the logfile

# mkdir /usr/openv/netbackup/logs/bprd

[Navadeepan_Pill]

Hi Bob,

Thanks for the reply. I have already created bprd dir in the logs folder.

17:04:54.416 [2851] <2> get_behavior_rec: ?

17:04:54.417 [2851] <2> get_behavior_rec: MD5 digest line

17:04:55.616 [2851] <2> launch: /usr/openv/netbackup/bin/bpsched, pid=19808

17:05:00.851 [2851] <2> childterm: pid=19808 exit=200, signo=0 core=no

17:05:00.851 [2851] <2> schild: wait2() ECHILD

17:05:00.851 [2851] <2> listen_loop: select() interrupted

17:14:54.722 [2851] <2> get_behavior_rec: ?

17:14:54.723 [2851] <2> get_behavior_rec: MD5 digest line

17:14:55.921 [2851] <2> launch: /usr/openv/netbackup/bin/bpsched, pid=19907

17:15:01.156 [2851] <2> childterm: pid=19907 exit=200, signo=0 core=no

17:15:01.156 [2851] <2> schild: wait2() ECHILD

17:15:01.156 [2851] <2> listen_loop: select() interrupted

17:24:54.038 [2851] <2> get_behavior_rec: ?

17:24:54.039 [2851] <2> get_behavior_rec: MD5 digest line

17:24:55.249 [2851] <2> launch: /usr/openv/netbackup/bin/bpsched, pid=20024

17:25:00.556 [2851] <2> childterm: pid=20024 exit=200, signo=0 core=no

17:25:00.556 [2851] <2> schild: wait2() ECHILD

17:25:00.556 [2851] <2> listen_loop: select() interrupted

17:34:54.434 [2851] <2> get_behavior_rec: ?

17:34:54.435 [2851] <2> get_behavior_rec: MD5 digest line

17:34:55.634 [2851] <2> launch: /usr/openv/netbackup/bin/bpsched, pid=20135

17:35:30.104 [2851] <2> bprd: socket fd from accept() is 7

17:35:30.108 [2851] <2> listen_loop: request complete

17:35:30.110 [20185] <2> logconnections: BPRD ACCEPT FROM 10.11.10.101.63209 TO 10.10.64.104.13720

17:35:30.111 [20185] <2> process_request: setsockopt SO_LINGER on 7 succeeded.

17:35:30.366 [2851] <2> bprd: socket fd from accept() is 7

17:35:30.369 [2851] <2> listen_loop: request complete

17:35:30.371 [20186] <2> logconnections: BPRD ACCEPT FROM 10.11.10.101.63212 TO 10.10.64.104.13720

17:35:30.371 [20186] <2> process_request: setsockopt SO_LINGER on 7 succeeded.

17:35:30.967 [2851] <2> childterm: pid=20185 exit=0, signo=10 core=yes

17:35:30.967 [2851] <2> schild: child(ren) not ready to terminate

17:35:30.967 [2851] <2> listen_loop: select() interrupted

17:35:31.127 [2851] <2> childterm: pid=20186 exit=0, signo=10 core=yes

17:35:31.127 [2851] <2> schild: child(ren) not ready to terminate

17:35:31.127 [2851] <2> listen_loop: select() interrupted

17:35:36.360 [2851] <2> childterm: pid=20135 exit=0, signo=0 core=no

17:35:36.360 [2851] <2> schild: wait2() ECHILD

17:35:36.360 [2851] <2> listen_loop: select() interrupted

After this time, there is no messages in the bprd log. Pls. help

Best Regards

Navadeepan

[Chia_Tan_Beng]

What's your patch level?

[Navadeepan_Pill]

Its 5.0 MP4

[Chia_Tan_Beng]

Try restart bprd using /usr/openv/netbackup/bin/initbprd

[Navadeepan_Pill]

Hi All,

Thanks for your inputs. We have opened a case with Symantec. Finally they told us that its a bprd bug in 5.0 which is fixed in 5.1 & 6.0.

They will provide new binary to solve the issue.

Thanks.

Best Regards

Navadeepan

[Stumpr2]

Thanks for the followup. I never played with 5.0

It had a lot of bugs when it came out so I migrated from 4.5 FP6 to 5.1