All of a sudden, after my "friendly" Windows server admin re-booted my LMS 3.2 box (without stopping the daemon!), my Discovery jobs are returning zero devices discovered. Prior to this, I was discovering 135 devices; which is correct for our environment. Tried deleting all the jobs & configuring new ones, but I get the same results. Tried stopping & re-starting the daemon service with no luck. Basically, we use UTT to feed a NAM process which is still showing entries on a daily basis, so I assume the DCR is still functioning; albeit off older network scans. Discovery is just not updating, therefore, I'm missing recent network adds & moves. Jobs are completing as "successful" but only run for 1 or 2 seconds. Anybody ever see anything like this before? Thought I'd try here for a "quick fix" before calling in a TAC case.....
All LMS modules are the latest. Recently updated to CS 3.3.0 and CM 5.2.1. Also updated RME to 4.3.1. Everything ran great after these updates. Box is an HP/Compaq DL360 G4 running Windows Server 2003 R2 64-bit; dual 3gig processors; 8gig RAM; dual mirrored 72.8gig SCSI Ultra 320 drives.
Here's a screen shot of the discovery job report: