Hello, you can add a line to the processd.pl script ($SPECROOT/lib/SDPM) to remove the VNMDB.LOCK file whenever processd is restarted.
Regards Andreas -----Original Message----- From: Sean Carnes [mailto:[email protected]] Sent: Thursday, December 31, 2009 11:18 PM To: spectrum Subject: Re: [spectrum] Spectro Server not restarting There is a way to do this I posted it at the bottom and should work but I just have a question or two and some things to share that I have discovered in our setup. Do you have redundant servers? If so it is one of the reasons that I believe they do not enable this by default. If your ss did go down un-gracefully for whatever reason it may or may not have left the db in a bad/corrupt etc state which could cause other issues when starting up and I have definitely experienced this many times after an un-graceful shut-down. It will then retry up to the limit etc etc. I believe it also is not enabled by default because if you do have redundant servers and it properly failed over to the redundant server the events that are stored locally in that redundant instance would not immediately come back to the primary landscape. Sometimes archive manager needs to be started first, the verification of the secondary's locally stored events being cleared out next and then start the primary SS and verify that it has failed back. This is indicated somewhere in the manuals for a redundant configuration. I am sure there are other reasons in a redundant setup not to do this, I have seen some bugs, in 8.1 but not in 9.1, related to failing back to the primary where without bringing the secondary completely down it will just be in kind of limbo and stops showing new alarms in oneClick. If you do not have a hot/warm redundant configuration and/or do not mind about the possible further failure scenarios in either a standalone or redundant configuration that may result from auto-removing the .vnmdb.lock file then you can create another processd install ticket for a script to delete this file in whatever method you choose (perl, bat, sh, bash, etc) and then set its priority in the ticket to start before the spectroserver process. I haven't done it for this specific purpose but I believe it should do the trick. Let me know if you give it a try. Regards, Sean Sean Carnes C&C Network Operations Center Cablevision Systems Corp. 172*85*77/5163905910 >>> "Murtey, Patrick" <[email protected]> 12/31/09 1:15 PM >>> Hi All, Happy New Years for those of You's still working like myself. I am sure this question has been asked before, but I have already spent an hour searching my email archives and cant find the answer. So here it is again. In the Install tickets / partslist you can set Spectrum to Auto restart, and Start on reboot. But what if the server came down un-gracefully, and a .vnmdb.lock file was created. How do you get the lock file to be removed so that when the server is powered back up the SpectroServer can restart? Just had this happen to me. The Spectro Server lost power, when it came back up the SpectroServer process did not start, even though the autobootstart was set to 'yes' because the .lock file was there. There is nothing mentioned on 2770 guide about this. Thanks Patrick Murtey Network and Systems Management Manager MGM MIRAGE Information Technology [email protected] <mailto:[email protected]> --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] -------------------------------------------------------- The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain Cablevision proprietary information, which is privileged, confidential, or subject to copyright belonging to Cablevision. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof. -------------------------------------------------------- --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
