Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

dbsrv6 eats all CPU

Hello,

We seem to have a problem with RME3.3 on Solaris 8. The ConfigPurge takes over 30 hours to complete and during this time the corresponding dbsrv6 process makes the CPU run on 100% utilization constantly.

The system manages about 800 Cisco devices, so this should not be the problem.

Has anybody seen this problem before?

Thank you very much for your response!

Kind regards,

Friso Trines

Telindus

The Netherlands

1 REPLY
New Member

Re: dbsrv6 eats all CPU

Hi,Friso

You are probably running into CSCdv82740.

Please have a look into the bug tool kit to the

description of the problem :

http://www.cisco.com/kobayashi/bugs/bugs.html

To Avoid ChangeAudit CPU HOG.

Please do the following.

1. The ChangeAudit process will start collecting

the config from devices if it receives syslog

messages, notifying changes in config. The number

of such syslog messages may he high and frequently

coming in, so the ChangeAudit will be busy

collecting config, If this is the case, uncheck the

option "Listen to Syslog messages" it appears under

RME--)Adm--)ConfigurationManagement--)GeneralSetup

--)ChangeProbeSetup and see the results.

2. Check the schedule of "ConfigRetrieval" process

and "SNMP Poller" processes ( RME--)Adm--)

ConfigurationManagement--)GeneralSetup--)

ChangeProbeSetup), if these processes are running

very frequently then schedule it to run once in week

or so . This may reduce CPU HOGS.

3. When config's for the devices are fetched, if we

do not give correct credentials, config collection

wouldn't have happened, so every time you restart

the ChangeAudit process it will try to fetch config's

for the devices.

Verify the device credentials using Admn--)

Inventory--)CheckDeviceAttributes

and give the correct credentials for devices which have wrong values entered for it.

Best Regards,

Joseph Melrose

94
Views
1
Helpful
1
Replies
CreatePlease to create content