Service and Website Logs
Locate website access and PHP error logs and identify configured mail, web server, database, FTP and security service logs.
Eenos application logs do not replace each service's own diagnostics. Check the active service configuration: package versions, operating systems and local overrides can change destinations or send messages to the journal.
Website access and PHP errors
| Eenos template location | Contents |
|---|---|
/var/log/domlogs/<domain> | Domain HTTP access records from the selected web server. |
/var/log/domlogs/<domain>-bytes_log | Domain byte-accounting records used for bandwidth collection. |
<account-home>/logs/<domain>-<php>.error.log | Website PHP-FPM error log from the pool template. <php> is the configured PHP identifier. |
Use the account's actual home directory, which need not be under /home. Website PHP errors are separate from the panel's eenosd-php-fpm.log. Runtime-wide PHP-FPM logs can also exist under /opt/eenos/php<version>/usr/var/log/, according to the selected package and configuration.
For a website error, correlate the domain request time, HTTP status and PHP/runtime error. Review the serving layer too when Nginx proxies to Apache or another backend.
Runtime sandbox setup logs
The current bootstrap helpers write account-level logs under the actual account home:
| Location | Purpose |
|---|---|
<account-home>/logs/sanbox-nodejs.log | Node.js sandbox setup. |
<account-home>/logs/sanbox-python.log | Python sandbox setup. |
<account-home>/logs/sanbox-ruby.log | Ruby sandbox setup. |
The filenames use sanbox, exactly as written. These are setup diagnostics, not a universal location for an application's runtime stdout/stderr. Check the application's configured process manager or service for runtime output. WordPress wp-content/debug.log, when debugging is enabled, is likewise a website diagnostic rather than the AppForge daemon log; avoid leaving sensitive debug output publicly accessible.
Web services
These are common Eenos/package locations; confirm configured paths before using them as the sole source of evidence.
| Component | Common locations |
|---|---|
| Nginx | /var/log/nginx/access.log, /var/log/nginx/error.log |
| Apache | /var/log/httpd/access_log, /var/log/httpd/error_log |
| OpenLiteSpeed | /var/log/lsws/access.log, /var/log/lsws/error.log |
| Varnish access logging | /var/log/varnish/varnishncsa.log, when varnishncsa is enabled |
| ModSecurity | /var/log/nginx/modsec_audit.log or /var/log/httpd/modsec_audit.log, if that engine/configuration writes there |
Audit logs may contain request bodies and sensitive application data. A missing ModSecurity audit file can reflect the selected engine, logging policy or lack of matching events; check configuration rather than creating an empty file.
Mail and authentication
| Component | Where to look |
|---|---|
| Exim | Common files: /var/log/exim_mainlog, /var/log/exim_rejectlog, /var/log/exim_paniclog; verify log_file_path. |
| MailTrack | Collector diagnostics and tracking database. |
| Dovecot | Configured log_path/info_log_path or journal/syslog; packages can use /var/log/dovecot.log or /var/log/mail.log. |
| Mailman | /var/log/mailman/, with filenames depending on core/web configuration. |
| SSH authentication | Journal or distribution auth log, commonly /var/log/auth.log or /var/log/secure. |
Exim's mainlog describes delivery attempts and outcomes; a reject log records rejected traffic, and a panic log warrants investigation of serious errors. Correlate by message ID rather than only sender address.
Databases, FTP and antivirus
| Component | Common location or configuration check |
|---|---|
| MySQL/MariaDB | Configured error log or journal; /var/log/mysql/error.log is one package layout. |
| PostgreSQL | Configured log_directory and logging collector; /var/log/postgresql/ is one package layout. |
| MongoDB | Configured systemLog.path, commonly /var/log/mongodb/mongod.log. |
| Pure-FTPd transfers | /var/log/pure-ftpd/transfer.log in the Eenos template. |
| ClamAV daemon | /var/log/clamd.log in the Eenos template. |
| ClamAV on-access scanner | Configured log or journal; /var/log/clamonacc.log where enabled. |
| FreshClam | Configured update log, commonly /var/log/freshclam.log. |
Do not assume every listed service is installed. See Service Monitor for status and reading logs for bounded diagnostics.