Page not Found after a long period of time

Hi Rik

I have 3 choices for session storage: User's computer in a cookie, on core cache database, in $_SESSION memory. It is presently set to "in a cookie", as this seems to last longest.

Expiration is set at 7 days.

The time until "Page not found" appears is a bit challenging. I don't have precise measurements, but my gut says that if the storage is set to be a cookie, it lasts a day. If it's set to Core cache DB, it will work for a few hours. Same as if I use $_SESSION.

"Page and Else" is a cache clearing feature from .. uhh.. the Admin Menu module, I think. Clearing the registry invokes registry_rebuild(), while page and else clears the cache, cache_boostrap, cache_filter, cache_page tables, I believe (just taking a cursory look at what admin_menu does

For what it's worth, if I check the configuration of the view when the issue is present, I find that the Contextual Filter selection is missing the Global Filter option. Once I clear the cache, and re-check the configuration, the Contextual Filter type has been selected back to Global Filter (field or search term).

I'm going to see if I can measure how long it takes for the issue to occur, and see if that gives me any insight.

Thanks for your help!

Hi Rik

I'll give that a shot, and see how it goes.

I set up a small python script to poll the page that was generating the error.. and since running that, the error did not reappear overnight (as I have come to expect it to)... go figure?

The site is presently in development, and as such, we haven't scheduled cron - so it runs on the first user's visit using Drupal's automated cron.

Thanks for the suggestion - I'll disable the "404 check" script I wrote, apply your suggestions, and let you know.

Tim

Hi Rik

about 3.5 hours later, the problem re-surfaced. That was with session cache API using a small file, and without frequent harassment by my 404 checking script.

The session file is still there, and dated from earlier this morning from shortly after my response to you (9:28 AM or thereabouts). It's contents "look right" - it has the machine name and value of the taxonomy term I have been filtering on.

I'm going to try to move this site over to another (non-IIS) web server to see if there's anything with that...

Hi

Well, I'm keenly interested in having the module work :) When the system is behaving, it perfectly solves a need that we have. When it stops working, it's very odd!

None of the displays in the view in question have caching turned on.

I've still been experimenting with the timing of the thing. I ran the 404 checking script overnight, but at a 2 hour interval, and the issue did not re-appear overnight.. the site was working just fine in the morning.

So, I turned that off, and let it sit for more than 2 hours, and sure enough, there's the issue again. Hypothesizing that cron runs every 3 hours (by default in a drupal 7 install), that on the occasion that when I access the site, and cron runs, the error appears.

Though.. I would expect that this would be the case with installs of this module on other sites.. and as you point out, that's not the case.

I've since turned cron off on the site, and am letting it sit .. I'll ratchet up the time an hour at a time and see if I can get it to occur with the automatic cron off.

I admit .. I'm flipping switches to see what happens.

I didn't have time to bring the site over to another server to see if that solves the issue.. hoping to do that before I leave today so it has time to timeout over the weekend.

Thanks again for your continued help :)

Tim

Yeah, that's what I was trying to test.

I'm considering turning on crontab on an hourly basis, call it from Nagios, and see if the issue goes away. I'd like to find out what the problem is.. but it's getting to be rather time consuming :-/

I think I'm leaning toward it being an IIS issue, to be honest. I copied the site to a Linux VM, and let it sit over the weekend. Monday morning, the IIS site is 404ing, and the Apache site is not.

Either that, or it's a PHP version. Linux is 5.4.39, and IIS is 5.4.14.. so I'll upgrade PHP on the Windows server, and see if anything changes.

Hmmm, so same versions of PHP, the site on IIS generates the error after 3ish hours, while the site on Apache does not.

I will admit - I wasn't all that careful about ensuring identical configurations between platforms, so it stands to reason that there might be an issue there.

It's making me lean more towards some sort of weirdness in IIS, rather than Drupal or PHP.

In any case, I'm going to add the site's cron URL to Nagios, and see if that makes the issue not reappear.

Thanks again,

Tim