Getting Database Error Mails Despite of Applying Patch

I see. The contents of the file looks like a legitimate file generated by vB (it stores only timestamp and error number - all digits).

What Oleg is trying to say is that the dat file showed up because of the email alerts queuing up. When you get 1000 requests a minuet on a site, the email can't run that fast so it back-logs it to the file per the vb instructions.
It is correct that the timestamps match up, as when the rogue plugin ran, that's when all the db errors would start to flood the mail queue.

The file can safely be deleted.

Originally Posted by Brian Cummiskey

What Oleg is trying to say is that the dat file showed up because of the email alerts queuing up. When you get 1000 requests a minuet on a site, the email can't run that fast so it back-logs it to the file per the vb instructions.
It is correct that the timestamps match up, as when the rogue plugin ran, that's when all the db errors would start to flood the mail queue.

The file can safely be deleted.

That makes more sense, thanks for explaining it that way however shouldn't I see something in the mailqueue table? I would assume so.

Well regardless I have not had time to look into this thoroughly but will do so tonight in my spare time... I get what your saying Brain 100% but I want to know more about this myself including the entire code if there's more than just that shown in the thread.

Thanks for the replies you two sorry I invaded the thread as well OP .

Assuming vb coded it this way (i'm not sure, but it's the logical answer) when there's a DB issue, it can't save stuff to the db possibly (ie, connection problems) so they chose to use a flat file instead of use the mailqueue db table.

Hello!

Hello


1. Runing VBSEO 3.6
2. Patched the abstract file as mentioned on the Announcement
3. Ran the checkplugins2 file (nothing has shown up)
4. Repaired datastore template


result:
I am still getting 61 emails per minute with the invalid SQL warning:


Database error in vBulletin 3.8.2:


Invalid SQL:
SELECT * FROM datastore WHERE title='pluginlist';


MySQL Error :
Error Number :
Request Date : Thursday, January 26th 2012 @ 02:38:14 AM
Error Date : Thursday, January 26th 2012 @ 02:38:14 AM

After you run the checkplugins2 , make sure you click on the 'repair datastore' link.

Originally Posted by Brian Cummiskey

After you run the checkplugins2 , make sure you click on the 'repair datastore' link.

Brian, I don't have that link, as it does not detect anything, this is the result:

vBSEO - Check vB instance for suspicious plugins

Checking datastore pluginslist: OK

---

Checking plugins code

---

Done.

Originally Posted by Brian Cummiskey

After you run the checkplugins2 , make sure you click on the 'repair datastore' link.

Brian, I don't have that link, as it does not detect anything, this is the result:

vBSEO - Check vB instance for suspicious plugins

Checking datastore pluginslist: OK

---

Checking plugins code

---

Done.

run version 2 of the script.

Originally Posted by Brian Cummiskey

run version 2 of the script.

I've ran the 2 versions with the same result.

Originally Posted by faculty

I've ran the 2 versions with the same result.

Hey faculty, give this a try and let the community know if it helped

Database error invalid SQL select