Daemon Status

Scanopy monitors daemon health and displays a status tag next to each daemon name in the UI. Every daemon carries exactly one tag, showing the most important condition that currently applies.

Status Reference

Awaiting Connection

Blue tag. The daemon record exists but the daemon has never checked in.

Every daemon passes through this state. Creating a daemon provisions its record on the server before the daemon itself exists, so the tag appears as soon as you finish the wizard and clears on first contact.

How to resolve:

1. Run the install artifact from the wizard on the daemon host — until you do, there is nothing to connect
2. Confirm the daemon process or service is running (systemctl status scanopy-daemon, launchctl print system/com.scanopy.daemon, Get-Service scanopy-daemon, or service scanopy-daemon status)
3. DaemonPoll: check the daemon can reach the server on port 60072
4. ServerPoll: check the daemon's URL is correct and the server can reach it on port 60073
5. Check the daemon logs for registration errors — daemon_not_provisioned means a 0.17.5+ daemon tried to register itself against a record that doesn't exist, which happens when it was installed by hand with a legacy shared key instead of from a provisioned daemon's install artifact

If the tag persists, see Daemon Troubleshooting.

Standby

Purple tag. The daemon is registered but hasn't run a discovery session in over 30 days.

How to resolve:

• Run a manual discovery session to bring the daemon back to active status
• Verify the daemon process is still running on the host
• Check that scheduled discovery is configured if you expect automatic scans

Unreachable

Red tag. The server cannot reach a ServerPoll daemon at its configured URL.

How to resolve:

1. Verify the daemon service is running on the host (systemctl status scanopy-daemon, launchctl print system/com.scanopy.daemon, Get-Service scanopy-daemon, or service scanopy-daemon status)
2. Check that the daemon's configured URL is correct and reachable from the server
3. Check firewall rules — the server must be able to connect to the daemon
4. Restart the daemon's service and retry

See Daemon Troubleshooting for detailed connectivity debugging.

Deprecated

Orange tag. The daemon is running a version with a scheduled sunset date. It still connects and runs discovery normally until that date, after which it becomes Unsupported. The daemon card and upgrade dialog show the exact date and a countdown, and the org owner and each daemon's maintainer receive an email when a sunset is announced.

How to resolve:

• Upgrade the daemon before the sunset date — see Managing Daemons for installation steps. See Daemon Support Lifecycle for how sunset dates are set.

Unsupported

Red tag. The daemon's version is past its sunset date. The server rejects every request from it, so it can no longer connect or run discovery. The daemon exits and, under a service manager configured to restart it, will keep restarting and failing until it is updated.

How to resolve:

• Upgrade the daemon to the latest version — see Managing Daemons. Once updated it reconnects automatically.

Outdated

Yellow tag. A newer daemon version is available. The current version still works but may be missing features or fixes.

How to resolve:

• Upgrade the daemon at your convenience — see Managing Daemons for installation steps

Unknown

Gray tag. The server has no recorded version for this daemon — it has not yet reported one, or predates version reporting. Once a support floor is enforced, a daemon whose version cannot be confirmed is treated as unsupported.

How to resolve:

• Confirm the daemon is running a current release and has connected at least once. If it persists on a recent daemon, check the daemon logs for registration errors.

Healthy

Green tag. The daemon is running a current version and communicating with the server normally.

Status Priority

When multiple conditions apply, the UI shows the highest-priority one:

Unsupported > Unreachable > Standby > Awaiting Connection > Deprecated > Outdated > Unknown > Healthy

The Home tab shows all active statuses across your daemons.

Troubleshooting

If a daemon shows an unexpected status:

• Check daemon logs for errors or connection failures
• Verify connectivity between server and daemon (for ServerPoll daemons)
• Upgrade the daemon if Deprecated or Outdated
• Run a discovery session if a daemon is in Standby

For more help, see Daemon Troubleshooting and Managing Daemons.