Troubleshooting

Installlation logs

The setup wizard of the grammm Appliance saves its log to /var/log/grammm-setup.log. If, for example, the wizard fails the certificate generation, the reasons should be visible in that file.

System logs

The grammm Appliance inherits system logging settings from systemd. Refer to the systemd-journald(8) manpage for details. To display logs, use the journalctl(8) command from a root login shell prompt:

journalctl -u gromox-http -n 1000
journalctl -f

Useful options that can independently be combined are:

  • -f for follow mode

  • -n to show that many of the most recent lines

  • -u to limit the display to one particular service unit

Some logs are emitted to files rather than journald. These include:

URI Prefix

Process

Files

/dav

nginx

/var/log/nginx/grammm-web-access.log, /var/log/nginx/grammm-web-error.log

/dav

php-fpm

/var/log/grammm-dav/grammm-dav-php.log

/Microsoft-Server-ActiveSync

nginx

/var/log/nginx/grammm-web-access.log, /var/log/nginx/grammm-web-error.log

/Microsoft-Server-ActiveSync

php-fpm

/var/log/grammm-sync/grammm-sync-fpm.log

/web

nginx

/var/log/nginx/grammm-web-access.log, /var/log/nginx/grammm-web-error.log

/web

php-fpm

/var/log/gromox

Coredumps

The grammm Appliance inherits the coredump defaults from systemd. The sysctl variable for the core pattern is set to:

kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %e

systemd-coredump stores dumps in /var/lib/systemd/coredump. Refer to the systemd-coredump(8) and coredump.conf(5) manpages for details. Dumps are normally LZ4-compressed and need to be decompressed before they can be used with gdb; for this, you will need to install the lz4 program (zypper in lz4).