Lookout 4.5.1 slow

[MEWART]

Over the past several days, Lookout 4.5.1 (build 19) started to run very slow. The PC is running fine, any application I open runs normal. Lookout is running about 1/3 to 1/4 speed. It's not using any processor time, and the drive isn't full. Inputs (external pushbuttons) have to be held 3 - 4 times longer to take affect. The process are running, but are slow also. I tried closing the server / client and open the LKS files, but they run the same way. This PC has been running flawless for 8+ yrs with no monitor, KB, or mouse, so there are no bugs to contend with. Any ideas would be helpful. Thanks, Mark

[Mike@DTSI]

what is the normal cpu and memory usage?

Mike

[MEWART]

8.7MB private memory, CPU usage basicly 0 (1% on occasion)

[Mike@DTSI]

Memory usage for lookout.exe, lkcitdl.exe

CPU Usage seems fine.  I have had issues where the process slow to a crawl when Citadel was loading the database.  Even citadel 5 slows down a bit.

Guess we need Ryan in here 🙂

Mike

[MEWART]

lkcitdl.exe is 1.7MB memory again CPU is basicly 0 (1% occasionaly). I agree it's probably a DB problem, but I can't clear it. I've tied to let Citadel rebuild the DB but no change. I've thought about blowing away Lookout and reinstalling it, but I think there is a better way.

Our problem is we took this PC for granted as it just runs, normaly.

Ryan would be a help, Thanks, mark

[Mike@DTSI]

You have the latest logo installed?  as well as the lookout updates?

http://joule.ni.com/nidu/cds/view/p/id/492/lang/en
http://joule.ni.com/nidu/cds/view/p/id/494/lang/en

Mike

[MEWART]

Logos 4.5. I guess my problem with this is it ran un-interuped, no problems for 8+ yrs. There is no real user intervention to the process other than external triggers from closure contacts. The PC is a RAID arrray and running current service packs under W2K. I suppose one of them could be the problem, but not likly. This just smells like a DB problem and I'm simply not versed in DB management.

[Ryan.S]

If it's the database problem, to create a new one should fix it. If you already did it, it's not the issue.

From your description, the input and output take effect slowly, could it be a communication problem? Which object do you use? Serial? I don't remember if the Lookout 4.5.1 can log the serial communication. If it can, enable the diagnostic file on serial port and maybe we can find something.

Besides the input and output, do you see any other slow behaviour?

[MEWART]

Everything is slow. The I/Os are Fieldpoint 1601 (x4). This morning we found lighting left on by Lookout. It appears to getting worse. I'm going to have to pull a drive and put it into a different PC to see what happens. Basicly is it software or hardware. The PC is running in RAID 1, and although there are no reports of drive problems, I'm starting to think this may be a failed drive and with Lookout's drive activity (logging) the drives can't replicate and this particular Windows app is suffering. I'll let you know.

[MEWART]

Update: Turns out 2 failed drives in a RAID array. Apparently Lookout uses the drives much harder than the basic Windows functions. We moved the applications to a new PC and all is well. Thanks for the help and advice.