Rogue entries bpjobd (frames received on socket)

Hi VOX,.

I get the below reported by the appliance while it writes duplications to tapes (LTO5), can you please advise me with more details regarding this as I think it may indicate an issue?

I have already had a look and can not find anything like this nowhere, fragment size is set to 65,535 Megabytes which should be roughty 500GB. May I kindly ask to advise more on the below etc. ? thank you very much.

/bpjobd/log.101719:04:10:21.064 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365723, Frame Type JOBUPDATE, Frame Size 28 received on socket 40
./bpjobd/log.101719:04:10:21.069 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365723, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 40
./bpjobd/log.101719:04:10:22.072 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBUPDATE, Frame Size 28 received on socket 38
./bpjobd/log.101719:04:10:22.077 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 38
./bpjobd/log.101719:04:10:23.171 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365737, Frame Type JOBUPDATE, Frame Size 16 received on socket 18
./bpjobd/log.101719:04:10:24.297 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBUPDATE, Frame Size 28 received on socket 38
./bpjobd/log.101719:04:10:24.302 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 38
./bpjobd/log.101719:04:10:26.550 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBUPDATE, Frame Size 28 received on socket 38
./bpjobd/log.101719:04:10:26.555 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 38
./bpjobd/log.101719:04:10:27.231 [11207] <4> <tid:1089505600> MonitorTask::processRequest: Frame Type JOBSREQUEST, Frame Size 24 received on socket 22
./bpjobd/log.101719:04:10:28.216 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365723, Frame Type JOBUPDATE, Frame Size 28 received on socket 40
./bpjobd/log.101719:04:10:28.220 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365723, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 40


./bpjobd/log.101719:04:20:43.171 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365857, Frame Type JOBUPDATE, Frame Size 32 received on socket 18
./bpjobd/log.101719:04:20:43.177 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365857, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 18
./bpjobd/log.101719:04:20:44.021 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBUPDATE, Frame Size 28 received on socket 38
./bpjobd/log.101719:04:20:44.036 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 38
./bpjobd/log.101719:04:20:46.533 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBUPDATE, Frame Size 28 received on socket 38
./bpjobd/log.101719:04:20:46.538 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 38
./bpjobd/log.101719:04:20:49.422 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBUPDATE, Frame Size 28 received on socket 38
./bpjobd/log.101719:04:20:49.426 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 38
./bpjobd/log.101719:04:20:52.118 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365723, Frame Type JOBUPDATE, Frame Size 28 received on socket 40
./bpjobd/log.101719:04:20:52.122 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365723, Frame Type JOBRUNUPDATE, Frame Size 16 received on socket 40
./bpjobd/log.101719:04:20:52.135 [11207] <4> <tid:1081100608> ProviderTask::processRequest: Job ID 365721, Frame Type JOBUPDATE, Frame Size 28 received on socket 38
Tags (2)
5 Replies
Highlighted

Re: Rogue entries bpjobd (frames received on socket)

Highlighted

Re: Rogue entries bpjobd (frames received on socket)

Already checked it, I am not going to remove bpdbjobs directory as it was always there... I think that Marianne meant on the client side...

Highlighted

Re: Rogue entries bpjobd (frames received on socket)

bpdbjobs is a Master Server function, and I have also never had to look at those logs too.

Plus you need to remember the severity coding is in the message :

<2> info
<4> extended info
<8> warning
<16> error
<32> critical

...so your messages are extended info and can be ignored.

I don't have a bpjobd or bpdbjobs logs folder on any of my Master Servers.

 

Highlighted
Moved:

Re: Rogue entries bpjobd (frames received on socket)

Highlighted

Re: Rogue entries bpjobd (frames received on socket)

@Unknown77 

As per @sdo 's post - the severity code is <4>. So, nothing to be concerned about.

There is really no need for this folder on a NBU master server - unless you are troubleshooting a specific Activity Monitor issue with Veritas. 

If you really want to know what the log entries mean, you will need to ask Veritas. 
My guess is that they will advise you to upgrade as you still seem to be on version 7.5. 
Various changes were made to Jobs database over the years....