Plug-In Ticket Closer: DB Error #1062 after osTicket Update

mastertera

Dear Support Team

Last Week we updated osTicket to the latest Version.
No we have some issues with the Ticket Closer Plug-In.
There are an DB Error #1062.
Ialready deleted the Plug-In and the last-run key in the Database. But it not help. This is the Error we got:

[INSERT INTO ost_config SET key = 'last-run', value = 1666005608, updated = NOW()] Duplicate entry 'last-run' for key 'namespace' ---- Backtrace ---- #0 C:\inetpub\wwwroot\support\Include\mysqli.php(203): osTicket->logDBError('DB Error #1062', '[INSERT INTO o...') #1 C:\inetpub\wwwroot\support\Include\class.orm.php(3482): db_query('INSERT INTOos...', true, true) #2 C:\inetpub\wwwroot\support\Include\class.orm.php(658): MySqlExecutor->execute() #3 C:\inetpub\wwwroot\support\Include\class.config.php(176): VerySimpleModel->save(true) #4 C:\inetpub\wwwroot\support\Include\class.config.php(109): ConfigItem->save() #5 C:\inetpub\wwwroot\support\Include\class.config.php(119): Config->create('last-run', 1666005608) #6 C:\inetpub\wwwroot\support\Include\class.config.php(84): Config->update('last-run', 1666005608) #7 C:\inetpub\wwwroot\support\Include\plugins\autocloser\class.CloserPlugin.php(188): Config->set('last-run', 1666005608) #8 C:\inetpub\wwwroot\support\Include\plugins\autocloser\class.CloserPlugin.php(79): CloserPlugin->is_time_to_run(Object(CloserPluginConfig)) #9 C:\inetpub\wwwroot\support\Include\plugins\autocloser\class.CloserPlugin.php(68): CloserPlugin->logans_run_mode() #10 C:\inetpub\wwwroot\support\Include\class.signal.php(98): CloserPlugin->{closure}(NULL, Array) #11 C:\inetpub\wwwroot\support\Include\class.cron.php(123): Signal::send('cron', NULL, Array) #12 C:\inetpub\wwwroot\support\Include\api.cron.php(19): Cron::run() #13 C:\inetpub\wwwroot\support\Include\api.cron.php(40): CronApiController->run() #14 C:\inetpub\wwwroot\support\api\cron.php(23): LocalCronApiController::call() #15 {main}

Thank you for your help

Best regards
Michael

KevinTheJedi

mastertera

You are using a 3rd party plugin. You will need to reach out to the maker of the 3rd party plugin for further assistance. It's probably not updated to fit the new Plugin backend.

Cheers.