What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Is restarting really required?

Votes:

0

Your Vote:

Up

Down

When updating prtg it asks for a restart. Is this really necessary? Restarting a server is not very favored.

What is done by restarting? If only the services need to be started, this could be done manually as well.

installation prtg restart update

Created on Jan 10, 2011 12:44:59 PM by  Uwe (0) 1



5 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down

When updating PRTG, we avoid restarts whenever possible. When PRTG requests a restart after installation, it is required to make sure all files are up to date. This can be due to blocked files. If PRTG requests a restart after every update, please make sure no backup software, anti-virus scanner, or other system tool blocks the files and prevents the installer from updating them.

Created on Jan 10, 2011 3:29:07 PM by  Daniel Zobel [Product Manager]



Votes:

0

Your Vote:

Up

Down

Hmm interesting. I never had problems with restarting but the last two updates, PRTG has asked for updates and nothing on the server has changed.

Any ideas what could be causing this? There's no backup/antivirus etc running.

Cheers

Created on Mar 31, 2011 3:51:31 AM by  Jithen Singh (0) 1



Votes:

0

Your Vote:

Up

Down

These were most likely some 'blocked files'. Please do watch carefully if this re-occurs with the next updates.

Created on Mar 31, 2011 12:40:04 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I'm seeing this with all releases now, no matter how careful I am.

This time, I stopped the host and probe services manually, validated that everything had stopped correctly and the installer /still/ wanted to reboot.

Unfortunately, the installer doesn't seem to have written to PRTG Server Install.log this time, so I have no way of telling, but previously the log reported this:

2011-10-14 13:33:43.500   Dest filename: C:\Program Files\PRTG Network Monitor\PRTG Server.exe
2011-10-14 13:33:43.500   Time stamp of our file: 2011-10-11 16:56:30.000
2011-10-14 13:33:43.500   Dest file exists.
2011-10-14 13:33:43.500   Time stamp of existing file: 2011-10-07 00:15:46.000
2011-10-14 13:33:43.500   Installing the file.
2011-10-14 13:33:43.594   The existing file appears to be in use (5). Will replace on restart.
2011-10-14 13:33:43.594   Leaving temporary file in place for now.
2011-10-14 13:33:43.594   -- File entry --

Could it be that the auto update installer is not allowing enough time for the host service to stop on large systems (we have thousands of sensors)?

Stuart

Created on Oct 20, 2011 1:25:39 PM by  Stuart Hall (10) 1



Votes:

0

Your Vote:

Up

Down

The installer is set to wait 300seconds for the PRTG Services to shut down. We think this is a good value, because usually if the services don't shut down in 5 minutes, they are hanging and won't exit at all.

Created on Oct 21, 2011 1:59:31 PM by  Torsten Lindner [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.