rmeng Database connection error

thongams2000 · ‎01-30-2013

I've got an error message here while trying to open the rmeng database -

*** Error ***

Could not connect to database: Database server not found (DBD: login failed)

I am using LMS 3.2 , RME 4.3. Need help on troubleshooting the error.

thongams2000 · ‎01-30-2013

pdshow output :

Process State Pid

******* ***** ***

UPMDbEngine Program started - No mgt msgs received 10836

UPMDbMonitor Running normally 2908

Tomcat Program started - No mgt msgs received 3884

TomcatMonitor Running normally 9952

Apache Program started - No mgt msgs received 632

RMEDbEngine Program started - No mgt msgs received 4720

Proxy Program started - No mgt msgs received 3480

ProcSysBus Program started - No mgt msgs received 6396

OpsxmlDbEngine Program started - No mgt msgs received 10084

OpsXMLRuntime Program started - No mgt msgs received 6612

CWAPublisher Administrator has shut down this server 0

NameServer Program started - No mgt msgs received 12144

NameServiceMonitor Running normally 8768

EDS Running normally 5692

LicenseServer Program started - No mgt msgs received 9444

ESS Program started - No mgt msgs received 11288

EssMonitor Running normally 9588

EventFramework Program started - No mgt msgs received 6044

SyslogCollector Program started - No mgt msgs received 4912

diskWatcher Running normally 5260

DCRDevicePoll Never started 0

CSSCPServer Program started - No mgt msgs received 6220

CSRegistryServer Running normally 10716

CSDiscovery Never started 0

CmfDbEngine Program started - No mgt msgs received 7404

CmfDbMonitor Running normally 11192

DCRServer Running normally 7708

CMFOGSServer Program started - No mgt msgs received 10960

EssentialsDM Waiting to initialize. 7104

ConfigMgmtServer Administrator has shut down this server 0

ICServer Administrator has shut down this server 0

RMEOGSServer Administrator has shut down this server 0

PMCOGSServer Administrator has shut down this server 0

UPMProcess Running normally 6136

EDS-GCF Running normally 11912

jrm Running normally 10940

1008 Never started 0

2227 Never started 0

2228 Never started 0

2623 Never started 0

2640 Never started 0

2647 Never started 0

2648 Never started 0

2765 Never started 0

2971 Never started 0

3210 Never started 0

3459 Never started 0

3844 Never started 0

3845 Never started 0

3965 Never started 0

4412 Never started 0

4644 Never started 0

4913 Never started 0

4915 Never started 0

4920 Never started 0

4951 Never started 0

4961 Never started 0

4968 Never started 0

4973 Never started 0

4998 Never started 0

4999 Never started 0

5023 Never started 0

5024 Never started 0

5040 Never started 0

5056 Never started 0

5057 Never started 0

5074 Never started 0

5092 Never started 0

5116 Never started 0

5140 Never started 0

5159 Never started 0

CTMJrmServer Administrator has shut down this server 0

ChangeAudit Administrator has shut down this server 0

SyslogAnalyzer Administrator has shut down this server 0

2596 Program started - No mgt msgs received 7064

Vinod Arya · ‎01-31-2013

Not sure what you are trying , when you say trying to open RME DB. Are you trying to connect to RME DB via ODBC?

Please confirm or if this error is seen somwhere esle?

I would like to suggest you as first thing to upgrade to LMS 3.2.1 once this issue is resolved?

Are you on win/sol? I see you processes down as :

CTMJrmServer Administrator has shut down this server 0

ChangeAudit Administrator has shut down this server 0

SyslogAnalyzer Administrator has shut down this server 0

ConfigMgmtServer Administrator has shut down this server 0

ICServer Administrator has shut down this server 0

RMEOGSServer Administrator has shut down this server 0

PMCOGSServer Administrator has shut down this server 0

EssentialsDM Waiting to initialize. 7104

If you have a windows machine and you have Windows Remote Management service running, it may be an issue as it takes the same port some RME services need.

You can try to disbale it and restart Deamon manager, it should work. if that service needs to run, you have to follow this procedure :

> shutdown the daemon Manager (net stop ccrmdmgtd)

> remove ctmregistry* from NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/lib

> start the daemon Manager (net start crmdmgtd)

-Thanks

-Thanks Vinod **Rating Encourages contributors, and its really free. **

thongams2000 · ‎01-31-2013

Hi Vinod,

Thanks for the reply..

I am trying to login the rmeng database using -

https://MYSERVER/dbreader/dbreader.html

I have a windows 2008 server and I access it using RDP. It would be very helpful if you can tell me how to check the

Windows Remote Management service ports and the RME service ports.

Basically the issue is with RME Database. The RMEDbEngine is shutting down automatically very frequently and due to which other dependent proccesses also showing shut down in the above output. I found that the size of Syslog databases - SyslogSecond.db, SyslogThird.db are very big and consuming a lot of space. So I was finding a way to check the database tables.

Regards.

Vinod Arya · ‎01-31-2013

Basically ports acquired by processes can be seen by any free utility like cports or currports. They display the list of all currently opened TCP/IP and UDP ports on your local computer.

However that is not important. If you simply follow the process mentioned above of deleting ctmregistry* files from directory and restart daemon manager it should be fine.

Than you can check pdshow -brief to see all processes come up.

-Thanks Vinod **Rating Encourages contributors, and its really free. **

Vinod Arya · ‎01-31-2013

For syslog.db issue you may have to delete many tables from DB access. We usually dont recommend to access DB and do anything with that.

However there are other mechanisms where you could try to perform the following Administrative tasks:

•Back up Syslog messages (see Setting the Backup Policy).

•Purge Syslog messages (see Setting the Purge Policy).

•Perform a Forced Purge (see Performing a Forced Purge).

However if purging all data from syslog is an option, and start all over for syslog only, you can use the following perl utility to purge all syslog data from syslog*.db and reclaim space with default size.

NMSROOTMDC\tomcat\webapps\rme\WEB-INF\debugtools\dbcleanup\DBSpaceReclaimer.pl.

-Thanks

-Thanks Vinod **Rating Encourages contributors, and its really free. **

thongams2000 · ‎01-31-2013

Hi,

I tried deleting ctmregistry* files following the same procedure as given by you but the RMEDbEngine shuts down again after sometime and now I can see the following three files again in the NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/lib

ctmregistry

ctmregistry.backup

ctmregistry_1359642613752_0.40037950228351094

I am also not able to run a force purge, getting the following error message :

SLCA0117: Syslog Force purge Job Creation Failed. Check the log for details.

Regards.

Vinod Arya · ‎02-01-2013

Please share the latest pdshow -brief from server and try pdexec EssentialsDM and share EssentialsDM.log.

-thanks

-Thanks Vinod **Rating Encourages contributors, and its really free. **

thongams2000 · ‎02-01-2013

Hi,

I think the EssentialsDM is down because the RMEDbEngine went down. I tried restarting both. It will run for sometime and then shuts off again automatically.

pdshow -brief output before the proccess restart :

Process State Pid

******* ***** ***

UPMDbEngine Program started - No mgt msgs received 3836

UPMDbMonitor Running normally 6248

Tomcat Program started - No mgt msgs received 6324

TomcatMonitor Running normally 5852

Apache Program started - No mgt msgs received 6024

RMEDbEngine Administrator has shut down this server 0

Proxy Program started - No mgt msgs received 10088

ProcSysBus Program started - No mgt msgs received 4084

OpsxmlDbEngine Program started - No mgt msgs received 9856

OpsXMLRuntime Program started - No mgt msgs received 2308

CWAPublisher Administrator has shut down this server 0

NameServer Program started - No mgt msgs received 10268

NameServiceMonitor Running normally 11632

EDS Running normally 10108

LicenseServer Program started - No mgt msgs received 6608

ESS Program started - No mgt msgs received 7724

EssMonitor Running normally 7556

EventFramework Program started - No mgt msgs received 2784

SyslogCollector Program started - No mgt msgs received 11036

diskWatcher Running normally 11524

DCRDevicePoll Never started 0

CSSCPServer Program started - No mgt msgs received 948

CSRegistryServer Running normally 6996

CSDiscovery Never started 0

CmfDbEngine Program started - No mgt msgs received 10992

CmfDbMonitor Running normally 7092

DCRServer Running normally 1224

CMFOGSServer Program started - No mgt msgs received 11740

EssentialsDM Administrator has shut down this server 0

ConfigMgmtServer Administrator has shut down this server 0

ICServer Administrator has shut down this server 0

RMEOGSServer Administrator has shut down this server 0

PMCOGSServer Administrator has shut down this server 0

UPMProcess Running normally 12276

EDS-GCF Running normally 10260

jrm Running normally 4148

1008 Never started 0

2227 Never started 0

2228 Never started 0

2623 Never started 0

2640 Never started 0

2647 Never started 0

2648 Never started 0

2765 Never started 0

2971 Never started 0

3210 Never started 0

3459 Never started 0

3844 Never started 0

3845 Never started 0

3965 Never started 0

4412 Never started 0

4644 Never started 0

4913 Never started 0

4915 Never started 0

4920 Never started 0

4951 Never started 0

4961 Never started 0

4968 Never started 0

4973 Never started 0

4998 Never started 0

4999 Never started 0

5023 Never started 0

5024 Never started 0

5040 Never started 0

5056 Never started 0

5057 Never started 0

5074 Never started 0

5092 Never started 0

5116 Never started 0

5140 Never started 0

5159 Never started 0

CTMJrmServer Administrator has shut down this server 0

ChangeAudit Administrator has shut down this server 0

SyslogAnalyzer Administrator has shut down this server 0

2596 Program started - No mgt msgs received 8596

Vinod Arya · ‎02-05-2013

There are a lot of DB related errors which would need various logs to be collected and troubleshooting involving LMS engineering team.

I would recommedn to open a TAC case.

if you are not worried about the data lost from RME Db, you can try to re-initialize the RME DB which, in one issue, i remember fixed the problem, in similar errors we see here.

-Thanks

-Thanks Vinod **Rating Encourages contributors, and its really free. **

Vinod Arya · ‎02-05-2013

Procedure for DB reinitialise and commands :

https://supportforums.cisco.com/docs/DOC-8796

-Thanks

-Thanks Vinod **Rating Encourages contributors, and its really free. **