• Anonymous
  • Login
  • Register



OpenLog - Response: OpenLog's use of LSIStackTrace was crashing the server.

Created on Jun 4, 2009
Created by John Smart

Just wanted to document this in case anyone comes searching. No idea why this bit me now vs before, but I'm pretty sure OpenLog was crashing an ND7.0.3 server (that had with multiple custom fixpacks, if that matters).

The server kept crashing unpredictably, but it was running one specific agent every time it crashed.

Strangely, it didn't crash in the same spot on that agent, nor every time. The agent never ran more than once at a time. Not sure if it's related or not, but the agent happens to be using the now-unsupported mqlsx library, too. (Don't ask.)

Setting NoLSIStackTrace to True seems to have solved it. No more crashes.

Even stranger, several other agents in the same database use OpenLog, and none of them have NoLSIStackTrace set to True. It appears specific to this one agent.

Then again, it could all be a red herring! I'm unwilling to ask our administrator to let me change that agent back to see if that crashes the server some more. :-) I'm pretty sure that the LSIStackTrace calls were the culprit, though.

For anyone new to OpenLog: Use it anyway! It saves a lot of time. Just be aware that if a server does go down, try checking the nsd file and change NoLSIStackTrace to True on any agents that may have been involved.








Documents
     
Creation Date
Author
Subject
Mar 13, 2006 John Smart LSI_Info not thread safe
Mar 13, 2006 Julian Robichaux     Response: First I've heard of it
Aug 17, 2006 Leo St-Jacques     Response: More on LSI_Info()
Jun 4, 2009 John Smart     Response: OpenLog's use of LSIStackTrace was crashing the server.
     
In this field you can enter the actual content.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.

Please note that the first time you use the new UI your description is converted from rich text to MIME. You might want to copy and paste the raw plain text from the old UI in the new UI so that you don't loose information.