AppForge Application and Job Logs
Locate AppForge daemon and per-job logs, correlate WordPress operations by job ID, and understand configurable history retention.
AppForge maintains a daemon log, per-job event files and database history. Use the job identifier from the failed or incomplete operation to correlate them.
Default locations
| Location | Purpose |
|---|---|
/var/log/eenos/appforge/appforge.log | Daemon, catalog, provider and operational diagnostics. |
/var/log/eenos/appforge/jobs/<job-id>.log | Per-job events, including state transitions. |
/var/lib/eenos/appforge/appforge.db | Jobs, audit events, sessions and operation state; not a text log. |
<job-id> is the operation's canonical UUID. Job files contain newline-delimited JSON event records, including timestamp, job ID and state, with available kind/category/resource/error information. They are not guaranteed to contain every command's stdout/stderr.
Configuration overrides
The defaults can be overridden in /usr/local/eenos/etc/appforge.conf. logfile belongs in the [appforge] section. The job directory is derived from the parent of the configured logfile, followed by jobs/; moving the main log therefore changes the job-log location too.
Do not confuse database with logfile or move files while diagnosing a running operation.
Read application and service diagnostics
tail -n 100 /var/log/eenos/appforge/appforge.log
journalctl -u eenos-appforge.service --since '1 hour ago' --no-pager -n 100Read the selected job file after replacing its placeholder with the actual UUID. Compare its latest state and error code with the operation shown in the interface. A successful download job does not by itself prove a later installation completed.
The job-log API checks access to the selected job and returns at most the last 65,536 bytes, marking larger logs as truncated. A shortened interface excerpt does not necessarily mean the on-disk file was shortened.
Rotation and history cleanup
The daemon uses a watched file handler with external rotation support. The reviewed /etc/logrotate.d/eenos-appforge policy uses daily rotation, maxsize 20M, seven retained rotations and delayed compression. Logrotate applies size checks when it runs; this is not an instantaneous hard file-size cap.
AppForge defaults include 30 days for eligible completed job history and 90 days for eligible audit history. Cleanup is periodic and batched. Unresolved operation-journal entries can retain related jobs, and job cleanup also removes corresponding log files and eligible orphan logs. These settings are independent of the main daemon log's rotation policy.
Preserve incomplete operations
Do not delete job records, logs or operation journals to release an operation that appears stuck. Diagnose its recorded state and reconcile the website first; deleting evidence does not undo a partial WordPress change.