Hello there,

I have a strange issue. For some reason the PRTG Core Server Service stops at 12:42 AM (Eastern Time zone). I have updated to the current version and its stable (PRTG Network Monitor 17.1.30.1681 x64).

I have a colleague using an older version “16.4.28.7421”, and he doesn’t have this issue.

Dear Ahmed Omar,

The Core Log shows a shut down during the night here:

3/24/2017 12:42:33 AM PRTG is shutting down
3/24/2017 12:42:33 AM Shutdown: Stopping Background Tasks
3/24/2017 12:42:33 AM Shutdown: Stopping Library Engine
3/24/2017 12:42:33 AM Shutdown: System Information
3/24/2017 12:42:33 AM Shutdown: Stopping Webserver
3/24/2017 12:42:33 AM Shutdown: Saving Configuration
3/24/2017 12:42:33 AM Configuration File: Saving
3/24/2017 12:42:33 AM Configuration File: Saving Step 1 0 ms
3/24/2017 12:42:33 AM Configuration File: Saving Step 2 0 ms
3/24/2017 12:42:33 AM Configuration File: Saving Step 3 0 ms
3/24/2017 12:42:34 AM Configuration File: Saving Step 4 812 ms
3/24/2017 12:42:34 AM Configuration File: Saving Step 5 812 ms
3/24/2017 12:42:36 AM Configuration File: Saving Step 6 2637 ms
3/24/2017 12:42:36 AM Configuration File: Saved 2652 ms
3/24/2017 12:42:36 AM Shutdown: Stopping Data Calculation Engine
3/24/2017 12:42:36 AM Shutdown: Releasing Memory for Background Tasks
3/24/2017 12:42:36 AM Shutdown: Stopping Data Synchronizer Engine
3/24/2017 12:42:37 AM Shutdown: wait (49,0)
3/24/2017 12:42:37 AM Shutdown: Stopping Aggregation Scheduler Engine
3/24/2017 12:42:37 AM Shutdown: Stopping Probe Engine
3/24/2017 12:42:37 AM Shutdown: Stopping Scheduler Engine
3/24/2017 12:42:37 AM Shutdown: Stopping Dependency Engine
3/24/2017 12:42:37 AM Shutdown: Stopping Correlation Engine
3/24/2017 12:42:37 AM Shutdown: Releasing Memory for CorrelationThread
3/24/2017 12:42:37 AM Shutdown: Stopping Raw Data Storage Engine
3/24/2017 12:42:37 AM Shutdown: Setting Read Only flag for custom lookups
3/24/2017 12:42:37 AM Shutdown: Releasing Memory for Probes
3/24/2017 12:42:37 AM Shutdown: Releasing Memory for Data Synchronizer Engine
3/24/2017 12:42:37 AM Shutdown: Releasing Memory for Aggregation Scheduler Engine
3/24/2017 12:42:37 AM Shutdown: Releasing Memory for Raw Data Storage Engine
3/24/2017 12:42:37 AM Shutdown: Releasing Memory for Libraries
3/24/2017 12:42:37 AM Shutdown: Releasing Memory for Schedules
3/24/2017 12:42:37 AM Shutdown: Releasing Memory for Dependencies
3/24/2017 12:42:37 AM Shutdown: Releasing Memory for SystemInformation
3/24/2017 12:42:37 AM Shutdown: Saving Data Cache Step 1
3/24/2017 12:42:37 AM Shutdown: Saving Data Cache Step 2
3/24/2017 12:42:38 AM Shutdown: Saving Data Cache Done
3/24/2017 12:42:38 AM Shutdown: Releasing Memory for Webserver
3/24/2017 12:42:38 AM Shutdown: Stopping Notifications
3/24/2017 12:42:38 AM Shutdown: Releasing Memory for MIBs
3/24/2017 12:42:38 AM Shutdown: Releasing Memory for Logs and Tickets
3/24/2017 12:42:38 AM Shutdown: Done
3/24/2017 12:42:38 AM Stop Done
3/24/2017 12:42:38 AM System Cleanup Done

Article Comments

Hello there,

We'll need the complete logs to investigate what is happening. Please forward us a Support Bundle including the system log files for analysis. The Support Bundle can be sent via the "Contact Support" ribbon in the lower right corner of the web interface or from within Setup > Contact support. If you're not able to run/access PRTG this can also be done using the 'Logs & Info' tab within the "PRTG Administration Tool" application. Please enter PAE848479 when submitting the Bundle.

Best Regards,
Luciano Lingnau [Paessler Support]


Apr, 2017 - Permalink

Thank you for the reply. However I have worked with your support team. I did open a ticket and I still believe it's still open.

Here is the last reply I got. The ticket number is PAE8444XX. I was sending this to the group to see if anyone else has upgraded to the latest version and had this issue.

Thanks Ahmed

From: Paessler Support Team [mailto:support@paessler.com] 
Sent: Wednesday, March 29, 2017 1:29 AM
To: -----------------
Cc: --------------------------
Subject: Re: (Case PAE8444XX) Configuration&Usage: PRTG core windows service is stopping and I updated (95)

Dear Ahmed Omar,

We can see no issues from PRTG's logs with the Windows services it depends on. However, that cannot really be logged from within PRTG, so you will have to check this yourself if those services were shut down by any chance.


With kind regards / Mit freundlichen Gruessen

Torsten Lindner
Support Team, Paessler AG
support@paessler.com

Apr, 2017 - Permalink

Hello Ahmed,
thank you for your reply.

Ok, I'll leave your post here on the KB open in case someone wants to share their feedback or encounters a similar issue. About your case PAE8444XX, Torsten will contact you again.

Best Regards,
Luciano Lingnau [Paessler Support]


Apr, 2017 - Permalink