UnitFail Notifier systemd failure alerts
Silent service failures and crashing background daemons on production Linux hosts often go unnoticed until customers experience downtime, while manually monitoring systemctl…
After payment, Stripe emails your download link within a few minutes (valid 7 days). Pass buyers also get the private All-Access Vault on GitHub.
Digital goods, delivered instantly. If a tool doesn't work as described, we fix it or refund you — see Terms.
requirements.txt — list of dependencies
What's in the ZIP
- Python source, README and requirements
Why PyForge: Ready-made tools with full source code.
More details
Silent service failures and crashing background daemons on production Linux hosts often go unnoticed until customers experience downtime, while manually monitoring systemctl states across multiple machines is inefficient. Without automated notification hooks, developers must constantly inspect journalctl logs to catch restart loops, crashed workers, and missed timer schedules. The tool installs a global systemd OnFailure drop-in configuration and a dedicated alert template featuring recursion protection to prevent notification loops. It queries systemctl to detect failed units, inspect exit codes, track restart counts, and catch stalled timers. For every incident, it extracts the latest journalctl log lines and dispatches structured diagnostic payloads through generic HTTP webhooks, ntfy push servers, or standard SMTP email. Example: Run python3 unitfail_notifier_systemd_fail.py --help to review the complete command-line interface. Trigger a manual alert test by running python3 unitfail_notifier_systemd_fail.py notify --unit nginx.service --config /etc/unitfail/config.json to assemble unit properties and transmit recent journal lines directly to configured notification channels. This tool does not automatically restart crashed services, repair corrupted unit definitions, or support alternative init systems like SysVinit or OpenRC.
Quick Start
Runs on Python 3.9 or newer. Check requirements.txt in the ZIP and install what it lists with pip install -r requirements.txt.
1 — Install the dependencies
pip install -r requirements.txt2 — Run it
How agents & programs use it: Install its requirements in a virtual environment; scripts and AI agents can then run it as a subprocess.
Why developers buy from PyForge
- Save hours: ready-made, tested tools. Skip writing, debugging and maintaining it yourself.
- Ready in minutes: one file, drop it in your project and run it.
- Zero dependencies: no pip install chains, no supply-chain risk.
- Full source code: readable, auditable, yours to modify.
- Runs locally and offline: no account, no API key, no data leaves your machine.
- Pay once, own it: no subscription.
- Tested before release: every tool is checked before it goes on sale.
All-Access Pass
Get every PyForge tool with the All-Access Pass
39 tools today plus every future release, lifetime commercial license, one payment of $99.
This tool: $49 · All 39 tools: $99
See the All-Access Pass