Forum GLPI-Project

louiszavier

Member

Registered: 2012-05-15

Posts: 2

[GLPI] Monitoring of automatic actions

Hi everyone!

I really appreciate if someone here could help me out with this issue I'm experiencing.  Even after upgraded version 80.7 to 83.1, I'm still getting this error.

Below is the exact error I'm getting:

The following automatic actions are in error. They require intervention.

mailgate : Retrieve email (Mail receivers)

Your help is greatly appreciated!

Thanks,
LZ

yllen

GLPI-DEV

From: Sillery (51)

Registered: 2008-01-14

Posts: 15,278

Re: [GLPI] Monitoring of automatic actions

Verify the configuration of your mail receivers

---

CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6  - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)

louiszavier

Member

Registered: 2012-05-15

Posts: 2

Re: [GLPI] Monitoring of automatic actions

Verify the configuration of your mail receivers

It was working for about a week when I first set it up on v80.7, but then the error mentioned started kicking in. Given that I can't attach a snapshot of my Receiver here so I'm just going to list the settings out:

Name (Email address): helpdesk@mydomain.com
Ative: Yes
Server: Exchange IP
Connection options: IMAP
Mail folder: Inbox
Port (optional): 143
Connection string: {192.168.0.x:143/imap}Inbox
Login: helpdesk

Or should I be looking into cron job/task and if so what should I be looking at?

Your help is greatly appreciated!

LV

kriber

Member

From: Germany

Registered: 2010-12-10

Posts: 16

Re: [GLPI] Monitoring of automatic actions

hi

similar problem here.

GLPI-Ticket:
   
[GLPI] Monitoring of automatic actions
The following automatic actions are in error. They require intervention.
closeticket : Automatischer Abschluss der Tickets (=Automatic tickets closing)[edit]

Job Info/Config:

Name :     closeticket    Comments :    
Description :     Automatic tickets closing
Run frequency :    
Status :    
Run mode :    
Run period :      ->
Number of days this action logs are stored :         Last run :     29-05-2012 08:58 Blank
         Next run :     29-05-2012 12:58 - Execute

Statistics :

Run count :     488
Start date :     15-11-2011 11:48
Minimal time :     0.00 Sec(s)
Maximal time :     161.15 Sec(s)
Average time :     1.92 Sec(s)
Total duration :     939.34 Sec(s)
Minimal count :     0 Elements
Maximal count :     58 Elements
Average count :     1.21 Elements
Total count :     589 Elements
Average speed :     0.63 Elements / Sec(s)

Protocoll:
29-05-2012 08:58    0.014s    0    Job done, nothing to do
29-05-2012 04:58    0.034s    0    Job done, nothing to do
29-05-2012 00:56    7.195s    7    Job done, complete execute
28-05-2012 20:56    0.036s    0    Job done, nothing to do
28-05-2012 16:54    0.013s    0    Job done, nothing to do
28-05-2012 12:54    0.034s    0    Job done, nothing to do
28-05-2012 08:52    0.013s    0    Job done, nothing to do
28-05-2012 04:52    0.025s    0    Job done, nothing to do
28-05-2012 00:50    15.564s    9    Job fertig, complete execute
27-05-2012 20:50    0.024s    0    Job done, nothing to do
27-05-2012 16:48    0.013s    0    Job done, nothing to do
27-05-2012 12:48    0.039s    0    Job done, nothing to do
27-05-2012 08:46    0.013s    0    Job done, nothing to do
27-05-2012 04:46    0.028s    0    Job done, nothing to do
27-05-2012 00:44    11.136s    4    Job fertig, complete execute
....

these things look ok, I think, cron job is also doing well... why do I get this ticket?

thanks kriber

Last edited by kriber (2012-05-29 11:44:30)

---

GLPI 0.80.5 | Ubuntu Server 10.04.1 lts | Apache 2.2.14 | PHP 5.3.2-1 | MySQL  5.1.41