Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-26 Thread Jacques Distler
> On Jan 25, 2016, at 9:43 AM, Jacques Distler > wrote: > >> Have you tried installing directly from our latest svn trunk into a separate >> directory with a clean DB? > > Haven't tried that yet. Trying it was something of a washout. Trunk does not compile on MacOSX 10.9. (You probably knew

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-25 Thread Jacques Distler
> On Jan 25, 2016, at 8:57 AM, Cyrus Daboo wrote: > > -t Slave is not meant for normal operation. I realize that. But it has the advantage of skipping the database checks and (apparently) succeeds in binding to Port 8443. Neither of the other two modes get that far. > > I wonder if you have

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-25 Thread Cyrus Daboo
Hi Jacques, --On January 23, 2016 at 8:13:57 PM -0600 Jacques Distler wrote: On the other hand, starting up the server with bin/run -n -t Slave gets a lot further. And, just to complete the trilogy, bin/run -n -t Single gets further than bin/run -n but not far enough to actually

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-23 Thread Jacques Distler
On the other hand, starting up the server with bin/run -n -t Slave gets a lot further. And, just to complete the trilogy, bin/run -n -t Single gets further than bin/run -n but not far enough to actually listen on port 8443: Using /usr/local/CalDAV-7.0/CalendarServer/.develop/virtualen

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-23 Thread Jacques Distler
On the other hand, starting up the server with bin/run -n -t Slave gets a lot further. > On Jan 20, 2016, at 3:57 PM, Jacques Distler > wrote: > > Here are the processes initiated when the CalendarServer starts up > (PostgreSQL is already running): > > PID TTY TIME CMD > 70038

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-20 Thread Jacques Distler
> On Jan 20, 2016, at 6:25 PM, Morgen Sagen wrote: > > The .sqlite file gets removed at the end of migrateDelegatesToStore( ), which > implies that method completed without error. > > Are there delegate assignments in proxies.sqlite to begin with? > > Are there still records in your directory

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-20 Thread Morgen Sagen
The .sqlite file gets removed at the end of migrateDelegatesToStore( ), which implies that method completed without error. Are there delegate assignments in proxies.sqlite to begin with? Are there still records in your directory service for the delegators and delegates? (migrateDelegatesToStor

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-20 Thread Jacques Distler
> On Jan 20, 2016, at 3:25 PM, Cyrus Daboo wrote: > > Hi Jacques, > > --On January 19, 2016 at 10:53:14 AM -0600 Jacques Distler > wrote: > >> Here is the error.log, with DefaultLogLevel set to "debug". As you can >> see, after the database checks, nothing happens ... till I kill the >> serv

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-20 Thread Cyrus Daboo
Hi Jacques, --On January 19, 2016 at 10:53:14 AM -0600 Jacques Distler wrote: Here is the error.log, with DefaultLogLevel set to "debug". As you can see, after the database checks, nothing happens ... till I kill the server. When it hangs what processes do you see running? There should be

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-19 Thread Jacques Distler
> On Jan 19, 2016, at 10:30 AM, Cyrus Daboo wrote: > > Can you set the "DefaultLogLevel" key to "debug" on the plist config you are > using and then try a bin/run again and attach the result from the error.log > file? Here is the error.log, with DefaultLogLevel set to "debug". As you can see,

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-19 Thread Cyrus Daboo
Hi Jacques, --On January 17, 2016 at 2:27:56 PM -0600 Jacques Distler wrote: Does anything show up in the various log files calendarserver outputs too? Nope. access.log shows only the server starting up (and, when I hit ^C, shuttung down): Log opened - server start: [Sun Jan 17 14:16:

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-18 Thread Jacques Distler
% sudo bin/run -n Using /usr/local/CalDAV-7.0/CalendarServer/.develop/virtualenv/bin/python as Python Starting server... Reading configuration from file: /usr/local/CalDAV-7.0/CalendarServer/conf/caldavd-dev.plist 2016-01-18 11:56:41-0600 [-] Log opened. 2016-01-18 11:56:41-0600 [-] ControlSocke

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-17 Thread Jacques Distler
> On Jan 17, 2016, at 2:19 PM, ebach wrote: > > Does anything show up in the various log files calendarserver outputs too? Nope. access.log shows only the server starting up (and, when I hit ^C, shuttung down): Log opened - server start: [Sun Jan 17 14:16:53 2016]. Log closed - server

Re: [CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-16 Thread Jacques Distler
> On Jan 17, 2016, at 12:52 AM, Jacques Distler > wrote: > >bin/calendarserver_upgrade > > completed without errors. But > > bin/run -n > > stalls at > > 2016-01-17 00:26:57-0600 [-] [twistedcaldav.upgrade#warn] Migrating > delegates to the store > > How can I diagnose what's ca

[CalendarServer-users] Trouble upgrading from 5.3 to 7.0

2016-01-16 Thread Jacques Distler
bin/calendarserver_upgrade completed without errors. But bin/run -n stalls at 2016-01-17 00:26:57-0600 [-] [twistedcaldav.upgrade#warn] Migrating delegates to the store How can I diagnose what's causing the problem? After hitting ^C (the only way to get out), the old proxi