From: Frederic BRIAND (no email)
Date: Thu Sep 13 2007 - 08:32:51 EDT
Ali Nebi wrote:
> Hi all,
>
> i have some problems in a mail server and i don't know how to solve
> these problems.
>
> I get these errors:
>
> /usr/libexec/postfix/lmtp: bad command startup -- throttling : 588
> Time(s)
> 198.231.4.83.rbl-plus.mail-abuse.org: RBL lookup error: Host or
> domain name not found. Name service error for
> name=198.231.4.83.rbl-plus.mail-abuse.org type=A: Host not found, try
> again : 2 Time(s)
> 3.77.214.79.rbl-plus.mail-abuse.org: RBL lookup error: Host or
> domain name not found. Name service error for
> name=3.77.214.79.rbl-plus.mail-abuse.org type=A: Host not found, try
> again : 2 Time(s)
> dict_ldap_lookup: Search error -5: Timed out : 2 Time(s)
> network_biopair_interop: error reading 5 bytes from the network:
> Connection reset by peer : 2 Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeaa10 *** : 2
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeaa30 *** : 4
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeabb0 *** : 2
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeac10 *** : 2
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeac50 *** : 2
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeacb0 *** : 4
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeacf0 *** : 2
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdead30 *** : 2
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdead70 *** : 4
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeadb0 *** : 4
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeaf20 *** : 4
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeb070 *** : 2
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeb0c0 *** : 2
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: *** glibc detected ***
> lmtpd: double free or corruption (out): 0x00002aaaacdeb0d0 *** : 2
> Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]: /lib64/libc.so.6(db.001 : 20 Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]:
> 2aaaaaac6000-2aaaaaacc000 rw-s 00000000 fd:00 57246642
> /var/lib/imap/db/db.002 : 20 Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]:
> 2aaaaaad3000-2aaaaab75000 rw-s 00000000 fd:00 57246649
> /var/lib/imap/db/db.003 : 20 Time(s)
> non-LMTP response from
> hermod.iguanait.com[/var/lib/imap/socket/lmtp]:
> 2aaaaab75000-2aaaaab8d000 rw-s 00000000 fd:00
> fatal: open dictionary: expecting "type:name" form instead of
> "/var/lib/imap/socket/lmtp"
> fatal: open dictionary: expecting "type:name" form instead of
> "/var/lib/imap/socket/lmtp"
> fatal: open dictionary: expecting "type:name" form instead of
> "/var/lib/imap/socket/lmtp"
> fatal: open dictionary: expecting "type:name" form instead of
> "/var/lib/imap/socket/lmtp"
> fatal: open dictionary: expecting "type:name" form instead of
> "/var/lib/imap/socket/lmtp"
> fatal: open dictionary: expecting "type:name" form instead of
> "/var/lib/imap/socket/lmtp"
>
> When this happen with don't receive mails and if we send the people
> don't receive our mails.
>
> We have installed fedora 6,cyrus-imapd-2.3.9-6.fc6, postfix-2.3.3-2.
>
> If you need more info, please ask me, i will post the needed info.
>
> How can i solve these problems ?
> Is that some bug in cyrus?
>
> Thanks in advanced!
> Regards, Ali Nebi!
>
> ----
> 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
Hi,
I've had a similar problem on a small Fedora 6 dedicated server
recently, not with Cyrus or Postix though, but with a PHP module (tidy).
The output was the same. I googled a long time to find out what the
problem was, and as it happens, it seems to be a Fedora problem. The
server was fine until the glibc was updated. In fact, starting from
Fedora 3, the glibc tries to detect errors before they occur, and when
this happens the default behavior is to log a message and kill the process.
There seems to be a trick to solve the problem, with an environment
variable you must set, but I've not tested it. We moved to CentOS 5.
Here is what the Fedora 3 release note states:
The version of glibc provided with Fedora Core 3 performs additional
internal sanity checks to prevent and detect data corruption as early as
possible. By default, should corruption be detected, a message similar
to the following will be displayed on standard error (or logged via
syslog if stderr is not open):
*** glibc detected *** double free or corruption: 0x0937d008 ***
By default, the program that generated this error will also be killed;
however, this (and whether or not an error message is generated) can be
controlled via the MALLOC_CHECK_ environment variable. The following
settings are supported:
0 — Do not generate an error message, and do not kill the program
1 — Generate an error message, but do not kill the program
2 — Do not generate an error message, but kill the program
3 — Generate an error message and kill the program
Note:
If MALLOC_CHECK_ is explicitly set a value other than 0, this causes
glibc to perform more tests that are more extensive than the default,
and may impact performance.
Should you have a program from a third party ISV that triggers these
corruption checks and displays a message, you should file a defect
report with the application's vendor, since this indicates a serious bug.
Here is the link
http://docs.fedoraproject.org/release-notes/fc3/x86/
Hope this helps
FB
---- 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
|
|
|