NCM: Device Server /opt/voyence/logs/sysmons.log multiple "Send Request" and PUT errors generated by the SysAdmin/SyncServlet

Products

• VMware

Issue/Introduction

On the NCM Device Server in the /opt/voyence/logs/sysmons.log there are multiple "Send Request" and PUT errors generated by the SysAdmin/SyncServlet 
 

Send request to: http://10.76.192.49:8080/SysAdmin/SyncServlet?from=host-voyencedev-01&type=state

Apr 14 16:50:43 442374272#2: Connecting to http://10.76.192.49:8080/SysAdmin/SyncServlet?from=host-voyencedev-01&type=state

Apr 14 16:50:43 442374272#2: Hostname: 10.76.192.49

Apr 14 16:50:43 442374272#2: URI: /SysAdmin/SyncServlet?from=host-voyencedev-01&type=state

Apr 14 16:50:43 442374272#1: llPROF: check1 after setup milli 0, secs 0

Apr 14 16:50:43 442374272#1: llPROF: check2 after connect milli 0, secs 0

Apr 14 16:50:43 442374272#7: send: "PUT /SysAdmin/SyncServlet?from=host-voyencedev-01&type=state HTTP/1.1

Apr 14 16:50:43 442374272#7: "

Apr 14 16:50:43 442374272#1: Write failed: Last Error Resource temporarily unavailable

Apr 14 16:50:43 442374272#1: Write failed: Resource temporarily unavailable

Apr 14 16:50:43 442374272#7: Disconnecting...

Apr 14 16:50:43 442374272#7: Connection closed

Apr 14 16:50:43 442374272#1: Unknown Error

Environment

VMware Smart Assurance - NCM
VMware Smart Assurance - SMARTS

Resolution

There is no solution in current NCM versions (including latest 10.1.11). This is a Legacy error and can be ignored as it does not impact the functionality of NCM and will be resolved in a future release of NCM.  

These entries have been found in 10.1.x through 10.1.8 versions of NCM.

Additional Information

Users may consider removing SysAdmin utility from NCM application server or combination server if it's not used/required as a workaround until the reported log entries are fixed in future NCM release. Steps to remove SysAdmin utility from NCM application or combination server-

1. Navigate to $TOMCAT_HOME/webapps directory. 
2. Stop tomcat service with command "systemctl stop tomcat".
3. Remove SysAdmin (directory) and SysAdmin.war from $TOMCAT_HOME/webapps directory. 
4. Start tomcat service with command "systemctl start tomcat".