Server Management - Systems Insight Manager
1823278 Members
3056 Online
109648 Solutions
New Discussion юеВ

Re: Email flood

 
John Considine
Occasional Advisor

Email flood

We get alerts from SIM by email but on occassions we get maybe 200+ emails sent from the same server at the same time, how can I stop this as its driving the network manager mad.
6 REPLIES 6
Nick Hromyak
Frequent Advisor

Re: Email flood

Which version of SIM?

IIRC - there was an email flood patch on SIM 4.1 some time ago.

Edwin Walstra
Occasional Advisor

Re: Email flood

I had the same problem a few weeks ago. I've installed SIM all over and placed the SQL database on a different server. That worked for me.

Edwin.
Christian Mentschik
Regular Advisor

Re: Email flood

we have the same problem, before SIM 4.1 with all patches, upgrade to 4.2 and then the big mail flood! we got 1000 of old messeges.

christian
OlivierV
Trusted Contributor

Re: Email flood

Check disk space on the drive where you have your SQL DB. We also had this issue when stopping SQL without previously stopping SIM.
Tim McGue
Regular Advisor

Re: Email flood

We had the same problem. We updated from 4.0 to 4.2. After the upgrade every previous event alerted again through pager/e-mail. I have our server shutdown until I have time to call in for support. I was truly disappointed as this problem first happened in 4.0 and I was surprised they didn't get it fixed for 4.2.

Tim
David Claypool
Honored Contributor

Re: Email flood

I've checked with development and they confirm that the email flood patch was checked in and included with the 4.2 release.

One easy way to determine if there is a new issue with an email flood is to go to one of your email notification tasks in Options --> Events --> Automatic Event Handling --> Manage Tasks and to disable one of them, wait a few minutes and then re-enable it. If it starts firing off emails after being re-enabled, then there is a new problem we'll have to look at.

If you don't get an email flood from that, there is another known issue with 4.2 (see thread http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=762032 for a description) in which the global settings for timeout and retry are being ignored, which can lead to lots of erroneous 'Server unreachable' events. As is mentioned in the thread, the system protocol settings is being checked so you can place your tuning values there as a workaround.