LMS 3.2 CSDiscovery stalled
I am using LMS 3.2 and Device Discovery never finishes. It discoevers the majority of devices and then hangs. The only way to stop it is to run pdterm CSDiscovery from the server command line. I used to have exactly this problem under LMS 3.1 and was advised it was a bug and 3.2 would fix it. Discovery has run ok under 3.2 for 6 months but is no longer working.
Update - Discovery is working when limited to very small subnets. For any number of devices over approx 100 it stalls.
I have turned on debugging for CSDiscovery and am seeing a java OutOfMemory error - see below extract from csdiscovery.log
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : java.lang.OutOfMemoryError: Java heap space
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:144)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at java.io.Writer.write(Writer.java:126)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at org.apache.log4j.helpers.QuietWriter.write(QuietWriter.java:39)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:292)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at org.apache.log4j.WriterAppender.append(WriterAppender.java:150)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at org.apache.log4j.Category.callAppenders(Category.java:187)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at org.apache.log4j.Category.forcedLog(Category.java:372)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at org.apache.log4j.Category.fatal(Category.java:346)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at com.cisco.nm.csdiscovery.adaptor.CSDiscoveryAdaptor.updateOGSGroup(CSDiscoveryAdaptor.java:2054)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at com.cisco.nm.csdiscovery.adaptor.CSDiscoveryAdaptor.updateDevices(CSDiscoveryAdaptor.java:1666)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at com.cisco.nm.csdiscovery.adaptor.CSDiscoveryAdaptor.addDevices(CSDiscoveryAdaptor.java:1637)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at com.cisco.nm.csdiscovery.adaptor.CSDiscoveryAdaptor.putAllProcessed(CSDiscoveryAdaptor.java:759)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at com.cisco.nm.discovery.framework.DiscoveryController.updateProcessedNodes(DiscoveryController.java:688)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at com.cisco.nm.discovery.framework.DiscoveryController.finishDiscovery(DiscoveryController.java:637)
[Jul 14 22:26:03] INFO [LoggingOutputStream : Thread-2 flush] : at com.cisco.nm.discovery.framework.DiscoveryController.run(DiscoveryController.java:1304)
Can I increase the heap size? Where do I go to adjust?
Similar Messages
-
LMS 4.2.2 Fault discovery stalls, never complete
Using LMS 4.2.2 on a network with approx 800 devices. Fault discovery runs for long periods without completion, previously known devices sit in learning state for long long periods. Some devices do become known but this seems random as to which ones. Faults are still reported on devices in a learning state, which means there are often many faults reported which are false. However because devices are in learning state the false positives cannot be weeded out. This problem has been occuring since LMS 4.0 so have not had Fault and event monitoring working properly for some time, however would seriously like to utilise this feature.
Would appreciate any pointers as to where to start... MarkI am having the IP vs. device name issue as well. The funny thing is if you hover over the IP of the device in Fault Monitor, you can see the device name listed. I was on a conference call with Cisco recently and pointed this out. One of the reps said the faults and alerts showing IP address issue should be fixed in version 4.2.3, but I don't know if he was basing this on first-hand knowledge or was just assuming. Does anyone know if this is the case?
As for throttling alerts. I had a false positive alert from a device that I put in a custom fault group and changed the threshold on to keep them from firing. You probably have already resolved this issue, but I didn't see a resolution listed here. You would have to determine if raising a threshold for a device is adequate for your situation.
Thank you,
Mark -
Cisco LMS 4.1 Installation on Windows Server 2008 R2, Databases not created
Hi There,
As always, I am trying to install LMS 4.1 on windows server 2008 R2 and after the installation and login to the LMS I find the following:
DCRServer is down or may not be completely up. Check if the DCRServer process is running.
And after some troubleshooting I found that the LMS is not creating the CMF database and the other databases. Attached is the installation log file, if someone could help me with it would be appreciated. Please note the following:
1. I have downloaded the installation file from Cisco website twice, so I do not think it is the file that is corrupted, also it is only evaluation license.
2. I have met all the prerequisites and requirement as in the documentation guides, but maybe there is something still wrong.
Thanks,Also Here is more info output:
C:\Program Files (x86)\CSCOpx>pdshow -brief
Process State Pid
Tomcat Program started - No mgt msgs received 1572
TomcatMonitor Running normally 2236
Apache Program started - No mgt msgs received 2436
DataPurge Administrator has shut down this server 0
DCRServer Failed to run 0
CMFOGSServer Administrator has shut down this server 0
EssentialsDM Administrator has shut down this server 0
ConfigMgmtServer Never started 0
ConfigUtilityService Never started 0
CTMJrmServer Administrator has shut down this server 0
ChangeAudit Never started 0
SyslogAnalyzer Program started - No mgt msgs received 2976
ICServer Running normally 5096
EnergyWise Never started 0
PMCOGSServer Administrator has shut down this server 0
IPMOGSServer Administrator has shut down this server 0
IPMProcess Never started 0
TISServer Program started - No mgt msgs received 2544
DFMOGSServer Program started - No mgt msgs received 876
InventoryCollector Running normally 3052
Interactor Program started - No mgt msgs received 5136
InventoryCollector1 Program started - No mgt msgs received 5144
Interactor1 Program started - No mgt msgs received 5308
PTMServer Program started - No mgt msgs received 5320
UPMProcess Never started 0
TISDiscoveryJobCreate Administrator has shut down this server 0
SyslogCollector Running normally 5340
Proxy Program started - No mgt msgs received 5348
PMServer Running normally 5360
NameServer Program started - No mgt msgs received 5680
NameServiceMonitor Running normally 5876
LicenseServer Program started - No mgt msgs received 5884
FHPurgeTask Never started 0
EventFramework Program started - No mgt msgs received 5892
EPMServer Program started - No mgt msgs received 5904
FHServer Administrator has shut down this server 0
NOSServer Program started - No mgt msgs received 5580
diskWatcher Running normally 5640
DFMMultiProcLogger Program started - No mgt msgs received 5864
DFMLogServer Program started - No mgt msgs received 4896
DFMCTMStartup Administrator has shut down this server 0
DfmBroker Running normally 6104
DfmServer Running normally 6416
DfmServer1 Running normally 6424
DCRDevicePoll Never started 0
CSRegistryServer Running normally 6432
CSDiscovery Never started 0
AdapterServer1 Program started - No mgt msgs received 6440
AdapterServer Program started - No mgt msgs received 6448
C:\Program Files (x86)\CSCOpx>pdshow DCRServer
Process= DCRServer
State = Failed to run
Pid = 0
RC = -3
Signo = 1073741821
Start = N/A
Stop = 07/02/2012 17:39:06
Core = Not applicable
Info = Application failed or was registered incorrectly.
C:\Program Files (x86)\CSCOpx>net stop crmdmgtd
The Cisco Prime Daemon Manager service is stopping..........................................
The Cisco Prime Daemon Manager service was stopped successfully.
C:\Program Files (x86)\CSCOpx>bin\perl.exe objects\db\conf\configureDb.pl action=validate dsn=cmf
INFO: C:\PROGRA~2\CSCOpx/objects/db/conf/ConfigureDB.LOCK locked for the operation...
ERROR: [StandardDbUpgrade] : Database cmf is not installed.
INFO: C:\PROGRA~2\CSCOpx/objects/db/conf/ConfigureDB.LOCK released for the future operations...
C:\Program Files (x86)\CSCOpx>bin\perl.exe bin\dbpasswd.pl all
ERROR: There is no database available to change password.
C:\Program Files (x86)\CSCOpx>bin\perl.exe bin\dbRestoreOrig.pl dsn=cmf dmprefix=Cmf npwd=pwd
'cmf' is not a valid data source for the product. -
LMS 3.2 discovery process runs for ever
Dear friends,
I am having a problem with discovery on Ciscoworks LMS 3.2. The discovery process runs eternally and does not discover any devices.
Here are the individual device versions:
Name Version Size Status Expiration Date
1. CM 5.2 300 Purchased Never
2. DFM 3.2 300 Purchased Never
3. HUM 1.0 100 Evaluation Sun Jul 26 12:18:01 GMT+03:00 2009
4. IPM 4.2 300 Purchased Never
5. RME 4.3 300 Purchased Never
6. VNM 1.0 Unlimited Purchased Never
Please find enclosed the csdiscovery.log which indicates the following error
1000 [main] DEBUG com.cisco.nm.csdiscovery.CSDiscoveryManager - FATAL: Exception occured in the start discovery Exception occured during start of discovery in CS.
Reason : failed to initialize DiscoveryController
I am also enclosing the CSDiscovery-config.xml under the config directory and the specific job as well.
ngdiscovery.log shows 0 bytes. I am not sure if it is to be populated only when we initiate some debugging?
Thanks a lot
GautamIt seems you're missing some critical files. Under NMSROOT/conf/csdiscovery, you should have the following zip files:
SharedDiscoveryAUS.zipSharedDiscoveryCluster.zipSharedDiscoveryGeneral.zipSharedDiscoveryIGX.zip
The casusers group should have full control on all four files. If these files really are missing, you will need to contact TAC to get new ones, or you will need to reinstall Common Services. -
LMS 3.2 CS Discovery finding "0" devices
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:
Thanks,
RickThe pdshow looks fine and it seems the discovery ran fine today:
Process= CSDiscovery
State = Transient terminated
Pid = 0
RC = 0
Signo = 0
Start = 8/20/2010 12:22:55 PM
Stop = 8/20/2010 12:24:00 PM
Campus Manager Data Collection and the discovery process are separate and should not be mixed up. The discovery log showed this error:
[ Thu Aug 19 13:32:43 CDT 2010 ] FATAL [DiscoveryUtil : isDCRServerRunning] : DCRServer is not running.
This seems accurate comparing with the pdshow:
Process= DCRServer
State = Running normally
Pid = 12136
RC = 0
Signo = 0
Start = 8/19/2010 1:34:04 PM
Stop = Not applicable
Core = Not applicable
Info = DCRServer is up and running
So it seems this last discovery captured on the logs could not run because indeed the DCRServer was down at that time.
Please post a screenshot of Common Services > Device and Credentials > Device Discovery. Do you see 0 devices discovered there? Check under Common Services > Device and Credentials > Device Management, if you expand "All Devices" do you see devices there? -
LMS 4.2.2 virtual appliance fresh install : DCR Server Error
Hello,
I have installed a new version of LMS 4.2 on virtual appliance (VMware 4.1) and I have an issue.
When I go the "Device Administration --> Manage Device State" I have the following error :
Server Error
Error
Error in communicating with DCR Server. For more details click here.
DCR Server may be down. Please start the DCR Server and then refresh the page.
Following the details link I have : (I did all the check written below).
DCR Server Error
The communication error may be due to the following reasons:
The DNS resolution does not match with server assigned IP Address. Workaround: DNS resolvable IP Address should be same as server IP Address. DHCP is enabled in the server. Workaround: DHCP should be disabled in the server. The server’s original IP Address may have changed. Workaround: Restart Cisco Prime Daemon Manager. CTM registry corruption has occurred due to rebooting the server without stopping the Cisco Prime Daemon Manager. Workaround: Delete the ctmregistry and ctmregistry.backup file in NMSROOT/MDC/tomcat/webapps/cwhp/WEB-INF/LIB and then restart the Cisco Prime Daemon Manager. DCR Server and related process might be down. Workaround: Check the processes to make sure DCR Server is running, and restart it if not. The hostname change is not done by the hostnamechange.pl in LMS. Workaround: Hostname change should be done using NMSROOT/bin/hostnamechange.pl in LMS. LMS self signed certificate would have been expired. Workaround: Regenerate the certificate and restart the daemon manager.
I try to reinstall LMS 4.2 with or without patches 4.2.1 and 4.2.2 I always have the same problem. The DCR server process is running.
Here the result of the show application status LMS in SSH :
S-CISCO-LAN-MS/sysadmin# show application status LMS
Process State Pi
d
ESS Program started - No mgt msgs received 27
14
EssMonitor Running normally 29
50
EventFramework Program started - No mgt msgs received 32
95
SyslogCollector Running normally 32
96
RMEDbEngine Program started - No mgt msgs received 32
97
DfmBroker Running normally 34
24
DfmServer Running normally 36
62
DfmServer1 Running normally 36
63
FHDbEngine Program started - No mgt msgs received 36
64
EPMDbEngine Program started - No mgt msgs received 40
81
EPMServer Running normally 42
20
AdapterServer Program started - No mgt msgs received 43
20
AdapterServer1 Program started - No mgt msgs received 43
21
FHServer Running normally 43
22
INVDbEngine Program started - No mgt msgs received 43
23
PMServer Running normally 4582
IpmDbEngine Program started - No mgt msgs received 4708
UPMDbEngine Program started - No mgt msgs received 4840
UPMDbMonitor Running normally 4949
ANIDbEngine Program started - No mgt msgs received 4953
MACUHIC Running normally 4990
UTLITE Running normally 4991
CmfDbEngine Program started - No mgt msgs received 4992
CmfDbMonitor Running normally 5104
DFMLogServer Program started - No mgt msgs received 5106
DFMCTMStartup Administrator has shut down this server 0
FHPurgeTask Never started 0
DFMMultiProcLogger Program started - No mgt msgs received 5108
CSDiscovery Never started 0
DCRDevicePoll Never started 0
CSRegistryServer Running normally 5109
Tomcat Program started - No mgt msgs received 5110
TomcatMonitor Running normally 5206
Apache Running normally 5567
DCRServer Running normally 5580
CMFOGSServer Program started - No mgt msgs received 5641
TISServer Program started - No mgt msgs received 5642
DFMOGSServer Program started - No mgt msgs received 5757
NOSServer Running normally 5795
PTMServer Running normally 5796
InventoryCollector Running normally 5797
Interactor Program started - No mgt msgs received 5885
InventoryCollector1 Program started - No mgt msgs received 5886
Interactor1 Program started - No mgt msgs received 6116
UPMProcess Running normally 6117
WlseUHIC Running normally 6118
UTManager Running normally 6119
VNMServer Program started - No mgt msgs received 6120
EssentialsDM Running normally 6121
ICServer Running normally 6310
EnergyWise Running normally 6581
ConfigMgmtServer Running normally 6582
PMCOGSServer Program started - No mgt msgs received 6583
ConfigUtilityService Running normally 6584
CAAMServer Running normally 6585
IPMOGSServer Program started - No mgt msgs received 6586
TopoServer Program started - No mgt msgs received 6587
LicenseServer Program started - No mgt msgs received 6588
FDRewinder Never started 0
NameServer Program started - No mgt msgs received 6591
NameServiceMonitor Program started - No mgt msgs received 6792
EDS Running normally 6870
ANIServer Running with busy flag set 7224
UTMajorAcquisition Never started 0
EDS-GCF Running normally 7257
jrm Running normally 7258
DataPurge Administrator has shut down this server 0
IPMProcess Program started - No mgt msgs received 7535
CTMJrmServer Administrator has shut down this server 0
SyslogAnalyzer Never started 0
ChangeAudit Never started 0
diskWatcher Running normally 8381
I run out of ideas...
Regards,
AbelHi Afroz!
Thanks for the quick reply!
1) I checked files - and indeed, the third link of the file was empty.
I restored contents of the same test server (as an attachment - original files) - now everything is working fine. Many thanks for your advice!
Because of what could this happen?
Current settings are as follows (i did not change them):
[lms42/root-ade etc]# ls -la /opt/CSCOpx/MDC/tomcat/shared/lib/ctm_config.txt
-rw-r--r-- 1 casuser casusers 1037 Jul 22 13:54 /opt/CSCOpx/MDC/tomcat/shared/lib/ctm_config.txt
[lms42/root-ade etc]# ls -la /opt/CSCOpx/MDC/tomcat/webapps/cwhp/WEB-INF/lib/ctm_config.txt
-rw-r--r-- 1 casuser casusers 1084 Jul 22 13:54 /opt/CSCOpx/MDC/tomcat/webapps/cwhp/WEB-INF/lib/ctm_config.txt
[lms42/root-ade etc]# ls -la /opt/CSCOpx/MDC/tomcat/lib/ctm_config.txt
-rwxr-xr-x 1 casuser casusers 1104 Aug 20 12:07 /opt/CSCOpx/MDC/tomcat/lib/ctm_config.txt
2) It was also noted that if address on the link "Inventory>Device Administration>Discovery>Schedule", then an error message appears:
Error
Error in getting the Discovery configuration information, please configure Standard / Custom Discovery and start the schedule.
- no any records for Discovery Schedule and not accessible button Add (for add new Discovery Jobs).
This is related errors? -
LMS 4.2.2. Standard vs Custom Discovery - Custom not really working ...
Hello Forum,
I did a new install on VM-ware, via LMS4.2.0 OVA file, updated to 4.2.2 and applied latest deviceupdates etc, like MDF and all.
In general it runs good, but, I have a huge problem with CSDiscovery.
My discovery only works in when I choose standard discovery.
Allthough it takes AGES, due to 1000's of Lightwieght AP's hence I need to filter them out.
Only problem with standard discovery is that I cannot get the routers to be managed via Loopback interface, as this option is only configureable in Custom Discovery, also the CDPID Filters for the AP ONLY applies in Custom Discovery, to make Discover faster.
So I need Custom Discovery badly ...
BUT when I run Custom Discovery, with the exact same setting, as in Std Discovery, the discovery skids over seed devices and marks then unreachable !
It like runs way to fast all over the devices !
I then enabled debugging on and looked into ngdiscovery.log in /var/adm/CSCOpx/log
Here I see entries like SNMP timeout on device etc, but this is simply not true, as I can run the same setting when doing std discovery !
I am deeply puzzled - So I copied the backed up system-config.xml file hence restoring the default settings, and restarted LMS.
same problem ... std dis work, cust discovery skids over the seed-devices - ie never gets around to discover anything...
I am so fortunate to have access to a LMS 4.2.1 installation, on OVA too, and I edited the system-config.xml there and added CDPID filtrers for LAP's and ran Cust dis WITH NO PROBLEMS and super fast !
So I know the settings are right in the xml file ...
I can reproduce this in my installation - Std works - Cust runs haywire !
everytime ...
I am actuall surprised that the CDPID filters are NOT aplied to std dis, via the XML file !
Only reads XLM file when doing Cust dis.
This i can also verify in the Job-specific files in /opt/CSCOpx/objects/csdiscovery/JOBID
Are there any bugs related to Custom Discovery vs Std in 4.2.2 ??
I am on the leap to start all over and NOT go to patch 2, staying on 4.2.1 ...
But my time is running and I am on the clock here ...
Please advice, aswell as give you feedback on your experience with cust disc in 4.2.2 on OVA (SoftAppliance)
regrads
MartinHi Karel,
Below are the supprted , windows OS ,please check if you are installing it on one of them.
LMS 4.2 supports the following Windows systems:
•Windows 2008 Standard Edition Release 1 with SP1 and SP2
•Windows 2008 Enterprise Edition Release 1 with SP1 and SP2
Note Only 64-bit Operating Systems is supported on the above versions.
•Windows Server 2008 R2 Standard Edition with SP1
•Windows Server 2008 R2 Enterprise Edition with SP1
Note Only 64-bit Operating Systems are supported on the above versions.
If above is correct then share the Installation.log , it will be under c:/ drive
Thanks-
Afroz
[Do rate the useful post]
****Ratings Encourages Contributors **** -
HI,
I installed the LMS 4.0.1 and I'm facing a problem with DFM. None Fault is showed.
The Fault Discovery Process never finishes, it is always Running, according attached file.
I checked the LMS Process MAnagement and 4 process are as "Transient Terminated". The process are: CSDiscovery, DCRDevicePoll, FHPurgeTask,UTMajorAcquisition. I started all process but 2 minutes later the process goes to "Transient Terminated".
All Windows Services related with CiscoWorks are UP.
Someone knows this issue?
Thanks for your help.
LuisHi duong,
I'm using the ping sweep. not using the "Use DCR as Seed List" as there were more than 5000 devices.
Earliar LMS pick the devices. once the discovery was running for a long time . to stop the same we have restarted
the CSDiscovry process. After this we are facing the issue.
Channa -
LMS 3.2: Running CSCOpx processes
After a Device Package update, I see the following procs left running:
root 8268 1 24 15:39:15 ? 1:11 /opt/CSCOpx/objects/dmgt/dmgtd.sol
root 10304 2006 0 15:51:01 ? 0:00 /opt/CSCOpx/bin/in.tftpd -s /tftpboot
casuser 23883 1 0 Dec 23 ? 0:10 /opt/vgi/csco/CSCOpx/objects/wfengine/program/PolicyScheduler
casuser 23878 1 0 Dec 23 ? 0:05 /opt/vgi/csco/CSCOpx/objects/wfengine/program/DataStore
casuser 23880 1 0 Dec 23 ? 0:12 /opt/vgi/csco/CSCOpx/objects/wfengine/program/GGLogger
casuser 23881 1 0 Dec 23 ? 0:05 /opt/vgi/csco/CSCOpx/objects/wfengine/program/GGProxy
casuser 23889 1 0 Dec 23 ? 0:04 /opt/vgi/csco/CSCOpx/objects/wfengine/program/GGHelper
casuser 23879 1 0 Dec 23 ? 0:06 /opt/vgi/csco/CSCOpx/objects/wfengine/program/GGScript
casuser 23882 1 0 Dec 23 ? 1:25 /opt/vgi/csco/CSCOpx/objects/wfengine/program/OpsBREngine
casuser 11683 1 24 15:59:39 ? 1:32 /opt/vgi/csco/CSCOpx/lib/jre/bin/java -classpath /opt/vgi/csco/CSCOpx/lib/class
I let it stand for 3-5 mins, but didn't see any more procs coming back up, so I manually restarted dmgtd. My question here is: Does it really take that "long" to bring everything but up, or was I not patient enough?
After dmgtd stop, I still see some CSCOpx procs running:
root 10304 2006 0 15:51:01 ? 0:00 /opt/CSCOpx/bin/in.tftpd -s /tftpboot
casuser 23883 1 0 Dec 23 ? 0:10 /opt/vgi/csco/CSCOpx/objects/wfengine/program/PolicyScheduler
casuser 23878 1 0 Dec 23 ? 0:05 /opt/vgi/csco/CSCOpx/objects/wfengine/program/DataStore
casuser 23880 1 0 Dec 23 ? 0:12 /opt/vgi/csco/CSCOpx/objects/wfengine/program/GGLogger
casuser 23881 1 0 Dec 23 ? 0:05 /opt/vgi/csco/CSCOpx/objects/wfengine/program/GGProxy
casuser 23889 1 0 Dec 23 ? 0:04 /opt/vgi/csco/CSCOpx/objects/wfengine/program/GGHelper
casuser 23879 1 0 Dec 23 ? 0:06 /opt/vgi/csco/CSCOpx/objects/wfengine/program/GGScript
casuser 23882 1 0 Dec 23 ? 1:25 /opt/vgi/csco/CSCOpx/objects/wfengine/program/OpsBREngine
casuser 11683 1 25 15:59:39 ? 4:11 /opt/vgi/csco/CSCOpx/lib/jre/bin/java -classpath /opt/vgi/csco/CSCOpx/lib/class
Is that "normal"? I thought in earlier versions there's none left "standing" after stopping dmgtd.I simply let Device Pkg Update install the CiscoView Cat3560 pkg pictured earlier. It's then left unattended. The reason I developed the inclination to manually intervene at all was because I had a similar issue with LMS procs (*OGS* ones) not coming back properly in LMS 3.1 on my production box (alluded to in this thread: https://supportforums.cisco.com/message/2006396#2006396), while LMS 3.2 is currently only on my test box.
Here's the proc status around 5pm yesterday:
1.
1395
Administrator has shut down this server
0
0
0
N/A
Not applicable
2.
ANIDbEngine
Program started - No mgt msgs received
18767
0
0
01/04/10 16:37:53
Not applicable
3.
ANIServer
Running with busy flag set
19377
0
0
01/04/10 16:40:49
Not applicable
4.
CampusOGSServer
Administrator has shut down this server
0
0
0
01/04/10 16:11:30
01/04/10 16:32:15
5.
ChangeAudit
Administrator has shut down this server
0
-113
0
01/04/10 16:11:59
01/04/10 16:31:56
6.
CmfDbEngine
Program started - No mgt msgs received
19381
0
0
01/04/10 16:40:54
Not applicable
7.
CmfDbMonitor
Failed to run
0
0
6
01/04/10 16:11:14
01/04/10 16:40:58
8.
CMFOGSServer
Program started - No mgt msgs received
19460
0
0
01/04/10 16:41:10
Not applicable
9.
ConfigMgmtServer
Administrator has shut down this server
0
-113
0
01/04/10 16:11:39
01/04/10 16:32:05
10.
CSDiscovery
Administrator has shut down this server
0
0
0
N/A
Not applicable
11.
CSRegistryServer
Running normally
18809
0
0
01/04/10 16:38:02
Not applicable
12.
CTMJrmServer
Running normally
19572
0
0
01/04/10 16:41:31
Not applicable
13.
CWAPublisher
Administrator has shut down this server
0
0
0
01/04/10 16:41:50
01/04/10 16:44:38
14.
DCRDevicePoll
Administrator has shut down this server
0
0
0
N/A
Not applicable
15.
DCRServer
Running normally
19400
0
0
01/04/10 16:40:58
Not applicable
16.
diskWatcher
Running normally
19630
0
0
01/04/10 16:41:41
Not applicable
17.
EDS
Running normally
19293
0
0
01/04/10 16:40:22
Not applicable
18.
EDS-GCF
Administrator has shut down this server
0
0
0
01/04/10 16:11:39
01/04/10 16:33:46
19.
ESS
Program started - No mgt msgs received
18673
0
0
01/04/10 16:37:35
Not applicable
20.
EssentialsDM
Running normally
19468
0
0
01/04/10 16:41:15
Not applicable
21.
EssMonitor
Running normally
18677
0
0
01/04/10 16:37:39
Not applicable
22.
EventFramework
Program started - No mgt msgs received
18708
0
0
01/04/10 16:37:45
Not applicable
23.
FDRewinder
Administrator has shut down this server
0
0
0
N/A
Not applicable
24.
ICServer
Administrator has shut down this server
0
0
0
01/04/10 16:11:39
01/04/10 16:32:07
25.
IpmDbEngine
Program started - No mgt msgs received
18727
0
0
01/04/10 16:37:49
Not applicable
26.
IPMOGSServer
Administrator has shut down this server
0
-113
0
01/04/10 16:12:03
01/04/10 16:31:52
27.
IPMProcess
Program started - No mgt msgs received
19595
0
0
01/04/10 16:41:37
Not applicable
28.
jrm
Running normally
19538
0
0
01/04/10 16:41:24
Not applicable
29.
LicenseServer
Program started - No mgt msgs received
19242
0
0
01/04/10 16:40:13
Not applicable
30.
MACUHIC
Running normally
18780
0
0
01/04/10 16:37:57
Not applicable
31.
NameServer
Program started - No mgt msgs received
19246
0
0
01/04/10 16:40:14
Not applicable
32.
NameServiceMonitor
Running normally
19287
0
0
01/04/10 16:40:18
Not applicable
33.
OpsxmlDbEngine
Program started - No mgt msgs received
18796
0
0
01/04/10 16:37:58
Not applicable
34.
OpsXMLRuntime
Program started - No mgt msgs received
19641
0
0
01/04/10 16:41:46
Not applicable
35.
PMCOGSServer
Administrator has shut down this server
0
0
0
01/04/10 16:11:39
01/04/10 16:32:09
36.
ProcSysBus
Program started - No mgt msgs received
19634
0
0
01/04/10 16:41:41
Not applicable
37.
RMEDbEngine
Program started - No mgt msgs received
18713
0
0
01/04/10 16:37:45
Not applicable
38.
RMEOGSServer
Program started - No mgt msgs received
19478
0
0
01/04/10 16:41:19
Not applicable
39.
SyslogAnalyzer
Administrator has shut down this server
0
-113
0
01/04/10 16:11:59
01/04/10 16:31:55
40.
SyslogCollector
Program started - No mgt msgs received
18710
0
0
01/04/10 16:37:45
Not applicable
41.
TomcatMonitor
Running normally
18864
0
0
01/04/10 16:38:07
Not applicable
42.
UTLITE
Running normally
18784
0
0
01/04/10 16:37:58
Not applicable
43.
UTMajorAcquisition
Administrator has shut down this server
0
0
0
N/A
Not applicable
44.
UTManager
Administrator has shut down this server
0
2
0
01/04/10 16:11:39
01/04/10 16:32:04
45.
VNMServer
Program started - No mgt msgs received
18792
0
0
01/04/10 16:37:58
Not applicable
46.
WlseUHIC
Running normally
18788
0
0
01/04/10 16:37:58
Not applicable
Here's the status overnight this morning:
1.
1177
Never started
0
0
0
N/A
Not applicable
2.
1195
Never started
0
0
0
N/A
Not applicable
3.
1293
Never started
0
0
0
N/A
Not applicable
4.
1390
Never started
0
0
0
N/A
Not applicable
5.
1391
Never started
0
0
0
N/A
Not applicable
6.
1393
Never started
0
0
0
N/A
Not applicable
7.
1394
Never started
0
0
0
N/A
Not applicable
8.
1395
Administrator has shut down this server
0
0
0
N/A
Not applicable
9.
1398
Never started
0
0
0
N/A
Not applicable
10.
1399
Never started
0
0
0
N/A
Not applicable
11.
1400
Never started
0
0
0
N/A
Not applicable
12.
1401
Never started
0
0
0
N/A
Not applicable
13.
1402
Never started
0
0
0
N/A
Not applicable
14.
1403
Never started
0
0
0
N/A
Not applicable
15.
1404
Never started
0
0
0
N/A
Not applicable
16.
1405
Never started
0
0
0
N/A
Not applicable
17.
1406
Never started
0
0
0
N/A
Not applicable
18.
1407
Never started
0
0
0
N/A
Not applicable
19.
1408
Never started
0
0
0
N/A
Not applicable
20.
1409
Never started
0
0
0
N/A
Not applicable
21.
1410
Never started
0
0
0
N/A
Not applicable
22.
1562
Never started
0
0
0
N/A
Not applicable
23.
1993
Never started
0
0
0
N/A
Not applicable
24.
1996
Never started
0
0
0
N/A
Not applicable
25.
2034
Never started
0
0
0
N/A
Not applicable
26.
ANIDbEngine
Program started - No mgt msgs received
18767
0
0
01/04/10 16:37:53
Not applicable
27.
ANIServer
Running with busy flag set
19377
0
0
01/04/10 16:40:49
Not applicable
28.
CampusOGSServer
Administrator has shut down this server
0
0
0
01/04/10 16:11:30
01/04/10 16:32:15
29.
ChangeAudit
Administrator has shut down this server
0
-113
0
01/04/10 16:11:59
01/04/10 16:31:56
30.
CmfDbEngine
Program started - No mgt msgs received
19381
0
0
01/04/10 16:40:54
Not applicable
31.
CmfDbMonitor
Failed to run
0
0
6
01/04/10 16:11:14
01/04/10 16:40:58
32.
CMFOGSServer
Program started - No mgt msgs received
19460
0
0
01/04/10 16:41:10
Not applicable
33.
ConfigMgmtServer
Administrator has shut down this server
0
-113
0
01/04/10 16:11:39
01/04/10 16:32:05
34.
CSDiscovery
Administrator has shut down this server
0
0
0
N/A
Not applicable
35.
CSRegistryServer
Running normally
18809
0
0
01/04/10 16:38:02
Not applicable
36.
CTMJrmServer
Running normally
19572
0
0
01/04/10 16:41:31
Not applicable
37.
CWAPublisher
Administrator has shut down this server
0
0
0
01/04/10 16:41:50
01/04/10 16:44:38
38.
DCRDevicePoll
Administrator has shut down this server
0
0
0
N/A
Not applicable
39.
DCRServer
Running normally
19400
0
0
01/04/10 16:40:58
Not applicable
40.
diskWatcher
Running normally
19630
0
0
01/04/10 16:41:41
Not applicable
41.
EDS
Running normally
19293
0
0
01/04/10 16:40:22
Not applicable
42.
EDS-GCF
Administrator has shut down this server
0
0
0
01/04/10 16:11:39
01/04/10 16:33:46
43.
ESS
Program started - No mgt msgs received
18673
0
0
01/04/10 16:37:35
Not applicable
44.
EssentialsDM
Running normally
19468
0
0
01/04/10 16:41:15
Not applicable
45.
EssMonitor
Running normally
18677
0
0
01/04/10 16:37:39
Not applicable
46.
EventFramework
Program started - No mgt msgs received
18708
0
0
01/04/10 16:37:45
Not applicable
47.
FDRewinder
Administrator has shut down this server
0
0
0
N/A
Not applicable
48.
ICServer
Administrator has shut down this server
0
0
0
01/04/10 16:11:39
01/04/10 16:32:07
49.
IpmDbEngine
Program started - No mgt msgs received
18727
0
0
01/04/10 16:37:49
Not applicable
50.
IPMOGSServer
Administrator has shut down this server
0
-113
0
01/04/10 16:12:03
01/04/10 16:31:52
51.
IPMProcess
Program started - No mgt msgs received
19595
0
0
01/04/10 16:41:37
Not applicable
52.
jrm
Running normally
19538
0
0
01/04/10 16:41:24
Not applicable
53.
LicenseServer
Program started - No mgt msgs received
19242
0
0
01/04/10 16: -
LMS Prime: After adding a new Certificate LMS Services not starting
Hello,
we changed the LMS from a self signed certificate to a certificate issued from our corporate ca. Since about 30 services could start anymore. We are using LMS 4.1 on a Soft Appliance.
I verified the certifcate with the SSLUtil and everything looked just fine.
Any ideas?
Affected are following services.
ANIServer
ChangeAudit
CMFOGSServer
ConfigMgmtServer
ConfigUtilityService
CSDiscovery
CTMJrmServer
DCRDevicePoll
DFMOGSServer
EngergyWise
EssentialDM
FDRewinder
FHPurgeTask
ICServer
Interactor
Interactor1
InventoryCollector
InventoryCollector1
IPMOGSServer
IPMProcess
NOSServer
PMCOGSServer
PTMServer
SyslogAnalyser
TISServer
UPMProcess
UTMajorAcquisistion
VNMServer
WiseUHIC
Regards
AlexI enabled debugging for the dcr server and i found in the daemons.log this entries.
In EPMOgsAdapter:EPMOgsadapter is sleeping. Waiting for OGSServer to come up com.cisco.nm.xms.ctm.common.CTMException: URN_NOT_FOUND : ur
n "ogs_server_urn" : Not found !!
27/Sep/2011 17:01:27:152 ERROR ? ? - URN_NOT_FOUND : urn "ogs_server_urn" : Not found !!
27/Sep/2011 17:01:27:152 ERROR ? ? - URN_NOT_FOUND : urn "ogs_server_urn" : Not found !!
27/Sep/2011 17:01:27:152 ERROR ? ? - URN_NOT_FOUND : urn "ogs_server_urn" : Not found !!
In EPMOgsAdapter:since isOGSup is not true
In EPMOgsAdapter:EPMOgsadapter is sleeping. Waiting for OGSServer to come up com.cisco.nm.xms.ctm.common.CTMException: URN_NOT_FOUND : ur
n "ogs_server_urn" : Not found !!
Does anybody knows what the OGSServer is? -
LMS 3.2 Adding Devices Manually
Can anyone tell me if I need a seed devices to add devices manually or can I just bypass this portion of the setup since I'm NOT going to be discovering anything with Ciscoworks.(My envoronment is to complex to perform and discovering) Or do I need a seed device anyhow for functionality of Ciscoworks and other processes?
Please advaise & thank you in advance,
ErickIf you are adding devices manually, there is no need for a seed device. The whole purpose of seed devices is to use it as staging for discovering neighboring devices.
There is a great document written on the CSDiscovery process in LMS by Joe.
https://supportforums.cisco.com/docs/DOC-9005 -
Help with LMS 4.1 device discovery?
Hello,
I'm new to the LMS family and seem to be having an issue with device discovery. The discovery session launches, (I get an email telling me it launched) but the summary page tells me that while the devices are discovered, none of them are reachable.
I've checked the SNMP strings, and they match (and also worked under Whats Up). Is there a specific log I can look at to find out what's going on under the hood of LMS?
Thanks,
Cam WyndIf you go into the processes and click on CSDiscovery then start, it will run the discovery. That's just a work around for now.
-
I go to Device Allocation Settings from the getting started page. and on the left side i get the following message
DCRServer is down or may not be completely up. Check if the DCRServer process is running.
I dont see any service by that name, I tried rebooting, running
C:\Program Files (x86)\CSCOpx\bin>DCR.bat
This is a new installation on a new server windows 2008 R2 STD 64bit
Xeon [email protected]
4GB Ram, virtual set to 8192 min.
HD has 48.7 GB free
No AV on it yet,
I am logged in as administrator local,
Server is in a VM Environment
J.P.My tests on different operationg systems (2003 R2 x86, 2008 R1 x86) led to the same results
Installation log file (2008 R1 x86) attaced. The size of my "lms-4-0-Win-eval.exe" file is 1 964 554 Кbytes.
> pdshow DCRServer
Process= DCRServer
State = Failed to run
Pid = 0
RC = -14
Signo = 1073741810
Start = N/A
Stop = 10/5/2010 2:29:28 PM
Core = Not applicable
Info = Application failed or was registered incorrectly.
> pdshow -brief
Process State Pid
UPMDbEngine Program started - No mgt msgs received 484
UPMDbMonitor Running normally 2328
Tomcat Program started - No mgt msgs received 2348
TomcatMonitor Running normally 2412
Apache Program started - No mgt msgs received 3228
RMEDbEngine Program started - No mgt msgs received 4508
Proxy Program started - No mgt msgs received 4548
NameServer Program started - No mgt msgs received 4556
NameServiceMonitor Running normally 4616
EDS Running normally 4656
LicenseServer Program started - No mgt msgs received 5012
IpmDbEngine Program started - No mgt msgs received 5024
INVDbEngine Program started - No mgt msgs received 5136
FHPurgeTask Never started 0
FHDbEngine Program started - No mgt msgs received 5324
ESS Program started - No mgt msgs received 5380
EssMonitor Running normally 5484
EventFramework Program started - No mgt msgs received 5768
PMServer Running normally 5776
SyslogCollector Running normally 6104
EPMDbEngine Program started - No mgt msgs received 6112
EPMServer Program started - No mgt msgs received 4964
FHServer Running normally 5696
diskWatcher Running normally 5724
DFMMultiProcLogger Program started - No mgt msgs received 5748
DFMLogServer Program started - No mgt msgs received 5744
DFMCTMStartup Administrator has shut down this server 0
DfmBroker Program started - No mgt msgs received 5952
DfmServer Running normally 6200
DfmServer1 Running normally 6208
DCRDevicePoll Never started 0
CSSCPServer Program started - No mgt msgs received 6216
CSRegistryServer Running normally 6224
CSDiscovery Never started 0
CmfDbEngine Program started - No mgt msgs received 6232
CmfDbMonitor Running normally 7164
DCRServer Failed to run 0
CMFOGSServer Never started 0
EssentialsDM Never started 0
ConfigMgmtServer Never started 0
ConfigUtilityService Never started 0
ICServer Never started 0
EnergyWise Never started 0
PMCOGSServer Never started 0
IPMOGSServer Never started 0
TISServer Never started 0
DFMOGSServer Never started 0
InventoryCollector Never started 0
Interactor Never started 0
InventoryCollector1 Never started 0
Interactor1 Never started 0
NOSServer Never started 0
PTMServer Never started 0
UPMProcess Never started 0
EDS-GCF Running normally 7676
jrm Running normally 6572
CTMJrmServer Never started 0
ChangeAudit Never started 0
SyslogAnalyzer Never started 0
DataPurge Administrator has shut down this server 0
IPMProcess Never started 0
ANIDbEngine Program started - No mgt msgs received 7940
ANIServer Never started 0
UTMajorAcquisition Never started 0
MACUHIC Running normally 8148
UTLITE Running normally 8152
UTManager Never started 0
VNMServer Never started 0
WlseUHIC Never started 0
AdapterServer1 Program started - No mgt msgs received 8164
AdapterServer Program started - No mgt msgs received 8172 -
Hello,
A new install of LMS 4.0 is showing the following error(s) in various parts of the UI:
1. JRM server is down or inaccessible for this user (Admin > System)
2. Error in communicating with DCR Server. (Inventory > Add/Import/Manage Devices)
3. Self Test Fail to query ani.DbVersion Error: Invalid user ID or password (DBD: login failed)
Thanks for any and all assistance.Output of pdshow
=================
Process= UPMDbEngine
State = Program started - No mgt msgs received
Pid = 312
RC = 0
Signo = 0
Start = 1/17/2011 2:18:00 PM
Stop = Not applicable
Core = Not applicable
Info = Application started by administrator request.
Process= UPMDbMonitor
State = Running normally
Pid = 132
RC = 0
Signo = 0
Start = 1/17/2011 2:18:04 PM
Stop = Not applicable
Core = Not applicable
Info = DbMonitor Running Normally.
Process= Tomcat
State = Program started - No mgt msgs received
Pid = 196
RC = 0
Signo = 0
Start = 1/17/2011 2:18:08 PM
Stop = Not applicable
Core = Not applicable
Info = Application started by administrator request.
Process= TomcatMonitor
State = Running normally
Pid = 2896
RC = 0
Signo = 0
Start = 1/17/2011 2:18:12 PM
Stop = Not applicable
Core = Not applicable
Info = Tomcat Server up
Process= Apache
State = Program started - No mgt msgs received
Pid = 3904
RC = 0
Signo = 0
Start = 1/17/2011 2:21:42 PM
Stop = Not applicable
Core = Not applicable
Info = Application started by administrator request.
Process= RMEDbEngine
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= Proxy
State = Program started - No mgt msgs received
Pid = 5628
RC = 0
Signo = 0
Start = 1/17/2011 2:25:02 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= NameServer
State = Program started - No mgt msgs received
Pid = 5636
RC = 0
Signo = 0
Start = 1/17/2011 2:25:03 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= NameServiceMonitor
State = Running normally
Pid = 5700
RC = 0
Signo = 0
Start = 1/17/2011 2:25:07 PM
Stop = Not applicable
Core = Not applicable
Info = NameServer is fully up now !
Process= EDS
State = Running normally
Pid = 5740
RC = 0
Signo = 0
Start = 1/17/2011 2:25:11 PM
Stop = Not applicable
Core = Not applicable
Info = Initialization complete
Process= EDS-GCF
State = Running normally
Pid = 6000
RC = 0
Signo = 0
Start = 1/17/2011 2:26:29 PM
Stop = Not applicable
Core = Not applicable
Info = GCF Initialization complete at Mon Jan 17 14:27:29 EST 2011
Process= LicenseServer
State = Program started - No mgt msgs received
Pid = 6008
RC = 0
Signo = 0
Start = 1/17/2011 2:26:29 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= INVDbEngine
State = Program started - No mgt msgs received
Pid = 6016
RC = 0
Signo = 0
Start = 1/17/2011 2:26:31 PM
Stop = Not applicable
Core = Not applicable
Info = Application started by administrator request.
Process= FHPurgeTask
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= FHDbEngine
State = Program started - No mgt msgs received
Pid = 2868
RC = 0
Signo = 0
Start = 1/17/2011 2:26:37 PM
Stop = Not applicable
Core = Not applicable
Info = Application started by administrator request.
Process= ESS
State = Program started - No mgt msgs received
Pid = 1588
RC = 0
Signo = 0
Start = 1/17/2011 2:26:41 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= EssMonitor
State = Running normally
Pid = 2716
RC = 0
Signo = 0
Start = 1/17/2011 2:26:45 PM
Stop = Not applicable
Core = Not applicable
Info = ESS is fully up now !
Process= DCRServer
State = Failed to run
Pid = 0
RC = -3
Signo = 1073741821
Start = N/A
Stop = 1/17/2011 3:30:31 PM
Core = Not applicable
Info = Application failed or was registered incorrectly.
Process= CMFOGSServer
State = Administrator has shut down this server
Pid = 0
RC = 0
Signo = 0
Start = 1/17/2011 2:31:46 PM
Stop = 1/17/2011 3:30:31 PM
Core = Not applicable
Info = Server started by admin request
Process= EssentialsDM
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= ConfigMgmtServer
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= ConfigUtilityService
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= ICServer
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= EnergyWise
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= PMCOGSServer
State = Program started - No mgt msgs received
Pid = 7444
RC = 0
Signo = 0
Start = 1/17/2011 2:31:46 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= IPMOGSServer
State = Administrator has shut down this server
Pid = 0
RC = 0
Signo = 0
Start = 1/17/2011 2:31:46 PM
Stop = 1/17/2011 3:30:31 PM
Core = Not applicable
Info = Server started by admin request
Process= TISServer
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= DFMOGSServer
State = Program started - No mgt msgs received
Pid = 7468
RC = 0
Signo = 0
Start = 1/17/2011 2:31:46 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= InventoryCollector
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= Interactor
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= InventoryCollector1
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= Interactor1
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= PTMServer
State = Program started - No mgt msgs received
Pid = 7652
RC = 0
Signo = 0
Start = 1/17/2011 2:31:50 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= UPMProcess
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= EventFramework
State = Program started - No mgt msgs received
Pid = 7660
RC = 0
Signo = 0
Start = 1/17/2011 2:31:50 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= jrm
State = Administrator has shut down this server
Pid = 0
RC = 1
Signo = 0
Start = 1/17/2011 3:12:10 PM
Stop = 1/17/2011 3:30:31 PM
Core = Not applicable
Info = Server started by admin request
Process= CTMJrmServer
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= ChangeAudit
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= SyslogAnalyzer
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= DataPurge
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= IPMProcess
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= TISDiscoveryJobCreate
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= PMServer
State = Running normally
Pid = 5592
RC = 0
Signo = 0
Start = 1/17/2011 2:40:10 PM
Stop = Not applicable
Core = Not applicable
Info = PMServer is up and running
Process= SyslogCollector
State = Running normally
Pid = 5624
RC = 0
Signo = 0
Start = 1/17/2011 2:40:14 PM
Stop = Not applicable
Core = Not applicable
Info = SyslogCollector Started at Mon Jan 17 14:40:14 EST 2011
Process= EPMDbEngine
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= EPMServer
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= FHServer
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= NOSServer
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= diskWatcher
State = Running normally
Pid = 6612
RC = 0
Signo = 0
Start = 1/17/2011 2:43:34 PM
Stop = Not applicable
Core = Not applicable
Info = diskWatcher initialized OK.
Process= DFMMultiProcLogger
State = Program started - No mgt msgs received
Pid = 6492
RC = 0
Signo = 0
Start = 1/17/2011 2:43:34 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= DFMLogServer
State = Program started - No mgt msgs received
Pid = 7112
RC = 0
Signo = 0
Start = 1/17/2011 2:43:34 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= DFMCTMStartup
State = Administrator has shut down this server
Pid = 0
RC = 0
Signo = 0
Start = 1/17/2011 2:43:34 PM
Stop = 1/17/2011 3:30:31 PM
Core = Not applicable
Info = Server started by admin request
Process= DfmBroker
State = Program started - No mgt msgs received
Pid = 7232
RC = 0
Signo = 0
Start = 1/17/2011 2:43:34 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= DfmServer
State = Running normally
Pid = 7272
RC = 0
Signo = 0
Start = 1/17/2011 2:43:38 PM
Stop = Not applicable
Core = Not applicable
Info = DfmServer initialized OK.
Process= DfmServer1
State = Running normally
Pid = 7300
RC = 0
Signo = 0
Start = 1/17/2011 2:43:38 PM
Stop = Not applicable
Core = Not applicable
Info = DfmServer1 initialized OK.
Process= DCRDevicePoll
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= CSRegistryServer
State = Running normally
Pid = 7304
RC = 0
Signo = 0
Start = 1/17/2011 2:43:38 PM
Stop = Not applicable
Core = Not applicable
Info = CSRegistryServer is running in other process
Process= CSDiscovery
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= ANIDbEngine
State = Program started - No mgt msgs received
Pid = 7312
RC = 0
Signo = 0
Start = 1/17/2011 2:43:40 PM
Stop = Not applicable
Core = Not applicable
Info = Application started by administrator request.
Process= ANIServer
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= UTMajorAcquisition
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= MACUHIC
State = Running normally
Pid = 7836
RC = 0
Signo = 0
Start = 1/17/2011 2:43:44 PM
Stop = Not applicable
Core = Not applicable
Info = Started.
Process= UTLITE
State = Running normally
Pid = 7740
RC = 0
Signo = 0
Start = 1/17/2011 2:43:45 PM
Stop = Not applicable
Core = Not applicable
Info = Started.
Process= UTManager
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= WlseUHIC
State = Never started
Pid = 0
RC = 0
Signo = 0
Start = N/A
Stop = Not applicable
Core = Not applicable
Info = Not applicable,
Process= AdapterServer1
State = Program started - No mgt msgs received
Pid = 7708
RC = 0
Signo = 0
Start = 1/17/2011 2:43:45 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request
Process= AdapterServer
State = Program started - No mgt msgs received
Pid = 7672
RC = 0
Signo = 0
Start = 1/17/2011 2:43:45 PM
Stop = Not applicable
Core = Not applicable
Info = Server started by admin request -
Best Practise - Monitoring LMS 3.2 - System
Hi there,
are there any best practises how to monitor LMS 3.2 system for faulty conditions?
Is it possible to extract problems like Campus DataCollections was not started, RME-Invenory fails for xxx devices, CW2000-process xyx died unexpected ...
Is there any script include in LMS usable for system/application monitoring?
Thanks for your thoughts
Best Regards
LotharThe Daemon Manager itself tries to maintain daemon health. It can detect if a daemon dies, and it will try to restart it.
However, if you want to monitor health on your own, the pdshow command is the way to do it. Most daemons should always be running. In LMS 3.2, you may have a few which can be down in a healthy system:
DFMCTMStartup
DataPurge
CSDiscovery
UTMajorAcquisition
CWAPublisher
DCRDevicePoll
FDRewinder (Solaris only)
(any numbered process like 1001)
Any other daemon should be running.
RME also has the ability to notify you if a job fails. Go to RME > Admin > System Preferences > Collection Failure Notification, and enable notifications when the desired collection fails.
Maybe you are looking for
-
i bought my wife an iPad2 for her birthday and 1 1/2 months later she won another in a raffle, to my delight. but now that we have 2 iPad2s, i'm having trouble sharing my itunes id when trying to setup the find my ipad app (moble me). any ideas how
-
Images in RTF template giving errors
Hi, I am using "XML Publisher Template Builder for Word" ver 5.6 Build 45. My requirement says that i need to put all data values in a Rectangular BOX. I made the template and tested the same by using Priview option of Template Buider, and it looks G
-
Problem with CUPS and Canceling jobs
I am using OS 10.3.9 on a 1.42 MDD PowerMac I am having a problem trying to cancel Jobs using the CUPS interface. When I select "Cancel" I get an error "client-error-forbidden". I have tried logging in as Root but the same error occurs. I have run "C
-
I dont think ill be using windows for much more than revit and autocad (i use autocad on the mac side, but just in case), but i want to make sure I am not going to have a problem in the future. I am a grad student in interior design, and have access
-
Hi, We would like to know if there are any documentation on how to setup manual entries infocubes in BW ? Also how do you get the web report to accept manual entries ? Do you have to do any special programming ?