[Scott Rush]

Thanks everyone!

I did it via a file yesterday.

Epic is good at presenting to upper management before pulling me or any of our techs in so there is no questioning of their solutions when there is high visibility and a gap.

I just do it rather than try and change the direction when it has gotten so far down the rails … and Epic knows it.

I hear ya about some of these Epic kids.

I wonder if their mamas know they are “playing” adult.  😉

The turn over at Epic is astonishing!

Epic doesn’t solve everything.

It is not the end all, be all.

Ha ha  … just had to say that to a forum where people would understand.

[Scott Rush]

No argument here, but Epic can’t prevent this from happening in their system.

I guess moving to Epic did not solve ALL our problems.  😉

(Sarcasm)

[Scott Rush]

I just thought of a way this can be happening without you knowing it.

If you have Global Monitor check your settings.

There is a setting in Global Monitor that will restart the monitor if it notices it is down.

So if you stop it, Global Monitor will start, and then you start, it is running twice.

If you do not have Global Monitor, please disregard.

[Scott Rush]

One of the problems is that hcimonitord does not check to see if it is already running for that process.  If you start it again, it creates the process again.

[Scott Rush]

You may have more than one hcimonitord running for that process.

Do the following.

1. setsite to whatever site is giving you the problem.

2. ps -ef | grep hcimonitord

3. You should only see one hcimonitord for each process in that site.

If you have more that is what is causing the each alerts to fire.

[Scott Rush]

I see the logic in it.

11 and 13.

Thanks Charlie!

[Author]

Replies