Forum GLPI-Project

GAESI

Member

Registered: 2020-10-01

Posts: 6

[Resolved] The INTERVAL rule part must be a positive integer (> 0)

Hi there,

I am having problems with GLPI when editing tickets.

Information :
GLPI Version: 10.0.2
Plugin:
- Fusion inventory
- Credits
- Dashboard
- FormCreation
- TaskDrop

Last week, I could not schedule a task after the date of August 1, 2022, it is August 1, 2022 and I cannot schedule a ticket task and cannot modify tickets.

Each change displays this message:

Uncaught Exception InvalidArgumentException: The INTERVAL rule part must be a positive integer (> 0) in /var/www/glpi/vendor/rlanvin/php-rrule/src/RRule.php at line 254

In the logs I get this message:

[2022-08-01 10:20:00] glpiphplog.CRITICAL: *** Uncaught Exception InvalidArgumentException: The INTERVAL rule part must be a positive integer (> 0) in /var/www/glpi/vendor/rlanvin/php- rrule/src/RRule.php at line 254
  Backtrace:
  src/Features/PlanningEvent.php:925 RRule\RRule->__construct()
  src/Features/PlanningEvent.php:606 PlanningExternalEvent::getRsetFromRRuleField()
  src/Planning.php:290 PlanningExternalEvent::populatePlanning()
  src/CommonITILTask.php:322 Planning::checkAlreadyPlanned()
  src/CommonDBTM.php:1572 CommonITILTask->prepareInputForUpdate()
  front/commonitiltask.form.php:94 CommonDBTM->update()
  front/tickettsk.form.php:39 include()

Obviously in the RRule.php file the variable $parts['INTERVAL'] returns the value 0

I don't understand where the problem comes from, I deactivated my plugins but that doesn't change anything.

I updated GLPI v9.5 to GLPI v10.0.2, but that doesn't change anything either.

I even did a brand new installation of GLPI, then I connected it to my GLPI database and I still encounter the problem.

Looking forward to your feedback and your help, thank you in advance!

Last edited by GAESI (2022-08-02 09:48:35)

GAESI

Member

Registered: 2020-10-01

Posts: 6

Re: [Resolved] The INTERVAL rule part must be a positive integer (> 0)

Hi there,

Following my topic on Github, the user "cedric-anne'" gave me an answer (thanks to him) : Github GLPi issues 12356

If you run the following query :

SELECT `id`, `rrule` FROM `glpi_planningexternalevents` WHERE `rrule` != ''

you will get a query response like this :

1 	{"freq":"daily","interval":"1","until":"2020-12-05...
4 	{"freq":"daily","interval":"1","until":"2021-02-13...
5 	{"freq":"daily","interval":"1","until":"2021-05-01...
[...]
115 	{"freq":"daily","interval":"1","until":"2022-01-30...
116 	{"freq":"daily","interval":"1","until":"2022-04-17...
117 	{"freq":"daily","interval":"1","until":"2022-07-03...
218 	{"freq":"monthly","interval":"0","until":""}

here, my problem came from the entry with the id 218 which had an interval of 0

So I corrected from the database this value to "1".

Since then, my problem has been solved.

This error can occur if you create an external task, which repeats itself with an interval of "0" (yes the option exists, that's what caused the problem for us)

Last edited by GAESI (2022-08-02 09:49:38)