Forum Discussion

Iwan_Tamimi's avatar
Iwan_Tamimi
Level 6
11 years ago

bpjobd log size increased rapidly

Hi All,

Yesterday on our Netbackup master server the logs of bpjobd in /usr/openv/netbackup/logs/bpjobd suddenly increased very fast. The size suddenly reached 30 GB, it stopped because no more space,and it did happen before too. It caused netbackup to stop.  (our system is Netbackup ES 7.5.0.4 running on RHel 6.1on VCS 5.1 cluster)

What could be the caused?

 

Regards,

Iwan

 

this is the tail of the log from the previous log:

10:19:36.206 [1971] <4> <tid:139716187891456> ProviderTask::processRequest: Job ID 491270, Frame Type JOBUPDATE, Frame Size 16 received on socket 51
10:19:36.209 [1971] <4> <tid:139716187891456> ProviderTask::processRequest: Job ID 491270, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 51
10:19:36.712 [1971] <4> <tid:139716187891456> ProviderTask::processRequest: Job ID 491271, Frame Type JOBUPDATE, Frame Size 16 received on socket 63
10:19:36.716 [1971] <4> <tid:139716187891456> ProviderTask::processRequest: Job ID 491271, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 63
10:19:37.259 [1971] <4> <tid:139716187891456> ProviderTask::processRequest: Job ID 491270, Frame Type JOBUPDATE, Frame Size 16 received on socket 51
10:19:37.262 [1971] <4> <tid:139716187891456> ProviderTask::processRequest: Job ID 491270, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 51
10:19:37.286 [1971] <4> <tid:139716187891456> ProviderTask::processRequest: Job ID 491270, Frame Type JOBUPDATE, Frame Size 16 received on socket 51
10:19:37.288 [1971] <4> <tid:139716187891456> ProviderTask::processRequest: Job ID 491270, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 51
10:19:38.011 [1971] <4> <tid:139716187891456> ProviderTask::processRequest: Job ID 491275, Frame Type JOBUPDATE, Frame Size 16 received on socket 66
10:19:38.242 [1971] <4> <tid:139716187891456> ProviderTask::processRequest: Job ID 491275, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 66

 

7.5
Backup and Recovery
Error messages
NetBackup
Troubleshooting
  • Marianne's avatar
    Marianne
    11 years ago

    Is there any reason why this log folder was created?

    Unless you are busy troubleshooting this process, there is no need for this folder.

    Simply remove it. 

3 Replies

Sort By
Replies have been turned off for this discussion
  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    Is there any reason why this log folder was created?

    Unless you are busy troubleshooting this process, there is no need for this folder.

    Simply remove it. 

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    In all honesty - I have ONLY ever created bpjobd folder when a call was logged with Symantec Support about Activity Monitor problem. The log folder was monitored as the customer had a very busy 24x7 environment and folder was removed once sufficient logs were collected for the case.

    Some people simply run the 'mklogdir' batch file because they have no idea what logs are needed or too lazy to give it a proper thought.

    The only log folders that I want on a master are: admin bpdbm and bprd. If master is a media server as well, bpbrm and bptm. I also feel that level 0 logs are perfectly fine for 99.99 percent of troubleshooting.
    I only ever increase logging level when asked by Symantec Support engineer for specific problem where level 0 does not contain sufficient info.

  • Iwan_Tamimi's avatar
    Iwan_Tamimi
    Level 6
    11 years ago

    Marrianne,

    Thank you for your reply, I don't know why it is there, it could be last time our consultant put it there. I will remove it, but I just curious why it could be so busy creating log, is it normal or something wrong with the process?

    Regards,

    Iwan