Demo
Demo

Knowledge base

application-log verifiedimportant

Process log

in the configuration this is a lineapplication-log: syslog,/var/log/mailerq/mailerq.log

Where the engine reports its own state: start-up, database and broker connections, configuration reloads, crashes.

Values

Values
comma-separated destinations: syslog and/or a file path
Default
syslog,/var/log/mailerq/mailerq.log · taken from the build
applying
restart required
where it can be set
in the config file · with a startup flag · as an environment variable

In detail

Ships writing to two destinations at once — syslog and a file — which is why the same lines appear both in journalctl -u mailerq and in /var/log/mailerq/mailerq.log. Lines carry a severity and a component: [Info] [2026-09-17 15:34:50] [Memory] 5 MTA IPs, 3 pools, …. This is the log that answers "why did the node not start" and "when did it last reload settings", and the one to read when a change made in the database appears to have been ignored — a [Loader] Reloading … line is the proof that it was not.

What happens if you get it wrong

Pointed only at a file, with syslog removed.journalctl -u mailerq goes quiet, and every check that reads the unit's journal — including Hub's installer steps — stops seeing anything.inference · inference