Clone
3
Troubleshooting
Patrick Gniza edited this page 2026-08-17 10:48:39 +02:00

Deutsch | English

Troubleshooting

Inspect effective Compose configuration

Because the active backend is selected through .env, start with:

docker compose config

Check that the expected backend override was loaded.


Wrong database backend starts

Check .env:

DATABASE_BACKEND=mssql
COMPOSE_FILE=docker-compose.yml:docker-compose.${DATABASE_BACKEND}.yml

or:

DATABASE_BACKEND=firebird
COMPOSE_FILE=docker-compose.yml:docker-compose.${DATABASE_BACKEND}.yml

Then inspect the running container environment:

docker compose exec romexis env | grep -E 'SERVER_DB|ROMEXIS_DB|MSSQL|FIREBIRD'

Expected backend identifiers:

SERVER_DB=5  # MSSQL
SERVER_DB=4  # Firebird

Firebird mode still starts MSSQL initialization

If SERVER_DB is missing, the entrypoint may default to MSSQL.

Check:

docker compose exec romexis env | grep SERVER_DB

The Firebird Compose override must set:

SERVER_DB=4

MSSQL_SA_PASSWORD required in Firebird mode

This means the old MSSQL init script is still being executed or old script content is present in the image.

Check inside the Romexis container:

docker compose exec romexis cat /opt/init-romexis-db.sh
docker compose exec romexis ls -lah /opt/init-romexis-*

Rebuild and recreate:

docker buildx prune -a -f
./scripts/build-local.sh server
docker compose up -d --force-recreate

Firebird shows unixODBC isql help

If you see:

unixODBC - isql and iusql

then the wrong isql tool is used.

Use:

isql-fb

or set:

export ISQL=isql-fb

Admin container does not start RomexisConfig

Check logs:

docker compose logs -f romexis-admin

If ADMIN_VNC_LIFECYCLE=true, RomexisConfig starts only after a VNC/noVNC client connects.

Open:

http://localhost:6080/vnc.html?host=localhost&port=6080&autoconnect=true

Admin JavaFX or translucency errors

Romexis Admin requires Openbox and xcompmgr.

The Admin image should include:

openbox
xcompmgr
x11-utils
openjfx
libopenjfx-java
libopenjfx-jni

Errors such as TRANSLUCENT translucency is not supported usually mean the compositor is missing or not running.


Admin splash screen is not shown

The splash screen uses xmessage from x11-utils.

Check:

docker compose run --rm --entrypoint which romexis-admin xmessage

mRomexis Web App build fails because WAR is missing

mromexis-html.war exists only in Romexis 6.5.3 and newer.

Check the payload:

docker run --rm --entrypoint find   gitea.buchhorster.de/planmeca/romexis-payload:6.5.3.444.203   /opt/romexis -name 'mromexis-html.war'

mRomexis Web App backend calls fail

Check proxy logs:

docker compose logs -f proxy

Check Romexis backend reachability from the proxy container:

docker compose exec proxy wget -O- http://romexis:8093/ || true

Build still uses old files

Clean local build cache:

docker buildx prune -a -f

Then rebuild with the local script:

./scripts/build-local.sh all

Recreate the runtime stack:

docker compose up -d --force-recreate

Start container with bash for debugging

Romexis server:

docker compose exec romexis bash

Admin image shell:

docker compose run --rm --entrypoint /bin/bash romexis-admin

mRomexis Web App image shell:

docker compose run --rm --entrypoint /bin/bash romexis-app