We've encountered a problem with a client's site based on SPIP 2.0.5. Sometimes a request for a public page will hang. I've never seen the problem, but others here have. We can solve the problem by deleting everything in /tmp/ via FTP and reloading the page.
Apparently, SPIP encounters a deadlock of some description while regenerating a page. I assume that this has something to do with lock being acquired and not released properly (perhaps after max_execution_time?).
We can't seem to upgrade the site to SPIP 2.0.8 because the upgrade procedure complains about the database schema. We've used Champs Extras 2 to add columns to spip_articles. Could this be the cause of the "can't upgrade" problem?
If this is a known problem which is resolved in a later version, then I'll do the work to upgrade the site. If it's not a known problem, can anyone provide any suggestions about finding the cause and fixing it? At the moment, I'm not even sure what it *is* so it's rather hard to know where to start.
We've encountered a problem with a client's site based on SPIP 2.0.5.
Sometimes a request for a public page will hang. I've never seen the
problem, but others here have. We can solve the problem by deleting
everything in /tmp/ via FTP and reloading the page.
No it's not a known problem, but I have a similar experience on a very
low traffic site I have. Sometimes, when you haven't gone to visit the
site for a long time, you just don't get a page at all. It "breaks"
and gives a white page. Probably the time needed for the database to
reload its tables? I don't know. But reloading makes the page appear.
We've encountered a problem with a client's site based on SPIP 2.0.5.
Sometimes a request for a public page will hang. I've never seen the
problem, but others here have. We can solve the problem by deleting
everything in /tmp/ via FTP and reloading the page.
No it's not a known problem, but I have a similar experience on a very
low traffic site I have. Sometimes, when you haven't gone to visit the
site for a long time, you just don't get a page at all. It "breaks"
and gives a white page. Probably the time needed for the database to
reload its tables? I don't know. But reloading makes the page appear.
That sounds like it might be a different problem.
This is a relatively well visited site (peak of 400, average of 200 visits per day according to SPIP) and it's on the same web and database servers as most of our other sites and they haven't had this problem. When we (or our clients) see this, the request does not complete. The browser just sits there, in progress -- downloading nothing -- forever (or until HTTP time-out).
The client is a retail business and they use the site in their shops to show customers products they don't have on display, so it's something of a problem.
The browser just sits there, in progress -- downloading nothing -- forever
(or until HTTP time-out).
any trace in the (php, spip, apache) logs?
The client is a retail business and they use the site in their shops to show
customers products they don't have on display, so it's something of a
problem.
If the site doesn't work it's a problem, whoever the site owner is.
The browser just sits there, in progress -- downloading nothing -- forever
(or until HTTP time-out).
any trace in the (php, spip, apache) logs?
I have SPIP logs (the entire /tmp/ directory in fact), but no Apache logs. The site is hosted on a shared web-hosting cluster that I don't have direct access to. I'll need to ask the hosting company to set it up.
The client is a retail business and they use the site in their shops to show
customers products they don't have on display, so it's something of a
problem.
If the site doesn't work it's a problem, whoever the site owner is.
I meant that: if it doesn't work on *my* (the browser's) computer, then it might be their problem, my problem, my ISP's problem, etc... But if it doesn't work on *their* (the site owner's) own computers, then it's obviously *their* problem.
I have SPIP logs (the entire /tmp/ directory in fact), but no Apache logs.
The site is hosted on a shared web-hosting cluster that I don't have direct
access to. I'll need to ask the hosting company to set it up.
Not sure the will be usefull, but maybe you'll find that php crashes
for some reason.
