Upgraded to 4.2.2 now I have a white page for a forum

[DoubleGlasses]

Hi,

I recently ( a few hours ago ) upgraded to 4.2.2 - and I have a white page instead of a forum! I have been going down this list : http://www.vbulletin.com/docs/html/blank_pages

The only thing that stands out is the section about trying to make a new style.

When I got to the step about a style -

https://vborg.vbsupport.ru/external/2013/10/55.png

That's what I see when I try to make a new style with no parent. I'd love any insight - because I'm at a loss for why this is doing this....

Any insights are MORE than welcome!!

That file is the same one that gives me an error when I try to hit the content.php page...
The forum.php page loads but I get an error when I try to view posts... like this :


Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 30720 bytes) in /home/ICHOSETOHIDETHIS/public_html/includes/class_dm_content_read.php on line 121

Just to add : my admin CP works fine.. just no front end pages...

[tbworld]

For education reasons you should google : "php allowed memory size exhausted". This is typically set in your php.ini. file, in-which can be raised if your host gives you access to it.

It can also mean you have a memory leak in one of the MODS you are running.

See ... "memory_limit = `128M"
see ... "ini_set('memory_limit','128M');"

http://php.net/manual/en/ini.core.php

I have seen this occur when users have many styles. Do a little research before you play with these numbers.

[DoubleGlasses]

Hmmm... so I deactivated all of my mods - yet I still get this. I do have a question ( as I'm still reeling from a hacking attack) - When I look at my plugins - I see some like this ( Attached) And I can't help but think that's some malicious stuff too.....

[tbworld]

Forget about the memory size problem. You still need to get your board "clean". It sounds to me as if you still are infiltrated.
Let me know if you have followed the vbulletin guidelines on restoring your board. If not I will send you some references.

Unless you run a "clean" environment you will just keep re-infecting yourself.

Make sure:
Replace vbulletin files.
Replace templates in database.
Disable all Plugins.
Flush Datastore.
Parse all admin accounts.

Follow guidelines ...

Sorry you were hacked.

[meaters]

Horrible.

[DoubleGlasses]

Thanks tbworld - I think you ( or maybe another advisor ) gave me a link to 2 threads with instructions. I've been following those.

Any additional stuff would be helpful - I'm not sure if I saw anything about the datastore or parsing admin accounts.

Also - I've been checking the maintenance thing to find files that don't match - but it's flagging many of the new vbulletin files I just uploaded with 4.2.2 :(

Sorry for inundating you guys with a long list of questions....

Does that list look like non vbulletin files?

[tbworld]

I am guessing you were hacked when you were running v4.2.1? It is easier to get it back running under the same environment only clean.

You might have the files loaded in an incorrect area -- vbulletin would display the error you are receiving.

It looks as if those files should be in the ./include' folder not the './' folder,

--------------- Added 10 Oct 2013 at 15:43 ---------------

If the contents were incorrect being a bad version or malicious code you would have received this warning.

"forum.php File does not contain expected contents"

[DoubleGlasses]

Yep - 4.2.1

Hmmmmm - you know you are right!! When I look I have uploaded them in the wrong folder. I did upload twice because I noticed files missing. Sigh - Perhaps I'm just too sleepy to be fighting this right now....

Any advice for removing the files I put in the wrong place? Rather for identifying them?

Could having these files in the wrong folder be what's causing my issues? Seeing that I still have them with the plugin hooks deactivated?

--------------- Added 1381445862 at 1381445862 ---------------

Oh and if you could point me in the right direction for flushing datastores and parsing admin accounts - I'd be grateful.

[tbworld]

Yep - 4.2.1
Any advice for removing the files I put in the wrong place? Rather for identifying them?

Besides a backup no. You could grab a directory list of the include files and batch delete them from root directory, but it depends on what tools you have at your disposal.

You could do this, but be very careful with this command an incorrect entry can cause you a lot of trouble. Make sure you have a backup.
xargs -I{} sh -c 'rm {}' < 1.txt Could having these files in the wrong folder be what's causing my issues? Seeing that I still have them with the plugin hooks deactivated?
There are some file names that are duplicated in vbulletin. So the easy answer is yes it could.

[DoubleGlasses]

OK - then let me focus on clearing out any duplicates - then I can see if I have the same issue. Sigh - all this effort for a personal project forum!

[tbworld]

Get some sleep, handle the basics... we are around :)

[DoubleGlasses]

Alright - last update before I pass out :

I think I've locked everything down - i've followed the guides I got - but I realize inadvertedly uploading files to the root instead of the includes folder could be causing issues. I went ahead and went line by line to remove anything that didn't belong.

At the moment - If I leave the CMS disabled - the forums work, the blogs don't - and of course the CMS doesn't. I sort of feel like I'm chasing my tail. I'm not convinced that my database has been corrupted or that I have malicious code left....

If I wanted to simply roll back and do a fresh install - how would I go about doing so?

[DoubleGlasses]

I just wanted to do a final update :

tbworld thanks for your help.

1 - I got my forum back up and running
2 - I'm pretty confident that my forum is secure again
3 - After trying over and over to reinstall 4.2.2 - being unsure why I couldn't get the CMS or blogs to work, and then installing a clean version of 4.2.2 on a new environment and getting the same error - I realized it really was a memory allocation issue. Increasing that and restarting apache eliminated all of those issues. I suspect there are some functions in 4.2.2 that require more memory than in the previous version.

So now I'm off to find some good spam protection plugins - and all is well with the world again LOL

[tbworld]

Thanks for updating your progress, it really helps others in a similar situation.

I am glad you are up and running. :)

[ozzy47]

Yeah it is always helpful when members report back their findings. :)