VMware Cloud Community
NV1
Contributor
Contributor

Constant sfcb-CIMXML-Processor Errors

Hi Folks

We have just upgraded our vSphere Environment to ESXi, 5.0.0, 821926. All 33 hosts are logging the same errors constantly see below:

Nov 20 09:43:32 2012-11-20T00 daemon err 2012-11-20T00:13:32Z host05.host.domain sfcb-CIMXML-Processor[115343]: -#- HTTP header command is not expected

Nov 20 09:36:18 2012-11-20T00 daemon err 2012-11-20T00:06:18Z host05.host.domain sfcb-CIMXML-Processor[115097]: -#- HTTP header command is not expected

Nov 20 08:43:11 2012-11-19T23 daemon err 2012-11-19T23:13:11Z host05.host.domain sfcb-CIMXML-Processor[112592]: -#- HTTP header command is not expected

Nov 20 08:36:12 2012-11-19T23 daemon err 2012-11-19T23:06:12Z host05.host.domain sfcb-CIMXML-Processor[112368]: -#- HTTP header command is not expected

Nov 20 07:42:49 2012-11-19T22 daemon err 2012-11-19T22:12:49Z host05.host.domain sfcb-CIMXML-Processor[109989]: -#- HTTP header command is not expected

Nov 20 07:36:08 2012-11-19T22 daemon err 2012-11-19T22:06:08Z host05.host.domain sfcb-CIMXML-Processor[109749]: -#- HTTP header command is not expected

Nov 20 06:42:27 2012-11-19T21 daemon err 2012-11-19T21:12:27Z host05.host.domain sfcb-CIMXML-Processor[107338]: -#- HTTP header command is not expected

Nov 20 06:36:04 2012-11-19T21 daemon err 2012-11-19T21:06:04Z host05.host.domain sfcb-CIMXML-Processor[107091]: -#- HTTP header command is not expected

We have had a support call open for over a week re: this and VMware have not been able to resolve it. It is a very consistent error so was wondering if anyone else had encountered it and if they have found a resolution. The only way to stop these errors being logged is to stop the CIM service which causes other problems. The hardware is a mix of HP BL490c G6 BL490c G7 and BL620c G7 blades. All are logging the same errors.

We also have 2 IBM x3650 M4 Rack Servers and they are loggin the same error along with another error:

Nov 20 10:25:11 2012-11-20T00 daemon err 2012-11-20T00:55:11Z host01.domain sfcb-vmware_raw[5768]: IpmiIfcFruMulti: record len is equal to zero, not valid.

Nov 20 09:41:34 2012-11-20T00 daemon err 2012-11-20T00:11:34Z host01.domain sfcb-CIMXML-Processor[843491]: -#- HTTP header command is not expected

Nov 20 09:21:09 2012-11-19T23 daemon err 2012-11-19T23:51:09Z host01.domain sfcb-vmware_raw[5768]: IpmiIfcFruMulti: record len is equal to zero, not valid.

Nov 20 09:21:09 2012-11-19T23 daemon err 2012-11-19T23:51:09Z host01.domain sfcb-vmware_raw[5768]: IpmiIfcFruMulti: record len is equal to zero, not valid.

Nov 20 08:41:11 2012-11-19T23 daemon err 2012-11-19T23:11:11Z host01.domain sfcb-CIMXML-Processor[839593]: -#- HTTP header command is not expected

Nov 20 08:17:08 2012-11-19T22 daemon err 2012-11-19T22:47:08Z host01.domain sfcb-vmware_raw[5768]: IpmiIfcFruMulti: record len is equal to zero, not valid.

Nov 20 08:17:08 2012-11-19T22 daemon err 2012-11-19T22:47:08Z host01.domain sfcb-vmware_raw[5768]: IpmiIfcFruMulti: record len is equal to zero, not valid.

Nov 20 07:40:50 2012-11-19T22 daemon err 2012-11-19T22:10:50Z host01.domain sfcb-CIMXML-Processor[835655]: -#- HTTP header command is not expected

Any assistance with this would be much appreciated.

Reply
0 Kudos
5 Replies
Globale
Contributor
Contributor

We have the same error: sfcb-CIMXML-Processor HTTP header command is not expected

Can someone give some more information about the cause?

Reply
0 Kudos
stacycarter
Enthusiast
Enthusiast

I see this too, also on ESXi 4.1 U3 hosts....

Reply
0 Kudos
kimahansen
Contributor
Contributor

I opened a support case with VMware on this. This was the result:

1. Login with ssh or access console.

2 .Edit /etc/sfcb/sfcb.cfg

3. Change logLevel value to 2

4. Save file

5. Then I would restart the server

Alternatively instead of restarting the server, you can restart the service:

/etc/init.d/sfcbd-watchdog restart

For me, this just created a lot of more noise in the logs until i rebooted.

To prevent this noise, Vmware suggested:

/etc/init.d/sfcbd-watchdog restart >/scratch/log/sfcbd.log 2>&1

Did not test this, since my servers where already rebooted.

Reply
0 Kudos
stacycarter
Enthusiast
Enthusiast

kimahansen - So did VMware say that the errors are harmless?

Reply
0 Kudos
kimahansen
Contributor
Contributor

Yes, they told me those messages was harmless

Reply
0 Kudos