Over the past two weeks I have had a SEV1 case open with Symantec trying 
to isolate the root cause of nbpem crashing every night at 23:49, what was 
it?

If you run bpbackup with an empty file list, it kills the nbpem process, 
at least on NetBackup 6.0MP7 server with a NetBackup 6.0MP6 client.

Client (has a cron that did this every night, if the file was empty)
-------
bpbackup -w 4 -L /tmp/log -f /tmp/file_list
Where /tmp/file_list = 0 bytes.
EXIT STATUS 25: cannot connect on socket

Server:
-------
Before running the command, nbpem is up and healthy:
root     18534  0.1  0.1 142000 24816 ?        Sl   03:40   0:02 
/usr/openv/netbackup/bin/nbpem

After running the command shown above:
The process is dead and since nbpem is the scheduler, no new backups run 
until you manually restart this process.

I am checking now to see if it happens in 6.5.2a.

$ touch /tmp/0_byte_file
$ ls -l /tmp/0_byte_file
-rw-r--r-- 1 user group 0 Nov 18 04:33 /tmp/0_byte_file
$ sudo /usr/openv/netbackup/bin/bpbackup -w 4 -L /tmp/log -f /tmp/0_byte_file
No files found in /tmp/0_byte_file
EXIT STATUS 112: no files specified in the file list
$

The nbpem process remains up and it shows up as a failed job with error 112.

Justin.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu