10-10-2008 04:09 AM
I remember that I met similar problem before on my development computer, but I cannot reproduce it in a certain way.
Do you install DSC besides Lookout in the system? If you just installed the Lookout in a clean OS and run the process for a while, then you saw the problem, I'd like first to reproduce it with a clean machine if possible. Are there a lot of alarms generated by Lookout server? What's the database size? How many traces and how often is the data logged?
A simple server-client process with data logging and viewing doesn't have this problem. I will try to make more alarms and log more data.
I'm not sure if the problem is related to the OS.
11-09-2008 12:34 AM
Hi Ryan,
I'm sorry but I've had zero time to isolate this issue so far. I do know that the 2 systems affected are running clean installs of 6.2 beta with no DSC. Luckily, the network goes down very infrequently. I would like to know if you have any more info on this yet because I would like to expand 6.2 to more critical apps but am hesitant do to this problem.
Ed
11-11-2008 03:43 AM
Fortunately I reproduced the crash on my computer recently. I don't know whether the problem is only in Citadel 5.6(lookout 6.2), or it has been there for a while.
I notice that the problem is related to a certain database on my computer. After I detach the database, it will not crash. Good news is we can now reproduce the crash by a database. But we need some time to fix it.
One option for you is try to archive the current database into a new one. I archive the problem database on my computer to a new database, and detach the problem one, then it will not crash after network disconnected. Sorry for this problem.