-
☆ A M B ☆
- 24,524 Posts
Could the database have gotten corrupted? Or the cache filesystem? I’ve had both happen, in the one case I had to completely drop the database and re-create it from backup, so I think the filesystem used by the database was the culprit in that case. I’ve also had the image files corrupted so that the Resource Browser wouldn’t work, again I deleted the whole assets/images folder and re-uploaded it from backup via ftp and it started working again. This is all on totally different servers, by the way, so it can happen to anybody.
Fixed by installing x9.1 over the top!
Not sure what actually caused it, but not a database error, as still using the same db.
Thanks for responses.
Richard
Quote from: xwisdom at Mar 10, 2006, 11:33 AM... a good place to start is to have alook at the escape functions used inside the cache manager.
I did an
examdiff on the old (0.9) and new (0.9.1) cache_sync.processor.php files and there were only 5 lines different:
Before:
if (preg_match ("/\.pageCache/", $file)) {
$deletedfilesincache += 1;
$deletedfiles[] = $file;
unlink($this->cachePath.$file);
}
After:
if(strstr($file, '.pageCache')){
unlink($this->cachePath.$file);
$deletedfilesincache += 1;
$deletedfiles[] = $file;
}
Frankly, that just doesn’t look like it would matter as those lines only deal with wiping out cache files. So I’m going to have to start looking other places too. And incidentally, the "it just started happening" scenario that recardosanX describes is exactly how it happened to me too. Was cruising along fine till WHAM! Not good.
Next time someone has this problem, try deleting the assets/cache/siteCache.idx.php file and see if that helps. I’d be really curious.
Standard Disclaimer
I could be totally wrong.
Just wanted to chime in on this one as I am having the same problem. I just upgraded to the newest PHP with no improvements.
Apache 1.3.31
PHP 4.4.2
Mysql 3.23.43
Using Safari, I’ll get an error page that looks like the server just terminated the connection, but reloading the page will bring it up as expected. In addition, checking the cache directory, it looks like the cached file has been created completely, so it looks like a problem (at least on my machine) where the cache file is being built, but isn’t getting served up properly right after it’s been written. Could the server be trying to serve up a cached version of the page before it’s been written to disk or something?
@jcn
Next time someone has this problem, try deleting the assets/cache/siteCache.idx.php file and see if that helps. I’d be really curious.
Have you tried deleting this file: a
ssets/cache/siteCache.idx.php (not just the cached page file)
It won’t hurt to do so (and it will be recreated next time you edit a document)??
Standard Disclaimer
I could be totally wrong.
Had the same problem and deleting assets/cache/siteCache.idx.php seems to have fixed it.
Dunno if Refresh Site would’ve had the same effect (since I couldn’t get into the manager either - blank page).
I have since set all my snippets to uncached and pages to cached, so we’ll see if it occurs again.
It definitely acts as if PHP is in a loop or overloaded (ths site is running PHP 4.3.11), so maybe deleting the cache file just forces it to break.
0.92 is due any day, so I’m not going to fret unless and until it starts happening with that version also.
Quote from: ZAP at Apr 09, 2006, 11:25 PM
Had the same problem and deleting assets/cache/siteCache.idx.php seems to have fixed it.
Well at least I feel like we have a direction to look in now: something wacky in the caching routine.
Quote from: ZAPDunno if Refresh Site would’ve had the same effect (since I couldn’t get into the manager either - blank page).
It’s not likely that a refresh would have made any impact. I had tried that dozens of times. It’s wierd that your manager turned up blank too... that kind of throws a wrench in the caching process theory as the manager isn’t cached.
0.92 is due any day, so I’m not going to fret unless and until it starts happening with that version also.
Unfortunately, without knowing what is causing the problem, I can’t see any reason to assume it wouldn’t happen in 0.9.2. We just have to get to the bottom of this thing quick style.
Standard Disclaimer
I could be totally wrong.
Quote from: jaredc at Apr 10, 2006, 08:42 AM
Quote from: ZAPDunno if Refresh Site would’ve had the same effect (since I couldn’t get into the manager either - blank page).
It’s not likely that a refresh would have made any impact. I had tried that dozens of times. It’s wierd that your manager turned up blank too... that kind of throws a wrench in the caching process theory as the manager isn’t cached.
Not necessarily. If the problem was that a PHP process was stuck writing and rewriting to the cache file then that may have caused the manager to be affected as well. I was imagining that deleting the cache file forced a process to exit, not that the cache was just serving corrupted content.
I don’t KNOW that this is what happened, but it’s what seemed to fit the available evidence in my specific case...
I was futzing with the NewsListing and Publisher snippets when this happened (and it works fine now). Also I’m building this site on a really terrible host (I won’t mention names, but suffice to say they charge a dollar a month). I’ve found that they restrict me to one FTP thread at a time, and I wouldn’t be surprised if they had some sort of CPU use limitations also.
-
☆ A M B ☆
- 24,524 Posts
