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
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.