CDP Service won't start on Publisher: CUCM 6.1.2

[Giovanni Ceci]

Hey all,

I have a client whose Cisco CDP service will not start on the Publisher. The service is running fine on the Subscriber.

I tried many times to start it from the Control Center - Network Services Page, but it just won't start. When I do attempt to start it, I noticed that it creates Core Dump files in RTMT. I download them but I can't make out what they are (Probably useful for TAC engineers).

When I go to the command line and do a utils service list command, here's what it says for the CDP service:

Cisco CDP[STOPPED]  Component is not running

CUCM version = 6.1.2.1000-13

Any ideas?

Thanks,

Neocec

[Joseph Martini]

If you check from the command line of the publisher and run a "utils core list" do you see any core dump files from when you tried to start the service the last time?  Also if you have the CDP log files it would be helpful to attach them to this thread so we can take a look.

[Giovanni Ceci]

Hey,

So I ran the command and saw the dump files:

admin:utils core list

      Size         Date            Core File Name
=================================================================
  12056 KB   2011-02-15 00:35:31   core.25175.11.cdpd.1297748131
  12056 KB   2011-02-15 00:35:38   core.25221.11.cdpd.1297748138
  12052 KB   2011-02-15 00:35:52   core.25250.11.cdpd.1297748152
  12052 KB   2011-02-15 00:36:03   core.25280.11.cdpd.1297748163
  12052 KB   2011-02-15 00:36:19   core.25345.11.cdpd.1297748179
  12052 KB   2011-02-15 00:36:36   core.25415.11.cdpd.1297748196
  12052 KB   2011-02-15 00:36:53   core.25435.11.cdpd.1297748213
admin:

I then restarted the service just now and it failed again and generated more core dump files. The SDI traces are attached.

Thanks for your help!

Neocec

[Joseph Martini · Accepted solution]

Thanks for the logs I looked over them and the only other time I've seen this was due to a stuck cdpd process that wasn't completely shutdown or started preventing the service from starting up.  If you run this command we might see an instance of the process even though it's not started from the command line of the publisher "show open ports regexp cdp".  The fix is to reboot the publisher to clear out the stuck cdp process.  We haven't been able to reproduce the issue and this is only the second time I've ever seen this so it's unlikely it will return.

[Giovanni Ceci]

So we rebooted Publisher and Subscriber last night (we were also having replication problems) and sure enough the problem is resolved. Thanks for looking into it.

Neocec