6.0.0-alpha14
7/3/25

[#14891] Kronolith hangs every time
Summary Kronolith hangs every time
Queue Kronolith
Queue Version 4.2.25
Type Bug
State No Feedback
Priority 1. Low
Owners
Requester lameventanas (at) gmail (dot) com
Created 01/30/2019 (2346 days ago)
Due
Updated 03/02/2019 (2315 days ago)
Assigned 01/31/2019 (2345 days ago)
Resolved 03/02/2019 (2315 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
03/02/2019 03:52:21 PM lameventanas (at) gmail (dot) com Comment #10 Reply to this comment
Did you also upgrade PHP in the mean time?
PHP version is 7.2.14.
03/02/2019 03:49:31 PM Michael Rubinsky State ⇒ No Feedback
 
02/12/2019 08:05:45 AM build+horde (at) de-korte (dot) org Comment #9 Reply to this comment
Did you also upgrade PHP in the mean time?
02/12/2019 06:48:53 AM lameventanas (at) gmail (dot) com Comment #8 Reply to this comment
Finally pear.php.net is back.
I updated everything to the latest version, problem is still there.
02/12/2019 05:03:17 AM lameventanas (at) gmail (dot) com Comment #7 Reply to this comment

[Show Quoted Text - 9 lines]
Horde_Timezone appears to be 1.1.0.

My OS timezone data is version 2018g (2018-10-27).

02/12/2019 03:56:28 AM Michael Rubinsky Comment #6 Reply to this comment
It sounds like it might be this one: https://bugs.horde.org/ticket/14752
It's not the same bug.

An event with event_timezone = 'America/New_York' causes the infinite loop.
If I change it to NULL or 'Asia/Tokyo' it doesn't happen.
What version is your Horde_Timezone package? You might also try to 
make sure that the timezone data is up to date.


02/12/2019 02:50:09 AM lameventanas (at) gmail (dot) com Comment #5 Reply to this comment
It sounds like it might be this one: https://bugs.horde.org/ticket/14752
It's not the same bug.

An event with event_timezone = 'America/New_York' causes the infinite loop.
If I change it to NULL or 'Asia/Tokyo' it doesn't happen.

02/11/2019 05:02:47 AM Michael Rubinsky Comment #4
Priority ⇒ 1. Low
Reply to this comment
Indeed there have been a few of these types of bugs fixed over the 
last year or so.

It sounds like it might be this one: https://bugs.horde.org/ticket/14752


01/31/2019 11:34:52 AM lameventanas (at) gmail (dot) com Comment #3 Reply to this comment
Before anything else, make sure you're running the latest version 
from PEAR. If the version in this report is correct, at least for 
Kronolith you're 2 releases behind.
Believe me, I have been trying to update to the latest version for a 
long time already, but it has been impossible.
First pear.horde.org had an expired certificate, and now pear.php.net 
doesn't work.  So there is no way to update and I don't know when it 
will be possible.

Automatic installation methods in general suck, there is no control.   
There should be a manual option.

Anyway, I filed this report because I was expecting this to be a bug 
due to some recurring event in the database, so maybe we can find it 
out and determine if it is still present in the latest version or not.
01/31/2019 10:30:14 AM Jan Schneider State ⇒ Feedback
 
01/30/2019 02:44:05 PM build+horde (at) de-korte (dot) org Comment #2 Reply to this comment
Before anything else, make sure you're running the latest version from 
PEAR. If the version in this report is correct, at least for Kronolith 
you're 2 releases behind.
01/30/2019 02:09:35 PM lameventanas (at) gmail (dot) com Comment #1
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Kronolith hangs every time
Type ⇒ Bug
Priority ⇒ 2. Medium
Reply to this comment
Kronolith causes a runaway process in my server until PHP hits the 
execution time limit.

Whenever I enter the monthly view, the "loading" icon shows 
indefinitely and the Apache process uses 100% of the CPU time.

After some experimentation I could trace it down to one particular 
calendar being enabled.  I have two other calendars (with events) that 
don't cause any problem.

The request that causes the problem is: POST 
/services/ajax.php/kronolith/listEvents

Saved Queries