Problem
All three database services (mariadb, postgresql, mssql) fail to start on RHEL 10.3 Beta. This is different from issues #57/#58/#59 which address wait/retry logic — this issue is about the root cause of the services not starting at all.
Errors
MariaDB
ERROR 2002 (HY000): Can't connect to local server through socket '/var/lib/mysql/mysql.sock' (2)
The mariadb service never creates the socket file. The service may not be starting due to initialization or config issues on RHEL 10.
PostgreSQL
Job for postgresql.service failed because the control process exited with error code.
See "systemctl status postgresql.service" and "journalctl -xeu postgresql.service" for details.
psql: error: connection to server at "localhost" (::1), port 5432 failed: Connection refused
Is the server running on that host and accepting TCP/IP connections?
connection to server at "localhost" (127.0.0.1), port 5432 failed: Connection refused
Is the server running on that host and accepting TCP/IP connections?
The postgresql service exits immediately after starting. The control process returns a non-zero exit code.
MSSQL
/opt/mssql/bin/sqlservr: error while loading shared libraries: liblber-2.4.so.2: cannot open shared object file: No such file or directory
Job for mssql-server.service failed because the control process exited with error code.
Failed to restart msql-server.service: Unit msql-server.service not found.
See issue #62 for the liblber root cause. Also note the typo: msql-server vs mssql-server.
Impact
Because the database services never start:
- HammerDB's TPCC build phase fails (can't connect to any DB)
- All benchmark runs (10/20/40 users) execute against nothing
- Results have TPM=None and connection=None
- Schema validation fails with 6 pydantic errors
- Wrapper exits rc=106
The wait/retry improvements in issues #57/#58/#59 will help detect this faster, but won't fix the underlying startup failures on RHEL 10.
Environment
- RHEL 10.3 Beta (Coughlan), kernel 6.12.0-238.el10.x86_64
- Azure Standard_D64s_v5 (64 vCPU, 2 NUMA, 256 GB RAM)
- Packages pre-installed in VHD image: mariadb-server, mariadb-common, postgresql, postgresql-server, postgresql-contrib
- hammerdb-wrapper v2.6, HammerDB 3.2
- Running with
--no_system_packages
Problem
All three database services (mariadb, postgresql, mssql) fail to start on RHEL 10.3 Beta. This is different from issues #57/#58/#59 which address wait/retry logic — this issue is about the root cause of the services not starting at all.
Errors
MariaDB
The mariadb service never creates the socket file. The service may not be starting due to initialization or config issues on RHEL 10.
PostgreSQL
The postgresql service exits immediately after starting. The control process returns a non-zero exit code.
MSSQL
See issue #62 for the liblber root cause. Also note the typo:
msql-servervsmssql-server.Impact
Because the database services never start:
The wait/retry improvements in issues #57/#58/#59 will help detect this faster, but won't fix the underlying startup failures on RHEL 10.
Environment
--no_system_packages