Error message for database check is too generic

Problem with the databse (e.g., in Engineblock) are quite hard to debug. The main entrypoint to check when EB doesn't start is to check the health endpoint, like this:

╰─▶ docker compose exec -ti engine curl http://localhost/internal/health
{"status":"DOWN","message":"Unable to execute a query on the database."}

That helps a little, but doesn't actually say what is wrong.

The problem is that in the DB check at

Monitor-bundle/src/HealthCheck/DoctrineConnectionHealthCheck.php

Lines 67 to 71 in 33335e0

    
           } catch (ConnectionException) { 
        
               return HealthReport::buildStatusDown('Unable to connect to the database.'); 
        
           } catch (Exception) { 
        
               return HealthReport::buildStatusDown('Unable to execute a query on the database.'); 
        
           }

the exception is eaten. We should add explicit ERROR-level logging of the exception (so the exception is shown in the error logs).

Symfony env: production. See openconext-deploy
Scenario: Db contains an extra table, doctrine errors: Is the error visible in the logs?
Scenario: If mariadb version deviates from the configured version (in a breaking way)

Log exceptions at ERROR level in health checks

Log database health check exceptions at ERROR level

Log database health check exceptions at ERROR level (OpenConext#1977)

Navigation Menu

Repository navigation

Error message for database check is too generic #27

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	} catch (ConnectionException) {
	return HealthReport::buildStatusDown('Unable to connect to the database.');
	} catch (Exception) {
	return HealthReport::buildStatusDown('Unable to execute a query on the database.');
	}

Error message for database check is too generic #27

Description

Activity

johanib commented on Mar 30, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions