NDTS Daemon Operation

From Network for Advanced NMR
Revision as of 19:23, 2 June 2025 by Mmaciejewski (talk | contribs)
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 daemon’s log and audit files on every spectrometer workstation.

Service Control

# 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 refuses to start if another instance is already running.*

Heartbeat and Connectivity

  • The daemon sends a heartbeat to the Gateway every 10 minutes.
  • The Gateway forwards that heartbeat to the NDTS Receiver; entries are visible in vNOC.

Slack Notifications

When heartbeats stop, the Receiver posts to the facility’s Slack channel.

Condition Time-out Receiver Action Slack Message
≈ 20 min | Mark workstation offline | offline
+8 min | Re-post offline (max 3) | offline
– | Mark workstation online | online

Slack channel names (one per facility):

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

Version Tracking

  • On start-up, the daemon writes its version to the log.
  • A file named
/opt/nan-dtdaemon/running_workstation_version-X.Y.Z
 contains the version and start timestamp.

Experiment Transfer Audit

Every processed experiment appends one line to

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

Fields:

  1. Timestamp
  2. Workstation (Linux) user
  3. Selected NMRhub user (or unselected)
  4. Experiment start & end time
  5. Path to experiment data
  6. Daemon version
  7. Action (sent • spooled • sent-spooled • skipped-trivial • skipped-disabled)

Daemon Log File

  • Main log:
    /opt/nan-dtdaemon/logs/nan-dtdaemon.log
  • Verbosity is set by log_level 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 What to Check
service data-transport-daemon status
• Latest heartbeat timestamp in vNOC
• Gateway log for incoming files
Workstation powered off? Network drop? Firewall still allowing port 60195?
log_level trace left enabled → set back to info
Gateway unreachable → verify IP/port and Gateway service status

Next Step