Jonathan Marsden wrote:
>
> Attaching to one 'connected to but hung' pop3d with gdb shows a
> backtrace of:
>
> (gdb) bt
> #0 0x420dadf4 in read () from /lib/i686/libc.so.6
> #1 0x4002a480 in __DTOR_END__ () from /usr/lib/libsasl2.so.2
> #2 0x40024186 in randinit () from /usr
You might be running out of enthropy.
cat /dev/random to check.
Jonathan Marsden wrote:
On one of our (Red Hat 7.3, dual PIII CPU) servers running cyrus-imapd
(2.2 CVS as of late September 2002), last night POP3 and POP3S access
mysteriously "stopped working". IMAP and IMAPS access are still
On Fri, 10 Jan 2003, Jonathan Marsden wrote:
> Attaching to one 'connected to but hung' pop3d with gdb shows a
> backtrace of:
>
> (gdb) bt
> #0 0x420dadf4 in read () from /lib/i686/libc.so.6
> #1 0x4002a480 in __DTOR_END__ () from /usr/lib/libsasl2.so.2
> #2 0x40024186 in randi
On one of our (Red Hat 7.3, dual PIII CPU) servers running cyrus-imapd
(2.2 CVS as of late September 2002), last night POP3 and POP3S access
mysteriously "stopped working". IMAP and IMAPS access are still fine.
Looking at the logs shows things like:
Jan 10 02:11:16 aerogram pop3s[17907]: DBERROR
