Environment
Novell ZENworks 10 Configuration Management with Support Pack 3 - 10.3
Novell ZENworks 11 Configuration Management Support Pack 1 - ZCM 11 SP1
Situation
ERROR (in services-messages.log):
[DEBUG] [11/1/11 10:28:32 AM] [] [File Upload Servlet] [] [Upload Request Received: (6910) "null"] [] []
[DEBUG] [11/1/11 10:28:32 AM] [] [File Upload Servlet] [] [Invalid content type: null] [] []
[DEBUG] [11/1/11 10:28:32 AM] [] [File Upload Servlet] [] [Invalid content type: null] [] []
ERROR (in zmd-messages.log):
[DEBUG] [11/02/2011 17:28:56.265] [756] [ZenworksWindowsService] [15] [] [InventoryManager] [] [webService.getLastScanId FAILED: The request failed with HTTP status 400: Novell.Zenworks.FileUpload.INVALID_HTTP_CONTENT_TYPE.] [] []
Resolution
This is fixed in version 11.2 - see KB 7010044 "ZENworks Configuration Management 11.2 - update information and list of fixes" which can be found at https://www.novell.com/support
For 10.3.4 or 10.3.3: Please contact Novell Technical Support by creating a Service Request.
Additional Information
When the zenworks-inventorywebservice can't be reached in some cases the agent fails over to the zenworks-fileupload service.
One way to distinguish the bad requests from good ones is to determine which devices are sending too many active requests at a time. This script shows ip addresses of inbound requests to identify possible candidates for the FTF (note those with > 200 inbound requests).
netstat -aln | grep -i ":81" | awk '{print $5}' | cut -d ':' -f1 | awk '{arr[$1]++} END {for(i in arr) printf "%6s %s\n", arr[i],i}' | sort