Solved!
Go to SolutionQuestion about nsrpush in NetWorker 8.2.3.8
Good day everyone,
I have been racking my brain and searching Google to no avail on the error :
nsrpush -i -If /root/nsr_upgrade/test.txt
Another operation is active -- retry later
Inventory Operation Failed
Currently running NW 8.2.3.8 on a RHEL 6.8 server and have been upgrading my clients (over 3000) and nsrpush has been working perfectly.
I used the GUI Software Administration Wizard to monitor the current software distribution actions and there have been none since I did the last set yesterday.
I cannot find any documentation about what daemon or service nsrpush uses. Can anyone point me in the correct direction to complete my task of updating my clients?
Thank you in advance,
Lee
2129
1
Posted March 23rd, 2017 11:00
Hello.
Daemon is nsrcpd.
2129
0
Posted March 23rd, 2017 12:00
ledugarte,
Thank you very much! Now I know what logs to review. so, the last two entries in the nsrcpd.raw file states this:
0 03/21/2017 02:00:46 PM 3 1 110 704919296 19895 0 nw_zone_server.com nsrcpd SYSTEM error Connection timed out
40063 03/21/2017 02:00:46 PM 5 10 2 704919296 19895 0 nw_zone_server.com nsrcpd NSR critical Error initializing the operation.
And I've attempted to run the inventory several times today. This is an extremely busy server and I just cannot stop and start NetWorker anytime I want. Is there a problem with killing the daemon as it is supposed to terminate after a given amount of time and we are over 24 hours later?
Thank you again for your assistance!
Sincerely,
Lee
2130
0
Posted March 24th, 2017 07:00
Eduard,
Thank you very much for that info. I've done that and the inventory is working once again!
Have a great weekend!
Sincerely,
Lee
2129
0
Posted March 27th, 2017 06:00
you are welcome
edino1
39 Posts
2129
1
Posted March 24th, 2017 01:00
As you see other nsrpush operation is running in the background. You have to kill nsrcpd daemon and delete lock files cpdb.lck and nsrcpd.lck from /nsr/tmp . After that you will be able to run nsrpush operation again without restart of NetWorker server.