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.