I've got an urgent problem. Recently new Umbraco websites I created stop running after a while. I don't know what the problem is exactly, but I think it's got something to do with the default setup.
The problem is the website just keeps loading (local and on a test webserver) and never ends loading. There is no error in any log files. It's almost as if it's in some infinite loop. Sometimes after a very long time the website finally works and runs normal after this. Like it just took a very very long time to compile after new dll's have been added.
Older websites I created work perfectly fine, but all the newer ones give the above problems.
If this happens after each recycle on the server then I would start by removing DLL's one by one. Especially DLL's that are new in your recent set-ups.
Yes that's exactly what happens. Good idea I'll start with that.
P.S. I do the complete installation local and when I'm done I move it to a test server. I see the following error a lot in the log: At /umbraco/plugins/TaskScheduler/handlers/ScheduledTaskHandler.ashx (Referred by: ):
There doesn't appear to be anything obvious in what you've descirbed. On the surface it seems that it should run just fine.
I think you're in for some trial-and-error debugging unfortunately.
Here's how I'd attack the problem (on a local, dev copy of the site... and after backing it up first!)...
1. Create a super-simple 'test' template and call that for your homepage... that way you eliminate a lot of potential issues caused by macros and such that might obsucre the source of the issue. Something like the following:
If that works then the problem is in your templates/macros/items code. If not, it's more 'system' oriented.
2. Remove as many of the custom datatypes and packages and dlls as you can (as well as app_code) to remove them from consideration. Again, we're trying to quickly simplify the installation to isolate the problem.
If the site suddenly starts working you'll know it is in one of the items you removed and you can start again (remember that backup, right?!?) and remove items one-by-one until you find the offending item.
3. Always look in the umbracoLog table as well as the machine's Event Viewer for hints. You might also watch the CPU/Memory usage.
A crazy idea... if your application pool takes too long (or too much cpu or memory) to fully launch before it recycles itself you'll get an endless loop of non-responsiveness. You might try increasing those limits and timeouts while you're debugging this.
There are no scheduled tasks in the umbracoSettings.config file, but the website has been loading for over 15 min now and this error keeps popping up in the log:
1767 0 -1 19-5-2010 11:52:54 Error At /umbraco/plugins/TaskScheduler/handlers/ScheduledTaskHandler.ashx (Referred by: ):
Debug was still set to true because the websites aren't live yet and I'm still testing. After changing it to false there is no difference.
Another note: the websites seem to be running ok in UltiDev Cassini Web Server. They don't in my local IIS or the test server IIS. After adding new dll's the websites also doesn't run in UltiDev Cassini Web Server unless I restart the service.
Check to see if you've got some 'publish at' or 'unpublish at' fields set. I'm not sure if those would trigger the 'scheduled task' log entry or not but I've seen a few issues with them in 4.0.x and (again) it's best to simplify the site as much as possible.
The filepath for the 'TaskScheduler' is niggling me (/umbraco/plugins/TaskScheduler/handlers/ScheduledTaskHandler.ashx) ... that's definitely from the TaskScheduler package. If you aren't using it, then check if there are still any references to it - in the web.config, bin, etc.
I'm still looking at all the options. I've got a website with the same setup, but this website does seem to run normal. I'm first going to look at any differences between this website and the websites which aren't running.
P.S. If I place a static html page on these websites it does work, but everyting related to Umbraco doesn't work. The /umbraco/umbraco.aspx page also doesn't work.
Have you tried adding the task scheduler? If something is calling the TaskScheduler, it might temporarily fix your problem to have it installed while you find out what is calling it. The call to a non-existent TaskScheduler may be blocking the thread while it waits for a response, especially if it is called in code synchronously.
I will also try that. The websites are still loading infinite, but at one moment I got the following exception:
Server
Error in '/' Application.
Thread was being aborted.
Description:
An unhandled exception occurred
during the execution of the current web request. Please review the stack trace
for more information about the error and where it originated in the code.
Exception
Details: System.Threading.ThreadAbortException: Thread was
being aborted.
Source Error:
An unhandled
exception was generated during the execution of the current web request.
Information regarding the origin and location of the exception can be
identified using the exception stack trace below.
Yes. Some code is trying to initiate a call on a thread that is hung but in the process of trying to shut itself down. Recycling the Application Pool or doing an iisreset (touching web.config may work if you don't have direct access to the app pool) should clear this temporarily. This makes me lean more strongly towards some code calling something which then blocks the thread while it tries to complete. Try installing the TaskScheduler and if that fixes it, you will need to determine what is calling it and disable it so that you can remove the Task Scheduler if you don't need it.
I can't even install TaskScheduler package, because the moment the dll gets added to the bin folder the website get's in the infinit loop again. I need to do a hard reset to continue after that. The dll had been added, but not extra tables have been installed so the package is only half installed....
I think temporarily removing the custom (package installed) dlls from the bin directory may be required at this point. If one of those contains an event handler that is responding to a frequent event, it may be causing the other symptoms. As Douglas Robar said that may help isolate the problem. You don't have to uninstall the package, just remove the custom dlls (place them in a temporary location locally so that you can add them back). See if the site works.
If it does, you may be able to remove the partially installed package.
You can then:
Add the dlls back one by one until it breaks again to determine the source of the problem.
-Or- try installing the TaskScheduler package again while the site is working and then add all the dlls back in to see if the issue was related to calling a missing Task Scheduler.
Thanks Chris, but I'm seriously doubting if I should just start these websites from scratch and then test were it goes wrong. Removing a single dll causes the entire local IIS to crash and restarting it every time is frustrating. I still have no clue were it goes wrong. Sometimes it works now but a moment later it doesn't again. It's got something todo with the dll's I think, but I just can't figuere out what is causing the problem. What should I do?
Either approach is valid. Do whichever you feel would be less painful. The main thing is you need to find the problem and if logical guesses aren't providing an answer, we may need to use brute force.
Unless we can stop the IIS hangup, working with the existing site(s) may be more painful than starting one from scratch and adding things back in. If you create a package out of your custom Datatypes, templates and nodes, it might make rebuilding easier.
That's a good idea :). I'll try and make a package out of everything if it doesn't crash ;). There are a few things I still want to try, but if those don't help I'm really going to start over.
Well I finally got it solved. I hate it when you spend all day long looking for a bug and when you find it's pretty simple... Both websites which didn't work had a custom dll which had an ApplicationBase class. This code is called on application start. In this class there was an exception which caused the websites to crash en never complete loading. I putted my code in a try catch which should log when an exception occurs, but that didn't work for some reason. It's still a bit vague, but both websites are running again :).
I want to thank everyone for their help. This once again proves how awesome the Umbraco community is.
This also explains why both websites crashed after every dll which was removed or added. The application always restarts after this and always ran into my exception which made it crash.
Ouch! I was going to suggest (and you could try it if you have any trouble next time) to start with a bin folder with nothing but the default Umbraco dll's in it and then add one dll at a time so you can see which one if giving you the trouble. So instead of removing them one by one, this would be quite a bit faster.
You're right Sebastiaan. Next time I should start with the default Umbraco dll's and add the other dll's one by one because eventually it was the last dll I removed... It's just this code has been working perfect for months in other projects so I didn't expect the problem to be in my own dll's. That's why I started with removing the other dll's first. Well I've learned my lesson :).
Urgent! Websites stop running
Hello,
I've got an urgent problem. Recently new Umbraco websites I created stop running after a while. I don't know what the problem is exactly, but I think it's got something to do with the default setup.
Here is a small list of my setup:
- Install Umbraco 4.0.3 with ASP.NET 3.5 config
- Install the following packages:
- Tribal Yet Another Media Picker 4
- Robots.txt Editor
- Multiple File Upload (patched)
- User Control File Editor
- ImageGen
- FamFamFam Icons
- Google Sitemap
- Permanent Redirect
- Do the multiple fileupload fix discussed in this topic.
- Add some custom dll's to the website (always worked fine also in older projects without problems)
- Add extra datatypes, documenttypes, templates and nodes to Umbraco.
- Add Dotless for better css.
The problem is the website just keeps loading (local and on a test webserver) and never ends loading. There is no error in any log files. It's almost as if it's in some infinite loop. Sometimes after a very long time the website finally works and runs normal after this. Like it just took a very very long time to compile after new dll's have been added.
Older websites I created work perfectly fine, but all the newer ones give the above problems.
Please help me!
Jeroen
If this happens after each recycle on the server then I would start by removing DLL's one by one. Especially DLL's that are new in your recent set-ups.
Yes that's exactly what happens. Good idea I'll start with that.
P.S. I do the complete installation local and when I'm done I move it to a test server. I see the following error a lot in the log:
At /umbraco/plugins/TaskScheduler/handlers/ScheduledTaskHandler.ashx (Referred by: ):
Jeroen
There doesn't appear to be anything obvious in what you've descirbed. On the surface it seems that it should run just fine.
I think you're in for some trial-and-error debugging unfortunately.
Here's how I'd attack the problem (on a local, dev copy of the site... and after backing it up first!)...
1. Create a super-simple 'test' template and call that for your homepage... that way you eliminate a lot of potential issues caused by macros and such that might obsucre the source of the issue. Something like the following:
And call the page using the ?altTemplate syntax... http://localhost/default.aspx?altTemplate=test
If that works then the problem is in your templates/macros/items code. If not, it's more 'system' oriented.
2. Remove as many of the custom datatypes and packages and dlls as you can (as well as app_code) to remove them from consideration. Again, we're trying to quickly simplify the installation to isolate the problem.
If the site suddenly starts working you'll know it is in one of the items you removed and you can start again (remember that backup, right?!?) and remove items one-by-one until you find the offending item.
3. Always look in the umbracoLog table as well as the machine's Event Viewer for hints. You might also watch the CPU/Memory usage.
A crazy idea... if your application pool takes too long (or too much cpu or memory) to fully launch before it recycles itself you'll get an endless loop of non-responsiveness. You might try increasing those limits and timeouts while you're debugging this.
Let us know what you find out.
cheers,
doug.
Check your /config/umbracoSettings.config file for any scheduled tasks. That may be the culprit.
cheers,
doug.
Double check that the website isn't running in debug mode, (you've probably already done that).
As for the 'TaskScheduler' error log, do you have that package installed? (you didn't mention it above).
There are no scheduled tasks in the umbracoSettings.config file, but the website has been loading for over 15 min now and this error keeps popping up in the log: 1767 0 -1 19-5-2010 11:52:54 Error At /umbraco/plugins/TaskScheduler/handlers/ScheduledTaskHandler.ashx (Referred by: ):
Debug was still set to true because the websites aren't live yet and I'm still testing. After changing it to false there is no difference.
I haven't installed the TaskScheduler package on these websites. However I did on an other website, but that website runs normal.
Another note: the websites seem to be running ok in UltiDev Cassini Web Server. They don't in my local IIS or the test server IIS. After adding new dll's the websites also doesn't run in UltiDev Cassini Web Server unless I restart the service.
Check to see if you've got some 'publish at' or 'unpublish at' fields set. I'm not sure if those would trigger the 'scheduled task' log entry or not but I've seen a few issues with them in 4.0.x and (again) it's best to simplify the site as much as possible.
cheers,
doug.
The filepath for the 'TaskScheduler' is niggling me (/umbraco/plugins/TaskScheduler/handlers/ScheduledTaskHandler.ashx) ... that's definitely from the TaskScheduler package. If you aren't using it, then check if there are still any references to it - in the web.config, bin, etc.
I'm still looking at all the options. I've got a website with the same setup, but this website does seem to run normal. I'm first going to look at any differences between this website and the websites which aren't running.
P.S. If I place a static html page on these websites it does work, but everyting related to Umbraco doesn't work. The /umbraco/umbraco.aspx page also doesn't work.
Another result: The static html page works, but after adding an aspx page which isn't related to Umbraco in any way it also doesn't work.
Jeroen,
Have you tried adding the task scheduler? If something is calling the TaskScheduler, it might temporarily fix your problem to have it installed while you find out what is calling it. The call to a non-existent TaskScheduler may be blocking the thread while it waits for a response, especially if it is called in code synchronously.
--Chris
Hello Chris,
I will also try that. The websites are still loading infinite, but at one moment I got the following exception:
Server Error in '/' Application.
Thread was being aborted.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Threading.ThreadAbortException: Thread was being aborted.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[ThreadAbortException: Thread was being aborted.]
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +486
System.Web.ApplicationStepManager.ResumeSteps(Exception error) +501
System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) +123
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +379
Version Information: Microsoft .NET Framework Version:2.0.50727.3053; ASP.NET Version:2.0.50727.3053
Someone familiair with that?
Jeroen
Jeroen,
Yes. Some code is trying to initiate a call on a thread that is hung but in the process of trying to shut itself down. Recycling the Application Pool or doing an iisreset (touching web.config may work if you don't have direct access to the app pool) should clear this temporarily. This makes me lean more strongly towards some code calling something which then blocks the thread while it tries to complete. Try installing the TaskScheduler and if that fixes it, you will need to determine what is calling it and disable it so that you can remove the Task Scheduler if you don't need it.
--Chris
Now the Umbraco log says At /favicon.ico (Referred by: ): instead of the TaskScheduler. This is getting weird.
I can't even install TaskScheduler package, because the moment the dll gets added to the bin folder the website get's in the infinit loop again. I need to do a hard reset to continue after that. The dll had been added, but not extra tables have been installed so the package is only half installed....
Jeroen,
I think temporarily removing the custom (package installed) dlls from the bin directory may be required at this point. If one of those contains an event handler that is responding to a frequent event, it may be causing the other symptoms. As Douglas Robar said that may help isolate the problem. You don't have to uninstall the package, just remove the custom dlls (place them in a temporary location locally so that you can add them back). See if the site works.
If it does, you may be able to remove the partially installed package.
You can then:
Add the dlls back one by one until it breaks again to determine the source of the problem.
-Or- try installing the TaskScheduler package again while the site is working and then add all the dlls back in to see if the issue was related to calling a missing Task Scheduler.
--Chris
Thanks Chris, but I'm seriously doubting if I should just start these websites from scratch and then test were it goes wrong. Removing a single dll causes the entire local IIS to crash and restarting it every time is frustrating. I still have no clue were it goes wrong. Sometimes it works now but a moment later it doesn't again. It's got something todo with the dll's I think, but I just can't figuere out what is causing the problem. What should I do?
Jeroen
Jeroen,
Either approach is valid. Do whichever you feel would be less painful. The main thing is you need to find the problem and if logical guesses aren't providing an answer, we may need to use brute force.
Unless we can stop the IIS hangup, working with the existing site(s) may be more painful than starting one from scratch and adding things back in. If you create a package out of your custom Datatypes, templates and nodes, it might make rebuilding easier.
--Chris
Hi Chris,
That's a good idea :). I'll try and make a package out of everything if it doesn't crash ;). There are a few things I still want to try, but if those don't help I'm really going to start over.
Jeroen
Well I finally got it solved. I hate it when you spend all day long looking for a bug and when you find it's pretty simple... Both websites which didn't work had a custom dll which had an ApplicationBase class. This code is called on application start. In this class there was an exception which caused the websites to crash en never complete loading. I putted my code in a try catch which should log when an exception occurs, but that didn't work for some reason. It's still a bit vague, but both websites are running again :).
I want to thank everyone for their help. This once again proves how awesome the Umbraco community is.
Jeroen
This also explains why both websites crashed after every dll which was removed or added. The application always restarts after this and always ran into my exception which made it crash.
Ouch! I was going to suggest (and you could try it if you have any trouble next time) to start with a bin folder with nothing but the default Umbraco dll's in it and then add one dll at a time so you can see which one if giving you the trouble. So instead of removing them one by one, this would be quite a bit faster.
Glad you got it sorted!
You're right Sebastiaan. Next time I should start with the default Umbraco dll's and add the other dll's one by one because eventually it was the last dll I removed... It's just this code has been working perfect for months in other projects so I didn't expect the problem to be in my own dll's. That's why I started with removing the other dll's first. Well I've learned my lesson :).
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.