vBulletin Database Error
 

Alright, for the past hour or so, my site has been spitting out Database Errors. Now, the problem is, i don't know how to fix this because the email that is used for sending the DB Error logs isn't receiving the emails.

So now, i'm stuck with a non working website and confused members. Any suggestions guys?

Thanks in advance.

EDIT: Just to let you know, the most recent site/server change was to the "php.ini" file to increase the Maximum Memory Limit. No other changes have been made recently.

Can't help ya if we don't know the Database Error you are getting.

I understand that but I'm trying to find out what's wrong with the site myself but i'm not getting the emails and was wondering if there's another way to find out the cause.

Thanks though.

How did you edit this file? As in, what program was used?

Look in your error logs on your server.

Notepad++ was used.

Just as I'd assumed.

Notepad sometimes adds characters at the top or the bottom of these files, that you cannot see but WILL mess things up. If you have this file still in your vB packet, upload it to your server, to overwrite back to default. If not, must edit files with something like TextEdit, which is a free utility. You will see the added characters using TextEdit that you won't see using notepad.

Notepad is NOT for editing executable files or scripts.

Edit to add: I am not assuming the php.ini file is your problem, I am merely trying to eliminate it as a suspect.

Ah i get you. Thanks for that.

One thing though, TextEdit doesn't appear to be for Ubuntu or for Windows (My Operating Systems). Can you suggest an alternative please?

I use TextEdit with windowsXP no problem and it also integrates with my FileZilla FTP..

The first thing I would do though, were I you, is save a copy of your php.ini file as it is, then upload the stock one to overwrite on your server and see if this database error problem goes away. Then you can solve the mystery of file editing at a later time.

Let's see if your edits to this file are indeed causing the errors.

Yeah, I figured it out. I was looking at the TextEdit that comes bundled with OSXM my mistake.

I tried what you suggested and then rebooted my server but still no joy.