Server: NC12.0.0 + PHP-fpm + Calender-App = 100% CPU usage

Created on 7 Jul 2017 · 23Comments · Source: nextcloud/server

Issue was originally posted here.

There are two forum topics about this malfunction:

bug dav

Source

hollerauer

Most helpful comment

I have submitted a PR at fruux/sabre-vobject#383.

mvdnes on 8 Jul 2017

👍3

All 23 comments

After a LOT of stepping, I have found the cause in my case.

For me, there is a recurring event in my calendar with the following rule:

array (
  'FREQ' => 'YEARLY',
  'BYYEARDAY' => '360',
  'INTERVAL' => '1',
)

This recurrence is wrong and highly unusual. It is december 26 on normal years, and december 25 on leap years.

When determining the next event a bug occurs here: [RRuleIterator].

$this->currentDate can (and is in my case) a DateTimeImmutable, so the calls to setDate, add and sub do not do anything. They should be of the form $date = $date->setDate(...).

Changing this seems to relieve all my errors.
I would like to submit a pull request for this bugfix, but am unsure where.

mvdnes on 8 Jul 2017

I have submitted a PR at fruux/sabre-vobject#383.

mvdnes on 8 Jul 2017

👍3

I confirm that this seems to solve my issue too.

loconox on 11 Jul 2017

Confirmed. Solves the 100% load (endless loop) issue as described here: https://help.nextcloud.com/t/after-update-11-0-3-to-12-final-from-beta-chan-calendar-loading-infinitly-and-php-fpm-100-cpu-usage/12876

nekudo on 15 Jul 2017

Confirmed. Thanks for the fix.

mikelupe on 4 Aug 2017

I can confirm the issue is still in Nextcloud 12.0.3, and this fix resolves the issue for me.

Sailing74 on 18 Oct 2017

Will nextcloud patch their version of vobject with https://github.com/sabre-io/vobject/pull/383 ? Or do we wait forever on sabre to merge this?

BlackIkeEagle on 5 Dec 2017

@here, since the fix is merged in sabre/vobject, could nextcloud make use of the 4.1.4 version ?

BlackIkeEagle on 22 Dec 2017

Workaround for now:
edit ./3rdparty/sabre/vobject/lib/Recur/RRuleIterator.php
and change the three lines like this commit does: here

cl445 on 30 Jan 2018

Yes, there are workarounds. The question is if Nextcloud will, at some point, include one of these into their project. The workaround you mentioned is from July 2017 already as well.

Sailing74 on 31 Jan 2018

This issue hasn't changed and still is around in NC 12.0.5 and I guess as well in 13.x. Are there plans to officially integrate the "workarounds"?

mikelupe on 9 Feb 2018

I can confirm that the issue is still present in NC 13.0.1, and the workaround seems to solve.
I hope it will be included into the next NC stable version

g4b0 on 30 Mar 2018

Just upgraded via several stops from NC10 to NC13 and ran into this issue. https://github.com/sabre-io/vobject/pull/383 fixes the issue. Would be great to have this integrated...

ghost on 27 Apr 2018

This issue is still affecting NC 13.0.2. I have confirmed the changes from sabre-io/vobject#383 fixes it for me using the latest official nextcloud docker container.
Given this is low hanging fruit for an extremely annoying problem, what would it take to get this resolved for the next point release of NC 13?
I also see this is flagged with the "dav" label, however I was able to reliably recreate the issue by visiting the calendar view of the web interface, with no DAV involved.

jinnko on 25 May 2018

It would really be nice if this was fixed... I'm not looking forward to edit php files after an update so calendar functionality remains usable.

ghost on 26 May 2018

Just updated to 13.0.4 and error is still there...

nekudo on 12 Jun 2018

https://github.com/nextcloud/3rdparty/tree/master/sabre has to be updated to the latest sabre code.
Unfortunately sabre is pretty much dead and I believe the nc devs just do not know how to proceed.

In any case an update to the 3rdparty repo with the latest sabre code would help a lot.