Closed macosforgebot closed 11 years ago
nicolas@… originally submitted this as comment:1:ticket:342
I forgot to mention that the lenny's calendarserver version is 1.2.dfsg-8.
The failure trace is:
main:/etc/caldavd# caldavd /usr/lib/python2.5/site-packages/twisted/plugins/twisted_web2.py:22: DeprecationWarning: mktap and related support modules are deprecated as of Twisted 8.0. Use Twisted Application Plugins with the 'twistd' command directly, as described in 'Writing a Twisted Application Plugin for twistd' chapter of the Developer Guide.
from twisted.scripts.mktap import _tapHelper
Traceback (most recent call last):
File "/usr/bin/twistd", line 21, in <module>
run()
File "/usr/lib/python2.5/site-packages/twisted/scripts/twistd.py", line 27, in run
app.run(runApp, ServerOptions)
File "/usr/lib/python2.5/site-packages/twisted/application/app.py", line 614, in run
runApp(config)
File "/usr/lib/python2.5/site-packages/twisted/scripts/twistd.py", line 23, in runApp
_SomeApplicationRunner(config).run()
File "/usr/lib/python2.5/site-packages/twisted/application/app.py", line 330, in run
self.application = self.createOrGetApplication()
File "/usr/lib/python2.5/site-packages/twisted/application/app.py", line 411, in createOrGetApplication
ser = plg.makeService(self.config.subOptions)
File "/usr/lib/python2.5/site-packages/twistedcaldav/tap.py", line 749, in makeService
service = serviceMethod(options)
File "/usr/lib/python2.5/site-packages/twistedcaldav/cluster.py", line 206, in makeService_Combined
monitor.addProcess(process.getName(),
File "/usr/lib/python2.5/site-packages/twistedcaldav/cluster.py", line 78, in getName
"Can't create TwistdSlaveProcess without a TCP Port")
twistedcaldav.config.ConfigurationError: Can't create TwistdSlaveProcess without a TCP Port
nicolas@… originally submitted this as comment:2:ticket:342
Replying to nicolas@…:
On debian lenny disabling http (port set to 0) but with a valid https port (default 8443) the server doesn't start. Https only should be a valid option.
SOLVED
It may be a Debian specific bug, but the XML setup of the ssl port is commented out. So there was no port configured and the error message was indeed correct.
info@… originally submitted this as comment:3:ticket:342
Perhaps someone should close this ticket then.
@dreness originally submitted this as comment:7:ticket:342
Cannot reproduce this problem in r10318. Server starts and is operational with HTTPPort = 0 and BindHTTPPorts unset.
@wsanchez originally submitted this as comment:8:ticket:342
nicolas@… originally submitted this as ticket:342
On debian lenny disabling http (port set to 0) but with a valid https port (default 8443) the server doesn't start. Https only should be a valid option.