Eenos Log Files
Find Eenos panel, daemon, MailTrack, AppForge, backup, migration and website logs for server troubleshooting.
Use this reference to locate operational logs on an Eenos server. Read server-wide files through an authorized administrator shell. Log Files is a documentation submenu under WAP; it does not add a log viewer to the control panel.
Choose the right log
| Investigating | Guide |
|---|---|
| Panel errors, background tasks, resource monitoring or file operations | Panel and daemon logs |
| Mail delivery tracking, collector errors or missing tracking history | MailTrack logs |
| WordPress installation, catalog downloads or AppForge jobs | AppForge logs |
| Account backups, restores or hosting migrations | Backup and transfer logs |
| HTTP requests, PHP errors, mail services or other installed services | Service and website logs |
| Reading, correlating and retaining diagnostic evidence | Reading logs and retention |
Logs and activity history
Activity Logs records instrumented actions, actors and outcomes in /var/lib/eenos/audits/audits.db. Operational text logs provide diagnostic messages from applications and services. Use both when investigating an incident; neither guarantees a complete transcript of every action.
MailTrack and AppForge also have their own databases. These are application state and history stores, not text files to read with tail or delete to clear an error.
Paths and availability
Locations in these guides are Eenos defaults or explicitly marked service/package examples. Installed services, selected web server, operating system and configuration overrides affect which files exist. A log may be created only when its component first writes a message. A missing file alone does not establish a service failure.
Keep diagnostic data private
Logs can contain account names, addresses, IPs, paths and request details. Share only the relevant time range with sensitive values removed. Preserve ownership and permissions; do not place server logs in a public website directory.