Networker shows clone jobs as failed

Question

I have clone job scheduled to run only one day at week. It runs fine and I have no problems with clone job but somehow Networker marks clone job as failed every other day when the clone job isn't scheduled to run. Its not really problem just annoying when status of the clone job is always red, except on the day when it really runs. It started after upgrading Networker to 7.6 SP4 If I look at nsrtask.log then there are rows: 78814 4.01.2013 8:00:00  2 0 0 7092 4952 0 server.local nsrtask [clone.week clone] Starting 'nsrtask', process 3796 on server.local 79744 4.01.2013 8:00:00  0 0 0 7092 4952 0 server.local nsrtask [clone.week clone] Skipping this task based on schedule. 78832 4.01.2013 8:00:00  2 0 0 7092 4952 0 server.local nsrtask [clone.week clone] Task result: Skipping this task based on schedule. 78833 4.01.2013 8:00:00  2 0 0 7092 4952 0 server.local nsrtask [clone.week clone] Updating task resource 78835 4.01.2013 8:00:00  2 0 0 7092 4952 0 server.local nsrtask [clone.week clone] Exiting 'nsrtask', process 3796 on server.local And if it really tuns then there is row in nsrtask.log 78832 3.01.2013 9:41:46  2 0 0 5408 4536 0 server.local nsrtask [clone.week clone] Task result: Successful Before upgrade the log shows that 78814 22.10.2012 8:00:00  2 0 0 7736 664 0 server.local nsrtask [clone.week clone] Starting 'nsrtask', process 664 on server.local 79744 22.10.2012 8:00:00  0 0 0 7736 664 0 server.local nsrtask [clone.week clone] Skipping this task based on schedule. 78832 22.10.2012 8:00:00  2 0 0 7736 664 0 server.local nsrtask [clone.week clone] Task result: Successful 78833 22.10.2012 8:00:00  2 0 0 7736 664 0 server.local nsrtask [clone.week clone] Updating task resource 78835 22.10.2012 8:00:00  2 0 0 7736 664 0 server.local nsrtask [clone.week clone] Exiting 'nsrtask', process 664 on server.local Only difference is 'Task result' row. Before it was 'Successful', now it is 'Skipping this task based on schedule'. I can only guess that it counts job failed if the result isn't 'Successful'. If they changed the nsrtask return codes then why they didn't include the 'Skipping this task based on schedule' result as sucess but as an error?

coganb · Accepted Answer

Hi,

This is a known issue (bug reference NW143549 'Clone job runs with an error on a skip schedule'). This is fixed in the latest cumulative version of NetWorker 7.6.4 which you can download from here:

ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/7.6/

-Bobby

coganb · Answer

You're correct - there is no viewable knowlegebase article for this and there should be. -Bobby

sasilik · Answer

Oh damn, I just upgraded it to 7.6.4.4 in the beginning of december. I guess I must do another upgrade soon then. I just wonder why I can't find the article when I search it from support site. Wouldn't asked even the question if article would be viewable/findable.

NetWorker

Was this post helpful?