Time Zone not following system time [SOLVED]
Posted: September 9th, 2017, 7:49 pm
Hello, I've noticed some odd things recently with 2.2.1 [bcc4dd7] on Windows 10. I travel around a lot for my job and was just in Osaka (UTC+9) a few days ago. I've been back in US Central Time (UTC-5) for a few days, and my Windows 10 system time shows the correct time. When I added a release from Radarr, the SABnzbd time was at UTC+9, the file started downloading right away (scheduled to start tonight at 2300), and a warning I received was "WARNING (in 14 hours): too many connections to...."
Here is a snippet from the log file:
After being shutdown for more than 24 hours as I traveled back to the US,SABnzbd started up on 2017-09-08 at 11:17 UTC-5. The log shows SABnzbd has the time set at UTC+9
When I noticed the error, I restarted SABnzbd, at which time it went back to the correct time zone:
During this whole time, the Windows system time was correctly on UTC-5. In fact, the warning shows that somehow there are two time zone settings at play in SABnzbd:
The log shows it still thought it was in Japan UTC+9, but the GUI showed "WARNING (in 14 hours)" as I stated above. I didn't think to capture a screen shot, but it definitely showed the warning was in 14 hours. That means it was comparing the time of the warning to the system time and calculating that it was occurring 14 hours in the future.
I hope this is enough to accurately describe the issue. I searched through the forum and saw several replies indicating SABnzbd simply uses the system time. I think I saw today that's not what is happening. In case it's relevant, neither my Sonarr nor Radarr logs have any 2017-09-10 entries, meaning they don't seem to be sending the time change to SABnzbd.
Here is a snippet from the log file:
Code: Select all
2017-09-07 02:53:18,358::INFO::[urlgrabber:72] URLGrabber starting up
2017-09-07 02:53:30,619::INFO::[interface:553] Successful login from 127.0.0.1
2017-09-07 07:00:00,000::INFO::[downloader:277] Pausing
2017-09-09 01:17:14,450::INFO::[SABnzbd:1147] --------------------------------
2017-09-09 01:17:14,450::INFO::[SABnzbd:1148] SABnzbd.exe-2.2.1 (rev=bcc4dd75cfeab41a4b56308709c04fd568859d1f)
When I noticed the error, I restarted SABnzbd, at which time it went back to the correct time zone:
Code: Select all
2017-09-10 09:21:18,482::INFO::[_cplogging:219] [10/Sep/2017:09:21:18] ENGINE Bus STOPPING
2017-09-10 09:21:26,450::INFO::[_cplogging:219] [10/Sep/2017:09:21:26] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('127.0.0.1', 8080)) shut down
2017-09-10 09:21:26,450::INFO::[_cplogging:219] [10/Sep/2017:09:21:26] ENGINE Stopped thread '_TimeoutMonitor'.
2017-09-10 09:21:26,450::INFO::[_cplogging:219] [10/Sep/2017:09:21:26] ENGINE Bus STOPPED
2017-09-10 09:21:26,450::INFO::[_cplogging:219] [10/Sep/2017:09:21:26] ENGINE Bus EXITING
2017-09-10 09:21:26,450::INFO::[_cplogging:219] [10/Sep/2017:09:21:26] ENGINE Bus EXITED
2017-09-10 09:21:26,450::INFO::[_cplogging:219] [10/Sep/2017:09:21:26] ENGINE Re-spawning C:\Program Files\SABnzbd\SABnzbd.exe C:\Program Files\SABnzbd\SABnzbd.exe -p
2017-09-09 19:21:27,467::INFO::[SABnzbd:1147] --------------------------------
2017-09-09 19:21:27,467::INFO::[SABnzbd:1148] SABnzbd.exe-2.2.1 (rev=bcc4dd75cfeab41a4b56308709c04fd568859d1f)
Code: Select all
2017-09-10 09:18:13,539::WARNING::[downloader:636] Too many connections to server xxxxxx
I hope this is enough to accurately describe the issue. I searched through the forum and saw several replies indicating SABnzbd simply uses the system time. I think I saw today that's not what is happening. In case it's relevant, neither my Sonarr nor Radarr logs have any 2017-09-10 entries, meaning they don't seem to be sending the time change to SABnzbd.