Re: ubuntu serve - cyrus fails to start
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 br...@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
br...@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
Re: ubuntu serve - cyrus fails to start
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 br...@fastmail.fm
mailto:br...@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
br...@fastmail.fm mailto:br...@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 n...@onlight.com
Onlight llc. www.onlight.com
219 N. Milwaukee St., Ste. 2A v. 414.272.4477
Milwaukee, Wisconsin 53202 f. 414.290.0335
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
ubuntu serve - cyrus fails to start
Ubuntu server 14.04.2
Linux poseidon 2.6.32-042stab088.4 #1 SMP Thu Apr 3 17:41:05 MSK 2014
x86_64 x86_64 x86_64 GNU/Linux
cyrus-imapd-2.4 (2.4.17+caldav~beta9-3)
After rebooting my server yesterday (after a package upgrade having nothing
to do with cyrus afaict) cyrus-imapd is silently failing. The logs complain
that the socket does not exist:
status=deferred (connect to poseidon..com[/run/cyrus/socket/lmtp]: No
such file or directory)
Indeed, there's nothing cyrus related in /var/run (/run). In
/etc/init.d/cyrus-imapd:
NAME=cyrmaster
DAEMON=/usr/sbin/${NAME}
PIDFILE=/var/run/${NAME}.pid
Attempting to manually start it tells me nothing:
# service cyrus-imapd status [or start]
[no response]
None of the cyrus or postfix configs have been altered recently. I see
nothing in any log to suggest a problem upon startup.
/etc/cyrus.conf:
START {
recover cmd=/usr/sbin/cyrus ctl_cyrusdb -r
#idled cmd=idled
#mupdatepush cmd=/usr/sbin/cyrus ctl_mboxlist -m
delprunecmd=/usr/sbin/cyrus expire -E 3
tlsprunecmd=/usr/sbin/cyrus tls_prune
}
SERVICES {
imapcmd=imapd -U 30 listen=imap prefork=0 maxchild=100
imaps cmd=imapd -s -U 30 listen=imaps prefork=0 maxchild=100
#pop3cmd=pop3d -U 30 listen=pop3 prefork=0 maxchild=50
#pop3s cmd=pop3d -s -U 30 listen=pop3s prefork=0 maxchild=50
nntpcmd=nntpd -U 30 listen=nntp prefork=0 maxchild=100
#nntps cmd=nntpd -s -U 30 listen=nntps prefork=0 maxchild=100
#lmtp cmd=lmtpd listen=localhost:lmtp prefork=0 maxchild=20
#lmtpcmd=lmtpd -a listen=localhost:lmtp proto=tcp4
lmtpunixcmd=lmtpd listen=/run/cyrus/socket/lmtp prefork=0
maxchild=20
sieve cmd=timsieved listen=localhost:sieve prefork=0
maxchild=100
notify cmd=notifyd listen=/var/run/cyrus/socket/notify
proto=udp prefork=1
#mupdate cmd=mupdate listen=3905 prefork=1
#mupdate cmd=mupdate -m listen=3905 prefork=1
#imap cmd=proxyd listen=imap prefork=0 maxchild=100
#imaps cmd=proxyd -s listen=imaps prefork=0 maxchild=100
#pop3 cmd=pop3proxyd listen=pop3 prefork=0 maxchild=50
#pop3s cmd=pop3proxyd -s listen=pop3s prefork=0 maxchild=50
#lmtp cmd=lmtpproxyd listen=lmtp prefork=1 maxchild=20
}
EVENTS {
checkpoint cmd=/usr/sbin/cyrus ctl_cyrusdb -c period=30
delprunecmd=/usr/sbin/cyrus expire -E 3 at=0401
expunge cmd=cyr_expire -X 8 at=0600
tlsprunecmd=/usr/sbin/cyrus tls_prune at=0401
#squatter_1 cmd=/usr/bin/nice -n 19 /usr/sbin/cyrus squatter -s
period=120
#squatter_a cmd=/usr/sbin/cyrus squatter at=0517
}
Note the lmtp/lmtpunix lines. At some point i made a change, then a second
one. Unfortunately, that was a long time ago and i stupidly didn't leave
any comments here. However, everything has been working well for several
years.
/etc/imapd.conf:
configdirectory: /var/lib/cyrus
proc_path: /run/cyrus/proc
mboxname_lockpath: /run/cyrus/lock
lmtpsocket: /run/cyrus/socket/lmtp
idlesocket: /run/cyrus/socket/idle
notifysocket: /run/cyrus/socket/notify
syslog_prefix: cyrus
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.
I found this bug report from the previous version which seems to be related:
http://www.ubuntuupdates.org/package/core/trusty/universe/base/cyrus-imapd-2.4
Finally, the following is from apt-history log for the update done
yesterday. I've included everything regardless of whether i know it's of
consequence. I also rebooted the server afterwards so it's entirely
possible that the package upgrades have nothing to do with the problem with
cyrus.
amd64 (2.88dsf-41ubuntu6, 2.88dsf-41ubuntu6.1)
apache2-bin:amd64 (2.4.7-1ubuntu4.1, 2.4.7-1ubuntu4.4)
apache2-data:amd64 (2.4.7-1ubuntu4.1, 2.4.7-1ubuntu4.4)
apache2-doc:amd64 (2.4.7-1ubuntu4.1, 2.4.7-1ubuntu4.4)
apache2-mpm-prefork:amd64 (2.4.7-1ubuntu4.1, 2.4.7-1ubuntu4.4)
apache2-utils:amd64 (2.4.7-1ubuntu4.1, 2.4.7-1ubuntu4.4)
apache2.2-bin:amd64 (2.4.7-1ubuntu4.1, 2.4.7-1ubuntu4.4)
apache2:amd64 (2.4.7-1ubuntu4.1, 2.4.7-1ubuntu4.4)
apt-utils:amd64 (1.0.1ubuntu2.6, 1.0.1ubuntu2.7)
apt:amd64 (1.0.1ubuntu2.6, 1.0.1ubuntu2.7)
ca-certificates:amd64 (20130906ubuntu2, 20141019ubuntu0.14.04.1)
dpkg-dev:amd64 (1.17.5ubuntu5.3, 1.17.5ubuntu5.4)
dpkg:amd64 (1.17.5ubuntu5.3, 1.17.5ubuntu5.4)
dselect:amd64 (1.17.5ubuntu5.3, 1.17.5ubuntu5.4)
e2fslibs:amd64 (1.42.9-3ubuntu1, 1.42.9-3ubuntu1.2)
e2fsprogs:amd64 (1.42.9-3ubuntu1, 1.42.9-3ubuntu1.2)
gnupg:amd64 (1.4.16-1ubuntu2.1, 1.4.16-1ubuntu2.3)
gpgv:amd64 (1.4.16-1ubuntu2.1, 1.4.16-1ubuntu2.3)
isc-dhcp-client:amd64 (4.2.4-7ubuntu12, 4.2.4-7ubuntu12.1)
isc-dhcp-common:amd64
Re: ubuntu serve - cyrus fails to start
Gadzooks! It appears that the server is actually missing some things.
# ls -l /usr/sbin/cyr*
-rwxr-xr-x 1 root root 2046 Mar 3 2014 /usr/sbin/cyrus
# ls -l /usr/lib/cyrus/bin/
total 24
drwxr-xr-x 2 root root 4096 Apr 27 18:29 ./
drwxr-xr-x 3 root root 4096 Apr 27 18:29 ../
-rwxr-xr-x 1 root root 2945 Mar 3 2014 init-helper*
-rwxr-xr-x 1 root root 4018 Mar 3 2014 makedirs*
-rwxr-xr-x 1 root root 4965 Mar 3 2014 upgrade-db*
# dpkg --get-selections | grep cyr
cyrus-admin-2.4install
cyrus-clients-2.4install
cyrus-commoninstall
cyrus-common-2.4deinstall
cyrus-imapd-2.4deinstall
libcyrus-imap-perl24install
hmmm ...
# dpkg-query -s cyrus-common-2.4
Package: cyrus-common-2.4
Status: deinstall ok config-files
...
# dpkg-query -s cyrus-imapd-2.4
Package: cyrus-imapd-2.4
Status: deinstall ok config-files
This is saying that the packages have been selected for removal. But, a) I
certainly have not done so; and b) they already seem to be gone. And i see
nothing at all about them in appt's history logs.
Deep breaths.
On Tue, Apr 28, 2015 at 7:49 PM, lowpass zijn.digi...@gmail.com 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 br...@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
br...@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
Re: ubuntu serve - cyrus fails to start
Nothing in syslog? That's where I would be looking for startup messages
from cyrus master.
Bron.
On Wed, Apr 29, 2015, at 09:49 AM, 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
br...@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 br...@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
--
Bron Gondwana br...@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
Re: ubuntu serve - cyrus fails to start
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 br...@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
Re: ubuntu serve - cyrus fails to start
I had done an upgrade of some packages. I listed those at the end of my
first message. I don't think any of them had anything to do with cyrus,
though. But i'd rebooted the server afterwards; i think that's why the
problem with cyrus began to appear.
# zgrep cyrus-imapd /var/log/apt/
I had already tried that. Nothing at all.
# sh -x /etc/init.d/cyrus-imapd start
+ LC_ALL=C
+ export LC_ALL
+ PATH=/sbin:/usr/sbin:/bin:/usr/bin
+ PATH=/sbin:/usr/sbin:/bin:/usr/bin
+ NAME=cyrmaster
+ DAEMON=/usr/sbin/cyrmaster
+ PIDFILE=/var/run/cyrmaster.pid
+ DESC=Cyrus IMAPd
+ test -x /usr/sbin/cyrmaster
+ exit 0
Good idea about shell debugging, thanks. In any case, it's failing because
cyrmaster no longer exists. :-(
Bron: no, nothing in syslog. I'd checked that first thing.
I'm mystified as to what has happened. I think i'll try to (re)install
those packages and see what comes of it. But, realistically, it looks like
i should rebuild the server.
On Tue, Apr 28, 2015 at 8:49 PM, Nic Bernstein n...@onlight.com wrote:
You told us that you had run some apt commands prior to this problem, but
you haven't told us what they were. If you tried to install something
which replaces cyrus-imapd, you may have forced its removal.
What does zgrep cyrus-imapd /var/og/apt/* show?
-nic
On 04/28/2015 07:38 PM, lowpass wrote:
Gadzooks! It appears that the server is actually missing some things.
# ls -l /usr/sbin/cyr*
-rwxr-xr-x 1 root root 2046 Mar 3 2014 /usr/sbin/cyrus
# ls -l /usr/lib/cyrus/bin/
total 24
drwxr-xr-x 2 root root 4096 Apr 27 18:29 ./
drwxr-xr-x 3 root root 4096 Apr 27 18:29 ../
-rwxr-xr-x 1 root root 2945 Mar 3 2014 init-helper*
-rwxr-xr-x 1 root root 4018 Mar 3 2014 makedirs*
-rwxr-xr-x 1 root root 4965 Mar 3 2014 upgrade-db*
# dpkg --get-selections | grep cyr
cyrus-admin-2.4install
cyrus-clients-2.4install
cyrus-commoninstall
cyrus-common-2.4deinstall
cyrus-imapd-2.4deinstall
libcyrus-imap-perl24install
hmmm ...
# dpkg-query -s cyrus-common-2.4
Package: cyrus-common-2.4
Status: deinstall ok config-files
...
# dpkg-query -s cyrus-imapd-2.4
Package: cyrus-imapd-2.4
Status: deinstall ok config-files
This is saying that the packages have been selected for removal. But, a) I
certainly have not done so; and b) they already seem to be gone. And i see
nothing at all about them in appt's history logs.
Deep breaths.
On Tue, Apr 28, 2015 at 7:49 PM, lowpass zijn.digi...@gmail.com 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 br...@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
br...@fastmail.fm
Cyrus Home Page: http://www.cyrusimap.org/
List
