Unsolved
This post is more than 5 years old
25 Posts
0
4179
Backup failed "save is unable to start active session in 315533226 seconds"
Hi,
Recently I getting backup failure on one of the client, failure as below. I have found some suggestion solution through the support forum it is caused by a large time discrepancy between backup server and client? But the time system seems fine, any clue I can get this resolve?
Client / incr 1291181402 1 1 retry attempted
39077:(pid 7620): error, Automatically cancelling save request: save is unable to start active session in 315533226 seconds
5777:(pid 7620): Cannot open save session with Backupserver
Thank you.
ble1
2 Intern
2 Intern
•
14.3K Posts
0
December 8th, 2010 10:00
Can you dump here output of date for both server and client (if your server/client is Windows then include both date and time form CLI). When I look at those seconds I have a feeling that time is correct.. even day and month might be, but year won't.
Mark_Bellows
240 Posts
0
December 8th, 2010 13:00
Hello
Please review this:
Log into powerlink, click on the Seach Support tab and enter Automatically cancelling save request: save is unable to start active in the search feild
You will receive this as one of the results:
esg105567
Symptoms
Client or server initiated backups fail with the following error:
lgto_auth for `nsrmmd' failed: Automatically cancelling save request: save is unable to start active session in 7776234 seconds
save mmd auth failed: Automatically cancelling save request: save is unable to start active session in 7776234 seconds
direct save returns: Automatically cancelling save request: save is unable to start active session in 7776234 seconds
39077:(pid 3556): error, Automatically cancelling save request: save is unable to start active session in 7776234 seconds (number -7)
In the above example, 7776234 seconds = 2160 hours = 90 days. Therefore, the client system clock is offset (and incorrect) by 90 days.
Cause
A large date/time discrepancy between the NetWorker server and the client system time.
Work Around
Downgrade the client to 7.4.2 where the issue is is not present.
Resolution
1. Update the system clock on the NetWorker server or client so there is not a significant time difference.
2. This is a potential regression in 7.4.3 and above. The issue is not resolved yet and planned release is not fixed as of today.