On Apr 23, 2013, at 3:14 AM, Axel Rau <axel....@chaos1.de> wrote:
>
> Am 22.04.2013 um 23:22 schrieb Andre LaBranche <d...@apple.com>:
>
>> On Apr 22, 2013, at 9:28 AM, Axel Rau <axel....@chaos1.de> wrote:
>>
>>>
>>> Am 22.04.2013 um 17:39 schrieb Andre LaBranche <d...@apple.com>:
>>>
>>>> It doesn't seem likely to me that a fast shutdown of postgres could cause
>>>> this sort of error. Fast shutdown simply means that clients are not given
>>>> the chance to finish their running transactions before they are
>>>> disconnected, which is totally safe (those in-flight txns get rolled
>>>> back). Given the complaints in the log about SSL, I tend to suspect the
>>>> software update more than anything else…
>>> If feel a professional product like dcs should deal with such situations
>>> gracefully.
>>
>> Depending on how many of Calendar Server's dependencies are provided by your
>> OS, and depending on how many of those dependencies were upgraded in your OS
>> upgrade... I can imagine various sorts of breakage, although I don't have
>> any specific ideas based on your traceback.
> The OS version and installed dependencies are posted here
>
> http://article.gmane.org/gmane.comp.macosx.calendarserver.devel/1612/match=py27+pycalendar+2.1
>
>>
>> Are you able to bootstrap a new Calendar Server instance in the upgraded OS,
>> for testing purposes?
> I have a 2nd instance of the same version (4.2) running on FreeBSD 9.1, which
> does not show the problem (-;
>
> Axel
> PS: Complete logs of both servers available on request
Hi,
I'd like a look at your error.log please.
1) shut down Calendar Server, postgres, memcached
2) set the default LogLevel to debug in caldavd.plist
3) start service
4) reply privately with contents of error.log
Thx,
-dre
_______________________________________________
calendarserver-dev mailing list
calendarserver-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/calendarserver-dev
