ubuntu serve - cyrus fails to start

[Nic Bernstein]

Lowpass,
BTW; if you're trying to debug an init script, try running it manually 
with shell debugging:

    # sh -x /etc/init.d/cyrus-imapd start

And then post a sanitized version of that here, if you still need help.
     -nic

On 04/28/2015 06:49 PM, lowpass wrote:
> Thanks for the quick response, Bron. The symlink is ok.
>
> # ls -l /var/run
> lrwxrwxrwx 1 root root 4 Oct 18  2014 /var/run -> /run/
>
> I tried creating the dir myself as you suggested:
>
> # mkdir /run/cyrus
> # chown cyrus /run/cyrus/
> # service cyrus-imapd start
> [nothing]
>
> I tried removing the --quiet flag from the startup script with same 
> (non) results.
>
> What about the pid? As i understand, it's not cyrus that creates that 
> on startrup. In any case, it's NOT being created. From 
> /etc/init.d/cyrus-imapd:
>
> NAME=cyrmaster
> PIDFILE="/var/run/${NAME}.pid"
>
> I've posted a message on the Ubuntu forum as well, as i've a feeling 
> the problem is not with cyrus. I was hoping, though, that another 
> cyrus user might have run into this.
>
> On Tue, Apr 28, 2015 at 6:55 PM, Bron Gondwana <brong at fastmail.fm 
> <mailto:brong at fastmail.fm>> wrote:
>
>     On Wed, Apr 29, 2015, at 08:46 AM, lowpass wrote:
>>     I do have socket and lock dirs under /var/lib/cyrus but they were
>>     last modified several years ago and seem to be left over from
>>     some other config. Other dirs there have seen more recent
>>     activity. Everything seems to be pointing towards the socket &
>>     lock dirs being created under /run but there's nothing there.
>     /run is a tmpfs which gets created fresh on each reboot.
>     Cyrus starts as user 'cyrus' and has no permission to create the
>     directories it needs.
>     Your init script should create the directories - but if you moved
>     them somewhere other than where the package expects them to be,
>     then it won't create intermediate directories for you.
>     So, here's the thing:
>     1) double check that /var/run and /run are the same place -
>     they're mostly a symlink in recent Debian/Ubuntu systems.  If not,
>     I suggest that you audit your configuration to be all in /var/run
>     or all in /run (probably a good idea anyway for more consistency.
>     2) run these commands as root:
>     mkdir /run/cyrus
>     chown cyrus /run/cyrus
>     3) either put those commands in a startup script that runs before
>     Cyrus starts, or edit the init script for Cyrus - though note that
>     if you edit the init script, you'll have to re-apply those edits
>     on upgrade.
>     Unfortunately, this isn't something we can fix in the Cyrus
>     binaries.  They try to create the directories, but they just plain
>     don't have permissions to do so at that stage of the process.
>     Regards,
>     Bron.
>     --
>     Bron Gondwana
>     brong at fastmail.fm <mailto:brong at fastmail.fm>
>
>     ----
>     Cyrus Home Page: http://www.cyrusimap.org/
>     List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
>     To Unsubscribe:
>     https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
>
>
>
>
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

-- 
Nic Bernstein                             nic at onlight.com
Onlight llc.                              www.onlight.com
219 N. Milwaukee St., Ste. 2A	          v. 414.272.4477
Milwaukee, Wisconsin  53202		  f. 414.290.0335

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20150428/aa2f0ca6/attachment.html