The virtual appliance has been running for two weeks continuously. We’re cautiously optimistic - so far, so good. A couple of points to mention, things to watch out for:
VMWare/Virtual Appliances do not run as a Windows service – so when I kill my Windows console session, the virtual appliance dies, too. I’m leaving the console logged in and have Windows Terminal Services configured to leave the connection alive after I close out. In our organization, this isn’t a problem but in others where you have your terminal services configured to kill idle connections after a period of time, this could be a problem.
Nagios Tuning – I’ll be going back in to tighten our warning system in response to Nagios whining when our ISP gets saturated. If the VPN link between our app dev and data center locations becomes saturated because we’re downloading a large file, I can count on Nagios to send at least one ping complaining about ping response or a single dropped packet. We’re not that concerned about a saturated line yet – I’d prefer only to know when there’s a real problem.
Nagios doesn’t update changes you make to its configuration immediately – you have to commit your changes made through Monarch first, then kill all Nagios processes using ps –ef | grep nagios and then kill (process numbers). Recommitting your changes in Monarch (which doesn’t die when you kill Nagios) immediately starts the Nagios processes again and then your changes are visible. Monarch contains a handy backup tool to back up whatever config changes you make – never, ever forget to back up.
Although I spent a longer amount of time than I would have expected getting Exim4 and Sendmail configured, this did give me an opportunity to become more experienced with Linux and that is always a good thing.
No comments:
Post a Comment