Jobs stuck at "Queued for Execution" and confirmed the lockbox is unlocked.
search cancel

Jobs stuck at "Queued for Execution" and confirmed the lockbox is unlocked.

book

Article ID: 330910

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Customers will sometimes experience "Queued for Execution" in the Comment Window next to the Status showing "Running", please see the example below:



Have the following items below been verified:

  • Hostname and FQDN are entered in the Lockbox
  • Firewall is disable or no Firewall is between the Application Server and Device Server
  • Lockbox is unlocked.
  • Fresh install with no history. 

On the Device Server check the $VOYENCE_HOME/logs/ssxfrcgi.log and look for the following:

 Can not open master.addr : Permission denied  

Environment

NCM 10.1.X

Cause

Creating the $VOYENCE_HOME/data/ directory and coping the lockbox files over manually.

Resolution

When manually creating the $VOYENCE_HOME/data/ directory it was assigned the root:root permissions. That means NCM was able to complete the installation, however the voyence server account is not able to access the data/devserver directory which has the master.addr file. To change the $VOYENCE_HOME/data/ directory ownership from root:root to root:voyence please follow the directions below:

  • Log into the CLI of the Device Server. 
  • source /etc/voyence.conf
  • cd $VOYENCE_HOME
  • ls -ltr to confirm the /data directory ownership. (See below)

  • Change the ownership from root:root to root:voyence by running the command: chown root:voyence data (see below)

  • Now complete a ls -ltr and confirm that the ownership has changed. 



If you still are having problems and this has not resolved, then create a case with Broadcom Support.