[CalendarServer-users] calendarserver-users Digest, Vol 93, Issue 3

[Andy Knasinski]

version = "6.0b.trunk-r13264"

this is a new install. our previous install went bad due to a python update on this 10.7.4 workstation.

i changed debug to error for delegation.

> 
>> On May 12, 2014, at 8:43 AM, Andy Knasinski <ajk at nrgsoft.com> wrote:
>> 
>> Not sure how to check on version.
> 
> {9} andre at foci [cs/trunk] % cat calendarserver/version.py
> version = "6.0b.trunk-r13468"
> 
>> http://server.com:8008/.calendarserver_version
>> 
>> returns a "2"
> 
> Yeah that?s ? very old, and was only relevant a long time ago (or for very VERY long-range upgrades).
> 
>> proxydbservice is using sqlite
> 
> Have you tried using sqlite3 tools to export / dump the proxydb on a periodic basis, to check for any unexpected changes?
> 
>> i can't seem to find an error log, if i look at web admin
>> 
>> http://server.com:8008/admin/logs/
>> 
>> i see an access log and server log
> 
> You?re definitely using a recent version; the web admin log viewer is pretty new. This view of error.log should be the same as the on-disk view.
> 
>> We don't run any backup on this box.  
> 
> I think the next task is to find the logs. The log location is likely decided by how you installed Calendar Server. If you?re running from an SVN checkout, you?ll find them at data/Logs (relative to the SVN checkout directory). If not, check Calendar Server?s caldavd.plist for ?LogRoot?. Any config keys not defined in caldavd.plist inherit default values from twistedcaldav/stdconfig.py.
> 
> If the error.log doesn?t tell you anything useful at the default log level, you can increase the verbosity of the logs by setting DefaultLogLevel in caldavd.plist to something like info or debug.
> 
> At debug log level, in trunk and recent versions, something like the following is logged at ?debug? level whenever a client changes their delegate configuration:
> 
> 2014-05-12 10:06:00-0700 [DirectoryProxyAMPProtocol,0,] [txdav.who.delegates#debug] Setting delegate assignments for 10000000-0000-0000-0000-000000000001 (read) to [u'10000000-0000-0000-0000-000000000004']
> 
> You can set the verbosity for specific types of log messages (overriding the default) as follows, allowing you to fine-tune which messages you?d like to see.
> 
> 1) Look at sample log message of the type you wish to become more verbose, in the last square bracketed section before the actual message. In the above case, txdav.who.delegates#debug. This shows the log component and log level of the message.
> 
> 2) Set verbosity for that component in the LogLevels dict in caldavd.plist, e.g.
> 
>    <!-- Log level overrides for specific functionality -->
>    <key>LogLevels</key>
>    <dict>
>      <key>txdav.who.delegates</key>
>      <string>debug</string>
>    </dict>
> 
> The proxy / delegation related log messages you might expect to see will depend on which version of the server you?re running. Big changes lately in directory land :)