Seq Documentation and Support

Welcome to the Seq documentation hub. You'll find comprehensive guides and documentation to help you start working with Seq as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    


Ask A Question

Seq service did not start after reboot (and system time changed)

While evaulating Seq on a test server, we've twice seen the Seq service have not come back automatically after a server reboot. The only strange thing in the Event logs is both times the system time was changed to a couple hours back in time. We've tried to repro this locally, but haven't found a way to actually change the system time to confirm ("Some settings are managed by your organization"). Thus reporting this in hope somebody else can repro or confirm. Per stability troubleshooting steps: Seq v3.4.20 - The Services console lists "Seq Event Server and Web UI" and should start automatically. OS: Windows Server 2016 Standard .NET version: 4.6.01586 (60632) Hardware: VMWare, Intel(R) Xeon(R) CPU, E5530 @ 2.40GHz, 2394 Mhz, 2 Core(s), 2 Logical Processor(s), 8GB RAM + 9.25GB virtual Settings > Diagnostics: - API Endpoint events: 0/0 0/0 0/0 - Storage: The event store is arranged in segments from 2017-05-17 to 2017-06-20. - Out of 35 recorded days, 35 days totalling 62711 events are cached in RAM. - Uptime 0 days - Working set (bytes) 231411712 - Threads 25 - User thread pool threads available 32765 - IOCP thread pool threads available 999 - Memory utilization 25% - Free space (bytes) 70923096064 - Sample system memory 28 minutes ago - Manage segment cache resources 28 minutes ago Tail of log file from when the server did not come back up: 2017-05-19 14:37:04.933 +01:00 [Information] Received OS shutdown notification 2017-05-19 14:37:04.933 +01:00 [Information] Stopping HTTP listener 2017-05-19 14:37:04.933 +01:00 [Information] Signalling for 2 background worker(s) to complete 2017-05-19 14:37:06.261 +01:00 [Information] Stopping 10 scheduled tasks 2017-05-19 14:37:06.261 +01:00 [Information] Stopping broadcast channel 2017-05-19 14:37:07.173 +01:00 [Information] Seq stopped cleanly Event Viewer > System Log lists the following two events: Date: 19/05/2017 13:21:47 The Seq service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Date: 19/05/2017 13:21:47 A timeout was reached (30000 milliseconds) while waiting for the Seq service to connect. The only odd thing I can see is the server clock being adjusted around the same times, which is known to potentially cause issues. It caught my eye because the timestamps in the logs/event viewer don't match up (besides UTC/BST confusion), and there is this system log event timestamped 14:40:47: The system time has changed to ‎2017‎-‎05‎-‎19T13:40:47.094288300Z from ‎2017‎-‎05‎-‎19T12:23:40.322019000Z. Change Reason: An application or system component changed the time. Last time Seq did not come back, on 11. may, there was a similar "changed the time" event around when the server restarted (around 02:00-04:00 in the morning). Any ideas?

Posted by Anders 4 years ago