Administrative and Maintenance Tools - Suppress-o-Matic - Stop database error spam

What is Suppress-o-matic?
Suppress-o-matic is a change to the way vBulletin handles database error emails. It limits sending the same error email repeatedly to your inbox every time a database error is generated. On a busy site if a table is crashed or mysql itself goes down you could recieve several thousand emails. This causes the email server to bog down, and possibly the server itself if there is enough traffic generating emails.

Why do I want Suppress-o-matic?
It should be pretty clear, you still get the vital information that your vBulletin forum is offline for whichever reason, without the hassle of having to delete and manage your inbox afterwords.

Why do I have to edit the files?
If the database is down, there is no way to get to the plugins. Plugins are stored in the vBulletin database.

Isn't there a vBulletin Option for this?
There is an option to disable some emails, assuming that the settings table can be read. If it cannot then it doesn't work. It even states this on the option itself.

Can't I just remove my tech email from the config file?
This doesn't keep you up to date. What if a serious error like error 28 (no space left) crops up? This means that your server could potentially have serious issues. Not resolving these problems could cause major issues.

Are you considering adding more functionality to Suppress-o-matic?
We have plans to add a repair feature at some point in time, with an on/off switch.

What is SQlite?
SQLite is a tiny database engine that is found in PHP. It is very lite, and requires only that php have the extension. There is no other dedicated server for it. You can find more information here: http://en.wikipedia.org/wiki/SQLite


Whats required?
PHP5
SQLITE2 or newer (found in most php installations)
1 file edit
1 file to upload

Future versions:
Repair table feature



Project Credits:
Zachery - Project Planning, design goals, pestering.
Link14716 - Hard work.

This works for vBulletin 4.0 as well as 3.7+. vB4 thread located here.

[BirdOPrey5]

Originally Posted by ZomgStuff

Anyone try this on 4.0?

The author links to the 4.0 version in his description.

[Zachery]

Originally Posted by ZomgStuff

Anyone try this on 4.0?

https://vborg.vbsupport.ru/showthread.php?t=228146

[psychonikeo]

Installed, but still get tons of mails?

[adwade]

What is "your base vBulletin directory"? Is that the /forums directory that it's referring to, or the one above it /public_html on the server?

[Zachery]

Wherever you have your vBulletin files installed to, if all of the vBulletin files and folders are in the /forum/s directory than that is the correct one.

If you have the product installed and are getting tons of emails, check the permissions on your sqlite database.

[6impy]

I'm having a similar issue as psychonikeo.

sqlitedberrors.sqlite has the right permissions.

I echo'ed out: DIR .'/sqlitedberrors.sqlite' and it has the correct path.

I took a look in the sqlitedberrors.sqlite file and nothing is changing.

SQLite is properly installed because error_log is not spitting out any PHP errors for unrecognized commands.

Is there any way to see what the result/error of a query is?

$sqlitedb->queryExec("INSERT INTO dberrors (time, error, errorcode, ipaddress, script) VALUES (".TIMENOW.", '".sqlite_escape_string($this->error)."', '".$this->errno."', '$ipaddress', '$scriptpath')");

Edit:
Could it be the version of SQLite I'm running?

PDO Driver for SQLite 3.x enabled
PECL Module version (bundled) 1.0.1 $Id: pdo_sqlite.c 272374 2008-12-31 11:17:49Z sebastian $
SQLite Library 3.3.7
---
SQLite support enabled
PECL Module version 2.0-dev $Id: sqlite.c 282740 2009-06-25 00:07:20Z scottmac $
SQLite Library 2.8.17
SQLite Encoding iso8859

[6impy]

I fixed the problem I was having and thought I would share it with others who run into it.

For whatever reason, I needed to put the sqlitedberrors.sqlite file in a subfolder of the forum directory that was chmod'ed to 666 (sqlitedberrors.sqlite also being chmod'ed to 666)

e.g.
/path/to/web/forum/sqlite/sqlitedberrors.sqlite

instead of:
/path/to/web/forum/sqlitedberrors.sqlite

Then I modified the very first line of modified code (below the comments) that goes into /includes/class_core.php from:

if ($sqlitedb = new SQLiteDatabase(DIR .'/sqlitedberrors.sqlite', 0666, $sqliteerror)) {

to (look after the DIR part for the added subfolder)

if ($sqlitedb = new SQLiteDatabase(DIR .'/sqlite/sqlitedberrors.sqlite', 0666, $sqliteerror)) {

It's working perfectly and now I don't get hundreds of text messages when my database goes down.

Cheers,
Drew

[Zachery]

sounds like a permission error on the host OS/PHP more than SQLite.

[6impy]

That could be the case, but I tried changing ownership of the file and giving 777 to it. Nothing seemed to allow an update the content of the sqlite file. It would always spit out a query error on the insert. I even tried writing completely separate sqlite code to test it out. It only worked when I stuck it in a folder that was also writable.

Anyway, it may be of help to someone else...

[adwade]

Originally Posted by BirdOPrey5

I've been lucky enough to not ever need this, but now installed just in case- thanks.

DITTO!