Re: Cyrus IMAPd 2.2.3 Released
Carsten Hoeger wrote:
What about this issue:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=request%20info%20until%20latermsg=23996
Using 2.2.3 and saslauthd I get the same error.
Process 19491 attached - interrupt to quit
select(1, [0], NULL, NULL, {1480, 44}) = 1 (in [0], left {1477, 98})
time(NULL) = 1074265801
read(0, . login cyrus secret1\r\n, 4096) = 23
socket(PF_UNIX, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_UNIX, path=/var/run/sasl2//mux}, 110) = 0
writev(10, [{\0\5cyrus\0\7secret1\0\4imap\0\0, 24}], 1) = 24
read(10, \0\2, 2) = 2
read(10, OK, 2) = 2
close(10) = 0
select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
write(1, . NO Login failed: can\'t request..., 63) = 63
time(NULL) = 1074265801
select(1, [0], NULL, NULL, {1800, 0}
using cyrus-sasl-2.1.7
Not sure how applicable this will be, but in cyrus 2.2.1 and 2.2.2 using
saslauthd 2.1.15 I have no problem at all using saslauthd - pam -
pam_mysql - mysql
Eric
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.2.3 Released
Carsten Hoeger wrote:
On Thu, Jan 15, Rob Siemborski wrote:
I'm quite pleased to announce the long-awaited stable release of Cyrus
IMAPd 2.2.3. This release contains substantial new features over the 2.1
series including extensive support for mailbox annotations, NNTP, much
more stable process accounting, and of course, virtual domains.
What about this issue:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=request%20info%20until%20latermsg=23996
Using 2.2.3 and saslauthd I get the same error.
Process 19491 attached - interrupt to quit
select(1, [0], NULL, NULL, {1480, 44}) = 1 (in [0], left {1477, 98})
time(NULL) = 1074265801
read(0, . login cyrus secret1\r\n, 4096) = 23
socket(PF_UNIX, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_UNIX, path=/var/run/sasl2//mux}, 110) = 0
writev(10, [{\0\5cyrus\0\7secret1\0\4imap\0\0, 24}], 1) = 24
read(10, \0\2, 2) = 2
read(10, OK, 2) = 2
close(10) = 0
select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
write(1, . NO Login failed: can\'t request..., 63) = 63
time(NULL) = 1074265801
select(1, [0], NULL, NULL, {1800, 0}
using cyrus-sasl-2.1.7
2.1.7 or 2.1.17? I just went through the trouble of configuring
pam_mysql (0.4.7) for use with saslauthd (2.1.17) and it works fine with
Cyrus 2.2.3. If you share your config, perhaps we can help.
Just out of curiosity, is there some reason why you need to use PAM,
rather than using the SQL auxprop plugin?
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.2.3 Released
On Fri, 16 Jan 2004, Ken Murchison wrote:
Carsten Hoeger wrote:
On Thu, Jan 15, Rob Siemborski wrote:
I'm quite pleased to announce the long-awaited stable release of Cyrus
IMAPd 2.2.3. This release contains substantial new features over the 2.1
series including extensive support for mailbox annotations, NNTP, much
more stable process accounting, and of course, virtual domains.
What about this issue:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=request%20info%20until%20latermsg=23996
Using 2.2.3 and saslauthd I get the same error.
Process 19491 attached - interrupt to quit
select(1, [0], NULL, NULL, {1480, 44}) = 1 (in [0], left {1477, 98})
time(NULL) = 1074265801
read(0, . login cyrus secret1\r\n, 4096) = 23
socket(PF_UNIX, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_UNIX, path=/var/run/sasl2//mux}, 110) = 0
writev(10, [{\0\5cyrus\0\7secret1\0\4imap\0\0, 24}], 1) = 24
read(10, \0\2, 2) = 2
read(10, OK, 2) = 2
close(10) = 0
select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
write(1, . NO Login failed: can\'t request..., 63) = 63
time(NULL) = 1074265801
select(1, [0], NULL, NULL, {1800, 0}
using cyrus-sasl-2.1.7
2.1.7 or 2.1.17? I just went through the trouble of configuring
pam_mysql (0.4.7) for use with saslauthd (2.1.17) and it works fine with
Cyrus 2.2.3. If you share your config, perhaps we can help.
This works only for unqualified users. saslauthd pam module ignores
realms.
--
Igor
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.2.3 Released
Carsten Hoeger wrote:
What about this issue:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=request%20info%20until%20latermsg=23996
Using 2.2.3 and saslauthd I get the same error.
Process 19491 attached - interrupt to quit
select(1, [0], NULL, NULL, {1480, 44}) = 1 (in [0], left {1477,
98})
time(NULL) = 1074265801
read(0, . login cyrus secret1\r\n, 4096) = 23
socket(PF_UNIX, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_UNIX, path=/var/run/sasl2//mux}, 110) = 0
writev(10, [{\0\5cyrus\0\7secret1\0\4imap\0\0, 24}], 1) = 24
read(10, \0\2, 2) = 2
read(10, OK, 2) = 2
close(10) = 0
select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
write(1, . NO Login failed: can\'t request..., 63) = 63
time(NULL) = 1074265801
select(1, [0], NULL, NULL, {1800, 0}
using cyrus-sasl-2.1.7
Not sure how applicable this will be, but in cyrus 2.2.1 and 2.2.2 using
saslauthd 2.1.15 I have no problem at all using saslauthd - pam -
pam_mysql - mysql
IIRC Cyrus IMAPd 2.2.2 with 'saslauthd - pam_something' uses cyrus-sasl
= 2.1.15! I have verified this some time ago and I expect it's still the
same with 2.2.3.
Simon
Eric
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.2.3 Released
Jan 16 06:59:18 synodon imap[58231]: size read failed Jan 16 06:59:18 synodon imap[58231]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 06:59:24 synodon /kernel: pid 44231 (saslauthd), uid 0: exited on signal 11 (core dumped) Hmm, I not sure what that is. Can you give us backtrace and your saslauthd startup cmd? saslauthd -a pam (with pam_pgsql) still gives me that problem :-( Today I tried to use gdb on saslauthd and that's what I've got: Program received signal SIGSEGV, Segmentation fault. 0x28104942 in vfprintf () from /usr/lib/libc.so.4 I don't know if that will give you any clue Any help will be greatli appreciated! Dmitry
Re: Cyrus IMAPd 2.2.3 Released
On Wed, 28 Jan 2004 [EMAIL PROTECTED] wrote: Jan 16 06:59:18 synodon imap[58231]: size read failed Jan 16 06:59:18 synodon imap[58231]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 06:59:24 synodon /kernel: pid 44231 (saslauthd), uid 0: exited on signal 11 (core dumped) Hmm, I not sure what that is. Can you give us backtrace and your saslauthd startup cmd? saslauthd -a pam (with pam_pgsql) still gives me that problem :-( Today I tried to use gdb on saslauthd and that's what I've got: Program received signal SIGSEGV, Segmentation fault. 0x28104942 in vfprintf () from /usr/lib/libc.so.4 I don't know if that will give you any clue Any help will be greatli appreciated! This does not help. Run gdb against the saslauthd core file and type bt. -- Igor
Re: Cyrus IMAPd 2.2.3 Released
Quoting Igor Brezac [EMAIL PROTECTED]: On Wed, 28 Jan 2004 [EMAIL PROTECTED] wrote: Jan 16 06:59:18 synodon imap[58231]: size read failed Jan 16 06:59:18 synodon imap[58231]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 06:59:24 synodon /kernel: pid 44231 (saslauthd), uid 0: exited on signal 11 (core dumped) Hmm, I not sure what that is. Can you give us backtrace and your saslauthd startup cmd? saslauthd -a pam (with pam_pgsql) still gives me that problem :-( Today I tried to use gdb on saslauthd and that's what I've got: Program received signal SIGSEGV, Segmentation fault. 0x28104942 in vfprintf () from /usr/lib/libc.so.4 I don't know if that will give you any clue Any help will be greatli appreciated! This does not help. Run gdb against the saslauthd core file and type bt. This is output of gdb on one of my servers: [EMAIL PROTECTED] saslauthd]# gdb saslauthd saslauthd.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd...(no debugging symbols found)... Core was generated by `saslauthd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libcrypt.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libpam.so.1...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_pgsql.so...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libpq.so.3...(no debugging symbols found)...done. Reading symbols from /usr/lib/libmd.so.2...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libintl.so.5...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libssl.so.3...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libcrypto.so.3...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_skey.so...(no debugging symbols found)...done. Reading symbols from /usr/lib/libskey.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_unix.so...(no debugging symbols found)...done. Reading symbols from /usr/lib/libutil.so.3...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x28104942 in vfprintf () from /usr/lib/libc.so.4 (gdb) bt #0 0x28104942 in vfprintf () from /usr/lib/libc.so.4 #1 0x280eae92 in vsyslog () from /usr/lib/libc.so.4 #2 0x280eabe5 in syslog () from /usr/lib/libc.so.4 #3 0x2812e102 in pam_sm_acct_mgmt () from /usr/lib/pam_pgsql.so #4 0x2808c271 in pam_getenvlist () from /usr/lib/libpam.so.1 #5 0x2808c51d in _pam_dispatch () from /usr/lib/libpam.so.1 #6 0x2808b56c in pam_acct_mgmt () from /usr/lib/libpam.so.1 #7 0x8049ad0 in auth_pam () #8 0x804c7ac in do_auth () #9 0x804bee1 in do_request () #10 0x804bb39 in ipc_loop () #11 0x804c743 in main () #12 0x804972e in _start () (gdb) quit And this gdb output on the other one: [EMAIL PROTECTED] saslauthd]# gdb saslauthd saslauthd.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd...(no debugging symbols found)... Core was generated by `saslauthd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libcrypt.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libpam.so.1...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_pgsql.so...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libpq.so.3...(no debugging symbols found)...done. Reading symbols from /usr/lib/libmd.so.2...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libintl.so.5...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libssl.so.3...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libcrypto.so.3...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_skey.so...(no debugging symbols found)...done. Reading
Re: Cyrus IMAPd 2.2.3 Released
It is hard to tell from this. I do not think this is saslauthd problem. -Igor On Wed, 28 Jan 2004 [EMAIL PROTECTED] wrote: Quoting Igor Brezac [EMAIL PROTECTED]: On Wed, 28 Jan 2004 [EMAIL PROTECTED] wrote: Jan 16 06:59:18 synodon imap[58231]: size read failed Jan 16 06:59:18 synodon imap[58231]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 06:59:24 synodon /kernel: pid 44231 (saslauthd), uid 0: exited on signal 11 (core dumped) Hmm, I not sure what that is. Can you give us backtrace and your saslauthd startup cmd? saslauthd -a pam (with pam_pgsql) still gives me that problem :-( Today I tried to use gdb on saslauthd and that's what I've got: Program received signal SIGSEGV, Segmentation fault. 0x28104942 in vfprintf () from /usr/lib/libc.so.4 I don't know if that will give you any clue Any help will be greatli appreciated! This does not help. Run gdb against the saslauthd core file and type bt. This is output of gdb on one of my servers: [EMAIL PROTECTED] saslauthd]# gdb saslauthd saslauthd.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd...(no debugging symbols found)... Core was generated by `saslauthd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libcrypt.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libpam.so.1...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_pgsql.so...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libpq.so.3...(no debugging symbols found)...done. Reading symbols from /usr/lib/libmd.so.2...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libintl.so.5...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libssl.so.3...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libcrypto.so.3...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_skey.so...(no debugging symbols found)...done. Reading symbols from /usr/lib/libskey.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_unix.so...(no debugging symbols found)...done. Reading symbols from /usr/lib/libutil.so.3...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x28104942 in vfprintf () from /usr/lib/libc.so.4 (gdb) bt #0 0x28104942 in vfprintf () from /usr/lib/libc.so.4 #1 0x280eae92 in vsyslog () from /usr/lib/libc.so.4 #2 0x280eabe5 in syslog () from /usr/lib/libc.so.4 #3 0x2812e102 in pam_sm_acct_mgmt () from /usr/lib/pam_pgsql.so #4 0x2808c271 in pam_getenvlist () from /usr/lib/libpam.so.1 #5 0x2808c51d in _pam_dispatch () from /usr/lib/libpam.so.1 #6 0x2808b56c in pam_acct_mgmt () from /usr/lib/libpam.so.1 #7 0x8049ad0 in auth_pam () #8 0x804c7ac in do_auth () #9 0x804bee1 in do_request () #10 0x804bb39 in ipc_loop () #11 0x804c743 in main () #12 0x804972e in _start () (gdb) quit And this gdb output on the other one: [EMAIL PROTECTED] saslauthd]# gdb saslauthd saslauthd.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd...(no debugging symbols found)... Core was generated by `saslauthd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libcrypt.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libpam.so.1...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_pgsql.so...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libpq.so.3...(no debugging symbols found)...done. Reading symbols from /usr/lib/libmd.so.2...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libintl.so.5...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libssl.so.3...(no debugging symbols found)...done. Reading symbols from
Re: Cyrus IMAPd 2.2.3 Released
[EMAIL PROTECTED] wrote: Quoting Igor Brezac [EMAIL PROTECTED]: On Wed, 28 Jan 2004 [EMAIL PROTECTED] wrote: Jan 16 06:59:18 synodon imap[58231]: size read failed Jan 16 06:59:18 synodon imap[58231]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 06:59:24 synodon /kernel: pid 44231 (saslauthd), uid 0: exited on signal 11 (core dumped) Hmm, I not sure what that is. Can you give us backtrace and your saslauthd startup cmd? saslauthd -a pam (with pam_pgsql) still gives me that problem :-( Today I tried to use gdb on saslauthd and that's what I've got: Program received signal SIGSEGV, Segmentation fault. 0x28104942 in vfprintf () from /usr/lib/libc.so.4 I don't know if that will give you any clue Any help will be greatli appreciated! This does not help. Run gdb against the saslauthd core file and type bt. This is output of gdb on one of my servers: [EMAIL PROTECTED] saslauthd]# gdb saslauthd saslauthd.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd...(no debugging symbols found)... Core was generated by `saslauthd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libcrypt.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libpam.so.1...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_pgsql.so...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libpq.so.3...(no debugging symbols found)...done. Reading symbols from /usr/lib/libmd.so.2...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libintl.so.5...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libssl.so.3...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libcrypto.so.3...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_skey.so...(no debugging symbols found)...done. Reading symbols from /usr/lib/libskey.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/pam_unix.so...(no debugging symbols found)...done. Reading symbols from /usr/lib/libutil.so.3...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x28104942 in vfprintf () from /usr/lib/libc.so.4 (gdb) bt #0 0x28104942 in vfprintf () from /usr/lib/libc.so.4 #1 0x280eae92 in vsyslog () from /usr/lib/libc.so.4 #2 0x280eabe5 in syslog () from /usr/lib/libc.so.4 #3 0x2812e102 in pam_sm_acct_mgmt () from /usr/lib/pam_pgsql.so #4 0x2808c271 in pam_getenvlist () from /usr/lib/libpam.so.1 #5 0x2808c51d in _pam_dispatch () from /usr/lib/libpam.so.1 #6 0x2808b56c in pam_acct_mgmt () from /usr/lib/libpam.so.1 #7 0x8049ad0 in auth_pam () #8 0x804c7ac in do_auth () #9 0x804bee1 in do_request () #10 0x804bb39 in ipc_loop () #11 0x804c743 in main () #12 0x804972e in _start () (gdb) quit Something in the pam_pgsql module is causing vfprintf() to crash. Does this happen for every authentication, or just once in a while. If the latter, try running saslauthd -n 0 (zero), this might hide any memory leaks in PAM of the pgsql module. Unless you actually need PAM for some reason, I'd suggest using the SQL auxprop plugin included in SASL (which supports PgSQL). It will elimiate any PAM issues and allow you to use non-plaintext mechanisms as well. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: Cyrus IMAPd 2.2.3 Released
On Fri, Jan 16, Ken Murchison wrote: What about this issue: http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=request%20info%20until%20latermsg=23996 Using 2.2.3 and saslauthd I get the same error. [...] using cyrus-sasl-2.1.7 2.1.7 or 2.1.17? I just went through the trouble of configuring pam_mysql (0.4.7) for use with saslauthd (2.1.17) and it works fine with Cyrus 2.2.3. If you share your config, perhaps we can help. It's saslauthd -a pam using pam_ldap. And I can only use sasl2.1.7, as I don't have 2.1.17 currently on the platform I am testing. I was not even able to compile all things together and don't want to investigate any more time. I'll try with more recent environment within the next weeks. -- With best regards, Carsten Hoeger pgp0.pgp Description: PGP signature
Re: Cyrus IMAPd 2.2.3 Released
On Thu, Jan 15, Rob Siemborski wrote:
I'm quite pleased to announce the long-awaited stable release of Cyrus
IMAPd 2.2.3. This release contains substantial new features over the 2.1
series including extensive support for mailbox annotations, NNTP, much
more stable process accounting, and of course, virtual domains.
What about this issue:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=request%20info%20until%20latermsg=23996
Using 2.2.3 and saslauthd I get the same error.
Process 19491 attached - interrupt to quit
select(1, [0], NULL, NULL, {1480, 44}) = 1 (in [0], left {1477, 98})
time(NULL) = 1074265801
read(0, . login cyrus secret1\r\n, 4096) = 23
socket(PF_UNIX, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_UNIX, path=/var/run/sasl2//mux}, 110) = 0
writev(10, [{\0\5cyrus\0\7secret1\0\4imap\0\0, 24}], 1) = 24
read(10, \0\2, 2) = 2
read(10, OK, 2) = 2
close(10) = 0
select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
write(1, . NO Login failed: can\'t request..., 63) = 63
time(NULL) = 1074265801
select(1, [0], NULL, NULL, {1800, 0}
using cyrus-sasl-2.1.7
--
With best regards,
Carsten Hoeger
pgp0.pgp
Description: PGP signature
Re: Cyrus IMAPd 2.2.3 Released
Carsten Hoeger wrote:
What about this issue:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=request%20info%20until%20latermsg=23996
Using 2.2.3 and saslauthd I get the same error.
Process 19491 attached - interrupt to quit
select(1, [0], NULL, NULL, {1480, 44}) = 1 (in [0], left {1477, 98})
time(NULL) = 1074265801
read(0, . login cyrus secret1\r\n, 4096) = 23
socket(PF_UNIX, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_UNIX, path=/var/run/sasl2//mux}, 110) = 0
writev(10, [{\0\5cyrus\0\7secret1\0\4imap\0\0, 24}], 1) = 24
read(10, \0\2, 2) = 2
read(10, OK, 2) = 2
close(10) = 0
select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
write(1, . NO Login failed: can\'t request..., 63) = 63
time(NULL) = 1074265801
select(1, [0], NULL, NULL, {1800, 0}
using cyrus-sasl-2.1.7
Not sure how applicable this will be, but in cyrus 2.2.1 and 2.2.2 using
saslauthd 2.1.15 I have no problem at all using saslauthd - pam -
pam_mysql - mysql
Eric
Re: Cyrus IMAPd 2.2.3 Released
Carsten Hoeger wrote:
On Thu, Jan 15, Rob Siemborski wrote:
I'm quite pleased to announce the long-awaited stable release of Cyrus
IMAPd 2.2.3. This release contains substantial new features over the 2.1
series including extensive support for mailbox annotations, NNTP, much
more stable process accounting, and of course, virtual domains.
What about this issue:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=request%20info%20until%20latermsg=23996
Using 2.2.3 and saslauthd I get the same error.
Process 19491 attached - interrupt to quit
select(1, [0], NULL, NULL, {1480, 44}) = 1 (in [0], left {1477, 98})
time(NULL) = 1074265801
read(0, . login cyrus secret1\r\n, 4096) = 23
socket(PF_UNIX, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_UNIX, path=/var/run/sasl2//mux}, 110) = 0
writev(10, [{\0\5cyrus\0\7secret1\0\4imap\0\0, 24}], 1) = 24
read(10, \0\2, 2) = 2
read(10, OK, 2) = 2
close(10) = 0
select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
write(1, . NO Login failed: can\'t request..., 63) = 63
time(NULL) = 1074265801
select(1, [0], NULL, NULL, {1800, 0}
using cyrus-sasl-2.1.7
2.1.7 or 2.1.17? I just went through the trouble of configuring
pam_mysql (0.4.7) for use with saslauthd (2.1.17) and it works fine with
Cyrus 2.2.3. If you share your config, perhaps we can help.
Just out of curiosity, is there some reason why you need to use PAM,
rather than using the SQL auxprop plugin?
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: Cyrus IMAPd 2.2.3 Released
On Fri, 16 Jan 2004, Ken Murchison wrote:
Carsten Hoeger wrote:
On Thu, Jan 15, Rob Siemborski wrote:
I'm quite pleased to announce the long-awaited stable release of Cyrus
IMAPd 2.2.3. This release contains substantial new features over the 2.1
series including extensive support for mailbox annotations, NNTP, much
more stable process accounting, and of course, virtual domains.
What about this issue:
http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrussearchterm=request%20info%20until%20latermsg=23996
Using 2.2.3 and saslauthd I get the same error.
Process 19491 attached - interrupt to quit
select(1, [0], NULL, NULL, {1480, 44}) = 1 (in [0], left {1477, 98})
time(NULL) = 1074265801
read(0, . login cyrus secret1\r\n, 4096) = 23
socket(PF_UNIX, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_UNIX, path=/var/run/sasl2//mux}, 110) = 0
writev(10, [{\0\5cyrus\0\7secret1\0\4imap\0\0, 24}], 1) = 24
read(10, \0\2, 2) = 2
read(10, OK, 2) = 2
close(10) = 0
select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
write(1, . NO Login failed: can\'t request..., 63) = 63
time(NULL) = 1074265801
select(1, [0], NULL, NULL, {1800, 0}
using cyrus-sasl-2.1.7
2.1.7 or 2.1.17? I just went through the trouble of configuring
pam_mysql (0.4.7) for use with saslauthd (2.1.17) and it works fine with
Cyrus 2.2.3. If you share your config, perhaps we can help.
This works only for unqualified users. saslauthd pam module ignores
realms.
--
Igor
Re: Cyrus IMAPd 2.2.3 Released
On Fri, Jan 16, 2004 at 01:33:17PM -0700, [EMAIL PROTECTED] wrote: If I want to compile Cyrus IMAPD with DBD 4.2 support, and I have Cyrus SASL 2.1.17 compiled with DBD 4.1 support, do I need to recompile Cyrus SASL with DBD 4.2 support (does it have that support at all)? That would be wise, yes. Unless all your DBs have been compiled with the --with-uniquename switch, I guess.
Re: Cyrus IMAPd 2.2.3 Released
On Fri, 16 Jan 2004 [EMAIL PROTECTED] wrote: Hi folks, If I want to compile Cyrus IMAPD with DBD 4.2 support, and I have Cyrus SASL 2.1.17 compiled with DBD 4.1 support, do I need to recompile Cyrus SASL with DBD 4.2 support (does it have that support at all)? Yes. You need to fetch sasl from CVS or hack the configure script. -- Igor
Re: Cyrus IMAPd 2.2.3 Released
Quoting Igor Brezac [EMAIL PROTECTED]: Yes. You need to fetch sasl from CVS or hack the configure script. OK, that's clear. I'll better wait for new Cyrus SASL release that will support BDB 4.2. But I have another problem at one of my servers with Cyrus ASL 2.1.17 (I have the same v. 2.1.17 on all of my servers installed, but it happens only at this server). Here is the part of messages log file: Jan 16 06:58:37 synodon ctl_cyrusdb[58227]: checkpointing cyrus databases Jan 16 06:58:37 synodon ctl_cyrusdb[58227]: done checkpointing cyrus databases Jan 16 06:59:18 synodon /kernel: pid 44234 (saslauthd), uid 0: exited on signal 11 (core dumped) Jan 16 06:59:18 synodon imap[58231]: size read failed Jan 16 06:59:18 synodon imap[58231]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 06:59:24 synodon /kernel: pid 44231 (saslauthd), uid 0: exited on signal 11 (core dumped) Jan 16 06:59:24 synodon imap[58231]: size read failed Jan 16 06:59:24 synodon imap[58231]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 06:59:28 synodon /kernel: pid 44232 (saslauthd), uid 0: exited on signal 11 (core dumped) Jan 16 06:59:28 synodon imap[58231]: size read failed Jan 16 06:59:28 synodon imap[58231]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 07:01:27 synodon imap[58247]: login: [192.168.2.243] dsheard plaintext Jan 16 07:02:07 synodon /kernel: pid 44230 (saslauthd), uid 0: exited on signal 11 (core dumped) Jan 16 07:02:07 synodon imap[58250]: size read failed Jan 16 07:02:07 synodon imap[58250]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 07:02:30 synodon imap[58250]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-13): authentication failure: checkpass failed Jan 16 07:02:36 synodon imap[58250]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-13): authentication failure: checkpass failed What maight cause that error? Thank you for your help, Dmitry
Re: Cyrus IMAPd 2.2.3 Released
On Fri, 16 Jan 2004 [EMAIL PROTECTED] wrote: Quoting Igor Brezac [EMAIL PROTECTED]: Yes. You need to fetch sasl from CVS or hack the configure script. OK, that's clear. I'll better wait for new Cyrus SASL release that will support BDB 4.2. The actual code did not change, just the Berkeley detection did. If you remove db 4.1.25 from your system, the sasl configure script should find 4.2.52 (Do not forget to apply a patch from the sleepycat site: http://www.sleepycat.com/update/4.2.52/patch.4.2.52.html) But I have another problem at one of my servers with Cyrus ASL 2.1.17 (I have the same v. 2.1.17 on all of my servers installed, but it happens only at this server). Here is the part of messages log file: Jan 16 06:58:37 synodon ctl_cyrusdb[58227]: checkpointing cyrus databases Jan 16 06:58:37 synodon ctl_cyrusdb[58227]: done checkpointing cyrus databases Jan 16 06:59:18 synodon /kernel: pid 44234 (saslauthd), uid 0: exited on signal 11 (core dumped) Jan 16 06:59:18 synodon imap[58231]: size read failed Jan 16 06:59:18 synodon imap[58231]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 06:59:24 synodon /kernel: pid 44231 (saslauthd), uid 0: exited on signal 11 (core dumped) Jan 16 06:59:24 synodon imap[58231]: size read failed Jan 16 06:59:24 synodon imap[58231]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 06:59:28 synodon /kernel: pid 44232 (saslauthd), uid 0: exited on signal 11 (core dumped) Jan 16 06:59:28 synodon imap[58231]: size read failed Jan 16 06:59:28 synodon imap[58231]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 07:01:27 synodon imap[58247]: login: [192.168.2.243] dsheard plaintext Jan 16 07:02:07 synodon /kernel: pid 44230 (saslauthd), uid 0: exited on signal 11 (core dumped) Jan 16 07:02:07 synodon imap[58250]: size read failed Jan 16 07:02:07 synodon imap[58250]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-1): generic failure: checkpass failed Jan 16 07:02:30 synodon imap[58250]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-13): authentication failure: checkpass failed Jan 16 07:02:36 synodon imap[58250]: badlogin: [68.147.210.233] plaintext dennis.rendflesh SASL(-13): authentication failure: checkpass failed What maight cause that error? Hmm, I not sure what that is. Can you give us backtrace and your saslauthd startup cmd? -- Igor
Re: Cyrus IMAPd 2.2.3 Released
Rob Siemborski [EMAIL PROTECTED] writes: I'm quite pleased to announce the long-awaited stable release of Cyrus IMAPd 2.2.3. This release contains substantial new features over the 2.1 series including extensive support for mailbox annotations, NNTP, much more stable process accounting, and of course, virtual domains. This release also contains support for Berkeley DB 4.2, runtime configuration of cyrusdb backends, a socket map daemon compatible with Sendmail 8.13, and much more. Now that cyrus supports db4.2, is it recommended to upgrade installs that use db4.0 to db4,2 as part of an upgrade to 2.2.3? If so, is there anything I need to do other than point cyrus at the 4.2 libraries during the compile? (Is there a command I can run to tell what DB formats I'm using on my 2.1.15 install? I want to convert to the defaults if possible, although I'm already running skiplist for the mboxlistdb and the seendb) -- Ted Cabeen http://www.pobox.com/~secabeen[EMAIL PROTECTED] Check Website or Keyserver for PGP/GPG Key BA0349D2 [EMAIL PROTECTED] I have taken all knowledge to be my province. -F. Bacon [EMAIL PROTECTED] Human kind cannot bear very much reality.-T.S.Eliot[EMAIL PROTECTED]
Re: Cyrus IMAPd 2.2.3 Released
The actual code did not change, just the Berkeley detection did. If you remove db 4.1.25 from your system, the sasl configure script should find 4.2.52 (Do not forget to apply a patch from the sleepycat site: http://www.sleepycat.com/update/4.2.52/patch.4.2.52.html) I'm installing it from FreeBSD ports collection, and there is no option in Makefile to compile it with BDB 4.2. I can hack it to recognize WITH_BDB_VER=42, so this way it will add these options to configure script: -- with-bdb=db42 --with-bdb-incdir=/usr/local/include/db42 Is that what needs to be done? Hmm, I not sure what that is. Can you give us backtrace and your saslauthd startup cmd? What is that backtrace? The startup command is the saslauthd.sh script that comes as a part of FreeBSD cyrus-sasl2 port: [EMAIL PROTECTED] cyrus-sasl2]# ps ax|grep sasl 2442 ?? Is 0:00.51 /usr/local/sbin/saslauthd -a pam 2443 ?? I 0:00.50 /usr/local/sbin/saslauthd -a pam 2444 ?? I 0:00.49 /usr/local/sbin/saslauthd -a pam 2445 ?? I 0:00.49 /usr/local/sbin/saslauthd -a pam 2446 ?? I 0:00.49 /usr/local/sbin/saslauthd -a pam Thanks a lot! Dmitry
Re: Cyrus IMAPd 2.2.3 Released
On Fri, 16 Jan 2004 [EMAIL PROTECTED] wrote: The actual code did not change, just the Berkeley detection did. If you remove db 4.1.25 from your system, the sasl configure script should find 4.2.52 (Do not forget to apply a patch from the sleepycat site: http://www.sleepycat.com/update/4.2.52/patch.4.2.52.html) I'm installing it from FreeBSD ports collection, and there is no option in Makefile to compile it with BDB 4.2. I can hack it to recognize WITH_BDB_VER=42, so this way it will add these options to configure script: -- with-bdb=db42 --with-bdb-incdir=/usr/local/include/db42 Is that what needs to be done? I am not familiar with FreeBSD. My guess is that this is not going to work. Hmm, I not sure what that is. Can you give us backtrace and your saslauthd startup cmd? What is that backtrace? The startup command is the saslauthd.sh script that comes as a part of FreeBSD cyrus-sasl2 port: [EMAIL PROTECTED] cyrus-sasl2]# ps ax|grep sasl 2442 ?? Is 0:00.51 /usr/local/sbin/saslauthd -a pam 2443 ?? I 0:00.50 /usr/local/sbin/saslauthd -a pam 2444 ?? I 0:00.49 /usr/local/sbin/saslauthd -a pam 2445 ?? I 0:00.49 /usr/local/sbin/saslauthd -a pam 2446 ?? I 0:00.49 /usr/local/sbin/saslauthd -a pam Auch... saslauthd/pam is known to be unreliable, furthermore you cannot use saslauthd/pam combination for fully qualified userids ([EMAIL PROTECTED]) because libsasl (2.1.17+) ignores the realm (domain) portion. ;( -- Igor
Re: Cyrus IMAPd 2.2.3 Released
Auch... saslauthd/pam is known to be unreliable, furthermore you cannot use saslauthd/pam combination for fully qualified userids ([EMAIL PROTECTED]) because libsasl (2.1.17+) ignores the realm (domain) portion. ;( But it works just fine with my other 4 servers. I have saslauthd + pam + pam_pgsql (patched to make proper queries to the database to retrieve password for the user @ domain). I'll try to recompile it, may be it will solve that error. Do you think it might be a hardware problem? Thanks again, Dmitry
Re: Cyrus IMAPd 2.2.3 Released
Ted Cabeen wrote: Rob Siemborski [EMAIL PROTECTED] writes: I'm quite pleased to announce the long-awaited stable release of Cyrus IMAPd 2.2.3. This release contains substantial new features over the 2.1 series including extensive support for mailbox annotations, NNTP, much more stable process accounting, and of course, virtual domains. This release also contains support for Berkeley DB 4.2, runtime configuration of cyrusdb backends, a socket map daemon compatible with Sendmail 8.13, and much more. Now that cyrus supports db4.2, is it recommended to upgrade installs that use db4.0 to db4,2 as part of an upgrade to 2.2.3? If so, is there anything I need to do other than point cyrus at the 4.2 libraries during the compile? (Is there a command I can run to tell what DB formats I'm using on my 2.1.15 install? I want to convert to the defaults if possible, although I'm already running skiplist for the mboxlistdb and the seendb) Use the version command in cyradm. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: Cyrus IMAPd 2.2.3 Released
On Fri, 16 Jan 2004 [EMAIL PROTECTED] wrote: Auch... saslauthd/pam is known to be unreliable, furthermore you cannot use saslauthd/pam combination for fully qualified userids ([EMAIL PROTECTED]) because libsasl (2.1.17+) ignores the realm (domain) portion. ;( But it works just fine with my other 4 servers. I have saslauthd + pam + pam_pgsql (patched to make proper queries to the database to retrieve password for the user @ domain). I'll try to recompile it, may be it will solve that error. Do you think it might be a hardware problem? It is difficult to say because I do not know environment. I'd guess that it is not hardware related. -- Igor
Re: Cyrus IMAPd 2.2.3 Released
Hi folks! It's great that cyrus 2.2.3 Released now! This release also contains support for Berkeley DB 4.2, But on Gentoo linux distribution db package compiles with --with-uniquename flag. And cyrus do not found db: checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for db_create in -ldb-4.2... no checking for db_create in -ldb4.2... no checking for db_create in -ldb42... no checking for db_create in -ldb-4.1... no checking for db_create in -ldb4.1... no checking for db_create in -ldb41... no checking for db_create in -ldb-4.0... no checking for db_create in -ldb4.0... no checking for db_create in -ldb-4... no checking for db_create in -ldb40... no checking for db_create in -ldb4... no checking for db_create in -ldb-3.3... no checking for db_create in -ldb3.3... no checking for db_create in -ldb33... no checking for db_create in -ldb-3.2... no checking for db_create in -ldb3.2... no checking for db_create in -ldb32... no checking for db_create in -ldb-3.1... no checking for db_create in -ldb3.1... no checking for db_create in -ldb31... no checking for db_create in -ldb-3... no checking for db_create in -ldb30... no checking for db_create in -ldb3... no checking for db_create in -ldb... no checking for db_open in -ldb... no configure: error: Berkeley DB 3.x or later was not found. You may need to supply the --with-bdb-libdir or --with-bdb-incdir configure options. How to fix it? Thanks in advance, Dmitry.
Re: Cyrus IMAPd 2.2.3 Released
Does config.log show any clues? -Igor On Thu, 15 Jan 2004, Dmitry P. Schegolev wrote: Hi folks! It's great that cyrus 2.2.3 Released now! This release also contains support for Berkeley DB 4.2, But on Gentoo linux distribution db package compiles with --with-uniquename flag. And cyrus do not found db: checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for db_create in -ldb-4.2... no checking for db_create in -ldb4.2... no checking for db_create in -ldb42... no checking for db_create in -ldb-4.1... no checking for db_create in -ldb4.1... no checking for db_create in -ldb41... no checking for db_create in -ldb-4.0... no checking for db_create in -ldb4.0... no checking for db_create in -ldb-4... no checking for db_create in -ldb40... no checking for db_create in -ldb4... no checking for db_create in -ldb-3.3... no checking for db_create in -ldb3.3... no checking for db_create in -ldb33... no checking for db_create in -ldb-3.2... no checking for db_create in -ldb3.2... no checking for db_create in -ldb32... no checking for db_create in -ldb-3.1... no checking for db_create in -ldb3.1... no checking for db_create in -ldb31... no checking for db_create in -ldb-3... no checking for db_create in -ldb30... no checking for db_create in -ldb3... no checking for db_create in -ldb... no checking for db_open in -ldb... no configure: error: Berkeley DB 3.x or later was not found. You may need to supply the --with-bdb-libdir or --with-bdb-incdir configure options. How to fix it? Thanks in advance, Dmitry. -- Igor
Re: Cyrus IMAPd 2.2.3 Released
On Thu, Jan 15, 2004 at 11:24:35PM +0300, Dmitry P. Schegolev wrote: Hi folks! It's great that cyrus 2.2.3 Released now! This release also contains support for Berkeley DB 4.2, But on Gentoo linux distribution db package compiles with --with-uniquename flag. I don't think this has anything to do with --with-uniquename configure: error: Berkeley DB 3.x or later was not found. You may need to supply the --with-bdb-libdir or --with-bdb-incdir configure options. ^^^ Have you tried the above suggestion?
Re: Cyrus IMAPd 2.2.3 Released
Thursday 15 January 2004 23:51 Andreas (a): On Thu, Jan 15, 2004 at 11:24:35PM +0300, Dmitry P. Schegolev wrote: Hi folks! It's great that cyrus 2.2.3 Released now! This release also contains support for Berkeley DB 4.2, But on Gentoo linux distribution db package compiles with --with-uniquename flag. I don't think this has anything to do with --with-uniquename configure: error: Berkeley DB 3.x or later was not found. You may need to supply the --with-bdb-libdir or --with-bdb-incdir configure options. ^^^ Have you tried the above suggestion? I correct .ebuild file which compile db in Gentoo in one line in configure section(comment string --with-uniquename), recompile db, and cyrus find db fine! But Gentoo uses db with uniquename, and it is not comfortable to correct db's .ebuid each time new db version out.
Re: Cyrus IMAPd 2.2.3 Released
On Thu, Jan 15, 2004 at 06:51:36PM -0200, Andreas wrote: But on Gentoo linux distribution db package compiles with --with-uniquename flag. I don't think this has anything to do with --with-uniquename Ops, it could indeed, sorry. If this is the cause, then the configure test should include db.h.
