Stop vbulletin flood me with error emails.

[Domenico]

Hello,

I just took this text from vb.com:

" Vbulleting FLOODING ME with error emails
I really apreciate the fact that Vbulleting emails error messags to the admin, I SHOULD be aware of any errors that take place.

The problem is when vbulletin generates a separate email for EVERY error that takes place even if they are fractions of a second appart and its the exact same error.

I took down mysql so I could increase the MAX_CONNECTIONS (it was set to 100 and I had something like 200 people wanting to get on).
When I restarted mysql it wouldnt start due to the link libraries not being found, (thats another story with the freaking LD_LIBRARY_PATH). but anywho, it took me around 5 minutes to figure it out and get it all running again...

During those 5 minutes that forum was offline I received 1281 emails generated by vbulleting letting me know it couldnt connect to the local MySQL Server trhough the given socket.

My question: is it possible to limit the ammount of ERROR e-mail vbulleting will send to say 10 emails per hour or something like that? I FEAR the day something goes wrong while I'm out of town or out of reach and it takes me a few hours or even *GASP* a few days to fix a problem... opening up my email to find 8,000,000 error messages"

We have the same error and need a fix asap. We will upgrade to vb3.5 in a few weeks but for now we need this problem fixed.

Thank you!

[Marco van Herwaarden]

Possible yes, but very hard, since the database is down, the time of the last error can not be stored in the database.

[Andreas]

The last time we had a slight problem with the database I got approx. 20.000 eMails :D

[Domenico]

20.000? We got 200.000! :disappointed: :ermm: :tired:

How can we stop vBulletin from sending these useless mysql error messages?

[Marco van Herwaarden]

Simply take out the mail address from config.php

[Domenico]

Simply take out the mail address from config.php

Hmm, this sounds to simple to be true. :)

[Andreas]

Or disable eMail sending -> ACP / vBulletin Options / vBulletin Options / Error Handling & Logging

[MRGTB]

20.000? We got 200.000! :disappointed: :ermm: :tired:

How can we stop vBulletin from sending these useless mysql error messages?

LOL, I know what you mean. Man it was the worse type of spam I've ever had. I scared to start outlook express. And I'm on dial-up. I was sat there pulling my hair out. Bald now! :rolleyes:

[Domenico]

LOL, I know what you mean. Man it was the worse type of spam I've ever had. I scared to start outlook express. And I'm on dial-up. I was sat there pulling my hair out. Bald now! :rolleyes:

Man it surely sucks. And when everything was in after a few hours it took me another couple of hours to delete the messages. I'm using pocomail and it surely doesn't handle so many emails that well. You even deleted a couple of 100.000s emails at the same time?

:speechless:

@kirby, still using vB 2.x. We will upgrade to vB3.5 in a few weeks at last including some of your priceless plugins offcourse. ;)

[MRGTB]

what you could have done temp, was ban your your site by right click one of the emails sent and choosing BLOCK,. That would have sent all others and any future ones straight to trash.

Then after just unblock it from the outlook express ban list

[Paul M]

Hmm, this sounds to simple to be true. :)Nope, it's true, I often comment it out when I'm working on the database/server.

Possible yes, but very hard, since the database is down, the time of the last error can not be stored in the database.It's not hard to store it in a file though. I've often thought about doing it, but never bothered.

[Marco van Herwaarden]

What you all have been waiting for is finally released. :D :D

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

[Paul M]

Ah, you decided to bother then, Nice one. :up:

[Marco van Herwaarden]

Well same as you i have been thinking about this before, but never really done it.

But after yesterday i thought, what the heck, it shouldn't take too long to make (ofcourse it did, since i put in more options then i originally planned, just as always happens when i work on something).