Forum GLPI-Project

WizzurdOfOdd

Member

Registered: 2022-11-15

Posts: 21

cron not working on queuednotification

Hi Im running the latest stable 10.0.5 of GLPI.
I installed it on an Ubuntu Server 2210 with mysql and php8.1

i can send notifications manually and receive tickets via mail, so that works.
i have set the cron to 1 minute and status planned, i tried both: CLI and GLPI but both dont seem to work.
it shows me the same last executed date (which makes sense) and next execution is as soon as possible.
if i press on execute now, it works like a charm, but well... that defeats the purpose if it, doesnt it? ;-)

the job seems also not to be stuck, in the protocol it states that the last amount was 0 "job done, nothing to do"

so im not really sure, where to start from here

please bear with me, im not a linux pro, but willing to learn, please point me in the direction and i try to figure it out then myself ;-) but if i cant it would be great if you can give me some more input

<3

regards,
Gerry

WizzurdOfOdd

Member

Registered: 2022-11-15

Posts: 21

Re: cron not working on queuednotification

2022-11-14 17:55:09 [7@webserver01]
Intern #1: Starte queuednotification
2022-11-14 17:57:33 [7@webserver01]
Intern #1: Starte queuednotification
2022-11-14 17:58:12 [7@webserver01]
Intern #1: Starte olaticket
2022-11-14 17:59:06 [7@webserver01]
Intern #1: Starte queuednotification
2022-11-15 07:09:34 [7@webserver01]
Intern #1: Starte graph
2022-11-15 07:17:33 [7@webserver01]
Intern #1: Starte slaticket
2022-11-15 07:51:01 [@webserver01]
Internal #1: Launch planningrecall
2022-11-15 07:51:06 [@webserver01]
Internal #1: Launch olaticket
2022-11-15 08:09:17 [7@webserver01]
Intern #1: Starte reservation
2022-11-15 08:20:33 [7@webserver01]
Intern #1: Starte RecurrentItems
2022-11-15 08:46:48 [7@webserver01]
Intern #1: Starte temp
2022-11-15 08:46:51 [7@webserver01]
Intern #1: Starte queuednotification
2022-11-15 09:23:16 [7@webserver01]
Intern #1: Starte closeticket
2022-11-15 12:47:30 [7@webserver01]
Intern #1: Starte alertnotclosed
2022-11-15 13:13:35 [7@webserver01]
Intern #1: Starte slaticket

these are the last few entries from today and yesterday's /var/log/glpi/cron.log 
it only shows that crons have been started, is that correct, so are they still running or is that a completed job?

Last edited by WizzurdOfOdd (2022-11-15 14:56:00)

WizzurdOfOdd

Member

Registered: 2022-11-15

Posts: 21

Re: cron not working on queuednotification

SOLVED!

what i did:
1. sudo apt-get install cron
2. nano /etc/crontab
3. added the line

*/1 * * * * root cd /var/www/glpi/front/ && php cron.php

you may need to adjust the path to fit your GLPI Directory.
4. restarted cron service
5. switched the necessary automated jobs from GLPI to CLI and set the timing accordingly

LaDenrée

HELPER

Registered: 2012-11-19

Posts: 6,287

Re: cron not working on queuednotification

you should run your cron as apache instead of root 

*/1 * * * *  www-data cd /var/www/glpi/front/ && php cron.php

---

Trouver la panne avant de réparer...
GLPI10.0.16 (ubuntu 22.04 PHP8.1  Mariadb10.6 ) plugins : comportements 2.7.3 reports 1.16.0 formcreator 2.13.9, datainjection 2.13.5 fields 1.21.9

patrickg

Member

Registered: 2023-01-13

Posts: 2

Re: cron not working on queuednotification

i have done exactly this in and outbound emails do not move unless i manually execute them for example from Automatic Actions - queuednotification and Automatic Actions - mailgate execute button. I am on version 10 not sure the exact ver.

*/5 * * * *  www-data cd /var/www/glpi/front/ && php cron.php restarted cron rebooted server

i have no delay on the entity.

what do i need to check?

have mailgate and queuednotification set to 5 min and CLI instead of glpi.

Last edited by patrickg (2023-02-13 20:07:34)

Saadh.eisa

Member

Registered: 2023-08-01

Posts: 2

Re: cron not working on queuednotification

The same issue I faced and the solution was simple.

Check Automatic Actions >> queuednotification

Status should be "scheduled" not "Running", if it was displayed as Running, below action solved the issue with me.

Solution: removing the x icon in "Next Run", cleared the running status and fixed the issue.