Hello,
Quoting jsekora@xxxxxxxxxxxxx:
Running strace on /usr/sbin/cyrus ctl_mboxlist -m (with
mupdate_server: localhost) ends with stuff like this:
137159 socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 8
137159 connect(8, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = 0
137159 sendto(8, "<179>Sep 15 14:04:38 cyrus/ctl_mboxlist[137159]:
getaddrinfo(localhost) failed: Servname not supported for
ai_socktype", 118, MSG_NOSIGNAL, NULL, 0) = 118
Do you have an entry for mupdate in your /etc/services file ?
It should be like :
mupdate 3905/tcp
mupdatetest -m PLAIN to localhost *does* seem to work, and lets me
authenticate successfully. That hints that forcing PLAIN auth
(which, again, I think would break Kerberos for our users) might
work; is that my only option?
Separate your frontend, backend and mupdate server, on differents
servers or, if you really can't,
with different conf and db files and differents ports or ip.
You then can have your frontend and backend authentify to mupdate with
sasldb and your user authentify to the frontend as you want.
And can anybody point me at a general guide for the sort of
upgrade/migration by starting with a single-server murder cluster
that I'm trying to do? (I thought I'd found one when I first
started thinking about this migration, but my google-fu is failing
me now.)
Before going tu murder, have a look to replication.
https://www.cyrusimap.org/3.10/imap/download/upgrade.html#how-are-you-planning-on-upgrading
https://www.cyrusimap.org/stable/imap/reference/admin/sop/replication.html
Sincerly,
Jean Charles Delépine
--
Service systèmes et réseaux - DISI
Université de Picardie Jules Verne
5, rue du moulin neuf - 80000 Amiens
------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T186bcddd95bbbfb3-M6a410b05b74afd8b3d3aff4e
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
