How to deal with the GLPI notification queue?

Question

Helpdesk

Settings-Automatic actions-queuednotification
Frequency: Execution 5 min.
Status: planned
CLI execution method
In crontab it says */2 * * * * /usr/bin/php7.0 /var/www/site.ru/front/cron.php &>/dev/null
In general, everything works, messages they are sent from the queue, but often several messages freeze, and the script processes other messages (for example, a notification about the creation of a new application arrives), but the hung messages hang in the queue and are not sent.
But if you click Run in the automatic action from the browser , the messages will be sent.

Answer 1

The problem was in the timezone in the /etc/php/7.0/cli/php.ini file.
When executed from the browser, the /etc/php/7.0/apache2/php.ini file is used (which was configured and the time was correct)
And when run through the cli (php /var/www/glpi/front/cron.php --force queuednotification ) uses
/etc/php/7.0/cli/php.ini (which used a different timezone)
The second file (/etc/php/7.0/cli/php.ini ) was not changed when setting up the server, and the only thing I changed in it ends up being "date.timezone = ". set your timezone.
All of this is happening on Debian GNU/Linux 8.11 (jessie).
Based on: https://www.opennet.ru/openforum/vsluhforumID8/785...