[CalendarServer-users] Update to r3599 failed

Bastien Semene bsemene at cyanide-studio.com
Tue Jan 20 03:01:02 PST 2009


Hi everyone,

I'm using CalendarServer since some months on FreeBSD 7.0 and it worked 
fine. I didn't updated it since a while and it seems the r3599 (or 
older) fails to launch but I have no log about it.

I made a new install to test the last revision. Creating a new directory 
and fetching the last revision through SVN.
I did the changes to make it work on FreeBSD :
- modifying bash's bin path
- autorizing root to launch memcached (this was in cluster.py in my 
previous install, so according to Trac it is a really old revision I 
worked on).

This the launch log :

calendar# ./run
Using python as Python

exec python /usr/local/calendar/Twisted/bin/twistd  -n caldav -f 
/usr/local/calendar/CalendarServer/conf/caldavd-dev.plist -o 
ProcessType=Combined
2009-01-20 11:05:56+0100 [-] Log opened.
2009-01-20 11:05:56+0100 [-] twistd 2.5.0+rUnknown 
(/usr/local/bin/python 2.5.2) starting up
2009-01-20 11:05:56+0100 [-] reactor class: <class 
'twisted.internet.selectreactor.SelectReactor'>
2009-01-20 11:05:56+0100 [-] 
[calendarserver.tap.caldav.CalDAVServiceMaker#error] Unable to detect 
number of CPUs: getNCPU not supported on freebsd7
2009-01-20 11:05:56+0100 [-] 
[calendarserver.tap.caldav.CalDAVServiceMaker#info] 0 processors found. 
Configuring 4 processes.
2009-01-20 11:05:56+0100 [-] 
[calendarserver.tap.caldav.CalDAVServiceMaker#info] Adding memcached 
service
2009-01-20 11:05:56+0100 [-] twistedcaldav.accesslog.AMPLoggingFactory 
starting on "'logs/caldavd.sock'"
2009-01-20 11:08:19+0100 [-] Received SIGINT, shutting down.
2009-01-20 11:08:19+0100 [-] (Port None Closed)
2009-01-20 11:08:19+0100 [-] Main loop terminated.
2009-01-20 11:08:19+0100 [-] Server Shut Down.

I stopped the process at 11:08:19.
I put the log level in caldavd-dev.plist at "debug" level, but there's 
nothing in the error log.

I tried to find informations on google without results.
I'm regularly reading the threads here but find nothing related to this 
problem.

At this point I don't know where to find more information about this 
problem, so any idea or redirection is welcome.
Thank you,

Bastien Semene


More information about the calendarserver-users mailing list