EL9 Image breaks MariaDB connection

[wraeuk]

Updating to the latest image on an existing install (and maybe a new install?) fails to connect to MariaDB with the error

2024-11-20 3:57:35 16 [Warning] Aborted connection 16 to db: 'misp' user: 'misp' host: '172.18.0.5' (Got an error reading communication packets)

I've rolled back to the image release prior to the update to almalinx9 and my MISP is back online. The repo also has guidance on using an "el8" branch that doesn't have a build pipeline yet I don't think. Happy to get some guidance on what ghcr tag I should pin to.

[crym]

I have been trying to debug this as well. It seems to be triggered by some settings in the system_settings-table. One example is debug. With a clean install (tested with a local docker instance), the debug setting is not in the system_settings-table and the server starts just fine. If MISP_DEBUG is passed as an environment variable (as either true or false) everything works fine with or without debug-mode.

If debug is enabled/disabled (even if submitting the same existing value), the value is stored in the database as any of the values 0, 1 or 2 (which is the correct values), but now the server becomes unresponsive.

• mysql warning: Aborted connection 27 to db: 'misp' user: 'misp' host: '172.18.0.5' (Got an error reading communication packets)" Any request after this gets error 503 with the following error messages:
• proxy_fcgi: "AH01067: Failed to read FastCGI header"
• proxy_fcgi: "AH01075: Error dispatching request to : "
• php_fpm: "[pool www] child 195 exited on signal 6 (SIGABRT) after 111.969989 seconds from start"}

If debug is deleted from the table, everything works fine again. If it is changed to true or false, everything works and debug is enabled/disabled but is is listed in the GUI as "value not set"

[crym]

@wraeuk I use ghcr.io/nukib/misp:latest@sha256:0c959f7ffd1dc7e05078f710c8f17ab8a7620f8f15bcd28486d0029b761b83bd for MISP v2.5.1 (with Almalinux 8)

[AliceGrey]

@wraeuk & @crym I am also having the same issue with the DB errors. I had to remove the following from my system_settings to get it working again with 2.5.2:

MISP.contact Security.password_policy_length

and all of the Plugin.Enrichment_[plugin name]_restrict values. It's unclear whether this is a MISP bug or a bug with this docker.

You can re-create the issue by making a brand new NUKIB/misp docker setup, logging into the UI, enabling enrichment plugins, and then enabling ANY plugin and setting the restrict equal to the default org. It immediately crashes the db connection.

[AliceGrey]

Maybe @ondj could provide some context/details? I don't have a stock misp install with 2.5.2 I can test with. Just the NUKIB containers.