3.8.4 installation has gone completely down

[wacnstac]

Um, suddenly without any sort of error all I get is a blank page rendered at http://www.michigan-sportsman.com/forum All the source files still seem to be in place..... HELP!

[dodgeboard.com]

Re-upload the files, overwriting the current ones. Make sure you upload the PHP files in ASCII format.

[wacnstac]

It appears that all scripts on the site that utilize SQL are showing blank pages.

[dodgeboard.com]

That's what happens when the PHP files are uploaded in Binary format.

[wacnstac]

Um, none of these files have been uploaded recently. I don't think they all just changed to binary format in the last couple of minutes.

[dodgeboard.com]

Your original post was not clear about this. However, blank pages are normally caused by bad files due to format, corruption or hacking. Unless your files are modified, it wont hurt to re-upload the original vBulletin forum files and overwrite the current ones as a simple troubleshooting step.

[Lynne]

Here is a page from the manual about troubleshooting blank or 'white' pages: http://www.vbulletin.com/docs/html/blank_pages

[wacnstac]

dodgeboard, your answer is very MicroSoftish. My error log shows lots of these:

[23835] EACCELERATOR: PHP crashed on opline 8 of connect() at /home/msports/public_html/forum/includes/class_core.php:269

[dodgeboard.com]

dodgeboard, your answer is very MicroSoftish. My error log shows lots of these:

[23835] EACCELERATOR: PHP crashed on opline 8 of connect() at /home/msports/public_html/forum/includes/class_core.php:269

Must be because I am a MS Tech

Sorry you didn't like my help. I'll step out and let someone else help you

[wacnstac]

Just FYI it appears this happened because The apache suexec_log had grown to 3Gb in size. Might want to add that to the list instead of the standard MicroSoft line "reinstall the software".

[dodgeboard.com]

Note to self: Stop helping the "ungrateful".

[GHOwner]

Just FYI it appears this happened because The apache suexec_log had grown to 3Gb in size. Might want to add that to the list instead of the standard MicroSoft line "reinstall the software".

But in the world of technology, there's many different possibilities for the same error/issue. Sometimes the most generic answer can be the universal solver.

Don't complain about getting help from generous customers.

[Trevor Hannant]

Just FYI it appears this happened because The apache suexec_log had grown to 3Gb in size. Might want to add that to the list instead of the standard MicroSoft line "reinstall the software".

Solves the problems a lot of the time though if you look around...