Re: Murder / frontend does not connect to backend
Le jeudi 05 avril 2007 à 10:22 -0700, Andrew Morgan a écrit : On Thu, 5 Apr 2007, [EMAIL PROTECTED] wrote: Thanks Here's the frontend config. FYI, users are authenticated against a LDAP server with saslauthd and cyrus, proxy_murder and murder are defined locally on each machine in a sasldb2 database. FRONTEND CONFIG (proxy1) --- admins: cyrus postfix murder lmtp_admins: postman postfix murder mupdate_admins: murder proxyservers: proxy_murder mupdate_server: mupdate.rescom.mi mupdate_port: 3905 mupdate_username: murder mupdate_authname: murder mupdate_password: password mupdate_retry_delay: 10 infra1_password:password imapback_password:password proxy_authname:murder proxy_password:password ---/END FRONTEND --- BACKEND CONFIG (imapback) - servername:imapback.rescom.mi admins: cyrus proxy_murder murder mupdate_admins: murder proxy_murder proxyservers: proxy_murder mupdate_server: mupdate.rescom.mi mupdate_port: 3905 mupdate_username: murder mupdate_authname: murder mupdate_password: password /END BACKEND - MUPDATE (mupdate)-- admins: cyrus murder mupdate_admins: murder /END MUPDATE I chopped out the non-murder config options from above to make it simpler to see. On your frontend you have proxy_authname:murder (so the frontend will connect to the backend as user murder). On the backend you have proxyservers: proxy_murder (so only user proxy_murder is allowed to proxy for other users). I'm pretty sure you should set proxyservers: murder on the backend, or change to proxy_authname: proxy_murder on the frontend (sync those two usernames up). Andy I made the modifications but there is still no network communication between frontend and backend servers. I was just wandering if someone succeeded in a murder setup with Debian Etch and cyrus2.2 packages or if I need to give a try on the 2.3 release ? Thanks and Joyeuses Paques Arnaud Brugnon Opensquad.com Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Murder / frontend does not connect to backend
On Sat, 7 Apr 2007, Arnaud Brugnon wrote: I made the modifications but there is still no network communication between frontend and backend servers. I was just wandering if someone succeeded in a murder setup with Debian Etch and cyrus2.2 packages or if I need to give a try on the 2.3 release ? I use v2.2.13 on Debian, but it is compiled from source. I'm not using the Debian packages. Andy Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Murder / frontend does not connect to backend
Selon Andrew Morgan [EMAIL PROTECTED]: On Wed, 4 Apr 2007, [EMAIL PROTECTED] wrote: Thanks for your answer, I use 1 frontend because it's a test lab. Cyradm was just an example tool. My main question was How to troubleshoot IMAP connection to backend. I am unable to make a SELECT with imtest or any IMAP client. See below the results with imtest. [snip] S: L01 OK User logged in Authenticated. Security strength factor: 0 a SELECT INBOX a NO Server(s) unavailable to complete operation b SELECT user.user1.INBOX b NO Server(s) unavailable to complete operation and the log Mar 23 09:50:44 proxy1 cyrus/proxyd[12409]: connect(imapback.rescom.mi) failed: Invalid argument Why there is no communication when connecting to IMAP ? What does mean connect(default) failed: Invalid argument in the log ? Can you post your frontend, backend, and murder imapd.conf files (sanitize any passwords, of course)? I suspect there is an authentication problem. Andy Thanks Here's the frontend config. FYI, users are authenticated against a LDAP server with saslauthd and cyrus, proxy_murder and murder are defined locally on each machine in a sasldb2 database. FRONTEND CONFIG (proxy1) --- configdirectory: /var/lib/cyrus defaultpartition: proxy1 proxy1-default: /tmp altnamespace: no unixhierarchysep: no lmtp_downcase_rcpt: yes admins: cyrus postfix murder lmtp_admins: postman postfix murder mupdate_admins: murder proxyservers: proxy_murder allowanonymouslogin: no popminpoll: 1 autocreatequota: 0 umask: 077 sieveusehomedir: false sievedir: /var/spool/sieve hashimapspool: true allowplaintext: yes allowplainwithouttls:yes sasl_mech_list: PLAIN LOGIN sasl_pwcheck_method: saslauthd auxprop sasl_auxprop_plugin: sasldb sasl_auto_transition: no force_sasl_client_mech: plain login tls_cert_file: /etc/3mi/pki/server.cert tls_key_file: /etc/3mi/pki/server.key tls_ca_file: /etc/3mi/pki/rootca.pem imap_tls_cert_file: /etc/3mi/pki/server.cert imap_tls_key_file: /etc/3mi/pki/server.key imap_tls_ca_file: /etc/3mi/pki/rootca.pem tls_session_timeout: 1440 tls_cipher_list: TLSv1+HIGH:!aNULL:@STRENGTH mupdate_server: mupdate.rescom.mi mupdate_port: 3905 mupdate_username: murder mupdate_authname: murder mupdate_password: password mupdate_retry_delay: 10 infra1_password:password imapback_password:password proxy_authname:murder proxy_password:password lmtpsocket: /var/run/cyrus/socket/lmtp idlemethod: idled idlesocket: /var/run/cyrus/socket/idle notifysocket: /var/run/cyrus/socket/notify syslog_prefix: cyrus ---/END FRONTEND --- BACKEND CONFIG (imapback) - servername:imapback.rescom.mi configdirectory: /var/lib/cyrus defaultpartition: default partition-default: /var/spool/cyrus/mail altnamespace: no lmtp_downcase_rcpt: yes unixhierarchysep: no admins: cyrus proxy_murder murder mupdate_admins: murder proxy_murder allowanonymouslogin: no popminpoll: 1 umask: 077 autocreatequota: 0 sieveusehomedir: false sievedir: /var/spool/sieve hashimapspool: true allowplaintext: yes allowplainwithouttls:yes sasl_pwcheck_method: auxprop sasl_auxprop_plugin: sasldb sasl_mech_list: PLAIN sasl_minimum_layer: 0 sasl_auto_transition: no lmtpsocket: /var/run/cyrus/socket/lmtp idlemethod: poll idlesocket: /var/run/cyrus/socket/idle notifysocket: /var/run/cyrus/socket/notify syslog_prefix: cyrusback proxyservers: proxy_murder mupdate_server: mupdate.rescom.mi mupdate_port: 3905 mupdate_username: murder mupdate_authname: murder mupdate_password: password tls_cert_file: /etc/3mi/pki/server.cert tls_key_file: /etc/3mi/pki/server.key tls_ca_file: /etc/3mi/pki/rootca.pem imap_tls_cert_file: /etc/3mi/pki/server.cert imap_tls_key_file: /etc/3mi/pki/server.key imap_tls_ca_file: /etc/3mi/pki/rootca.pem /END BACKEND - MUPDATE (mupdate)-- configdirectory: /var/lib/mupdate defaultpartition: default partition-default: /tmp altnamespace: no lmtp_downcase_rcpt: yes unixhierarchysep: no admins: cyrus murder mupdate_admins: murder umask: 077 allowplaintext: yes sasl_pwcheck_method: auxprop sasl_auxprop_plugin: sasldb sasl_mech_list: PLAIN LOGIN syslog_prefix: mupdate /END MUPDATE Thanks for your help. -- Arnaud Brugnon Opensquad Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Murder / frontend does not connect to backend
On Thu, 5 Apr 2007, [EMAIL PROTECTED] wrote: Thanks Here's the frontend config. FYI, users are authenticated against a LDAP server with saslauthd and cyrus, proxy_murder and murder are defined locally on each machine in a sasldb2 database. FRONTEND CONFIG (proxy1) --- admins: cyrus postfix murder lmtp_admins: postman postfix murder mupdate_admins: murder proxyservers: proxy_murder mupdate_server: mupdate.rescom.mi mupdate_port: 3905 mupdate_username: murder mupdate_authname: murder mupdate_password: password mupdate_retry_delay: 10 infra1_password:password imapback_password:password proxy_authname:murder proxy_password:password ---/END FRONTEND --- BACKEND CONFIG (imapback) - servername:imapback.rescom.mi admins: cyrus proxy_murder murder mupdate_admins: murder proxy_murder proxyservers: proxy_murder mupdate_server: mupdate.rescom.mi mupdate_port: 3905 mupdate_username: murder mupdate_authname: murder mupdate_password: password /END BACKEND - MUPDATE (mupdate)-- admins: cyrus murder mupdate_admins: murder /END MUPDATE I chopped out the non-murder config options from above to make it simpler to see. On your frontend you have proxy_authname:murder (so the frontend will connect to the backend as user murder). On the backend you have proxyservers: proxy_murder (so only user proxy_murder is allowed to proxy for other users). I'm pretty sure you should set proxyservers: murder on the backend, or change to proxy_authname: proxy_murder on the frontend (sync those two usernames up). Andy Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Murder / frontend does not connect to backend
Selon Andrew Morgan [EMAIL PROTECTED]: On Tue, 3 Apr 2007, [EMAIL PROTECTED] wrote: Hello, I'm setting up a cyrus murder in a lab and I'm facing a problem. The architecture is quite simple : 1 frontend, 1 backend and a mupdate master We are using cyrus 2.2.13-10 on Debian etch. The Mupdate seems OK, I can LIST from everywhere. If I create a mailbox on the backend I can see it with mupdatetest on the frontend quickly. But I cannot make a single IMAP SELECT command on the frontend. This problem can be tracked with cyradm. When I try to create a mailbox. I've this strange message and there is NO trafic between frontend and backend. The same message arises when connecting with a IMAP client localhost cm user.user1.tutu createmailbox: Server(s) unavailable to complete operation Log line associated : Mar 23 00:01:31 proxy1 cyrus/proxyd[12155]: connect(default) failed: Invalid argument --- But if I try to delete a mailbox I can see trafic between front and back servers. So my (maybe first) question is : Why there is no communication when connecting to IMAP ? What does mean connect(default) failed: Invalid argument in the log Everything I found was related to authentication but this does not seem an issue in my setup. Thanks in advance In my experience, you cannot create a mailbox when connected to a frontend server. Your environment with 1 backend makes it seem silly, but in the case with multiple backends you would need some way to specify where to create the mailbox. In our case, our script randomly picks a backend, connects to it, and creates the mailbox. Andy Thanks for your answer, I use 1 frontend because it's a test lab. Cyradm was just an example tool. My main question was How to troubleshoot IMAP connection to backend. I am unable to make a SELECT with imtest or any IMAP client. See below the results with imtest. [snip] S: L01 OK User logged in Authenticated. Security strength factor: 0 a SELECT INBOX a NO Server(s) unavailable to complete operation b SELECT user.user1.INBOX b NO Server(s) unavailable to complete operation and the log Mar 23 09:50:44 proxy1 cyrus/proxyd[12409]: connect(imapback.rescom.mi) failed: Invalid argument Why there is no communication when connecting to IMAP ? What does mean connect(default) failed: Invalid argument in the log ? Thanks Arnaud Brugnon Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Murder / frontend does not connect to backend
On Tue, 3 Apr 2007, [EMAIL PROTECTED] wrote: Hello, I'm setting up a cyrus murder in a lab and I'm facing a problem. The architecture is quite simple : 1 frontend, 1 backend and a mupdate master We are using cyrus 2.2.13-10 on Debian etch. The Mupdate seems OK, I can LIST from everywhere. If I create a mailbox on the backend I can see it with mupdatetest on the frontend quickly. But I cannot make a single IMAP SELECT command on the frontend. This problem can be tracked with cyradm. When I try to create a mailbox. I've this strange message and there is NO trafic between frontend and backend. The same message arises when connecting with a IMAP client localhost cm user.user1.tutu createmailbox: Server(s) unavailable to complete operation Log line associated : Mar 23 00:01:31 proxy1 cyrus/proxyd[12155]: connect(default) failed: Invalid argument --- But if I try to delete a mailbox I can see trafic between front and back servers. So my (maybe first) question is : Why there is no communication when connecting to IMAP ? What does mean connect(default) failed: Invalid argument in the log Everything I found was related to authentication but this does not seem an issue in my setup. Thanks in advance In my experience, you cannot create a mailbox when connected to a frontend server. Your environment with 1 backend makes it seem silly, but in the case with multiple backends you would need some way to specify where to create the mailbox. In our case, our script randomly picks a backend, connects to it, and creates the mailbox. Andy Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
