[Kolab-devel] Kolab 2.1 - Possibile DOS?
Gunnar Wrobel
wrobel at pardus.de
Fri Jan 19 09:23:01 CET 2007
"gelpi at corona.it" <corona at gelpi.it> writes:
> Hi,
> too often my kolab 2.1 beta 3 installation stop working.
> what happens is that during kolab daily cron activity some component
> shut down and does not restart or ldap stop responding.
>
> The result is that mail server stops.
>
> This night I forget my thunderbird open and polling every 5 minutes 6
> mailboxes.
> At midnight kolab stop working with a message error of temporary lookup
> failure.
> In postfix.sum I found this lines:
>
> 1 77F5C6C345: virtual_alias_maps map lookup problem for
> gelpi at mydomain.it
> 1 dict_ldap_connect: Unable to bind to server
> ldap://127.0.0.1:389 as cn=nobody,cn=internal,dc=mydomain,dc=it: -1
> (Can't contact LDAP server)
> pickup (total: 1)
> 1 maildrop/77FA76C33B: Error writing message file
> postfix-script (total: 30)
>
> In the lines above I change the real domain.
>
> The solution is to restart kolab with /kolab/etc/rc all restart
>
> I try to cron the last command at 1 o'clock, but if there is a client
> open it simply stop kolab.
>
> This problem aries upgrading from beta 1 to beta 2. I upgrade to beta 3
> but this does not resolve it.
>
> I'll upgrade to beta 4 as soon as possible.
>
> I add also this information. My sasl log is full of lines
>
> <debug> saslauthd[14596]: ldap_simple_bind() failed -1 (Can't contact LDAP server).
> <info> saslauthd[14596]: Retrying authentication
> <debug> saslauthd[14596]: ldap_simple_bind() failed -1 (Can't contact LDAP server).
> <info> saslauthd[14596]: Retrying authentication
> <debug> saslauthd[14588]: ldap_simple_bind() failed -1 (Can't contact LDAP server).
> <info> saslauthd[14588]: Retrying authentication
> <debug> saslauthd[14588]: ldap_simple_bind() failed -1 (Can't contact LDAP server).
> <info> saslauthd[14588]: Retrying authentication
> <debug> saslauthd[14596]: ldap_simple_bind() failed -1 (Can't contact LDAP server).
> <info> saslauthd[14596]: Retrying authentication
>
> I install kolab one year ago using the december 15 snapshot. After that I upgrade to beta 1, then to beta 2 and to beta 3.
>
> I urgently need some help to investigate this problem and find a solution.
Check if you have a problem with random number generation. See
http://wiki.kolab.org/index.php/Timeout_problems
Cheers,
Gunnar
--
____ http://www.pardus.de _________________ http://gunnarwrobel.de _
>> Mail at ease - Rent a kolab groupware server at p at rdus <<
p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
More information about the devel
mailing list