Is there a way to start the Hyperic server 4.1. 1 with the alerts disabled

[hypermike]

I have upgraded, I think successfully from 4.1.0 to 4.1.1 on a my TEST linux ubuntu system after using a fixed db-upgrade.xml file and also running againt the mysql database the commands in db-upgrade.xml for my sql and schema 318 .. The database is from our production system and has about 100 systems that client's are pointing at the production server, NOT this test server. I would like to start up the TEST server to see that it actually upgraded OK and can start.. But Im afraid all the alerts and things will fire and cause mass confusion on the network...(since all the clients and alerts are pointing at a production server. Is there a way to start the Hyperic server 4.1. 1 with the alerts disabled ??? OR any other suggestions.. ?The TEST system is quite small and may get hung with all the activity of a server start up..

[hypermike]

I really need to know how to start up a Hyperic server 4.1.1 without having it send out lots of
alerts ,since the database its using is from a production server that all the clients are pointing at..
This is on a linux VM machine running Ubuntu. Since I'm NOT a linux admin Im NOT sure how to do it from the OS.. Was hoping to do this via editing some Hyperic file or the DB.. ANY HELP would really ne appreciated.
All I want to do is see if the server after upgrading from 4.1.0 to 4.1.1 with this DB was successful.
and will start. so I can upgrade the Hyperic servers client. I cant do that without starting the server
THe upgrade did say it upgraded successfully.

[edan_hyperic]

Perhaps the safest thing to do, since you are using a VM, is to configure your VM to use "private only" networking. That way, your HQ in a VM won't be able to send email, or even contact the production agents. You could just start Firefox in your VM to check it out HQ's web page.

If you are just worried about emails, you could edit server/conf/hq-server.conf and change server.mail.host to a bad value, like "xl2381lxk" so that HQ can't find the SMTP server. But a private network is still the safest option. I'm not exactly sure when HQ decides to contact the agents, so it'd be safest if HQ had no route to do so 🙂

IMHO, you're being awfully careful. I upgraded from 3.2.6 to 4.1.1 and just charged forward 😉 I had to use the patched db-upgrade.xml, but otherwise, life is good 😉

[edan_hyperic]

> I really need to know how to start up a Hyperic
> server 4.1.1 without having it send out lots of
> alerts ,since the database its using is from a
> production server that all the clients are pointing
> at..

For what it's worth, I copied my production HQ database into a test system, copied the product "server-4.1.1" directory to the test system, and booted up HQ. I logged in as soon as I could and went to Administration, HQ Server Settings, and disabled Alerts under Maintenance Properties. ($SERVER_URL/admin/config/Config.do?mode=edit)

It seemed to take it a few minutes to detect that any of the agents were not reporting, so it didn't send out any alerts.

I also set

server.mail.host=mailhost2

in conf/hq-server.conf so that it would fail even if it did try to send an email 🙂 I agree though, it would be nice to know if there was a startup flag or configuration property to disable alerts... I certainly can't see one in the docs.

Cheers!