We have moved at community.getvera.com

Author Topic: GCAL3 - General Discussion  (Read 192703 times)

guest141575

  • Guest
Re: GCAL3 - Google Calendar 3
« Reply #120 on: September 30, 2014, 01:57:50 pm »
Stuart, have a look at my calendar, especially at the blue ring. That's how it looked like this afternoon. Two groups (a and b) have lessons at the same time but the rightmost calendar event starts later and ends earlier.

I'm sure gc_EventsLeftToday had value 1 when I looked before today but I wasn't able to reproduce the problem this evening with 2 similar test events. If You can't see anything obvious in the schedule that the plugin can't handle maybe we just have to wait and see if it happens again.

(My GCal 3 plugin has gc_StartDelta and gc_EndDelta set to -60. gc_Interval is set to 1440)




Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - Google Calendar 3
« Reply #121 on: October 01, 2014, 12:00:21 am »
Stuart, have a look at my calendar, especially at the blue ring. That's how it looked like this afternoon. Two groups (a and b) have lessons at the same time but the rightmost calendar event starts later and ends earlier.

I'm sure gc_EventsLeftToday had value 1 when I looked before today but I wasn't able to reproduce the problem this evening with 2 similar test events. If You can't see anything obvious in the schedule that the plugin can't handle maybe we just have to wait and see if it happens again.

(My GCal 3 plugin has gc_StartDelta and gc_EndDelta set to -60. gc_Interval is set to 1440)

Looks like there was a timing issue because I had some <= and >= comparisons and depending on exactly when the check took place ....
I changed them to < and > and added in a second of leeway.  Seems to be working well now.   Let me know with this patched version.

Also here are my test results with two plugins: one with no start / end delta (Left0 --> EventsLeftToday) and one with start and end delta of -60 (Left60 --> EventsLeftToday)





« Last Edit: January 28, 2016, 07:11:39 pm by Stuart »

Offline Eldoctor62

  • Sr. Newbie
  • *
  • Posts: 23
  • Karma: +0/-0
Re: GCAL3 - Google Calendar 3
« Reply #122 on: October 01, 2014, 12:45:45 am »
Hi,

I installed a Gcal3 and everything worked well!
But today I installed 2 more ... And there Gcal3 is obviously much slower.
In the message I have. : Waiting for semaphore startup ... for 2 plug
Checking ... for 1 plug (I personally clicked)
After several "RELOAD" I have no change ...
Is this normal?

« Last Edit: October 01, 2014, 12:50:30 am by Eldoctor62 »

guest141575

  • Guest
Re: GCAL3 - Google Calendar 3
« Reply #123 on: October 01, 2014, 02:08:21 am »
Looks like there was a timing issue because I had some <= and >= comparisons and depending on exactly when the check took place ....
I changed them to < and > and added in a second of leeway.  Seems to be working well now.   Let me know with this patched version.

Also here are my test results with two plugins: one with no start / end delta (Left0 --> EventsLeftToday) and one with start and end delta of -60 (Left60 --> EventsLeftToday)

Thank You Stuart. Patched version is installed. I will let You know the results within a week :D

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - Google Calendar 3
« Reply #124 on: October 01, 2014, 09:37:40 am »
Hi,

I installed a Gcal3 and everything worked well!
But today I installed 2 more ... And there Gcal3 is obviously much slower.
In the message I have. : Waiting for semaphore startup ... for 2 plug
Checking ... for 1 plug (I personally clicked)
After several "RELOAD" I have no change ...
Is this normal?

Sorry that you are having trouble.  No it is not normal !  I routinely test with 3 plugins.   What version are you using ?  Are all three plugin instances pointing to the same calendar or different calendars ?    Do you have the same credentials set up for each calendar?

Please set gc_debug = 3 and get a log - this is the quickest way to figure out what's going on.   If you are unfamiliar with getting logs -- see the info here
http://forum.micasaverde.com/index.php/topic,26692.msg189513.html#msg189513

Offline Eldoctor62

  • Sr. Newbie
  • *
  • Posts: 23
  • Karma: +0/-0
Re: GCAL3 - Google Calendar 3
« Reply #125 on: October 02, 2014, 07:04:01 am »
Hello and thank you for your return

For the history I own Google calendar Switch ...
Before going on the market, I uploaded my Vera3 ui5 6 downloadable files on the first post.
After I installed from the market and everything went well for 3 plug ... I don uninstalled Google calendar switch. It was the day I was eui worries and since I tried the restoration of earlier dates but I have the same problem.
I think that there are corrupt files ...

I installed InfoViewer ...

In the log I have:
command ls etc/cmh-ludl/GCal3/ returned 0
checkin semaphore
command ls etc/cmh-ludl/GCal3/GCal3.sem returned 0
semaphore file returned '236
236 Blocked device semaphore request from semaphore 234

So I conclude that it is the 236 which pose problem ...

So I uninstalled all the device

But the problem is that I still have the same defect in the log ... I am surprised because the device is removed !!!
« Last Edit: October 02, 2014, 11:51:53 am by Eldoctor62 »

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - Google Calendar 3
« Reply #126 on: October 02, 2014, 12:39:38 pm »
Hello and thank you for your return

For the history I own Google calendar Switch ...
Before going on the market, I uploaded my Vera3 ui5 6 downloadable files on the first post.
After I installed from the market and everything went well for 3 plug ... I don uninstalled Google calendar switch. It was the day I was eui worries and since I tried the restoration of earlier dates but I have the same problem.
I think that there are corrupt files ...

I installed InfoViewer ...

In the log I have:
command ls etc/cmh-ludl/GCal3/ returned 0
checkin semaphore
command ls etc/cmh-ludl/GCal3/GCal3.sem returned 0
semaphore file returned '236
236 Blocked device semaphore request from semaphore 234

So I conclude that it is the 236 which pose problem ...

So I uninstalled all the device

But the problem is that I still have the same defect in the log ... I am surprised because the device is removed !!!

This looks like a problem that was in the 0.6x release which is fixed in the 0.7x release.
Can I suggest the following to make sure:
(1) delete the devices using the UI ( the garbage / trash can icon)
(2) run this code by going to Apps--> Develop Apps --> Test Luup Code (Lua).  It will remove all GCal files
(3) reinstall Google Calendar 3 from the marketplace
(4) go through the setup (i.e. upload your GCal3.json credentials file and the calendar url)

Code: [Select]
local result = os.execute("rm -rf /etc/cmh-ludl/*GCal*")

Offline Eldoctor62

  • Sr. Newbie
  • *
  • Posts: 23
  • Karma: +0/-0
Re: GCAL3 - Google Calendar 3
« Reply #127 on: October 02, 2014, 03:29:21 pm »
Wonderful !!!  :D

However I have installed version 0.7 ... Before I had not installed version 0.62

A little question : What address should we learn when we want to have a GCal3 with public holidays?

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - Google Calendar 3
« Reply #128 on: October 02, 2014, 03:56:38 pm »
Wonderful !!!  :D

However I have installed version 0.7 ... Before I had not installed version 0.62

A little question : What address should we learn when we want to have a GCal3 with public holidays?

So does 'Wonderful' mean it is now working ?  I hope so.

If you subscribe to a holiday calendar as described here
http://www.guidingtech.com/2329/add-public-holidays-google-calendar/
you can then get the calendar ID and use that in a plugin instance BUT it results in an error code - 401 unauthorized
So it seems that those calendars do not work with the authentication that google requires for personal calendars

The simplest way (I'm assuming it is simple) would be to import public holidays into your personal calendar.  You cannot just subscribe to a holiday calendar as these events do not show up when GCal3 searches your calendar.

If I find out a better way - I will post it.

Offline Eldoctor62

  • Sr. Newbie
  • *
  • Posts: 23
  • Karma: +0/-0
Re: GCAL3 - Google Calendar 3
« Reply #129 on: October 02, 2014, 04:07:29 pm »
Ok perfect! I started my installation start ...

I meet a new worry: - /

I have a module that says:

2/10/14 22: 00: 56 216 luup_log: 243 GCal3 gc_V 0.7.0: Device 243 Claimed semaphore

But stuck on Checking ...

Re-lock it after the other modules ... I am forced to mail another agenda that goes Successfully but the log file shows this address:

2/10/14 22: 03: 31 392 luup_log: 241: GCal3 gc_V 0.7.0: Device initializing # 241 <0x2b535680>
50 02/10/14 22: 03: 31 420 luup_log: 241: GCal3 gc_V 0.7.0: Command ls / etc / cmh-Ludl / GCal3 / returned '0 <0x2b535680>
50 02/10/14 22: 03: 31 421 luup_log: 241: GCal3 gc_V 0.7.0: Checking semaphore <0x2b535680>
50 02/10/14 22: 03: 31 447 luup_log: 241: GCal3 gc_V 0.7.0: Command ls-/etc/cmh ludl/GCal3/GCal3.sem returned '0 <0x2b535680>
50 02/10/14 22: 03: 31 449 luup_log: 241: GCal3 gc_V 0.7.0 Semaphore file returned '243 <0x2b535680>
50 02/10/14 22: 03: 31 475 luup_log: 241: GCal3 gc_V 0.7.0: Command ls-/etc/cmh ludl/GCal3/GCal3.sem returned '0 <0x2b535680>
50 02/10/14 22: 03: 31 475 luup_log: 241: GCal3 gc_V 0.7.0: Device 243 Blocked semaphore request from device 241 <0x2b535680>
50 02/10/14 22: 03: 31 482 luup_log: 242: GCal3 gc_V 0.7.0: Device initializing # 242 <0x2b535680>
50 02/10/14 22: 03: 31 511 luup_log: 242: GCal3 gc_V 0.7.0: Command ls / etc / cmh-Ludl / GCal3 / returned '0 <0x2b535680>
50 02/10/14 22: 03: 31 512 luup_log: 242: GCal3 gc_V 0.7.0: Checking semaphore <0x2b535680>

50 02/10/14 22: 03: 31 588 luup_log: 242: GCal3 gc_V 0.7.0: Command ls-/etc/cmh ludl/GCal3/GCal3.sem returned '0 <0x2b535680>
50 02/10/14 22: 03: 31.600 luup_log: 242: GCal3 gc_V 0.7.0 Semaphore file returned '243 <0x2b535680>

50 02/10/14 22: 03: 31 636 luup_log: 242: GCal3 gc_V 0.7.0: Command ls-/etc/cmh ludl/GCal3/GCal3.sem returned '0 <0x2b535680>
50 02/10/14 22: 03: 31 637 luup_log: 242: GCal3 gc_V 0.7.0: Device 243 Blocked semaphore request from device 242 <0x2b535680>
50 02/10/14 22: 03: 31 644 luup_log: 243 GCal3 gc_V 0.7.0: Device initializing # 243 <0x2b535680>

50 02/10/14 22: 03: 31.720 luup_log: 243 GCal3 gc_V 0.7.0: Command ls / etc / cmh-Ludl / GCal3 / returned '0 <0x2b535680>
50 02/10/14 22: 03: 31 721 luup_log: 243 GCal3 gc_V 0.7.0: Checking semaphore <0x2b535680>

50 02/10/14 22: 03: 31 801 luup_log: 243 GCal3 gc_V 0.7.0: Command ls-/etc/cmh ludl/GCal3/GCal3.sem returned '0 <0x2b535680>
50 02/10/14 22: 03: 31 813 luup_log: 243 GCal3 gc_V 0.7.0 Semaphore file returned '243 <0x2b535680>

50 02/10/14 22: 03: 31 890 luup_log: 243 GCal3 gc_V 0.7.0: Command ls-/etc/cmh ludl/GCal3/GCal3.sem returned '0 <0x2b535680>
50 02/10/14 22: 03: 31 891 luup_log: 243 GCal3 gc_V 0.7.0: Device 243 Claimed semaphore <0x2b535680>
50 02/10/14 22: 03: 31 915 luup_log: 243 GCal3 gc_V 0.7.0: 0.7.0 GCal3 gc_V: initialized variables ... <0x2b535680>

50 02/10/14 22: 03: 32 588 luup_log: 243 GCal3 gc_V 0.7.0: 0.7.0 GCal3 gc_V: Running Plugin ... <0x2b535680>
50 02/10/14 22: 03: 32 612 luup_log: 243 GCal3 gc_V 0.7.0: Device 243 released the semaphore - reason: initialization complete <0x2b535680>





50 02/10/14 22: 03: 34 310 luup_log: 243 GCal3 gc_V 0.7.0: Device 243 Claimed semaphore <0x30f35680>





50 02/10/14 22: 03: 41 109 luup_log: 242: GCal3 gc_V 0.7.0: Device # 242 initializing __LEAK__ this: 217088 start: 2183168 to 0x1990000 <0x30d35680>
50 02/10/14 22: 03: 41 116 luup_log: 241: GCal3 gc_V 0.7.0: Device initializing # 241 <0x30b35680>

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - Google Calendar 3
« Reply #130 on: October 02, 2014, 04:20:44 pm »
Ok perfect! I started my installation start ...

I meet a new worry: - /

I have a module that says:

2/10/14 22: 00: 56 216 luup_log: 243 GCal3 gc_V 0.7.0: Device 243 Claimed semaphore

But stuck on Checking ...


Ok - so what this is saying is that device 243 is trying to start and is blocking the others while it is trying - at a high level - this is ok.  Now we need to understand why that device is not starting correctly.   Since the order of startup can be random - we cannot assume it wil be the same device each time .....
So set gc_debug = 3 for all 3 plugins and try again - there will be much more log information but that will help track down why one of the devices is 'stuck' (and therefore blocking the others)

Offline Eldoctor62

  • Sr. Newbie
  • *
  • Posts: 23
  • Karma: +0/-0
Re: GCAL3 - Google Calendar 3
« Reply #131 on: October 02, 2014, 04:29:25 pm »
Ok thank you I understand;-)
so, ive got this:


50      10/02/14 22:24:33.168   luup_log:241: GCal3 gc_V 0.7.0:Device # 241 initializing <0x2b5db680>
50      10/02/14 22:24:33.197   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/ returned 0 <0x2b5db680>
50      10/02/14 22:24:33.197   luup_log:241: GCal3 gc_V 0.7.0:Checking semaphore <0x2b5db680>
50      10/02/14 22:24:33.223   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2b5db680>
50      10/02/14 22:24:33.225   luup_log:241: GCal3 gc_V 0.7.0:Semaphore file returned 0 <0x2b5db680>
50      10/02/14 22:24:33.226   luup_log:241: GCal3 gc_V 0.7.0:Device 241 requested semaphore <0x2b5db680>
50      10/02/14 22:24:33.252   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2b5db680>
50      10/02/14 22:24:33.253   luup_log:241: GCal3 gc_V 0.7.0:Device 241 claimed semaphore <0x2b5db680>
50      10/02/14 22:24:33.266   luup_log:241: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Variables initialized ... <0x2b5db680>
50      10/02/14 22:24:33.291   luup_log:241: GCal3 gc_V 0.7.0:Command ls /bin/bash returned 0 <0x2b5db680>
50      10/02/14 22:24:33.316   luup_log:241: GCal3 gc_V 0.7.0:Command ls /usr/lib/lua/googlejwt.sh returned 0 <0x2b5db680>

50      10/02/14 22:24:33.353   luup_log:241: GCal3 gc_V 0.7.0:Current version of /usr/lib/lua/googlejwt.sh is 0 <0x2b5db680>
50      10/02/14 22:24:33.378   luup_log:241: GCal3 gc_V 0.7.0:Command ls /usr/lib/lua/json.lua returned 0 <0x2b5db680>

50      10/02/14 22:24:33.450   luup_log:241: GCal3 gc_V 0.7.0:Existing openssl version is: 1.0.0d-1 <0x2b5db680>
50      10/02/14 22:24:33.450   luup_log:241: GCal3 gc_V 0.7.0:Function: checkforcredentials <0x2b5db680>
50      10/02/14 22:24:33.476   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3.json.lzo returned 256 <0x2b5db680>
50      10/02/14 22:24:33.502   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.pem returned 0 <0x2b5db680>
50      10/02/14 22:24:33.503   luup_log:241: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Timezone is 2 hrs and 0 min <0x2b5db680>
50      10/02/14 22:24:33.504   luup_log:241: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Running Plugin ... <0x2b5db680>
50      10/02/14 22:24:33.506   luup_log:241: GCal3 gc_V 0.7.0:Device 241 released the semaphore - reason: initialization complete <0x2b5db680>
50      10/02/14 22:24:33.511   luup_log:242: GCal3 gc_V 0.7.0:Device # 242 initializing <0x2b5db680>
50      10/02/14 22:24:33.537   luup_log:242: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/ returned 0 <0x2b5db680>
50      10/02/14 22:24:33.538   luup_log:242: GCal3 gc_V 0.7.0:Checking semaphore <0x2b5db680>
50      10/02/14 22:24:33.565   luup_log:242: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2b5db680>
50      10/02/14 22:24:33.566   luup_log:242: GCal3 gc_V 0.7.0:Semaphore file returned 0 <0x2b5db680>
50      10/02/14 22:24:33.568   luup_log:242: GCal3 gc_V 0.7.0:Device 242 requested semaphore <0x2b5db680>
50      10/02/14 22:24:33.593   luup_log:242: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2b5db680>
50      10/02/14 22:24:33.594   luup_log:242: GCal3 gc_V 0.7.0:Device 242 claimed semaphore <0x2b5db680>
50      10/02/14 22:24:33.606   luup_log:242: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Variables initialized ... <0x2b5db680>
50      10/02/14 22:24:33.632   luup_log:242: GCal3 gc_V 0.7.0:Command ls /bin/bash returned 0 <0x2b5db680>
50      10/02/14 22:24:33.657   luup_log:242: GCal3 gc_V 0.7.0:Command ls /usr/lib/lua/googlejwt.sh returned 0 <0x2b5db680>

50      10/02/14 22:24:33.693   luup_log:242: GCal3 gc_V 0.7.0:Current version of /usr/lib/lua/googlejwt.sh is 0 <0x2b5db680>
50      10/02/14 22:24:33.718   luup_log:242: GCal3 gc_V 0.7.0:Command ls /usr/lib/lua/json.lua returned 0 <0x2b5db680>

50      10/02/14 22:24:33.786   luup_log:242: GCal3 gc_V 0.7.0:Existing openssl version is: 1.0.0d-1 <0x2b5db680>
50      10/02/14 22:24:33.786   luup_log:242: GCal3 gc_V 0.7.0:Function: checkforcredentials <0x2b5db680>
50      10/02/14 22:24:33.812   luup_log:242: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3.json.lzo returned 256 <0x2b5db680>

50      10/02/14 22:24:33.867   luup_log:242: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.pem returned 0 <0x2b5db680>
50      10/02/14 22:24:33.868   luup_log:242: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Timezone is 2 hrs and 0 min <0x2b5db680>
50      10/02/14 22:24:33.868   luup_log:242: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Running Plugin ... <0x2b5db680>

50      10/02/14 22:24:33.913   luup_log:242: GCal3 gc_V 0.7.0:Device 242 released the semaphore - reason: initialization complete <0x2b5db680>
50      10/02/14 22:24:33.916   luup_log:243: GCal3 gc_V 0.7.0:Device # 243 initializing <0x2b5db680>

50      10/02/14 22:24:33.954   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/ returned 0 <0x2b5db680>
50      10/02/14 22:24:33.954   luup_log:243: GCal3 gc_V 0.7.0:Checking semaphore <0x2b5db680>
50      10/02/14 22:24:33.981   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2b5db680>
50      10/02/14 22:24:33.982   luup_log:243: GCal3 gc_V 0.7.0:Semaphore file returned 0 <0x2b5db680>
50      10/02/14 22:24:33.984   luup_log:243: GCal3 gc_V 0.7.0:Device 243 requested semaphore <0x2b5db680>

50      10/02/14 22:24:34.015   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2b5db680>
50      10/02/14 22:24:34.016   luup_log:243: GCal3 gc_V 0.7.0:Device 243 claimed semaphore <0x2b5db680>
50      10/02/14 22:24:34.028   luup_log:243: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Variables initialized ... <0x2b5db680>
50      10/02/14 22:24:34.054   luup_log:243: GCal3 gc_V 0.7.0:Command ls /bin/bash returned 0 <0x2b5db680>
50      10/02/14 22:24:34.079   luup_log:243: GCal3 gc_V 0.7.0:Command ls /usr/lib/lua/googlejwt.sh returned 0 <0x2b5db680>

50      10/02/14 22:24:34.134   luup_log:243: GCal3 gc_V 0.7.0:Current version of /usr/lib/lua/googlejwt.sh is 0 <0x2b5db680>

50      10/02/14 22:24:34.174   luup_log:243: GCal3 gc_V 0.7.0:Command ls /usr/lib/lua/json.lua returned 0 <0x2b5db680>

50      10/02/14 22:24:34.240   luup_log:243: GCal3 gc_V 0.7.0:Existing openssl version is: 1.0.0d-1 <0x2b5db680>
50      10/02/14 22:24:34.241   luup_log:243: GCal3 gc_V 0.7.0:Function: checkforcredentials <0x2b5db680>
50      10/02/14 22:24:34.266   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3.json.lzo returned 256 <0x2b5db680>
50      10/02/14 22:24:34.292   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.pem returned 0 <0x2b5db680>
50      10/02/14 22:24:34.293   luup_log:243: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Timezone is 2 hrs and 0 min <0x2b5db680>
50      10/02/14 22:24:34.293   luup_log:243: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Running Plugin ... <0x2b5db680>
50      10/02/14 22:24:34.295   luup_log:243: GCal3 gc_V 0.7.0:Device 243 released the semaphore - reason: initialization complete <0x2b5db680>

50      10/02/14 22:24:35.104   luup_log:241: GCal3 gc_V 0.7.0:Checking semaphore <0x30bdb680>
50      10/02/14 22:24:35.124   luup_log:242: GCal3 gc_V 0.7.0:Checking semaphore <0x30ddb680>

50      10/02/14 22:24:35.177   luup_log:242: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x30ddb680>
50      10/02/14 22:24:35.178   luup_log:242: GCal3 gc_V 0.7.0:Semaphore file returned 0 <0x30ddb680>
50      10/02/14 22:24:35.187   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x30bdb680>
50      10/02/14 22:24:35.188   luup_log:241: GCal3 gc_V 0.7.0:Semaphore file returned  <0x30bdb680>
50      10/02/14 22:24:35.211   luup_log:242: GCal3 gc_V 0.7.0:Device 242 requested semaphore <0x30ddb680>

50      10/02/14 22:24:35.248   luup_log:242: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x30ddb680>
50      10/02/14 22:24:35.248   luup_log:242: GCal3 gc_V 0.7.0:Device 242 claimed semaphore <0x30ddb680>
50      10/02/14 22:24:35.261   luup_log:242: GCal3 gc_V 0.7.0:StartMin is 2014-10-02T00:00:00.000Z StartMax is 2014-10-03T23:24:35.000Z <0x30ddb680>
50      10/02/14 22:24:35.286   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x30bdb680>
50      10/02/14 22:24:35.286   luup_log:241: GCal3 gc_V 0.7.0:Device 242 blocked semaphore request from device 241 <0x30bdb680>
50      10/02/14 22:24:35.288   luup_log:241: GCal3 gc_V 0.7.0:Next check will be in 5 sec on 2014-10-02 at 22:24:40 <0x30bdb680>

50      10/02/14 22:24:35.483   luup_log:242: GCal3 gc_V 0.7.0:Function: requestCalendar <0x30ddb680>

50      10/02/14 22:24:35.540   luup_log:242: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3242.token returned 0 <0x30ddb680>

50      10/02/14 22:24:36.103   luup_log:243: GCal3 gc_V 0.7.0:Checking semaphore <0x30fdb680>

50      10/02/14 22:24:36.137   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x30fdb680>
50      10/02/14 22:24:36.138   luup_log:243: GCal3 gc_V 0.7.0:Semaphore file returned 242 <0x30fdb680>

50      10/02/14 22:24:36.188   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x30fdb680>
50      10/02/14 22:24:36.188   luup_log:243: GCal3 gc_V 0.7.0:Device 242 blocked semaphore request from device 243 <0x30fdb680>
50      10/02/14 22:24:36.205   luup_log:243: GCal3 gc_V 0.7.0:Next check will be in 5 sec on 2014-10-02 at 22:24:41 <0x30fdb680>

50      10/02/14 22:24:36.425   luup_log:242: GCal3 gc_V 0.7.0:token info status: HTTP/1.1 200 OK <0x30ddb680>

50      10/02/14 22:24:36.463   luup_log:242: GCal3 gc_V 0.7.0:Token will expire in 1371 sec <0x30ddb680>
50      10/02/14 22:24:36.463   luup_log:242: GCal3 gc_V 0.7.0:Checking google calendar <0x30ddb680>
50      10/02/14 22:24:36.464   luup_log:242: GCal3 gc_V 0.7.0:Requested url: https://www.googleapis.com/calendar/v3/calendars/xxxxxxxxxxxxxxxxxxx@group.calendar.google.com/events?access_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxmH2&timeZone=utc&singleEvents=true&orderBy=startTime&timeMax=2014-10-03T23:24:35.000Z&timeMin=2014-10-02T00:00:00.000Z&fields=items(description%2Cend%2Cstart%2Csummary) <0x30ddb680>

50      10/02/14 22:24:36.928   luup_log:242: GCal3 gc_V 0.7.0:Calendar request status: HTTP/1.1 200 OK <0x30ddb680>
50      10/02/14 22:24:36.944   luup_log:242: GCal3 gc_V 0.7.0:Device 242 released the semaphore - reason: calendar check complete <0x30ddb680>
50      10/02/14 22:24:36.945   luup_log:242: GCal3 gc_V 0.7.0:Function: getEvents <0x30ddb680>
50      10/02/14 22:24:36.945   luup_log:242: GCal3 gc_V 0.7.0:There were 3 events retrieved <0x30ddb680>
50      10/02/14 22:24:36.947   luup_log:242: GCal3 gc_V 0.7.0:Effective Event Name A[0,0]{} <0x30ddb680>
50      10/02/14 22:24:36.960   luup_log:242: GCal3 gc_V 0.7.0:Effective Event Name VERTS[0,0]{} <0x30ddb680>
50      10/02/14 22:24:36.962   luup_log:242: GCal3 gc_V 0.7.0:Effective Event Name M[0,0]{} <0x30ddb680>
50      10/02/14 22:24:36.963   luup_log:242: GCal3 gc_V 0.7.0:Function: saveEvents <0x30ddb680>
50      10/02/14 22:24:36.964   luup_log:242: GCal3 gc_V 0.7.0:Active Events: A , VERTS <0x30ddb680>

50      10/02/14 22:24:37.022   luup_log:242: GCal3 gc_V 0.7.0:json event list [{'eventEnd':1412287200,'eventStart':1412200800,'eventParameter':'','eventName':'A'},{'eventEnd':1412287200,'eventStart':1412200800,'eventParameter':'','eventName':'VERTS'},{'eventEnd':1412373600,'eventStart':1412287200,'eventParameter':'','eventName':'M'}] <0x30ddb680>
50      10/02/14 22:24:37.024   luup_log:242: GCal3 gc_V 0.7.0:json active event list [{'eventParameter':'','eventName':'A'},{'eventParameter':'','eventName':'VERTS'}] <0x30ddb680>
50      10/02/14 22:24:37.025   luup_log:242: GCal3 gc_V 0.7.0:Function: getjsonEvents <0x30ddb680>
50      10/02/14 22:24:37.040   luup_log:242: GCal3 gc_V 0.7.0:Event 1: On 2014-10-02 event A will start at 00:00:00 and end at 00:00:00 <0x30ddb680>
50      10/02/14 22:24:37.044   luup_log:242: GCal3 gc_V 0.7.0:Event 2: On 2014-10-02 event VERTS will start at 00:00:00 and end at 00:00:00 <0x30ddb680>
50      10/02/14 22:24:37.045   luup_log:242: GCal3 gc_V 0.7.0:Event 3: On 2014-10-03 event M will start at 00:00:00 and end at 00:00:00 <0x30ddb680>
50      10/02/14 22:24:37.047   luup_log:242: GCal3 gc_V 0.7.0:Next Event: A -- 00:00 Oct 02 to 00:00 Oct 03 <0x30ddb680>
50      10/02/14 22:24:37.048   luup_log:242: GCal3 gc_V 0.7.0:Event-Start A 10/02 00:00 is already Active <0x30ddb680>
50      10/02/14 22:24:37.050   luup_log:242: GCal3 gc_V 0.7.0:Next check will be in 5724 sec on 2014-10-03 at 00:00:00 <0x30ddb680>





50      10/02/14 22:24:40.102   luup_log:241: GCal3 gc_V 0.7.0:Checking semaphore <0x30bdb680>
50      10/02/14 22:24:40.127   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x30bdb680>
50      10/02/14 22:24:40.128   luup_log:241: GCal3 gc_V 0.7.0:Semaphore file returned 0 <0x30bdb680>
50      10/02/14 22:24:40.130   luup_log:241: GCal3 gc_V 0.7.0:Device 241 requested semaphore <0x30bdb680>
50      10/02/14 22:24:40.155   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x30bdb680>
50      10/02/14 22:24:40.156   luup_log:241: GCal3 gc_V 0.7.0:Device 241 claimed semaphore <0x30bdb680>
50      10/02/14 22:24:40.157   luup_log:241: GCal3 gc_V 0.7.0:StartMin is 2014-10-02T00:00:00.000Z StartMax is 2014-10-03T23:24:40.000Z <0x30bdb680>

50      10/02/14 22:24:40.299   luup_log:241: GCal3 gc_V 0.7.0:Function: requestCalendar __LEAK__ this:49152 start:1654784 to 0x1c03000 <0x30bdb680>
50      10/02/14 22:24:40.325   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3241.token returned 0 <0x30bdb680>

50      10/02/14 22:24:41.102   luup_log:243: GCal3 gc_V 0.7.0:Checking semaphore <0x30fdb680>
50      10/02/14 22:24:41.128   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x30fdb680>
50      10/02/14 22:24:41.130   luup_log:243: GCal3 gc_V 0.7.0:Semaphore file returned 241 <0x30fdb680>

50      10/02/14 22:24:41.176   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x30fdb680>
50      10/02/14 22:24:41.177   luup_log:243: GCal3 gc_V 0.7.0:Device 241 blocked semaphore request from device 243 <0x30fdb680>
50      10/02/14 22:24:41.178   luup_log:243: GCal3 gc_V 0.7.0:Next check will be in 5 sec on 2014-10-02 at 22:24:46 <0x30fdb680>

50      10/02/14 22:24:41.256   luup_log:241: GCal3 gc_V 0.7.0:token info status: HTTP/1.1 200 OK <0x30bdb680>
50      10/02/14 22:24:41.270   luup_log:241: GCal3 gc_V 0.7.0:Token will expire in 1040 sec <0x30bdb680>
50      10/02/14 22:24:41.271   luup_log:241: GCal3 gc_V 0.7.0:Checking google calendar <0x30bdb680>
50      10/02/14 22:24:41.271   luup_log:241: GCal3 gc_V 0.7.0:Requested url: https://www.googleapis.com/calendar/v3/calendars/xxxxxxxxxxxxxxx@group.calendar.google.com/events?access_token=xxxxxxxxxxxxxxxxxxxxxxxxx&timeZone=utc&singleEvents=true&orderBy=startTime&timeMax=2014-10-03T23:24:40.000Z&timeMin=2014-10-02T00:00:00.000Z&fields=items(description%2Cend%2Cstart%2Csummary) <0x30bdb680>





50      10/02/14 22:24:42.578   luup_log:241: GCal3 gc_V 0.7.0:Calendar request status: HTTP/1.1 200 OK __LEAK__ this:81920 start:1961984 to 0x1c4e000 <0x30bdb680>
50      10/02/14 22:24:42.584   luup_log:241: GCal3 gc_V 0.7.0:Device 241 released the semaphore - reason: calendar check complete <0x30bdb680>
50      10/02/14 22:24:42.584   luup_log:241: GCal3 gc_V 0.7.0:Function: getEvents <0x30bdb680>
50      10/02/14 22:24:42.585   luup_log:241: GCal3 gc_V 0.7.0:There were 2 events retrieved <0x30bdb680>
50      10/02/14 22:24:42.587   luup_log:241: GCal3 gc_V 0.7.0:Effective Event Name J[0,0]{} <0x30bdb680>
50      10/02/14 22:24:42.590   luup_log:241: GCal3 gc_V 0.7.0:Effective Event Name M[0,0]{} <0x30bdb680>
50      10/02/14 22:24:42.591   luup_log:241: GCal3 gc_V 0.7.0:Function: saveEvents <0x30bdb680>
50      10/02/14 22:24:42.592   luup_log:241: GCal3 gc_V 0.7.0:Active Events: J <0x30bdb680>

Offline Eldoctor62

  • Sr. Newbie
  • *
  • Posts: 23
  • Karma: +0/-0
Re: GCAL3 - Google Calendar 3
« Reply #132 on: October 02, 2014, 04:33:38 pm »
If i make a reload i've got this :

50      10/02/14 22:32:15.136   luup_log:241: GCal3 gc_V 0.7.0:Device # 241 initializing <0x2c3b7680>
50      10/02/14 22:32:15.164   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/ returned 0 <0x2c3b7680>
50      10/02/14 22:32:15.165   luup_log:241: GCal3 gc_V 0.7.0:Checking semaphore <0x2c3b7680>
50      10/02/14 22:32:15.193   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2c3b7680>
50      10/02/14 22:32:15.194   luup_log:241: GCal3 gc_V 0.7.0:Semaphore file returned 243 <0x2c3b7680>

50      10/02/14 22:32:15.238   luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 __LEAK__ this:53248 start:471040 to 0x1ca5000 <0x2c3b7680>
50      10/02/14 22:32:15.249   luup_log:241: GCal3 gc_V 0.7.0:Device 243 blocked semaphore request from device 241 __LEAK__ this:69632 start:540672 to 0x1cb6000 <0x2c3b7680>

50      10/02/14 22:32:15.366   luup_log:242: GCal3 gc_V 0.7.0:Device # 242 initializing <0x2c3b7680>

50      10/02/14 22:32:15.430   luup_log:242: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/ returned 0 __LEAK__ this:163840 start:2027520 to 0x1e21000 <0x2c3b7680>
50      10/02/14 22:32:15.431   luup_log:242: GCal3 gc_V 0.7.0:Checking semaphore <0x2c3b7680>

50      10/02/14 22:32:15.496   luup_log:242: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2c3b7680>
50      10/02/14 22:32:15.497   luup_log:242: GCal3 gc_V 0.7.0:Semaphore file returned 243 <0x2c3b7680>

50      10/02/14 22:32:15.548   luup_log:242: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2c3b7680>
50      10/02/14 22:32:15.552   luup_log:242: GCal3 gc_V 0.7.0:Device 243 blocked semaphore request from device 242 <0x2c3b7680>
50      10/02/14 22:32:15.558   luup_log:243: GCal3 gc_V 0.7.0:Device # 243 initializing <0x2c3b7680>

50      10/02/14 22:32:15.612   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/ returned 0 <0x2c3b7680>
50      10/02/14 22:32:15.612   luup_log:243: GCal3 gc_V 0.7.0:Checking semaphore <0x2c3b7680>

50      10/02/14 22:32:15.668   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 __LEAK__ this:184320 start:2211840 to 0x1e4e000 <0x2c3b7680>

50      10/02/14 22:32:15.702   luup_log:243: GCal3 gc_V 0.7.0:Semaphore file returned 243 <0x2c3b7680>

50      10/02/14 22:32:15.773   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2c3b7680>
50      10/02/14 22:32:15.774   luup_log:243: GCal3 gc_V 0.7.0:Device 243 claimed semaphore <0x2c3b7680>
50      10/02/14 22:32:15.785   luup_log:243: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Variables initialized ... <0x2c3b7680>

50      10/02/14 22:32:15.825   luup_log:243: GCal3 gc_V 0.7.0:Command ls /bin/bash returned 0 <0x2c3b7680>

50      10/02/14 22:32:15.863   luup_log:243: GCal3 gc_V 0.7.0:Command ls /usr/lib/lua/googlejwt.sh returned 0 <0x2c3b7680>

50      10/02/14 22:32:15.915   luup_log:243: GCal3 gc_V 0.7.0:Current version of /usr/lib/lua/googlejwt.sh is 0 <0x2c3b7680>
50      10/02/14 22:32:15.944   luup_log:243: GCal3 gc_V 0.7.0:Command ls /usr/lib/lua/json.lua returned 0 <0x2c3b7680>

50      10/02/14 22:32:16.011   luup_log:243: GCal3 gc_V 0.7.0:Existing openssl version is: 1.0.0d-1 <0x2c3b7680>
50      10/02/14 22:32:16.011   luup_log:243: GCal3 gc_V 0.7.0:Function: checkforcredentials <0x2c3b7680>
50      10/02/14 22:32:16.037   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3.json.lzo returned 256 <0x2c3b7680>
50      10/02/14 22:32:16.065   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.pem returned 0 <0x2c3b7680>
50      10/02/14 22:32:16.066   luup_log:243: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Timezone is 2 hrs and 0 min <0x2c3b7680>
50      10/02/14 22:32:16.067   luup_log:243: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Running Plugin ... <0x2c3b7680>
50      10/02/14 22:32:16.068   luup_log:243: GCal3 gc_V 0.7.0:Device 243 released the semaphore - reason: initialization complete <0x2c3b7680>

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - Google Calendar 3
« Reply #133 on: October 02, 2014, 05:14:55 pm »
If i make a reload i've got this :

.......................................
.......................................

50      10/02/14 22:32:15.558   luup_log:243: GCal3 gc_V 0.7.0:Device # 243 initializing <0x2c3b7680>

50      10/02/14 22:32:15.612   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/ returned 0 <0x2c3b7680>
50      10/02/14 22:32:15.612   luup_log:243: GCal3 gc_V 0.7.0:Checking semaphore <0x2c3b7680>

50      10/02/14 22:32:15.668   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 __LEAK__ this:184320 start:2211840 to 0x1e4e000 <0x2c3b7680>

50      10/02/14 22:32:15.702   luup_log:243: GCal3 gc_V 0.7.0:Semaphore file returned 243 <0x2c3b7680>

50      10/02/14 22:32:15.773   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2c3b7680>
50      10/02/14 22:32:15.774   luup_log:243: GCal3 gc_V 0.7.0:Device 243 claimed semaphore <0x2c3b7680>
50      10/02/14 22:32:15.785   luup_log:243: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Variables initialized ... <0x2c3b7680>

50      10/02/14 22:32:15.825   luup_log:243: GCal3 gc_V 0.7.0:Command ls /bin/bash returned 0 <0x2c3b7680>

50      10/02/14 22:32:15.863   luup_log:243: GCal3 gc_V 0.7.0:Command ls /usr/lib/lua/googlejwt.sh returned 0 <0x2c3b7680>

50      10/02/14 22:32:15.915   luup_log:243: GCal3 gc_V 0.7.0:Current version of /usr/lib/lua/googlejwt.sh is 0 <0x2c3b7680>
50      10/02/14 22:32:15.944   luup_log:243: GCal3 gc_V 0.7.0:Command ls /usr/lib/lua/json.lua returned 0 <0x2c3b7680>

50      10/02/14 22:32:16.011   luup_log:243: GCal3 gc_V 0.7.0:Existing openssl version is: 1.0.0d-1 <0x2c3b7680>
50      10/02/14 22:32:16.011   luup_log:243: GCal3 gc_V 0.7.0:Function: checkforcredentials <0x2c3b7680>
50      10/02/14 22:32:16.037   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3.json.lzo returned 256 <0x2c3b7680>
50      10/02/14 22:32:16.065   luup_log:243: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3.pem returned 0 <0x2c3b7680>
50      10/02/14 22:32:16.066   luup_log:243: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Timezone is 2 hrs and 0 min <0x2c3b7680>
50      10/02/14 22:32:16.067   luup_log:243: GCal3 gc_V 0.7.0:GCal3 gc_V 0.7.0:Running Plugin ... <0x2c3b7680>
50      10/02/14 22:32:16.068   luup_log:243: GCal3 gc_V 0.7.0:Device 243 released the semaphore - reason: initialization complete <0x2c3b7680>

This looks more-or-less normal in the sense that the semaphore (probably just before the refresh) was claimed by device 243.  The other two devices were trying to startup but had to wait on 243.   The last lines show that 243 completed it's initialization and then released the semaphore.   What happened next ?   If 243 got 'lucky' and tried to get calendar info it would show as checking but there would be log info that tells us where / if it got 'stuck (again ?).   If not 243 then one of the others would have claimed the semaphore and initialized.

Need to see the rest of the log ......  The semaphore and blocking is not the problem.  It's working as it should - something else is getting in the way.

Offline Eldoctor62

  • Sr. Newbie
  • *
  • Posts: 23
  • Karma: +0/-0
Re: GCAL3 - Google Calendar 3
« Reply #134 on: October 02, 2014, 11:20:36 pm »
I started from the beginning ... By removing all ...
I recreated a module (241) with my calendar, default was GCal3241.token ??
After a reload Successfully initialized (but blocked)  He tells me it is retained after a check.

50      10/03/14 5:16:01.701    luup_log:241: GCal3 gc_V 0.7.0:Command ls /etc/cmh-ludl/GCal3/GCal3241.token returned 0 <0x30d4b680>

I feel that it comes from my google calendar but I do not understand because I do not have defects in .log

In fact I have two calendars that work well ...
All other even if I create them ask me problems.

I was wondering if it's because they had no event the day before or after ...

So I add "test" with recursion each day and the module works !!!!

Is there a minimum time between two events?

After my test if I do not program some thing 24 hours after the current day, the plug gets stuck on "Checking ..."

we advance ?
« Last Edit: October 03, 2014, 12:20:43 am by Eldoctor62 »