Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts NCM: Status for running job shows as "queued", but no progress is made (373445)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 2096Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Status for job running in Smarts Network Configuration Manager (Smarts NCM) shows as "queued", but no progress is made
Messages 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: end
Jan 23 12:34:49 -1437647968/status_0113563739790000#4: Checking Redirect location
Jan 23 12:34:49 -1437647968/status_0113563739790000#2: Send complete
Jan 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: 256
Jan 23 12:34:49 -1437647968#7: SSL State: warning-SSL negotiation finished successfully
Jan 23 12:34:49 -1437647968#7: SSL Read Alert: 256
Jan 23 12:34:49 -1437647968#7: SSL State: warning-SSL negotiation finished successfully
Jan 23 12:34:49 -1437647968#5: Freeing SSL connection...
Jan 23 12:34:49 -1437647968#5: SSL connection shutdown
Jan 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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant