NDTS Daemon Operation

From Network for Advanced NMR
Revision as of 19:21, 2 June 2025 by Mmaciejewski (talk | contribs) (Created page with "= Running and Monitoring the Daemon = This page explains how to control the **data-transport-daemon** service, verify connectivity, and interpret the logs produced on each spectrometer workstation. == '''Starting, Stopping, and Checking Status''' == <pre> # Start the daemon sudo /sbin/service data-transport-daemon start # Stop the daemon sudo /sbin/service data-transport-daemon stop # Restart (reloads configuration) sudo /sbin/service data-transport-daemon restart #...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Running and Monitoring the Daemon

This page explains how to control the **data-transport-daemon** service, verify connectivity, and interpret the logs produced on each spectrometer workstation.

Starting, Stopping, and Checking Status

# Start the daemon
sudo /sbin/service data-transport-daemon start

# Stop the daemon
sudo /sbin/service data-transport-daemon stop

# Restart (reloads configuration)
sudo /sbin/service data-transport-daemon restart

# Check status
sudo /sbin/service data-transport-daemon status
  • The daemon will refuse to start if an instance is already running on the workstation.*

Heartbeat and Connectivity

  • By default the daemon sends a **heartbeat** to the Gateway every **10 minutes**.
  • The Gateway forwards that heartbeat to the NDTS Receiver, where it is logged in the NAN Repository and surfaced in vNOC.

Slack Notifications

When a heartbeat is missed, the Receiver posts alerts to the facility’s Slack channel.

Condition Time-out Action Slack message
Missed heartbeat > 20 min ≈ 20 min Daemon marked offline “*offline*” message (repeats once)
Heartbeat resumes Daemon marked online “*online*” message

Channels are named:

  • ccrc-ndts-notifications
  • nmrfam-ndts-notifications
  • uchc-ndts-notifications

Version Information

  • On daemon start-up, the version is written to the log file (see below).
  • A file named **/opt/nan-dtdaemon/running_workstation_version-X.Y.Z** is created, timestamped with the start time.

Experiment Transfer Audit

Every processed experiment adds one line to

/opt/nan-dtdaemon/logs/ndtd_audit.txt

Fields:

  1. Timestamp # Workstation user # NMRhub user (or ‘‘unselected’’) # Start & End time
  2. Path to data # Daemon version # Action

(sent | spooled | sent-spooled | skipped-trivial | skipped-disabled)

Daemon Logs

  • Main log:
    /opt/nan-dtdaemon/logs/nan-dtdaemon.log
  • **log_level** is set in ndtd_configuration.dat
 (fatal < error < warning < info < debug < trace).

Example start-up excerpt (level INFO):

Thu Sep 28 13:17:03 2023 LOG_START Started dtd logger.
Thu Sep 28 13:17:03 2023 INFO NDTD Workstation version is 1.0.15
Thu Sep 28 13:17:03 2023 INFO *** This is a Topspin Workstation ***
Thu Sep 28 13:17:03 2023 INFO Ndtd Control Processor listening.

Troubleshooting Checklist

Symptom Check
service data-transport-daemon status

• Heartbeat timestamp in vNOC • Gateway log for incoming files

Workstation powered off? Network drop? Firewall blocking port 60195?
log_level trace left enabled → reset to info
Gateway unreachable → verify IP/port and gateway service status