Forum GLPI-Project

GillesZoratti

Member

From: Luxembourg

Registered: 2019-05-06

Posts: 19

[GLPI 9.5] -Mailgate erreur - S'exécute mais ne termine jamais son job

Bonjour,

depuis la migration de glpi 9.4.6 vers 9.5,
l'action automatique mailgate rencontre des problèmes.
Erreur:
L'action automatique se lance, mais ne se termine "jamais" elle reste en running, du coup elle reste totalement bloqué dans se status .

OS:
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

Php --version:
PHP 7.4.7 (cli) (built: Jun 12 2020 07:47:45) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.7, Copyright (c), by Zend Technologies

Error Log:
[Fri Jul 10 12:44:30.919120 2020] [php7:notice] [pid 1731] [client 148.110.18.74:55635] PHP Notice:  Undefined index: users_id in /var/www/html/glpi/inc/mailcollector.class.php on line 741, referer: https://glpi.cgdis.lu/front/crontask.form.php?id=9
[Fri Jul 10 12:44:30.919178 2020] [php7:notice] [pid 1731] [client 148.110.18.74:55635] PHP Notice:  Undefined index: _users_id_requester_notif in /var/www/html/glpi/inc/mailcollector.class.php on line 746, referer: https://glpi.cgdis.lu/front/crontask.form.php?id=9
[Fri Jul 10 12:44:30.919205 2020] [php7:notice] [pid 1731] [client 148.110.18.74:55635] PHP Notice:  Trying to access array offset on value of type null in /var/www/html/glpi/inc/mailcollector.class.php on line 746, referer: https://glpi.cgdis.lu/front/crontask.form.php?id=9
[Fri Jul 10 12:44:30.919228 2020] [php7:notice] [pid 1731] [client 148.110.18.74:55635] PHP Notice:  Trying to access array offset on value of type null in /var/www/html/glpi/inc/mailcollector.class.php on line 746, referer: https://glpi.cgdis.lu/front/crontask.form.php?id=9

Last edited by GillesZoratti (2020-07-10 12:58:15)

GillesZoratti

Member

From: Luxembourg

Registered: 2019-05-06

Posts: 19

Re: [GLPI 9.5] -Mailgate erreur - S'exécute mais ne termine jamais son job

Désolé, je créé des tickets trop rapidement
j'ai trouvé le problème est isoler sur un receiver qui n'arrive à faire son job correctement donc je pense qui ne retourne pas de 1 ou 0