User Details
- User Since
- Nov 7 2020, 8:05 AM (222 w, 1 d)
Dec 16 2024
Dec 13 2024
Oct 1 2024
Yes, the user hr1@os-s.de does not exist in the LDAP. It is not a vaild usser. Therefore no authentication is possible. But this should not be a cause for saslauthd to fail and terminate, am I correct?
The kolab-saslauthd terminates. I reconfigured systemd to automatically restart the daemon because otherwise the login would fail for valid users as well.
Actually the logs continue. Apparently my copy buffer did not copy the complete log. I guess the failed login of hr1 is the last thing of the old process. Then the saslauthd is restarted reading its configuration files:
Sep 23 2024
Any further ideas how to debug this? What error causes INVALIDARGUMENT? Or is this a sign for an uncaught error?
Sep 17 2024
Its kolab 16 on almalinux 9
libkolab-3.2.0-1.35.el9.kolab_16.x86_64
php-kolabformat-1.3.1-1.23.el9.kolab_16.x86_64
roundcubemail-1.5.8.4-4.3.el9.kolab_16.noarch
iRony-0.4.8.5-1.16.el9.kolab_16.noarch
But of course there might be much older entries on the IMAP server since I have been using kolab for the last 13-15 years. Unfortunately the log does not mention the exact entry it is having problems with.
Sep 10 2024
Ok. I have increased the debug output to 9. Unfortunately nothing is logged. kolab-saslauthd failed at 08:03:39 and is automatically restarted.
Sep 4 2024
I have increased the debug output to 5 so far. Currently it only logs failed authentications. I will increase it to 9 now. I was a bit hesitant because of the log size.
Aug 9 2024
Thanks a lot. Saslauthd fails every 3-14 days. Once I have more data, I will add it to the ticket.
Yes, this seems to fix the issue. When will this be included in the packages?
Aug 2 2024
Jul 16 2024
I can second that. I ran into this issue as well. The dependency is not configured therefore the package is missing when doing dnf install kolab.
Hi there,
I was just able to successfully upgrade from CentOS 7 to Almalinux 9. Everything seems to be working the in place upgrade of the 389ds and the cyrus imapd were a bit of a hassle, but after testing it several times based on backups it worked ok. I can share my list of commands.
Jun 3 2024
Oct 26 2023
Feb 28 2022
Since nobody is answering:
The reason for the above problem is the fact that apparently the following two packages are obsoleted by EPEL:
Jan 26 2022
Nov 7 2020
Guam logs:
2020-11-07 07:20:13.817 [error] <0.396.0> Supervisor {<0.396.0>,kolab_guam_listener} had child session started with {kolab_guam_session,start_link,undefined} at <0.18081.1> exit with reason no match of right hand value {error,closed} in kolab_guam_session:accept_client/1 line 178 in context child_terminated
2020-11-07 07:20:13.818 [error] <0.18185.1> gen_server <0.18185.1> terminated with reason: no match of right hand value {error,closed} in kolab_guam_session:accept_client/1 line 178
2020-11-07 07:20:13.819 [error] <0.18185.1> CRASH REPORT Process <0.18185.1> with 0 neighbours exited with reason: no match of right hand value {error,closed} in kolab_guam_session:accept_client/1 line 178 in gen_server:terminate/7 line 826
2020-11-07 07:20:13.819 [error] <0.396.0> Supervisor {<0.396.0>,kolab_guam_listener} had child session started with {kolab_guam_session,start_link,undefined} at <0.18185.1> exit with reason no match of right hand value {error,closed} in kolab_guam_session:accept_client/1 line 178 in context child_terminated
2020-11-07 07:20:13.819 [error] <0.18130.1> gen_server <0.18130.1> terminated with reason: no match of right hand value {error,closed} in kolab_guam_session:accept_client/1 line 178
2020-11-07 07:20:13.819 [error] <0.18130.1> CRASH REPORT Process <0.18130.1> with 0 neighbours exited with reason: no match of right hand value {error,closed} in kolab_guam_session:accept_client/1 line 178 in gen_server:terminate/7 line 826
2020-11-07 07:20:13.819 [error] <0.396.0> Supervisor {<0.396.0>,kolab_guam_listener} had child session started with {kolab_guam_session,start_link,undefined} at <0.18130.1> exit with reason no match of right hand value {error,closed} in kolab_guam_session:accept_client/1 line 178 in context child_terminated
2020-11-07 07:20:13.826 [error] <0.18128.1> gen_server <0.18128.1> terminated with reason: no match of right hand value {error,closed} in kolab_guam_session:accept_client/1 line 178
2020-11-07 07:20:13.826 [error] <0.18128.1> CRASH REPORT Process <0.18128.1> with 0 neighbours exited with reason: no match of right hand value {error,closed} in kolab_guam_session:accept_client/1 line 178 in gen_server:terminate/7 line 826
2020-11-07 07:20:13.826 [error] <0.396.0> Supervisor {<0.396.0>,kolab_guam_listener} had child session started with {kolab_guam_session,start_link,undefined} at <0.18128.1> exit with reason no match of right hand value {error,closed} in kolab_guam_session:accept_client/1 line 178 in context child_terminated
Happens as well on CentOS 7 after installing the current guam update guam-0.9.8-1.3.el7.kolab_16.x86_64