Viewing 2 reply threads
  • Author
    Posts
    • #15522

      Hallo zusammen.

      Hab jetzt schon länger gewühlt, komme aber nicht wirklich weiter.

      Seit einigen Tagen bekomme ich schön im 10 Minuten Abstand Mails vom Scheduler Daemon:

      Betreff "OTOBO Scheduler Daemon Cron: StatsReportsGenerateCron"
      Error: Unable to register the process in the database. Is another instance still running?
      You can use --force-pid to override this check.

      Angefangen hat es mit einer Mail, die einen SQL-Fehler enthielt:

      Betreff "OTOBO Scheduler Daemon Cron: StatsReportsGenerateCron"
      DBD::mysql::db do failed: Lock wait timeout exceeded; try restarting transaction at /opt/otobo/Kernel/System/DB.pm line 560.
      ERROR: OTOBO-otobo.Console.pl-Maint::Stats::Reports::GenerateCron-98 Perl: 5.34.0 OS: linux Time: Sun Aug 13 08:11:26 2023
      Message: Lock wait timeout exceeded; try restarting transaction, SQL: '
      DELETE FROM process_id
      WHERE process_name = ?
      AND process_host = ?'
      Traceback (180040):
      Module: Kernel::System::PID::PIDDelete Line: 232
      Module: Kernel::System::Console::Command::Maint::Stats::Reports::GenerateCron::PostRun Line: 196
      Module: (eval) Line: 487
      Module: Kernel::System::Console::BaseCommand::Execute Line: 487
      Module: (eval) Line: 155
      Module: Kernel::System::Daemon::DaemonModules::SchedulerTaskWorker::Cron::Run Line: 134
      Module: Kernel::System::Daemon::DaemonModules::SchedulerTaskWorker::Run Line: 243
      Module: (eval) Line: 386
      Module: main::Start Line: 386
      Module: /opt/otobo/bin/otobo.Daemon.pl Line: 164

      Log /opt/otobo/var/log/Daemon/SchedulerTaskWorkerERR.log zeigt:

      ...

      ERROR: OTOBO-otobo.Console.pl-Maint::Stats::Reports::GenerateCron-98 Perl: 5.34.0 OS: linux Time: Tue Aug 15 07:50:19 2023

      Message: There was an error executing Execute() in Kernel::System::Console::Command::Maint::Stats::Reports::GenerateCron: Error: Unable to register the process in the database. Is another instance still running?
      You can use --force-pid to override this check.Traceback (22177):
      Module: Kernel::System::Daemon::DaemonModules::BaseTaskWorker::_HandleError Line: 60
      Module: Kernel::System::Daemon::DaemonModules::SchedulerTaskWorker::Cron::Run Line: 189
      Module: Kernel::System::Daemon::DaemonModules::SchedulerTaskWorker::Run Line: 243
      Module: (eval) Line: 386
      Module: main::Start Line: 386
      Module: /opt/otobo/bin/otobo.Daemon.pl Line: 164

      Habe die Datenbank (mysql) auf Locks (SHOW OPEN TABLES) und hängengebliebene Prozesse (show full processlist) geprüft, sehe aber nichts.

      Es laufen “normal viele” Daemonprozesse und deren Registrierung scheint zu stimmen.

      bin/otobo.Console.pl Maint::Daemon::List

      Listing system daemons...
      SchedulerCronTaskManager
      SchedulerFutureTaskManager
      SchedulerGenericAgentTaskManager
      SchedulerTaskWorker
      SystemConfigurationSyncManager
      Done.

      root@...:~# ps -eo args | grep otobo | head -n -1
      perl bin/otobo.Daemon.pl start
      perl bin/otobo.Daemon.pl start
      perl bin/otobo.Daemon.pl start
      perl bin/otobo.Daemon.pl start
      perl bin/otobo.Daemon.pl start
      perl bin/otobo.Daemon.pl start

      Alle anderen Worker laufen normal durch …

      bin/otobo.Console.pl Maint::Daemon::Summary

      Gathering summary for all daemons...

      System configuration sync:
      Daemon is active.

      Tasks to be executed in future:
      +------+-------------------+---------------------+
      | Name | Type | To Execute At |
      +------+-------------------+---------------------+
      ...
      +------+-------------------+---------------------+

      Recurrent cron tasks:
      +---------------------------------+---------------------+-------------+---------------+---------------------+
      | Name | Last Execution | Last Status | Last Duration | Next Execution |
      +---------------------------------+---------------------+-------------+---------------+---------------------+
      | ArticleSearchIndexRebuild | 2023-08-15 07:56:00 | Success | < 1 Second | 2023-08-15 07:57:00 |
      | CommunicationLogDelete | 2023-08-15 03:00:00 | Success | < 1 Second | 2023-08-16 03:00:00 |
      | ConfigurationDeploymentCleanup | 2023-08-13 00:40:00 | Success | < 1 Second | 2023-08-20 00:40:00 |
      | CoreCacheCleanup | 2023-08-13 00:20:00 | Success | 1.0 Second(s) | 2023-08-20 00:20:00 |
      | EscalationCheck | 2023-08-15 07:55:00 | Success | < 1 Second | 2023-08-15 08:00:00 |
      | GenerateDashboardStats | 2023-08-15 07:05:00 | Success | < 1 Second | 2023-08-15 08:05:00 |
      | GeneticInterfaceDebugLogCleanup | 2023-08-15 03:02:00 | Success | < 1 Second | 2023-08-16 03:02:00 |
      | LoaderCacheDelete | 2023-08-13 00:30:00 | Success | < 1 Second | 2023-08-20 00:30:00 |
      | MailAccountFetch | 2023-08-15 07:50:00 | Success | 2.0 Second(s) | 2023-08-15 08:00:00 |
      | MailQueueSend | 2023-08-15 07:56:00 | Success | < 1 Second | 2023-08-15 07:57:00 |
      | RebuildEscalationIndex | 2023-08-15 07:56:00 | Success | < 1 Second | 2023-08-15 08:00:00 |
      | RegistrationUpdateSend | 2023-08-15 07:30:00 | Success | < 1 Second | 2023-08-15 08:30:00 |
      | RenewCustomerSMIMECertificates | 2023-08-15 02:02:00 | Success | < 1 Second | 2023-08-16 02:02:00 |
      | SessionDeleteExpired | 2023-08-15 06:55:00 | Success | < 1 Second | 2023-08-15 08:55:00 |
      | SpoolMailsReprocess | 2023-08-15 00:10:00 | Success | < 1 Second | 2023-08-16 00:10:00 |
      | StatsReportsGenerateCron | 2023-08-15 07:50:00 | Fail | < 1 Second | 2023-08-15 08:00:00 |
      | SupportDataCollectAsynchronous | 2023-08-15 07:01:00 | Success | < 1 Second | 2023-08-15 08:01:00 |
      | TicketAcceleratorRebuild | 2023-08-15 01:01:00 | Success | < 1 Second | 2023-08-16 01:01:00 |
      | TicketDraftDeleteExpired | 2023-08-15 07:55:00 | Success | < 1 Second | 2023-08-15 08:55:00 |
      | TicketNumberCounterCleanup | 2023-08-15 07:50:00 | Success | < 1 Second | 2023-08-15 08:00:00 |
      | TicketPendingCheck | 2023-08-15 06:45:00 | Success | 1.0 Second(s) | 2023-08-15 08:45:00 |
      | TicketUnlockTimeout | 2023-08-15 07:35:00 | Success | < 1 Second | 2023-08-15 08:35:00 |
      | WebUploadCacheCleanup | 2023-08-15 07:46:00 | Success | < 1 Second | 2023-08-15 08:46:00 |
      | DeleteExpiredOTATokens | 2023-08-15 04:00:00 | Success | < 1 Second | 2023-08-16 04:00:00 |
      +---------------------------------+---------------------+-------------+---------------+---------------------+

      Recurrent generic agent tasks:
      +-------------------------------+---------------------+-------------+---------------+---------------------+
      | Name | Last Execution | Last Status | Last Duration | Next Execution |
      +-------------------------------+---------------------+-------------+---------------+---------------------+
      ...
      +-------------------------------+---------------------+-------------+---------------+---------------------+

      Unhandled Worker Tasks:
      There are currently no tasks waiting to be executed.

      Handled Worker Tasks:
      There are currently no tasks being executed.

      Done.

      Hat jemand einen Tip, wo ich hingreifen muss?

      Hat sich da was in der Datenbank verhaspelt?

      Gibt es irgendwelche Aufräumtasks die ich probieren kann?

      VG,

      Andrej

    • #15523

      Nachtrag. Systemlog sagt …

      Tue Aug 15 11:20:20 2023 (Europe/Berlin) error OTOBO-otobo.Console.pl-Maint::Stats::Reports::GenerateCron-98 There was an error executing Execute() in Kernel::System::Console::Command::Maint::Stats::Reports::GenerateCron: Error: Unable to register the process in the database. Is another instance still running?

      Tue Aug 15 11:20:20 2023 (Europe/Berlin) notice OTOBO-otobo.Console.pl-Maint::Stats::Reports::GenerateCron-98 Can’t create PID Maint::Stats::Reports::GenerateCron, because it’s already running (SERVERFQDNHIER/180040)!

    • #15534

      Update.

      Leider oder zum Glück hat sich das Problem erledigt.

      Leider weil ich nicht sagen kann, was die Lösung war – vermutlich lief irgendein Systemswartungsjob der Sessions / alte PIDs weggeräumt hat? Ich habe in dem Moment lediglich Fehlersuche betrieben ohne etwas zu verändern.

      Falls jemandem noch etwas dazu einfällt gerne noch Tips ergänzen.

Viewing 2 reply threads
  • You must be logged in to reply to this topic.