Troubleshooting

Troubleshooting

Check status and logs first

herald status                 # daemon status and config summary
sudo systemctl status herald  # service status
journalctl -u herald -f       # follow live log output

Missing-file health check

A rotation or scheduled entry whose WAV file no longer exists on disk is flagged rather than failing silently — check herald status's missing-file count, herald list, or the "MISSING FILE" badge in the web UI.

AMI / unkey detection

Herald reads AMI credentials automatically from /etc/allmon3/allmon3.ini (Allmon3) or /etc/asterisk/manager.conf (Supermon / other frontends) on startup and on every config reload — no credentials belong in herald.conf itself. If neither file yields usable credentials, Herald falls back to polling the rpt stats kerchunk counter instead, which only catches local RF unkeys (not network keyups) and fires after the courtesy tone rather than at the actual unkey. If tail messages feel "late" or network-triggered announcements aren't firing, that fallback is the most likely cause — double-check the AMI credentials file Herald should be reading from.

Web UI

• The Allmon3/Supermon page not showing up, or a blank/unstyled page, usually means Apache/PHP isn't installed or enabled the way install.sh expects — see Getting Started for what a normal install does.
• All web UI actions run through the herald CLI via a narrow sudo rule for www-data (/etc/sudoers.d/herald-web) — if actions silently fail, confirm that file exists and hasn't been altered.

Filing a bug or feature request

Please open an issue and pick the Bug Report or Feature Request template — they'll prompt for the details (version, logs, steps to reproduce) that make it much faster to track down. One issue per report is easiest to work through.