February 2017 - calendarserver-users

Controlling log level 9.0
by Dirk-Willem van Gulik 29 May '17

29 May '17

How does one control the loglevel on 9.0: With:  <key>DefaultLogLevel</key> <string>warn</string> <!-- debug, info, warn, error —> The log is still showing (after memcache purge & restart): 2017-01-13T16:07:53+0000 [twext.enterprise.adbapi2#debug] ConnectionPool: txn free 'jobqueue.workCheck': free=1, busy=0, waiting=0 And secondly - can LogLevels be used to control this in a more grannular fashion ? I had hoped that <key>LogLevels</key> <dict> <key>twext.enterprise.adbapi2</key> <string>error</string> </dict> would do the trick - but no dice sofar. Dw.

3 3

unable to install calendarserver
by Emmanuel Bourreau 21 Feb '17

21 Feb '17

Hello, during the bin/develop, i have the following error Keychain init. Could not find identity 'org.calendarserver.test' Found certificate 'localhost' Traceback (most recent call last): File "bin/keychain_init.py", line 164, in <module> identityCreate() File "bin/keychain_init.py", line 67, in identityCreate raise RuntimeError(error if error else output) RuntimeError: security: No matching identity found for "localhost" Next, if i try a « bin/run -n » i obtain The configured TLS Keychain Identity (Keychain: org.calendarserver.test) cannot be used: Unable to load Keychain identity: org.calendarserver.test System : 10.11.6 Calendarserver 9.1 Can you help me ? Thanks Emmanuel

4 10

Multiple Memcached servers
by Rob Archibald 20 Feb '17

20 Feb '17

One of the benefits of Memcached is that it allows you to spread caching load across multiple servers. From looking at the config file for Calendar Server, it looked initially to me that it would support multiple Memcached servers, but now I guess I'm not so sure. This is how php handles multi-server configuration: $MEMCACHE_SERVERS = array( "10.1.1.1", //web1 "10.1.1.2", //web2 "10.1.1.3", //web3 ); I did a quick search of the code and I think I've found the connection method for memcache. I found this in txdav/who/cache.py so let me know if I've gone to the wrong place. It looks like it is only able to handle one server (hightlighted below). Am I missing some secret method to allow for multi-server memcached? def _getMemcacheClient(self, refresh=False): """ Get the memcache client instance to use for caching. @param refresh: whether or not to create a new memcache client @type refresh: L{bool} @return: the client to use @rtype: L{memcacheclient.Client} """ if refresh or not hasattr(self, "memcacheClient"): if config.Memcached.Pools.Default.MemcacheSocket: client_addr = "unix:{}".format(config.Memcached.Pools.Default.MemcacheSocket) else: client_addr = "{}:{}".format( config.Memcached.Pools.Default.BindAddress, config.Memcached.Pools.Default.Port, ) self.memcacheClient = ClientFactory.getClient([client_addr], debug=0, pickleProtocol=2) return self.memcacheClient

2 3

Re: [CalendarServer-users] Error on bin/develop
by Rob Archibald 18 Feb '17

18 Feb '17

Nevermind. After tracking it down deep enough to be able to ask the question, the answer wasn't far away. Turns out that after a bit more digging, I found that my system didn't have ldap.h available. After a simple apt-get install libldap2-dev, it finished with no errors. From: Rob Archibald [mailto:rob@robarchibald.com] Sent: Friday, February 17, 2017 4:38 PM To: 'calendarserver-users(a)lists.macosforge.org' Subject: Error on bin/develop I'm running Calendar Server 9.0 on Ubuntu 16.04.1. It seems to be working fine, but I have this nagging error in the back of my mind that makes me worry that something still isn't quite right. When I run bin/develop, I receive the following error: .../ccs-calendarserver-CalendarServer-9.0/bin/_py.sh: line 104: [: # 1 "<stdin>": integer expression expected .../ccs-calendarserver-CalendarServer-9.0/bin/_py.sh: line 109: [: # 1 "<stdin>": integer expression expected It works even though I receive this error, so I'm trying to understand it to see if it matters. This is in the middle of a function called cmp_version which is expecting numeric arguments. It receives these 2 values: 1. 20428 - seems OK 2. # 1 "<stdin>" - looks bad to me It looks like the c_macro function is the source of the bad 2nd value. From what I can tell, the function is being called on ldap.h and trying to get LDAP_VENDOR_VERSION, but instead gets back the bogus value. I'm guessing this means LDAP won't work for me? Blessings, Rob Archibald, M.M. CTO, EndFirst LLC Founder and Music Director, Ensign Symphony & Chorus rob(a)robarchibald.com

3 4

Error on bin/develop
by Rob Archibald 18 Feb '17

18 Feb '17

I'm running Calendar Server 9.0 on Ubuntu 16.04.1. It seems to be working fine, but I have this nagging error in the back of my mind that makes me worry that something still isn't quite right. When I run bin/develop, I receive the following error: .../ccs-calendarserver-CalendarServer-9.0/bin/_py.sh: line 104: [: # 1 "<stdin>": integer expression expected .../ccs-calendarserver-CalendarServer-9.0/bin/_py.sh: line 109: [: # 1 "<stdin>": integer expression expected It works even though I receive this error, so I'm trying to understand it to see if it matters. This is in the middle of a function called cmp_version which is expecting numeric arguments. It receives these 2 values: 1. 20428 - seems OK 2. # 1 "<stdin>" - looks bad to me It looks like the c_macro function is the source of the bad 2nd value. From what I can tell, the function is being called on ldap.h and trying to get LDAP_VENDOR_VERSION, but instead gets back the bogus value. I'm guessing this means LDAP won't work for me? Blessings, Rob Archibald, M.M. CTO, EndFirst LLC Founder and Music Director, Ensign Symphony & Chorus rob(a)robarchibald.com

1 0