Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 373445
Smarts NCM: Status for running job shows as "queued", but no progress is made
Last update date:
3/22/2024
Affected products:
Smart Assurance - NCM
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Status for job running in Smarts Network Configuration Manager (Smarts NCM) shows as "queued", but no progress is madeMessages similar to the following are seen in the syssyncs.log on the Smarts NCM Application Server: Line 4059: Jan 23 11:04:32 -1258591328/status_0113589606190000#7: recv: "HTTP/1.1 400 Server Busy" Line 4060: Jan 23 11:04:32 -1258591328/status_0113589606190000#7: recv: "Date: Wed, 23 Jan 2013 17:04:31 GMT" Line 4061: Jan 23 11:04:32 -1258591328/status_0113589606190000#7: recv: "Server: Apache" Line 4062: Jan 23 11:04:32 -1258591328/status_0113589606190000#7: recv: "Content-Length: 0" Line 4063: Jan 23 11:04:32 -1258591328/status_0113589606190000#7: recv: "Connection: close" Line 4064: Jan 23 11:04:32 -1258591328/status_0113589606190000#7: recv: "Content-Type: text/plain; charset=UTF-8" Line 4065: Jan 23 11:04:32 -1258591328/status_0113589606190000#7: recv: "" Line 4066: Jan 23 11:04:32 -1258591328/status_0113589606190000#2: ...getRespHeaders: end Line 4067: Jan 23 11:04:32 -1258591328/status_0113589606190000#4: Checking Redirect location Line 4068: Jan 23 11:04:32 -1258591328/status_0113589606190000#2: Send complete Line 4069: Jan 23 11:04:32 -1258591328/status_0113589606190000#1: HTTP send failed, Code:400 HTTP send failed, Code:400 means 'The request cannot be fulfilled due to bad syntax' Messages in the following pattern are repeatedly seen in the syssyncm.log on the Smarts NCM Application Server: Jan 23 12:34:49 -1437647968/status_0113563739790000#7: recv: "Content-Type: text/plain; charset=UTF-8"Jan 23 12:34:49 -1437647968/status_0113563739790000#7: recv: ""Jan 23 12:34:49 -1437647968/status_0113563739790000#2: ...getRespHeaders: endJan 23 12:34:49 -1437647968/status_0113563739790000#4: Checking Redirect locationJan 23 12:34:49 -1437647968/status_0113563739790000#2: Send completeJan 23 12:34:49 -1437647968#7: Disconnecting...Jan 23 12:34:49 -1437647968#5: Shutting down SSL connection...Jan 23 12:34:49 -1437647968#7: SSL Write Alert: 256Jan 23 12:34:49 -1437647968#7: SSL State: warning-SSL negotiation finished successfullyJan 23 12:34:49 -1437647968#7: SSL Read Alert: 256Jan 23 12:34:49 -1437647968#7: SSL State: warning-SSL negotiation finished successfullyJan 23 12:34:49 -1437647968#5: Freeing SSL connection...Jan 23 12:34:49 -1437647968#5: SSL connection shutdownJan 23 12:34:49 -1437647968#7: Connection closed When running a job in Smarts NCM, the status will show as queued, but no progress will be made.
Cause
This issue occurs because the Smarts NCM Application Server cannot connect to device server. The underlying cause that the self signed certificate (or CA) was copied and moved to the device server from the application server using a non preferred method. Using the ./makekeys.sh utility in the /bin directory on the Smarts NCM device server is the preferred method of placing the certificate on the device server.
Resolution
If you encounter this issue, do the following on the Smarts NCM device server: Go to the $NCM_Home/conf/CA directory and change the current voyenceca.crt to voyenceca.crt.old.Go to the $NCM_Home/bin directory and run the ./makekeys.sh utility to provide a new certificate.Restart services on the device server as follows: cd $NCM_Home/conf/CA mv voyenceca.crt voyenceca.crt.old cd $NCM_Home/bin ./makekeys.sh service vcmaster restart Run a job for that device server to test communication.
