Brett, I've had the same exact issues. I've had to manually kill the primary SS server process on a number of occasions. When I do this, the FT server finally kicks in and I see the yellow border on that landscape in the OneClick console. But like you say, once the primary goes down, the secondary FT box should kick in, and that is not happening because the secondary FT box still sees the primary as being up. I actually have a ticket open with support about this issue.
By the way, great suggestions Karen. I've done the ctrace and strace before, but never the corbatrace. Calvin [email protected] On Thu, May 7, 2009 at 1:53 PM, <[email protected]> wrote: > > > The first thing that I'd do is add the following line to the .vnmrc file: > > corbatrace=true > > Corba trace events will be displayed in the VNM.OUT file. The trace > information may help you determine what's happening before the SpectroServer > appears to hang. > > You could also add ctrace=true and strace=true to include communication and > system traces too. > > Any changes made to the .vnmrc file take effect when the SpectroServer is > started. > > Karen Kedda > Enterprise Monitoring Solutions > Berkley Technology Services LLC > 405 Silverside Rd., Suite 205 > Wilmington, DE 19809 > 302.746.2113 > [email protected] > > > *Brett Davis <[email protected]>* > > 05/07/2009 12:57 PM Please respond to > Brett Davis <[email protected]> > > To > "spectrum" <[email protected]> cc > Subject > [spectrum] SpectroSERVER hanging after CORBA app is connected for long > periods of time > > > > > We're having a problem when we fire up an application we wrote using the > CORBA API that listens for events. We have a fault-tolerant environment, > but after the CORBA application has been connected to the server and > listening for events for a while, the SpectroSERVER process just seems > to hang and the landscape will show up as being down in OneClick. As you > can imagine, this is extremely annoying since we set up the fault > tolerant environment to avoid these kinds of problems, but since the > SpectroSERVER process is hanging instead of crashing, it seems to still > be responding to heartbeats and the backup never knows to take over. > > Has anybody ever had anything similar happen? We've got approx 2k > devices modeled on this server. Our secondary landscape only has 1k > devices, and it doesn't seem to having this problem, but I didn't think > that 2k devices was even close to the limit for one landscape server. > > Any ideas, suggestions, or past experiences are appreciated > > -- > Brett Davis > IT Network and Security Operations > Purdue University > > > > > > > ************* > CONFIDENTIALITY NOTICE: This e-mail and the transmitted documents contain > private, privileged and confidential information belonging to the sender. > The information therein is solely for the use of the addressee. If your > receipt of this transmission has occurred as the result of an error, please > immediately notify us so we can arrange for the return of the documents. In > such circumstances, you are advised that you may not disclose, copy, > distribute or take any other action in reliance on the information > transmitted. > > - --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]
