A. “I don’t see anything in the Queue yet”

Expected behavior (most common). For a Scan workflow, NxWorkflowEngine will scan and build its working set before jobs appear in nxn_queue / NxUI Queue.

What to check

  • Confirm workflow engines are running:
    • ps -ef | grep NxWorkflow
  • Tail the newest workflow log:
    • cd /usr/share/SFS/logs
    • ls -lrt | tail
    • tail -f NxWorkflow_<workflowId>_<pid>.log

What “good” looks like in logs

  • Repeating Scanning <path> lines
  • Repeating scanObject <file> <size> <mtime> lines
  • Messages like exists in the current build table (means it’s already known and won’t be re-archived)

B. “The tail -f is barely moving / seems stuck”

Often normal with large files (checksum work) or deep directory traversal.

What to check

  • CPU usage for NxWorkflowEngine:
    • top (or ps -o pid,ppid,cmd,%cpu,%mem -p <pid>)
  • Log file still growing:
    • ls -l NxWorkflow_<id>_<pid>.log (watch size change)
  • You can also open the file and look for the last timestamp advancing.

C. “Workflow restarted / progress reset”

A restart of the workflow process can cause the scan to restart from the beginning.

Guidance

  • Avoid restarting NxWorkflow / NxWorkflowEngine unless necessary.
  • Prefer monitoring over intervention when it’s clearly scanning.

D. “It’s re-archiving things I believe already exist”

Your log example indicates correct behavior when it says:

  • <file> exists in the current build table.

If you see it reprocessing anyway, likely causes include:

  • Object changed since last scan (checksum differs; per manual, MD5 is used to detect alteration)
  • Different workflow/source path definition
  • Mirror/build table state differs across runs

What to check

  • Confirm the workflow ID and correct source path
  • Compare filenames/paths carefully (case, hidden files like ._*, .DS_Store)

E. “Read-only / volumes not accepting archive”

Per the manual, volume state impacts selection for archive operations:

  • ReadOnly volumes should not be selected for archive jobs.

What to check

  • In NxUI: Volumes / Drives (look for ReadOnly/Disabled indicators)
  • If the system is affected by the known “read-only option on the drive” issue, treat as environment/patch dependent (as you noted).

F. “Workflow engine running but nothing else happens”

Workflow engine may be scanning but not yet able to create queue work, or may be constrained by configuration.

What to check

  • Logs for errors/warnings near the end
  • Confirm NxQueue is running (queue service is responsible for launching jobs once present):
    • ps -ef | grep NxQueue
  • Confirm other core services present (NxREST/NxUI etc. are not required for scan, but NxQueue matters for job execution)