Comments on: GCALDaemon deb-package for Ubuntu/Kubuntu

By: Philip

Philip — Fri, 23 Sep 2011 04:43:37 +0000

Hi there,

I just got your deb running on mint 11 (ubuntu 11.04) – I initially took a look at the gcaldeamon instalation instructions and I added it to the too difficult pile – however when I did some searching I found your package and it works fine with the gcaldaemon-sync-now. I have not tried to run it in the background as I only need it to run as a cron job.

Thanks for that

Cheers

Phil

By: Matthäus Brandl

Matthäus Brandl — Thu, 11 Aug 2011 09:23:18 +0000

Hey Philipp,
is GCalDaemon still working for you. I tried to set up the LDAP server yesterday via your package, but verification of my account doesn’t work because a captcha is required.
Is there a possibility to turn it off, or is GCD broken?
Regards, Matthäus

By: Philipp C. Heckel

Philipp C. Heckel — Thu, 10 Feb 2011 12:39:23 +0000

Hey Christian,

I suppose that means that you did not configure GCALDaemon correctly.

The property “file.private.ical.url” should be something like this: file.private.ical.url=/calendar/ical/…/private/basic.ics. You can get that URL from the Google Calendar interface.

To change the value, either take a look in the file ~/.gcaldaemon/conf/gcal-daemon.cfg or use the graphical user interface via “Accessories” -> “Configure GCALDaemon” -> “File synchronizer” -> “New …”.

Regards,
Philipp

By: Christian

Christian — Wed, 09 Feb 2011 18:38:27 +0000

Hello Philipp,

thanks for the reply – it’s working now on my laptop ;-) !

But it is not working on the desktop PC. I added GCALDaemon to the auto start and I can see it in the list, but if I check the status after the start up I always get “…is NOT running”! If I try your last post, I get the error “…2011-02-09 10:27:09 | FATAL | Configurator | MISSING PRIVATE ICAL URL (FILE.PRIVATE.ICAL.URL)!…”

What should I do here?

Thanks a lot for your help in advance!

Regards
Christian

By: Philipp C. Heckel

Philipp C. Heckel — Sun, 06 Feb 2011 21:20:52 +0000

Hey Christian,

that can happen if you accidentally started it twice (which shouldn’t happen if you use the script); or if you have other applications running on that port (which is unlikely since 9090 is not a common port).

I’d suggest killing the application that’s “stealing the port”. First find the thief with “netstat -ntap | grep 9090″, then kill the listed PIDs with “kill -9 “.

Hope this helps.

Regards,
Philipp

By: Christian

Christian — Sun, 06 Feb 2011 21:07:38 +0000

Hey Philipp,

here is the output:
INFO | GCALDaemon V1.0 beta 16 starting…
INFO | RSS/ATOM feed converter enabled.
INFO | Local time zone is Mitteleuropäische Zeit.
INFO | HTTP server starting on port 9090…
FATAL | ADDRESS ALREADY IN USE
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at org.gcaldaemon.core.Configurator.startService(Configurator.java:743)
at org.gcaldaemon.core.Configurator.(Configurator.java:658)
at org.gcaldaemon.standalone.Main.main(Main.java:66)
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336)
at java.net.ServerSocket.bind(ServerSocket.java:336)
at java.net.ServerSocket.(ServerSocket.java:202)
at java.net.ServerSocket.(ServerSocket.java:114)
at org.gcaldaemon.core.http.HTTPListener.(HTTPListener.java:122)
… 7 more
FATAL | Service terminated!
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at org.gcaldaemon.core.Configurator.startService(Configurator.java:743)
at org.gcaldaemon.core.Configurator.(Configurator.java:658)
at org.gcaldaemon.standalone.Main.main(Main.java:66)
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336)
at java.net.ServerSocket.bind(ServerSocket.java:336)
at java.net.ServerSocket.(ServerSocket.java:202)
at java.net.ServerSocket.(ServerSocket.java:114)
at org.gcaldaemon.core.http.HTTPListener.(HTTPListener.java:122)
… 7 more

As far as I understood, another program is using this port. But I don’t know what to do…

Thanks ;-)
Christian

By: Philipp C. Heckel

Philipp C. Heckel — Sat, 29 Jan 2011 12:30:15 +0000

Hi Christian,

I just installed a fresh Ubuntu 10.10 in a virtual machine and it works like a charm. Try running the start-command manually and see if there is any errors:

/usr/bin/java -Xmx256m -cp /usr/share/gcaldaemon/lib/activation.jar:/usr/share/gcaldaemon/lib/commons-codec.jar:/usr/share/gcaldaemon/lib/commons-collections.jar:/usr/share/gcaldaemon/lib/commons-httpclient.jar:/usr/share/gcaldaemon/lib/commons-io.jar:/usr/share/gcaldaemon/lib/commons-lang.jar:/usr/share/gcaldaemon/lib/commons-logging.jar:/usr/share/gcaldaemon/lib/gcal-daemon.jar:/usr/share/gcaldaemon/lib/gdata-calendar.jar:/usr/share/gcaldaemon/lib/gdata-client.jar:/usr/share/gcaldaemon/lib/ical4j.jar:/usr/share/gcaldaemon/lib/jdom.jar:/usr/share/gcaldaemon/lib/logger.jar:/usr/share/gcaldaemon/lib/mail.jar:/usr/share/gcaldaemon/lib/rome.jar:/usr/share/gcaldaemon/lib/servlet-api.jar:/usr/share/gcaldaemon/lib/shared-asn1.jar:/usr/share/gcaldaemon/lib/shared-ldap.jar org.gcaldaemon.standalone.Main ~/.gcaldaemon/conf/gcal-daemon.cfg

I hope this helps a little.

Regards,
Philipp

By: Christian

Christian — Sat, 29 Jan 2011 09:44:21 +0000

Hey,

I just tried it on Ubuntu 10.10 Maverick and I could not get it running, if I run “gcaldaemon start” in the terminal and check it with “gcaldaemon status” I get “GCALDaemon is NOT runnig”.

Anyone an idea where the problem is, does anyone got it running on Maverick?

thanks for any help ;-)
Christian

By: Philipp C. Heckel

Philipp C. Heckel — Sun, 20 Jun 2010 09:22:31 +0000

Hey mc,

thanks for contributing. I’m sure it’ll help the others!

Regards,
Philipp

By: mc

mc — Sun, 20 Jun 2010 03:40:21 +0000

Problem on 1st June 16 post solved, though cause not known.

To fix changed file:
~/.gcaldaemon/conf/logger-config.cfg
line
log4j.appender.file.Directory=autodetect
line to:
log4j.appender.file.Directory=~/.gcaldaemon
and now I get a log file.

Though why the autodetect didn’t give me a log file I don’t know.
May have something to do with permissions.