error: OTRS Scheduler Daemon Cron: ArticleSearchIndexRebuild

Moderator: crythias

Post Reply
hkais
Znuny expert
Posts: 287
Joined: 16 Apr 2016, 08:55
Znuny Version: see in post
Real Name: Hans
Contact:

error: OTRS Scheduler Daemon Cron: ArticleSearchIndexRebuild

Post by hkais »

Hi there,

I have a scheduler running to process the new article index.

After a reboot, during the processing the articles, getting now this

Code: Select all

[b]subject[/b]: OTRS Scheduler Daemon Cron: ArticleSearchIndexRebuild

Error: Active indexing process already running! Skipping...
so it is popping up again and probably the last time caused by a automatic update of packages.
Is there a way to reset the status to normal, so that the cron can restart its job as normal?
Elected 2022-06 as an IT Governance Portal Expert. The portal for Znuny, OTRS and OTOBO users
Johannes
Moderator
Posts: 393
Joined: 30 Jan 2008, 02:26
Znuny Version: All of them ^^
Real Name: Hannes
Company: Znuny|OTTERHUB

Re: error: OTRS Scheduler Daemon Cron: ArticleSearchIndexRebuild

Post by Johannes »

Hi,

did you start the indexing "manual" ?
It should only happen when there is an active worker running, most of the time started manually.
Or when a reboot happened without stopping the daemon first, often by accident. Then there is a chance that there is a leftover PID entry in the db.
You can start the process by hand again and add a "--force". Wait until it is finished with the current set of tickets and the error should not happen again. Or you can delete the entry in the table "process_id". Whatever fits your need.
hkais
Znuny expert
Posts: 287
Joined: 16 Apr 2016, 08:55
Znuny Version: see in post
Real Name: Hans
Contact:

Re: error: OTRS Scheduler Daemon Cron: ArticleSearchIndexRebuild

Post by hkais »

Hi Johannes,

thank you for feedback
Johannes wrote: 07 Mar 2022, 14:44 did you start the indexing "manual" ?
It was created due to a reboot. No manual starting.
If on shutdown the daemon exceeds (afaik 90sec) it is getting terminated hard.
Johannes wrote: 07 Mar 2022, 14:44 Or when a reboot happened without stopping the daemon first, often by accident. Then there is a chance that there is a leftover PID entry in the db.

Or you can delete the entry in the table "process_id". Whatever fits your need.
good to know
Johannes wrote: 07 Mar 2022, 14:44 You can start the process by hand again and add a "--force". Wait until it is finished with the current set of tickets and the error should not happen again.
fixed it by triggering to run 1 article indexing manually.
Elected 2022-06 as an IT Governance Portal Expert. The portal for Znuny, OTRS and OTOBO users
Post Reply