I found the root cause, and this one is interesting, it fits the symptoms related to the datastore in the database, but has zero to do with the error messages returned. Misleading for troubleshooting.
Successfully wrote key to datapool with key 'ca-signer-1' Token is certsign, looking for root... Creating alias for root ca: Alias : root-1 Identifier: VkBjvHQvHV6Flt0T-ESDSm3Av4g NotBefore : 2020-10-05 11:52:00 NotAfter : 2050-10-06 11:52:00 The actual database did not exist. the problem was that I was trying to insert into a non existent datapool. the user existed, that's it. no schema, no tables. my history buffer cycled so I have no way to confirm what I did. You might want to add a check on start up that certain key tables exist, not just the ability to connect. That would have caught the problem since the data store didn't exist. I do see errors returned when unable to connect, but that's not enough. also when doing inserts, some pre-check that the table exists, and throws a corresponding SQL error, not an OpenSSL decrypt error. only database related SQL error seen in catchall.log 2020/10/15 15:41:36 openxpki.system.ERROR Database error: connection failed; __dbi_error__ => Host '10.0.1.32' is not allowed to connect to this MariaDB server, __dsn__ => dbi:mysql:database=openxpki;port=3306;host=10.0.1.90, __source__ => DBI::connect, __user__ => openxpki [pid=37407|sid=yoKv] _______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
