10. Troubleshooting

10.1. Log files

The log files are set in elza.yaml (see Configuration Reference); usually they are in the log directory of the working directory:

elza.log - the application log (elza.logFile),
siem.log - the security audit log (elza.siemLogFile, see Authentication and Security),
access_log.<date>.log - HTTP requests, when the access log is enabled (see Configuration Reference).

When the application does not start, look for the first ERROR in elza.log; with systemd, also check journalctl -u elza.

10.2. The database is locked

The start stops at:

Waiting for changelog lock....

The previous start did not finish a database migration and left the lock behind. Make sure no other instance of ELZA runs against the same database. Then release the lock and start again:

DELETE FROM db_databasechangeloglock;

10.3. A package is older than the imported one

The start fails with Package is an older version than the one already imported. The dpkg directory of the working directory contains an older version of a package than the database. Replace it with the package from the current distribution or remove it.

10.4. Wrong characters in texts

Czech or other non-ASCII characters are stored or displayed wrongly. The JVM runs with a non-UTF-8 default encoding. Start Java with:

java -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8 -jar elza-tomcat.jar

10.5. WebSocket does not work

The application loads, but changes made by other users or the progress of background tasks do not appear until the page is reloaded. The reverse proxy does not forward WebSocket connections on /stomp. See Running Behind a Reverse Proxy.

10.6. Data fixes for old versions

Errors when upgrading old 2.x installations are described in Appendix: Legacy Upgrades.