HTTP 500 errors when trying to read or reply to private messages

Tek7@Work

Tek7@Work

CGA President, Tribe of Judah Founder & President
Lloren and I are aware of the HTTP 500 issues with our private messaging (PM) system. We are hoping that upgrading to vBulletin 4.x will resolve. I believe (Lloren, feel free to correct me) that we're hoping to upgrade in the next week.
 
Yup yup. We plan on blowing up the forums to VB4 and moving everyone's cheese.

Prepare for disappointment!! :)

Actually it's going to be pretty nice.
 
Any update on this Tek and/or Lloren? I still get problems trying to send PMs
 
Delete old pms will help. We are planning to update the software next weekend
 
I deleted messages and refreshed. It looks like it helped - at least it cleared up the new message notification that wouldn't go away.
 
Unfortunately, it looks like the upgrade did not resolve the issues with the private messaging system. :(
 
It's weird. I can get it to go away be rebooting Apache. It looks like a FCGI timeout issue and everytime I up the "IPCCommTimeout" amount it will go away, but it keeps coming back.

Ticket submitted to vBulletin as well.
 
Still having this problem. :(

Seems most prevalent at 25-35 minutes past the hour.
 
Last edited:
I just updated our support ticket with vBulletin. Here's hoping they provide some leads on resolving the issue because it's really slowing me down tonight (and almost every night I try to reply to PMs).
 
I just pruned ~16,000 entries in our Scheduled Tasks Log table, which included entries dating back to 2005.

Here's hoping that fixed the issue.

But if you encounter the same HTTP 500 timeout issue when sending or trying to read private messages, please post a reply!
 
Just manually ran all enabled Scheduled Tasks and only one timed out: Hourly Cleanup #2. The script runs at 0:20 past the hour, which would line up with the timing for PM system issues.

The investigation continues!

EDIT: This vBulletin support thread may prove useful, even though the issue was reported on vB 3.8.4.
 
Last edited:
Running the Repair/Optimize tool on all table ran just fine until it ran into vb_3glowhostspamomatic_log. Now it's stalled and it looks like it'll throw a HTTP 500 error and time out.

EDIT: I unchecked the Glowhost Spam-O-Matic tables before running the Repair/Optimize and the task still throws a HTTP 500 error, just at a different point:

Code: 
vb_3groupmessage	Optimize	Status: Table is alre
OK

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Apache/2.2.3 (CentOS) Server at www.cgalliance.org Port 80
 
Last edited:
So do we have any Linux/CentOS/MySQL/PHP experts in the house that would be willing to work to resolve this issue?

Worst case scenario, we could pay our dedicated hosting provider to investigate and fix it, but I don't know what that would cost.
 
We are in mod_php mode now. We'll see how that goes.

The PM table is causing most of the PM access problems. I"m running some manual cleanup in the database which will take awhile. I'll update when it's done.
 
Last edited:
You must log in or register to reply here.
Back
Top