You may want to make sure your script is not using a user in the Administrator group, so that if for some reason you want to put a server in Admin Only mode, your script would return a failure and have the loadbalancer remove the server from the load balanced group if you set admin only mode to on, something I wish we had done at our installation.
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Friday, February 10, 2012 10:02 AM To: arslist@ARSLIST.ORG Subject: Re: Server 'Alive' check ** Well...in my situation, I have a Server Group...so the effort that I'm working on is to make my Load Balancer 'smarter' so that I can take a node out of rotation if it's not working, so this particular approach wouldn't quite work for me, but I agree that in a 'manual' manner, it seems to be a reasonable scenario :) From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of strauss Sent: Thursday, February 09, 2012 3:28 PM To: arslist@ARSLIST.ORG Subject: Re: Server 'Alive' check ** I am usually satisfied with watching the AR System Email Messages form from the User Tool - I keep an open session on a work desktop that refreshes an open query for Send Message = "Yes" every 5 minutes, and another open query for Message Type = "Outgoing" where I can refresh to see all outbound traffic. If I remote in to look at it and see a miscellaneous tli error dialog, SOMETHING blocked the connection, at least momentarily, and I start troubleshooting from there by clearing the dialog. A method that requires even less effort is that I also have a folder in my mailbox that gets copies of notifications to the central Helpdesk, where I am an Associate Member. If there is recent traffic (unread mail in that folder), there isn't a problem. Basically, if people are entering tickets via one of the mid-tiers or Kinetic Request, and notifications (or escalations) are going out, it's working. A corollary benefit of this is that I see outage notifications and maintain an awareness of what kinds of tickets are being entered by both support staff and customers. That may not be what you are looking for, but it works for us. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Thursday, February 09, 2012 4:12 PM To: arslist@ARSLIST.ORG Subject: Server 'Alive' check ** Listers, As we have discussed several times in the past a simple 'port check' isn't sufficient to tell you that your server is 'alive'. I'm looking for assistance with 'what do you check' when you are checking to see if your remedy server is alive and healthy. I'm not looking to check the MidTier in this effort...just the Remedy server itself. So far I have my script performing the following actions - Login - Search User Form - Execute Service The first of course ensures that the server is processing logins The second asks the remedy server to connect to the DB and return results The third 'exercises' it just a bit, asking it to do some things that one of our services does, and return a result These are of course just a small sampling of things I can have my script do...I was looking to the list to see if you have any 'oh yea, that's a good check' type of things that you typically do when embarking on this type of effort. _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
