On Jan 21, 2017, at 3:43 AM, Axel Rau <Axel.Rau@Chaos1.DE> wrote:
Am 18.12.2016 um 14:01 schrieb Axel Rau <Axel.Rau@chaos1.de <mailto:Axel.Rau@chaos1.de>>:
Am 18.12.2016 um 00:35 schrieb Andre LaBranche <dre@apple.com <mailto:dre@apple.com>>:
Do you by chance have the default log level set to debug? No it is set to ‚warn‘:
<key>DefaultLogLevel</key> <string>warn</string> <!-- debug, info, warn, error -->
Nobody any idea on that ?
Hi, I suspect this is related to the import ordering / race condition that you've noticed in the past. Is it still the case that the calendar server command line tools don't work in the freebsd CS port? I had a VM with this partially set up, but I banged on it enough last week that I sort of forget where it's at. Currently, attempts to "pkg install py27-calendarserver-9.0" yield a CS installation that is pretty broken: [cs@ ~]$ calendarserver_config -h Traceback (most recent call last): File "/usr/local/bin/calendarserver_config", line 6, in <module> from pkg_resources import load_entry_point File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3019, in <module> @_call_aside File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3003, in _call_aside f(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3032, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 657, in _build_master return cls._build_from_requirements(__requires__) File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 670, in _build_from_requirements dists = ws.resolve(reqs, Environment()) File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 849, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'Twisted==15.4.0' distribution was not found and is required by CalendarServer ... and if I explicitly install Twisted 15.4.0, the CLI tools work at least. Try this: [cs@ ~]$ calendarserver_config DefaultLogLevel DefaultLogLevel=warn The above should be similar to what the server actually does to obtain config values. If I change DefaultLogLevel in /usr/local/etc/caldavd.plist, that change is reflected by calendarserver_config. Also, can you share the command you use to actually start CS? I never invoke caldavd directly, and CS changes its process name after launch so you can't just look at it, and newproc.d on OS X will show you processes names and launch args, but not ALL of the args... All my attempts seem to result in: /usr/local/bin/twistd: Unknown command: caldav ... but I'm surely doing it wrong. • What I want to try is getting CS to run in the 'developer mode' from a git checkout, using the bin/run script. In that state, the location and import order of all the modules should be fairly predictable, and I suspect that might be enough to get the config to load as expected. But, I still have to wade through a bunch of broken stuff to get ./bin/develop to run cleanly. There are some aspects of the ./bin/develop script (and the scripts it sources) that just don't work very well on BSD. -dre