Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Looks like Umbraco 7 shuts down the application everytime a node is published. In the log it says "Application shutdown. Reason: ConfigurationChange". This sounds a bit drastic!?
The reason I'm asking is that one of our websites suddenly started hammering away on the CPU bringing the entire server to a stand still. It was using over 90% of the CPU power and kept doing it until we could kill the process. Why would it do that?
This is a known issue with a Windows Update, Microsoft is working on it: http://issues.umbraco.org/issue/U4-6338
I can confirm that uninstalling the hotfix solves the problem. We had the same issue last friday.
Ok, so this can make the entire application pool use all the CPU?
We have the KB3000850 update installed but cannot find the KB3007507 update in the installed updates list. How do we remove just KB3007507?
Yes, this can cause big CPU spiking as the application pool may go into a shutdown cycle.
Make sure to read the issue, KB3007507 is the actual cause of the problem, it can get installed as part of KB3000850 but not necessarily. So removing KB3000850 should help.
Ok, that's good to know. Only problem then is that KB3000850 fixes all kinds of stuff. Do you know when Microsoft will release an official fix? It doesn't feel right removing a lot of other - maybe important - fixes.
Make sure to add yourself as a watcher to the issue for updates!
We're on a locally-hosted Win2008 server with just the single Umbraco 7.5.3 site and started noticing lots of these shutdowns lately also (same issue, after any node is published), hadn't happened with 7.4.x versions. Have tried things like changing the app pool "Disable recycling for configuration" parameter, experimenting with the fcnMode parameter in web.config, etc., but keep getting these shutdowns.
We had the shutdown on publish problem as well on one of our setups.
Our solution after multiple days bug hunting:
Create a new IIS instance for that site.
I can't find any noticable difference between the old and the new instance, but it solved the problem for us.
(Windows Server 2012 R2 all patches applied)
I'm wondering if your solution applies in our single-server, single-site situation, and also unsure how to start a new IIS instance (or are you saying create a new IIS application and application pool, and move the site to that?).
Sorry for the probably dumb-sounding request, but we're really at wit's end and will likely pay for a support ticket soon as we're getting shutdowns after every node publish now.
Yes, I just added a new website in IIS with it's own application pool.
The only difference was the name (I added www. to the site name).
Same bindings, same everything.
Turn off old IIS-site;
Turn on the new one.
In our case: problem solved.
FYI: we've recently seen some people on Windows Server 2008 (not 2012!) have some success in changing from fcnMode="Single" to fcnMode="NotSet" (or just not specifying fcnMode in web.config, which then falls back to NotSet).
Even better results were achieved with fcnMode="Disabled" but make sure to read up on what that means in the comments here: http://shazwazza.com/post/all-about-aspnet-file-change-notification-fcn/
Note that when setting it to Disabled you can't change templates from the backoffice any more, you will need to manually recycle the application pool after changing the template.
Experimented just now with the "NotSet" value, which acts the same as "Default" (and "Single") for us, meaning it still triggers a shutdown after every node publish.
So far the only solution is "Disabled" (at least for Win 2008 / Umbraco 7.5.3), but yes changing templates/partial views, etc. requires touching web.config or recycling the app pool.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted