Patrick Boutilier wrote:
> 
> Matt,
> 
> This is most likely the problem of imapd and sasl being linked against
> different libdb's
> 
> Can you provide the results of:
> 
> ldd /usr/cyrus/bin/imapd
> ldd /usr/cyrus/bin/master
> ldd /usr/local/lib/libsasl.so

Hallo Patrick,

i have got the same Problem .... here are the results

mail1:/etc/rc.d/rc2.d # ldd /usr/cyrus/bin/imapd
        libsasl.so.7 => /usr/local/lib/libsasl.so.7 (0x40015000)
        libdl.so.2 => /lib/libdl.so.2 (0x40026000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x4002a000)
        libc.so.6 => /lib/libc.so.6 (0x40041000)
!!!     libdb.so.3 => /lib/libdb.so.3 (0x40124000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x40162000)
        libpam.so.0 => /lib/libpam.so.0 (0x40190000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
mail1:/etc/rc.d/rc2.d # ldd /usr/cyrus/bin/master
        libucdagent.so => /usr/lib/libucdagent.so (0x4001b000)
        libucdmibs.so => /usr/lib/libucdmibs.so (0x40025000)
        libsnmp.so => /usr/lib/libsnmp.so (0x4007e000)
        libdl.so.2 => /lib/libdl.so.2 (0x400bf000)
        libc.so.6 => /lib/libc.so.6 (0x400c3000)
!!!     libdb.so.2 => /lib/libdb.so.2 (0x401a6000)
        libz.so.1 => /usr/lib/libz.so.1 (0x401b5000)
        libm.so.6 => /lib/libm.so.6 (0x401c4000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
mail1:/etc/rc.d/rc2.d # ldd /usr/local/lib/libsasl.so
!!!     libdb.so.3 => /lib/libdb.so.3 (0x40012000)
        libdl.so.2 => /lib/libdl.so.2 (0x40050000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x40054000)
        libpam.so.0 => /lib/libpam.so.0 (0x40081000)
        libc.so.6 => /lib/libc.so.6 (0x40089000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

Different versions !! What should i do ??

regards

Danny

> 
> Matt J Bradshaw wrote:
> 
> >hello all,
> >
> >i'm running into some (painful!) problems with my fresh cyrus-imap 2.0.15
> >installation and would *really* appreciate any guru-advice i can get.
> >
> >master starts up fine (or at least appears to) and is listening on its
> >specified ports (143 and 993).  however, any connection to those ports
> >hangs waiting for the greeting and the spawned imapd process dies.  it
> >leaves this in the syslog:
> >
> >process 17601 exited, signalled to death by 11
> >
> >ouch.  that's pretty much all the diagnostics i have.  it's not a system
> >issue, packet-filtering and tcpwrappers are both fine.  :)
> >
> >build information:
> >
> >redhat-linux-6.2 (kernel2.2.16)
> >cyrus-imap-2.0.15
> >cyrus-sasl-1.5.24
> >BerkeleyDB-3.2.9
> >openssl-0.9.6b
> >
> >/etc/imapd.conf:
> >
> >configdirectory:       /var/imap
> >partition-default:     /var/spool/imap
> >admins:                        cyrus
> >sasl_pwcheck_method:   passwd
> >tls_cert_file:         /var/imap/server.pem
> >tls_key_file:          /var/imap/server.pem
> >allowplaintext:                yes
> >
> >the only funny compile option was to disable libwrap (--without-libwrap i
> >believe) as i thought tcpwrapper support was broken bc of past experience.
> >btw, you *may* want to change your use of tcpwrappers to bring it in line
> >with standard use.  this is with regard to the service name usually being
> >the process name (*not* the service name).  perhaps creating a wrapper
> >/usr/cyrus/bin/imapsd which calls 'imapd -s' would be appropriate.
> >nothing big at all, and i just failed to read the cyrus.conf(5) man page.
> >but still an issue.  i would either highlight it more prominently in the
> >install docs or change the behavior...  back to the issue at hand.  sorry
> >for the tangent.
> >
> >perhaps other issues revelent during the build:  i built sasl with almost
> >all mechanisms disabled.  i want the PLAIN (login) mechanism only, over an
> >ssl-encrypted channel.  so that's what i built for.  --enable-plain.
> >
> >any help would be *very* appreciated.  tia.
> >
> >regards,
> >
> >--matt
> >
> >

-- 
------------------------------------------------------------
DT Netsolution GmbH -  Talaeckerstr. 30 -  D-70437 Stuttgart
Tel: +49-711-5505915-0               Fax: +49-711-5505915-12
WEB: http://www.dtnet.de/           email: [EMAIL PROTECTED]

Reply via email to