Hi,
The error itself stems from the guest cleanup, which Gossamer Forum tries to run only about once / week, in 0.9.6. It has since changed to once per day, which is a more reasonable time limit. Unfortunately, you have such a level of guests that cleaning once / week is too much for a single request - hence the browser timeout. The other problem is that in the time it takes one to do the cleanup, another comes along, and also tries to clean up, and another, and another, .... All of these build up the load quite a bit, and slow each other down so more will build up, etc. Although the delete _should_ be very quick, due to an old implementation flaw in our SQL module, it was executed as several (maybe hundreds, or more, depending on the number of guests hitting your site) SQL deletes instead of just the three that are needed. This was, however, fixed some time ago. I strongly recommend you upgrade to the latest stable version - keep in mind that 0.9.6 was still a beta release.
If, for some reason, you are unable to upgrade, the easiest solution is going to be changing the relevant section of code in admin/GForum.pm. You need to find a line that looks like:
if ($CFG->{last_guest_cleanup} + 7 * 24 * 60 * 60 < time) {
(It was changed in some release since 0.9.6; the current 1.1.7 line looks like: if ($CFG->{last_guest_cleanup} + 24 * 60 * 60 < CORE::time) {
If you change that to:
if ($CFG->{last_guest_cleanup} + 60 < time) {
it ought to fix up the problem.
Although the above should make it go away, I strongly suggest upgrading to 1.1.7. Many modules have been streamlined and optimized to make the last few gforum.cgi releases significantly faster than 0.9.6.
[snip] - I don't really recommend running 0.9.6 under mod_perl - it had some memory leak issues that have since been fixed up.
Jason Rhinelander
Gossamer Threads
jason@gossamer-threads.com
The error itself stems from the guest cleanup, which Gossamer Forum tries to run only about once / week, in 0.9.6. It has since changed to once per day, which is a more reasonable time limit. Unfortunately, you have such a level of guests that cleaning once / week is too much for a single request - hence the browser timeout. The other problem is that in the time it takes one to do the cleanup, another comes along, and also tries to clean up, and another, and another, .... All of these build up the load quite a bit, and slow each other down so more will build up, etc. Although the delete _should_ be very quick, due to an old implementation flaw in our SQL module, it was executed as several (maybe hundreds, or more, depending on the number of guests hitting your site) SQL deletes instead of just the three that are needed. This was, however, fixed some time ago. I strongly recommend you upgrade to the latest stable version - keep in mind that 0.9.6 was still a beta release.
If, for some reason, you are unable to upgrade, the easiest solution is going to be changing the relevant section of code in admin/GForum.pm. You need to find a line that looks like:
if ($CFG->{last_guest_cleanup} + 7 * 24 * 60 * 60 < time) {
(It was changed in some release since 0.9.6; the current 1.1.7 line looks like: if ($CFG->{last_guest_cleanup} + 24 * 60 * 60 < CORE::time) {
If you change that to:
if ($CFG->{last_guest_cleanup} + 60 < time) {
it ought to fix up the problem.
Although the above should make it go away, I strongly suggest upgrading to 1.1.7. Many modules have been streamlined and optimized to make the last few gforum.cgi releases significantly faster than 0.9.6.
[snip] - I don't really recommend running 0.9.6 under mod_perl - it had some memory leak issues that have since been fixed up.
Jason Rhinelander
Gossamer Threads
jason@gossamer-threads.com
