Administration backend freezing

[carrotwax]

It used to work just fine, and then suddenly Joomla freezes when content is attempted to be added/changed in the backend. There's a web timeout. This is when I try to add content, add a menu item, and add an event via the event component. It just times out. Interestingly enough, one time out of 10 it works after 2 minutes. However, user registration in the front end works fine, and data is read from the database fine.

I couldn't see any deadlocks or anything weird. I could run insert SQL queries fine directly against the database. This is hosted by dreamhost. Could I get some ideas on what could be causing this?

[carrotwax]

I figured it out.

The cache directory was so full that even a directory listing froze. When I removed everything in that directory, voila, everything worked. [it was so full even rm * froze. I had to rename the directory and create a new one.]

I believe this was mainly due to bad web crawlers. I have an events component installed, which of course lets you click on any month in existance. That is, you can keep clicking "next month" for 100,000 years and get different pages. 99.9% of the pages in the cache were for the events page.

So I edited the robots.txt file and disallowed everything on the events component.

Now, is this a mild bug in caching? Caching shouldn't crash the system. The TTL of caching wasn't very high.

[ircmaxell]

Sounds like a server issue to me... dir listings (even with HUGE folders) should never freeze... RM * should never freeze eitehr (it may give you an error that the argument list is too long, but shouldn't freeze). I've tested this with folders with over 2 million files in them (I highly doubt you have THAT many cache files)...

[carrotwax]

Well, I've worked in unix systems for years, and I've seen it before. Depends how the filesystem is implemented. But my host is likely not going to rewrite the filesystem. :-)

[syhussaini]

Joomla Version 1.5.25

This topic has been posted here for a long time now.
But I just wanted to thank for a nice and easy resolution.
I ran into the same problem and applied your technique of cleaning cache (from front-end) and was able to fix it.

Can you please write back the steps to clean cache from back-end and or any other way.

Any inputs will be of great value.

[auss]

I have the same problem with Joomla 2.5 and K2

http://extensions.joomla.org/extensions ... mance/7244
this plugin solve the problem partially (in general this plugin works like magic really) but I think the main bottleneck still in database query because It appear at (save) action.