Hello, I have combined Cyrus IMAPD 2.07, Horde IMP 2.2.3, Cyrus SASL 1.5.24, BerkeleyDB 3.1.14 and Sendmail 8.11.0. Logins and passwords for both sendmail and imap/pop are stored in sasldb.db - the feature that attracted me a lot. But Cyrus IMAPD writes nothing to it's logfiles, although they are "touched" and assigned in syslog.conf as: ---------------------------- su-2.03# cat /etc/syslog.conf *.err;kern.debug;auth.notice;mail.crit /dev/console *.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security mail.info /var/log/maillog local1.* /var/log/maillog lpr.info /var/log/lpd-errs cron.* /var/log/cron *.err root *.notice;news.err root *.alert root *.emerg * local6.debug /var/log/imapd.log auth.debug /var/log/imapdauth.log ftp.* /var/log/ftpd.log !startslip *.* /var/log/slip.log !ppp *.* /var/log/ppp.log !pppd *.* /var/log/pppd.log !pinger *.* /var/log/pinger.log !qpopper *.* /var/log/qpopper.log su-2.03# ---------------------------- and ---------------------------- su-2.03# ls -l | grep imapd -rw-r--r-- 1 root wheel 1654645 30 ΟΛΤ 17:35 imapd.log -rw-r--r-- 1 root wheel 20613 30 ΟΛΤ 17:25 imapdauth.log su-2.03# ---------------------------- The problem with logging is a scaring one, but then arises the next: ---------------------------- # top last pid: 78019; load averages: 3.90, 2.67, 3.04 up 1+23:11:47 17:24:57 84 processes: 5 running, 79 sleeping CPU states: 98.8% user, 0.0% nice, 0.8% system, 0.4% interrupt, 0.0% idle Mem: 70M Active, 20M Inact, 20M Wired, 3500K Cache, 22M Buf, 9336K Free Swap: 400M Total, 34M Used, 366M Free, 8% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 77906 cyrus 59 0 5916K 1840K RUN 2:47 23.54% 23.54% imapd 77905 cyrus 61 0 5916K 1840K RUN 2:49 23.29% 23.29% imapd 77967 cyrus 62 0 5916K 1876K RUN 1:13 23.29% 23.29% imapd 77982 cyrus 62 0 5916K 1876K RUN 0:26 23.10% 23.10% imapd 78018 root 31 0 1956K 1080K RUN 0:00 2.22% 0.73% top 411 nobody 2 0 26916K 10848K poll 4:07 0.00% 0.00% squid 320 root 2 0 528K 240K select 2:18 0.00% 0.00% natd 62611 mysql 2 0 29672K 5740K poll 0:36 0.00% 0.00% mysqld 491 nobody 2 0 6404K 5016K accept 0:29 0.00% 0.00% httpd 558 root 10 0 844K 148K nanslp 0:28 0.00% 0.00% tail 472 nobody 2 0 6856K 5276K select 0:28 0.00% 0.00% httpd 301 nobody 2 0 6348K 4932K accept 0:27 0.00% 0.00% httpd 332 root 4 0 3568K 2224K bpf 0:17 0.00% 0.00% trafd 340 root 4 0 3568K 1664K bpf 0:16 0.00% 0.00% trafd 336 root 4 0 3568K 1284K bpf 0:13 0.00% 0.00% trafd ------------------------------ Sometimes imapd's come into a strange state, they live forever and take huge shares of CPU. At the same time, "normal" imapd's work lightning fast. Due to the lack of logging, it's hard for me to trace the roots of this problem. Could you suggest me a way of fixing the logging and some other ways of debuggind which is necessary in this situation? Best regards, Yar.
