bpdbjobs -restart doubt

What type of backup you are restarting??

All backup types.

That job definitely exists ?

# bpdbjobs -jobid 4334521

Yes.

Anything in any of the 'bpdbjobs' log files?

If you pick a job that fails to restart via the command line as you have shown, what happens if you restart it via the GUI ?

Anything in the bpjobd log ?

What is the version of NBU you are running ?

bpjobd should show something like this:

This was at VERBOSE = 5

18:33:48.712 [23614] <4> <tid:1> accept_new_connection: accepted a MONITOR connection (socket 13) from host womble, pid 23884
18:33:48.714 [23614] <4> <tid:10> MonitorTask::processRequest: Frame Type JOBSREQUEST, Frame Size 12 received on socket 13
18:33:48.722 [23614] <4> <tid:10> MonitorTask::processRequest: Frame Type JOBRESTART, Frame Size 4 received on socket 13
18:33:48.722 [23614] <4> <tid:10> MonitorTask::processRequest: JOBRESTART for job ID 888
18:33:48.728 [23614] <4> <tid:10> get_job_record: -Read Job Record LUT=1439314252 BITFIELD ( JobId = 00888) data = 0xa5ef5f847d0c027906800000
18:33:48.728 [23614] <4> <tid:10> MonitorTask::restartJob: restarting job ID 888
18:33:48.781 [23614] <4> <tid:10> MonitorTask::processRequest: Frame Type JOBMONDISCONNECT, Frame Size 0 received on socket 13
18:33:48.781 [23614] <4> <tid:10> MonitorTask::svc: closing MONITOR connection (socket 13) from host womble, pid 23884
18:33:49.394 [23614] <4> <tid:7> ProviderTask::processRequest: Job ID 907, Frame Type JOBUPDATE, Frame Size 269 received on socket 10 from JM
18:33:49.401 [23614] <4> <tid:7> ProviderTask::processRequest: creating job ID 907 ...

Taken from 7.6.1.2 running on Solaris

Have you noticed anything else odd, or not working ?

When did this issue start ? 

Has it every worked ?

If so, what has changed since it last worked ?  Eg. Any patches, EEBs installed, OS Patches ...

The job restarts normally.

A man of few words....

3 questions... 1 answer?

Please help us to help you!

Ouch, that's not what I was expecting to happen.

My next step would be to hope you are using the Java console, I would then look in the user_ops/nbjlogs having run a restart from the GUI to see if it logs what command the console has run (this only works on the Java console, and not for all actions), as this can be a really neat way to 1. Get commands for complex actions like setting up SLPs from the command line, and 2. See what command it runs when things don't work from the command line but do from the GUI.

I would also look in the log, as I mentioned with an example (below this post)  It could be the case, certainly if this is some code issue, that we won't get an answer and other methods will be required, but for the time being ...

Also, could you confirm if this every worked, and if so, what channges are known to have happened recently.