VMware Cloud Community
szyym
Contributor
Contributor

vmkernel and vmkwarning log flooded

Hi,

Could anyone tell me what this mean?

This two log files are constantly flooded by this warnings:

2019-12-19T12:06:37.203Z cpu12:2101773)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-19T12:06:37.203Z cpu12:2101773)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-19T12:06:38.205Z cpu12:2101773)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-19T12:06:38.205Z cpu12:2101773)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-19T12:06:39.207Z cpu12:2101773)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-19T12:06:39.207Z cpu12:2101773)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-19T12:06:40.209Z cpu12:2101773)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-19T12:06:40.209Z cpu12:2101773)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-19T12:06:41.211Z cpu12:2101773)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-19T12:06:41.211Z cpu12:2101773)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-19T12:06:42.214Z cpu12:2101773)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-19T12:06:42.214Z cpu12:2101773)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-19T12:06:43.216Z cpu12:2101773)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-19T12:06:43.216Z cpu12:2101773)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-19T12:06:44.216Z cpu16:2101773)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-19T12:06:44.216Z cpu16:2101773)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-19T12:06:45.217Z cpu16:2101773)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-19T12:06:45.217Z cpu16:2101773)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-19T12:06:46.220Z cpu16:2101773)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-19T12:06:46.220Z cpu16:2101773)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

I can't find anything regarding this "Net_RegisterCallback failed"

Version:  6.7.0 Update 3 (Build 15160138)

Manufacturer 

  Dell Inc. 

Model

  PowerEdge R520 

Tags (1)
0 Kudos
7 Replies
Vijay2027
Expert
Expert

Could be because R520 is not compatible with 67U3.

==> VMware Compatibility Guide - System Search

0 Kudos
Vijay2027
Expert
Expert

And this doesn't mean that it can't be done, but I wouldn't do it in production.

0 Kudos
szyym
Contributor
Contributor

Ok R520 is a test server but the same error I've got on another host (production this time) and it's dell r530 which is compatibile with 6.7

log from R530 (production)

2019-12-20T07:25:35.565Z cpu1:2555667)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-20T07:25:35.565Z cpu1:2555667)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-20T07:25:36.566Z cpu1:2555667)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-20T07:25:36.566Z cpu1:2555667)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-20T07:25:37.567Z cpu1:2555667)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-20T07:25:37.567Z cpu1:2555667)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-20T07:25:38.567Z cpu0:2555667)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-20T07:25:38.567Z cpu0:2555667)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

2019-12-20T07:25:39.568Z cpu0:2555667)WARNING: UserSocketInet: 4195: nfcd: Net_RegisterCallback failed

2019-12-20T07:25:39.568Z cpu0:2555667)WARNING: UserObj: 4823: nfcd: Poll on fd 4 failed: Invalid handle

so different hosts same error

0 Kudos
Vijay2027
Expert
Expert

Is NFCD (network file copy daemon) being used in your environment.

May be you can try stopping the service on the test server.

/etc/init.d/nfcd stop

0 Kudos
szyym
Contributor
Contributor

Restarting nfcd service on test host seems to fix the problem.

Will try at night with production.

0 Kudos
Vijay2027
Expert
Expert

Good to know. Let me know the results once you restart the service on Prod server.

0 Kudos
Vijay2027
Expert
Expert

Have you tried this on production server??

Please consider marking this answer as correct and helpful if this helps you.

0 Kudos