Exit code 2/INVALIDARGUMENT when SIGTERM is sent to the fmd container
- I have searched for duplicates (including closed issues)
- I have read the docs
- I have cleared the browser cache
Bug Summary
The signals SIGTERM, SIGHUP, SIGQUIT, SIGINT result in exit code 2/InvalidArgument. I do think it's a normal exit code. Also, I do not know if there is something wrong happening at stop.
Steps to reproduce
podman run --name testfmd fmd-server:0.14.0podman kill --signal 15 fmd-
podman inspect testfmd --format '{{.State.ExitCode}}'is2
Actual behaviour
Return exit code 2, invalid argument.
Expected behaviour
Return 0 or 143 in case of SIGTERM because POSIX/bash standard 128+(signal code).
Metadata
- FMD Android version: not related
- Device: not related
- Android version: not related
- ROM name: not related
- FMD Server version: 0.14.0
- Browser: not related
Logs
When run, here is the log of the container.
~ $ podman run --name testfmd fmd-server:0.14.0
Failed to connect to syslog: Unix syslog delivery error
2026-02-19T05:39:29Z WRN no config found, using defaults
2026-02-19T05:39:29Z INF using config configFile=
2026-02-19T05:39:29Z INF starting FMD Server dbDir=/var/lib/fmd-server/db version=0.14.0 webDir=
2026-02-19T05:39:29Z INF loading database
2026-02-19T05:39:29Z INF no SQLite DB found, creating one
2026-02-19T05:39:30Z INF migrating database...
2026-02-19T05:39:30Z INF running sql name=000001_create_tables
2026-02-19T05:39:31Z DBG fmd-server/user/migrations.go:31 record not found
[0.566ms] [rows:0] SELECT * FROM `db_settings` WHERE setting = "fmd_db_version" ORDER BY `db_settings`.`id` LIMIT 1
2026-02-19T05:39:31Z INF schema version does not yet exist, creating it
2026-02-19T05:39:31Z INF db versions CurrentSqlVersion=3 actualVersion=0
2026-02-19T05:39:31Z INF running sql name=000002_add_last_seen_time
2026-02-19T05:39:31Z INF database successfully migrated
2026-02-19T05:39:31Z INF listening for metrics MetricsAddrPort=[::1]:9100
2026-02-19T05:39:31Z INF listening on insecure port PortInsecure=8080