Hi Jeff, did you upgrade the code and config but run an old database?
The revocation_id feature was introduced with 3.4, the required changes are in the SQL schema so the setup should create the new columns if you create a new database. It is usually a BAD IDEA to upgrade the config "en bloc" without understanding the implications - we try hard to keep new code compatible with old config but a config update might change workflows or other settings that will crash existing installs! best regards Oliver Am 16.04.20 um 14:21 schrieb Jefferson Dümes: > Hi There, > > I am trying a the current dockerized version of OpenXPKI. When I try to > revocate a cert. I get this "Database error: execution of SQL query failed" > > From Workflow history by > Action/Descrition=NICE_DISPATCH_REVOKE/global_nice_revoke_certificate > > EXCEPTION: Database error: execution of SQL query failed; __dbi_error__ > => You can't specify target table 'certificate' for update in FROM > clause, __dsn__ => dbi:mysql:host=db;database=openxpki;port=3306, > __query__ => UPDATE certificate SET revocation_id = (SELECT > coalesce(max(revocation_id)+1, 1) FROM certificate) , status = ? WHERE ( > ( identifier = ? AND revocation_id IS NULL ) ), __source__ => > DBD::mysql::st::execute, __user__ => openxpki > > System Version 3.4.0 > Config Version config 3.4 > > Regards, > Jeff > > > _______________________________________________ > OpenXPKI-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openxpki-users > -- Protect your environment - close windows and adopt a penguin!
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
