SIGHUP'd the master. Nothing about idled appeared in the logs, I'm still getting the 'error sending to idled' errors in syslog. Trying to start by hand still gives:
I don't think that idled gets restarted if master is HUP'd. If you can do it, what I'd do is stop cyrus, run idled totally alone. If it starts then kill it and start cyrus up normally.
ok, I just tried a stop/start on Cyrus. idled is not running (not in process table.)
I'll try to shut Cyrus down, and start idled by hand tonight...
# su - cyrus -c '/usr/cyrus/bin/idled -C /etc/imapd.conf' bind: Address already in use
How do I figure out what exactly it is trying to bind to?
You could trace it. Do you see idled in the process table? fuser might also tell you what process has the socket open.
I've never done that. Can you give me the 3-line crash course in tracing? :)
-Craig
