Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-19024

iCal calendar broken since 14.0.6

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Calendar
    • Labels:
      None
    • ToDo:
    • Asterisk Version:
      13
    • Distro Version:
      12.7.4-1710-2.sng7
    • Distro:
      FreePBX Distro

      Description

      Greetings,

       

      I am sorry for reopening this issue. 'see bug 14.0.6 which is now closed.

      I had only time to go through this error in detail today.

       

      The issue:

      Before 14.0.7 of the calendar module, i cal imports caused high loads (I'm talking 400k i/o)

      AFTER installing the update:

      • The load dropped to 40k i/o operations. 
      • checking the calendar it SHOWS the correct data: all previous entries are deleted and it doesn't go so far in the future anymore.
      • However: Time conditions depending on the calendar go to "false". 

       

      I have reproduced this on 3 machines, all with the same error. 

      I have used outlook ical files, and also google calendar ical files. They both seem to be imported correctly. 

      Then i did a test to create an entirely new calendar, I even trief using a LOCAL calendar and even these are ignored. So the problem doesn't see mto be the ical file. But the way the calendar is checked.

      So i went to the logs. And then downgraded. Now there is a huge difference in output.

      (I'll save the logs in case more info is needed)

       

      USING 14.0.6:

      
      [2019-01-23 11:58:23] VERBOSE[25789][C-0005dc66] res_agi.c: Launched AGI Script /var/lib/asterisk/agi-bin/calendar.agi
       [2019-01-23 11:58:23] VERBOSE[25789][C-0005dc66] res_agi.c: calendar.agi,calendar,goto,c70c6d57-5e3d-4933-a406-47430ce7e19e,default,dHJ1ZXN0YXRl,ZmFsc2VzdGF0ZQ==: Checking Calendar
       [2019-01-23 11:58:23] VERBOSE[25789][C-0005dc66] res_agi.c: calendar.agi,calendar,goto,c70c6d57-5e3d-4933-a406-47430ce7e19e,default,dHJ1ZXN0YXRl,ZmFsc2VzdGF0ZQ==: Calendar: False
       [2019-01-23 11:58:23] VERBOSE[25789][C-0005dc66] res_agi.c: calendar.agi,calendar,goto,c70c6d57-5e3d-4933-a406-47430ce7e19e,default,dHJ1ZXN0YXRl,ZmFsc2VzdGF0ZQ==: Goto:falsestate
       [2019-01-23 11:58:23] VERBOSE[25789][C-0005dc66] res_agi.c: AGI Script Executing Application: (Goto) Options: (falsestate)
       [2019-01-23 11:58:23] VERBOSE[25789][C-0005dc66] pbx_builtins.c: Goto (timeconditions,2,4)
       [2019-01-23 11:58:23] VERBOSE[25789][C-0005dc66] res_agi.c: <SIP/3starsnet 1-00004797>AGI Script calendar.agi completed, returning 0
      

      USING 14.0.9 (latest)

      
      [2019-01-23 11:36:34] VERBOSE[21674][C-0005dc5d] res_agi.c: Launched AGI Script /var/lib/asterisk/agi-bin/calendar.agi
       [2019-01-23 11:36:34] VERBOSE[21674][C-0005dc5d] res_agi.c: calendar.agi,calendar,goto,ae95a02f-1b25-4418-8868-317478378252,default,dHJ1ZXN0YXRl,ZmFsc2VzdGF0ZQ==: Checking Calendar
       [2019-01-23 11:36:34] VERBOSE[21674][C-0005dc5d] res_agi.c: <SIP/3starsnet 1-00004784>AGI Script calendar.agi completed, returning 0
      

       

      IF this is a support problem, I will make contact with sangoma support to resolve this but:

      Since the problem is reproducable on at least 3 systems. It worked perfectly before, I believe this is a bug. 

      If more info is needed I am happy to help. 

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  arnoutvdk arnoutvdk
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    NextupJiraPlusStatus

                    Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.