I’ve been working with APROL in general for some time. A few days ago, we set up an APROL R4.4-01 system and tried to connect to MariaDB.
However, we haven’t been successful so far. While investigating the issue, we noticed that MariaDB is not running, and I haven’t found any way to start it manually.
Has anyone experienced a similar problem or could offer any advice or suggestions on what to do?
Hello @F_Ka,
MariaDB was moved to container. The issue could be connected the database isn not activated (AprolConfig, CaeManger). In past in AprolConfig as database for ParameterCenter
We setup a hardware Aprol Server and on this machine, MariaDB started up automatically. Until now, we did not examine the problem further, as there were more important jobs to do.
As an auxiliary solution, we created an extra docker container with MariaDB. Perhaps I can give you another update on Monday.
Update: The standard MariaDB instance (running in the APROL container) is now operational. However, we are still encountering access issues.
We can successfully connect to the database from the engine’s command line using: mysql -h127.0.0.1 -uburadmin -p
—as documented in the APROL R4.4-01 Instructions.
However, access via our in-house UCB interface library and external database tools such as DBeaver or HeidiSQL is currently not working.
The APROL documentation provides only limited information and notes that further documentation is still in progress. Therefore, we cannot rule out that some required MariaDB configuration steps may be missing.
If anyone else has experienced similar issues or has found a solution, any input would be highly appreciated.
At the moment, the situation feels quite uncomfortable, especially since two additional issues have emerged—one related to runtime access and another concerning trend recording.
If a connection cannot be established from external tools, it is possible that the MariaDB server is configured in “Secure” mode within the APROL TLS configuration.
In this configuration, clients are required to present a trusted client certificate to establish a connection — which may be missing or not configured in the external tools.
For testing purposes, you may temporarily switch the MariaDB Server configuration to “Insecure” mode. After making this change, rebuild and download the updated configuration to apply it.
Once the new configuration is applied, retry the connection from your external tool to verify if the issue is resolved.
Note: When using Python with MySQLdb in a custom UCB script, you can specify the client certificate and other connection options using the read_default_file parameter.
@ Gerald Wageneder: Thank you for your comment. Using “insecure” will be a first approach for project devellopment.
In a further step we have to check out how to set up Databese tools and some web application by using trustetd certificates.