lately we encountered the problem that our Azure Worker Role service restarts almost every day. This is a huge problem for us, since our service needs around 20 minutes to initialize and these restarts can cause downtimes.
I logged in to the instances via RDP and looked in the event logs to figure out what was causing these seemingly random restarts. I came accross a few entries that always preceded a restart:
The service installed by the MsiInstaller is "Windows Azure Remote Forwarder". I assume this service gets installed because we enabled Remote Desktop in our worker role configuration. The interesting thing is that we have RDP enabled for a long time (2 years or so) but the random restarts are just occuring since 4 weeks ago.
But there are a few things than I don't quite understand:
- Why is this service installed or updated so frequently?
- I know that the RestartManager is responsible for installing/updating services without having to restart the machine by stopping other services that are blocking files.
Is it possible that our service blocks some important files?
Could it be a problem that we use a local disk storage for temporary files? - Is it possible to tell the RestartManager to leave our Worker Role service alone?
- Is this just coincidence and the restarts are somehow triggered by our service, although no logs indicate errors on our side?
Any help is greatly appreciated.
Thanks,
Karsten
Restart Manager: The Restart Manager feature is - as you say yourself (others might read) - simply a way for setups to restart applications instead of requiring a system reboot by "making applications capable of shutting themselves down and restarting in a controlled fashion".
"amus"
- force overwrite all files regardless of version.Default MSI Logging: One debugging starting point is to log all your MSI operations properly - whenever you install, reinstall or repair there will be a log file in the temp directory (not always acceptable for some sysadmins). You can enable logging for all MSI installations by following the procedure in the
"Globally for all setups on a machine"
section in the above link.Self-Repair in Detail: I have written a lot about unexpected self-repair before. More than anyone wants to know. It is a terribly silly problem that does cause really expensive problems to resolve since few people are familiar with the operation of Windows Installer:
Debugging: All the information below is available in the above answers, but here are some quick pointers:
"MsiInstaller"
: IDs1001
and1004
.Pending Reboots: How often is this machine rebooted? Many machines have a lot of pending reboots registered that are never completed and problems can result. There are many registry locations that can be involved in triggering a reboot (warning). Get-PendingReboot-Query. And a similar PowerShell script.
Locking Problems: Just want to mention the problem of some applications locking resources in a very low-level way, for example anti-virus and malware protection suites.