 |
Forums |
Admin Discussion Forums: help Start New Thread
By: Scott Woodcock
 RE: Getting timeout errors - from where? [ reply ]
2010-06-25 17:04
|
I am still getting the timeout issue with the stand-alone version (ncal2gcal-0.1.6) - hoping that this may shed light on the root cause....
I have verified that I can get to my Google Calendar from my work PC (where my Lotus notes database archive is stored), but only with Internet Explorer and not Google Chrome. When I use Internet Explorer (7.0), I use the following URL: "http://www.google.com/calendar"; and then the browser changes that to "http://www.google.com/calendar/render"; and I have full access to my Google calendar.
However, when I put "http://www.google.com/calendar"; into Google Chrome browser, the browser then starts going into this infinite "redircting" loop with the following URL in the address bar: "https://www.google.com/accounts/ServiceLogin?service=cl&passive=1209600&continue=http://www.google.com/calendar/render%3Fgsessionid%3DY-G57JCnCq9HHe_14yXWHQ%26pli%3D1&followup=http://www.google.com/calendar";
I've tried to use different URLs and have clicked thru the "more" menu to get to the calendar from http://www.google.com (after I'm already logged-in to Google within Chrome), but everything I try results in that same infinite redirecting loop.
Again, I think some evil forces are at work here on my company network, and I wonder if the infinte redirecting loop that i'm seeing with Chrome is happening to ncal2gcal.
Output from attempt below:
C:/ncal2gcal/lib/ruby/1.8/net/http.rb:560:in `initialize': A connection attempt
failed because the connected party did not properly respond after a period of ti
me, or established connection failed because connected host has failed to respon
d. - connect(2) (Errno::ETIMEDOUT)
from C:/ncal2gcal/lib/ruby/1.8/net/http.rb:560:in `open'
from C:/ncal2gcal/lib/ruby/1.8/net/http.rb:560:in `connect'
from C:/ncal2gcal/lib/ruby/1.8/timeout.rb:53:in `timeout'
from C:/ncal2gcal/lib/ruby/1.8/timeout.rb:93:in `timeout'
from C:/ncal2gcal/lib/ruby/1.8/net/http.rb:560:in `connect'
from C:/ncal2gcal/lib/ruby/1.8/net/http.rb:553:in `do_start'
from C:/ncal2gcal/lib/ruby/1.8/net/http.rb:542:in `start'
from C:/ncal2gcal/lib/ruby/gems/1.8/gems/gcal4ruby-0.3.1/lib/gcal4ruby/b
ase.rb:212:in `do_get'
from C:/ncal2gcal/lib/ruby/gems/1.8/gems/gcal4ruby-0.3.1/lib/gcal4ruby/b
ase.rb:189:in `send_get'
from C:/ncal2gcal/lib/ruby/gems/1.8/gems/gcal4ruby-0.3.1/lib/gcal4ruby/s
ervice.rb:61:in `calendars'
from C:/ncal2gcal/lib/ruby/gems/1.8/gems/gcal4ruby-0.3.1/lib/gcal4ruby/c
alendar.rb:189:in `find'
from C:/ncal2gcal/lib/ruby/gems/1.8/gems/ncal2gcal-0.1.6/lib/ncal2gcal/g
oogle_calendar.rb:17:in `initialize'
from C:/ncal2gcal/lib/ruby/gems/1.8/gems/ncal2gcal-0.1.6/lib/ncal2gcal/s
ync.rb:19:in `new'
from C:/ncal2gcal/lib/ruby/gems/1.8/gems/ncal2gcal-0.1.6/lib/ncal2gcal/s
ync.rb:19:in `initialize'
from ./src/ncal2gcal_portable:64:in `new'
from ./src/ncal2gcal_portable:64
Press any key to continue . . .
|
By: Scott Woodcock
RE: Getting timeout errors - from where? [ reply ]
2010-06-14 14:32
|
Thanks for the response. It does look like I'm having some sort of work-related network/firewall issues. I see now that I can't even pull up my gmail calendar by logging in thru a web browser. I'll try to get that fixed first and then try again.
Scott
|
By: Elias Kugler
RE: Getting timeout errors - from where? [ reply ]
2010-06-14 05:49
|
Hi Scott!
This is a network timeout or gmail problem. The relevant line in the source is:
...
@cal = GCal4Ruby::Calendar.find(service, @calendar, {:scope => :first})
...
If the problems persists please check if your gmail-calendar exists and the name is the same as the command line parameter -C.
3<
|
By: Scott Woodcock
Getting timeout errors - from where? [ reply ]
2010-06-07 13:40
|
Any tips on getting past this timeout error? What piece is timing out: Google? Notes?
---------------------------------
C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/1.8/net/http.rb:560:in `
initialize': A connection attempt failed because the connected party did not pro
perly respond after a period of time, or established connection failed because c
onnected host has failed to respond. - connect(2) (Errno::ETIMEDOUT)
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/1.8/net/htt
p.rb:560:in `open'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/1.8/net/htt
p.rb:560:in `connect'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/1.8/timeout
.rb:53:in `timeout'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/1.8/timeout
.rb:93:in `timeout'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/1.8/net/htt
p.rb:560:in `connect'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/1.8/net/htt
p.rb:553:in `do_start'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/1.8/net/htt
p.rb:542:in `start'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/gems/1.8/ge
ms/gcal4ruby-0.3.1/lib/gcal4ruby/base.rb:212:in `do_get'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/gems/1.8/ge
ms/gcal4ruby-0.3.1/lib/gcal4ruby/base.rb:189:in `send_get'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/gems/1.8/ge
ms/gcal4ruby-0.3.1/lib/gcal4ruby/service.rb:61:in `calendars'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/gems/1.8/ge
ms/gcal4ruby-0.3.1/lib/gcal4ruby/calendar.rb:189:in `find'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/gems/1.8/ge
ms/ncal2gcal-0.1.5/lib/ncal2gcal/google_calendar.rb:17:in `initialize'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/gems/1.8/ge
ms/ncal2gcal-0.1.5/lib/ncal2gcal/sync.rb:19:in `new'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/lib/ruby/gems/1.8/ge
ms/ncal2gcal-0.1.5/lib/ncal2gcal/sync.rb:19:in `initialize'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/src/ncal2gcal_portab
le:63:in `new'
from C:/DOCUME~1/woodcock/LOCALS~1/Temp/ocrFB5A.tmp/src/ncal2gcal_portab
le:63
|
|
|
