Unsolved
1 Rookie
•
1 Message
0
25
March 3rd, 2025 02:48
'save' was unable to start the active session in 86946 seconds
Suddenly networker could not perform save. It was working previously. Here are the logs from nsrwatch.
Mon 10:41:08 Media Notice: Automatically cancelling the save request. 'save' was unable to start the active session in 86946 seconds. The elapsed time is over a day. This may be due to the date/time being
I already checked and time/date on both servers and client is the same.
All filesystem is ok and not full.
Client can ping the server so it means it has communication.
I already restarted networker service on both servers and client but still the same.
Here is the last line from daemon.raw.
61936 1740969910 5 3 17 1870653184 16358 0 server_hostname nsrexecd RAP critical 41 csp configuration service not initialized 0
61936 1740969910 5 3 17 1870653184 16358 0 server_hostname nsrexecd RAP critical 41 csp configuration service not initialized 0
61936 1740969910 5 3 17 1870653184 16358 0 server_hostname nsrexecd RAP critical 41 csp configuration service not initialized 0
61936 1740969910 5 3 17 1870653184 16358 0 server_hostname nsrexecd RAP critical 41 csp configuration service not initialized 0
61936 1740969910 5 3 17 1879045888 16358 0 server_hostname nsrexecd RAP critical 41 csp configuration service not initialized 0
61936 1740969910 5 3 17 1853867776 16358 0 server_hostname nsrexecd RAP critical 41 csp configuration service not initialized 0
61936 1740969910 5 3 17 1879045888 16358 0 server_hostname nsrexecd RAP critical 41 csp configuration service not initialized 0
61936 1740969910 5 3 17 1870653184 16358 0 server_hostname nsrexecd RAP critical 41 csp configuration service not initialized 0
61936 1740969910 5 3 17 1879045888 16358 0 server_hostname nsrexecd RAP critical 41 csp configuration service not initialized 0
61936 1740969910 5 3 17 1853867776 16358 0 server_hostname nsrexecd RAP critical 41 csp configuration service not initialized 0
Any idea what more to check?
bbeckers1
2 Intern
•
191 Posts
0
March 12th, 2025 20:33
if you want the daemon.raw to be meaningful wrg to times and errors, it should be rendered using nsr_render_log. Even better is if you would make sure you have runtime rendered the daemon.raw into a daemon.log, making troubleshooting way easier as one can easier grep for things and also rotate the logfil daily or do "tail -f" on the logfile. At leat assuming your backup server is Linux? Or is it Windows? But as you mention nsrwatch I assume for now it is a Linux backup server.
I assume it is the daemon.raw from the backup server or rather the client? I reckon CSP is realted to the NW NMC and hence this is the NW backup server? Does it work for the backup server itself and other clients?
I would expect you to look at policy logs underneath /nsr/logs/policy for the job being started on the backup server and not using nsrwatch for that, but actually look in the available policy logfiles and look for meaningful messages in the daemon.raw and do some basic connectivity validation as well with nsrrpcinfo from both ends for one.