VMware Cloud Community
satish_lx
Enthusiast
Enthusiast

sfcbd-watchdog cannot be stopped issue

I am trying to restart CIM agent because its not reporting any Hardware Infor ( Dell R730). I tried to do following but get this error.

VMware ESXi version 6.0.x

[root@esxi-01:/var/log] /etc/init.d/sfcbd-watchdog stop

Getting Exclusive access, please wait...

Exclusive access granted.

sfcbd cannot be stopped, please try again.

In syslog.log i am seeing this error:

2016-03-30T15:16:50Z sfcbd-watchdog: stopping sfcbd pid 1559790

2016-03-30T15:16:51Z sfcbd: Stopping sfcbd

2016-03-30T15:16:57Z sfcbd: Stopping sfcbd

2016-03-30T15:17:03Z sfcbd: Stopping sfcbd

2016-03-30T15:17:09Z sfcbd-watchdog: Waited for 3021b743-c2ce-400d-b238-0108ea3ff785 seconds, SIGKILL next for: 1549191 1549191

2016-03-30T15:17:09Z sfcbd: Sending KILL signal to sfcbd

2016-03-30T15:17:15Z sfcbd-watchdog: Waited for 4*5 seconds, SIGKILL next for: 1549191 1549191

2016-03-30T15:17:15Z sfcbd: Sending KILL signal to sfcbd

2016-03-30T15:17:21Z sfcbd-watchdog: Waited for 57680f44-0a8f-43b1-8978-2d2c043fdd85 seconds, SIGKILL next for: 1549191 1549191

2016-03-30T15:17:21Z sfcbd: Sending KILL signal to sfcbd

2016-03-30T15:17:27Z sfcbd-watchdog: Waited for 6c8ca1c0-15ec-4f99-971f-c5d21dbd7465 seconds, SIGKILL next for: 1549191 1549191

2016-03-30T15:17:27Z sfcbd: Sending KILL signal to sfcbd

2016-03-30T15:17:33Z sfcbd-watchdog: Waited for 7*5 seconds, SIGKILL next for: 1549191 1549191

2016-03-30T15:17:33Z sfcbd: Sending KILL signal to sfcbd

2016-03-30T15:17:39Z sfcbd-watchdog: Waited for 8*5 seconds, SIGKILL next for: 1549191 1549191

2016-03-30T15:17:39Z sfcbd: Sending KILL signal to sfcbd

2016-03-30T15:17:45Z sfcbd-watchdog: Waited for 9*5 seconds, SIGKILL next for: 1549191 1549191

2016-03-30T15:17:45Z sfcbd: Sending KILL signal to sfcbd

2016-03-30T15:17:51Z sfcbd-watchdog: Waited for 10*5 seconds, SIGKILL next for: 1549191 1549191

2016-03-30T15:17:52Z sfcbd: Sending KILL signal to sfcbd

2016-03-30T15:17:58Z sfcbd-watchdog: Waited for 11*5 seconds, SIGKILL next for: 1549191 1549191

2016-03-30T15:17:58Z sfcbd: Sending KILL signal to sfcbd

2016-03-30T15:18:04Z sfcbd-watchdog: Waited for 12*5 seconds, SIGKILL next for: 1549191 1549191

2016-03-30T15:18:04Z sfcbd-watchdog: Reached max kill attemtps(12). Watchdog is exiting and 1549191 1549191 are still running.

How do i force restart CIM? can i kill PID?

- If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!! Thanks Satish Patel - Journey toward "Virtual world"
Tags (3)
0 Kudos
5 Replies
satish_lx
Enthusiast
Enthusiast

Anybody...? who can help here?

- If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!! Thanks Satish Patel - Journey toward "Virtual world"
0 Kudos
AdilArif
Enthusiast
Enthusiast

As you said, did you try to kill the PID seen in the syslog?

Cheers, Adil Arif https://in.linkedin.com/pub/adil-arif/5b/a22/30 Blog: http://enterprisedaddy.com
0 Kudos
Das_ruhenheim
Contributor
Contributor

If i may, how did you resolve this issue? I'm having the same problem.

0 Kudos
DBugrimenko
Contributor
Contributor

+1

0 Kudos
Yasamal33
Contributor
Contributor

6x ProLiant BL460c Gen9 (blades)

4 of 6 instances have the same issue

0 Kudos