<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>I recently was looking at 9folders (android client) and why I can't see any folders on it other than inbox & sent. I decided to see what updates were available on Kolab16 under Centos. After the update, I'm now running 7.2.1511.</p>
<p>Once the update was done, I rebooted, and quickly noticed that I could not send email.I sa errors like this in the maillog:</p>
<p style="padding-left: 30px;">Sep 11 23:01:14 kolab16 postfix/trivial-rewrite[11366]: warning: ldap:/etc/postfix/ldap/mydestination.cf: table lookup problem<br />Sep 11 23:01:16 kolab16 imaps[3445]: badlogin: localhost [127.0.0.1] login [SASL(-13): authentication failure: checkpass failed]<br />Sep 11 23:01:24 kolab16 postfix/trivial-rewrite[11366]: warning: dict_ldap_connect: Unable to bind to server ldap://localhost:389 with dn uid=kolab-service,ou=Special Users,dc=sbsroc,dc=com: -5 (Timed out)</p>
<p>Somehow I didn't notice the ldap error at first glance and looked at other things, noticing the following in /var/log/kolab/pykolab.log:</p>
<p style="padding-left: 30px;">2016-09-11 23:04:02,420 pykolab.wallace ERROR Module resources.heartbeat() failed with error: Traceback (most recent call last):<br /> File "/usr/lib/python2.7/site-packages/wallace/__init__.py", line 89, in modules_heartbeat<br /> modules.heartbeat(module, lastrun)<br /> File "/usr/lib/python2.7/site-packages/wallace/modules.py", line 128, in heartbeat<br /> return modules[name]['heartbeat'](*args, **kw)<br /> File "/usr/lib/python2.7/site-packages/wallace/module_resources.py", line 417, in heartbeat<br /> resource_dns = auth.find_resource('*')<br /> File "/usr/lib/python2.7/site-packages/pykolab/auth/__init__.py", line 220, in find_resource<br /> result = self._auth.find_resource(address)<br /> File "/usr/lib/python2.7/site-packages/pykolab/auth/ldap/__init__.py", line 765, in find_resource<br /> self._bind()<br /> File "/usr/lib/python2.7/site-packages/pykolab/auth/ldap/__init__.py", line 1435, in _bind<br /> self.ldap.simple_bind_s(bind_dn, bind_pw)<br /> File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 837, in simple_bind_s<br /> res = self._apply_method_s(SimpleLDAPObject.simple_bind_s,*args,**kwargs)<br /> File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 818, in _apply_method_s<br /> return func(self,*args,**kwargs)<br /> File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 208, in simple_bind_s<br /> resp_type, resp_data, resp_msgid, resp_ctrls = self.result3(msgid,all=1,timeout=self.timeout)<br /> File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 469, in result3<br /> resp_ctrl_classes=resp_ctrl_classes<br /> File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 476, in result4<br /> ldap_result = self._ldap_call(self._l.result4,msgid,all,timeout,add_ctrls,add_intermediates,add_extop)<br /> File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 99, in _ldap_call<br /> result = func(*args,**kwargs)<br />TIMEOUT</p>
<p>When I finally honed in on the ldap server, I tried to start it:</p>
<p style="padding-left: 30px;">[root@kolab16 ~]# systemctl restart dirsrv@service.service<br />Job for dirsrv@service.service failed because a configured resource limit was exceeded. See "systemctl status dirsrv@service.service" and "journalctl -xe" for details.</p>
<p>So I ran the suggestion:</p>
<p style="padding-left: 30px;">[root@kolab16 ~]# journalctl -xe<br />Sep 11 23:17:44 kolab16.sbsllc.local imaps[12089]: starttls: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits reused) no authentication<br />Sep 11 23:17:46 kolab16.sbsllc.local imaps[11890]: badlogin: localhost [127.0.0.1] plaintext odoo@mydomain.com SASL(-13): authentication failure: checkpass fai<br />Sep 11 23:18:14 kolab16.sbsllc.local imaps[12089]: timeout_select: reading from ptloader: Connection timed out<br />Sep 11 23:18:14 kolab16.sbsllc.local imaps[12089]: ptload failed: but canonified support@mydomain.com -> support@mydomain.com<br />Sep 11 23:18:16 kolab16.sbsllc.local polkitd[926]: Registered Authentication Agent for unix-process:12166:120602 (system bus name :1.36 [/usr/bin/pkttyagent<br />Sep 11 23:18:16 kolab16.sbsllc.local systemd[1]: Failed to load environment files: No such file or directory<br />Sep 11 23:18:16 kolab16.sbsllc.local systemd[1]: dirsrv@service.service failed to run 'start' task: No such file or directory<br />Sep 11 23:18:16 kolab16.sbsllc.local systemd[1]: Failed to start 389 Directory Server service..<br />-- Subject: Unit dirsrv@service.service has failed<br />-- Defined-By: systemd<br />-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel<br />-- <br />-- Unit dirsrv@service.service has failed.<br />-- <br />-- The result is failed.</p>
<p>The 389 server is not running... I couldn't log in to roundcube, could send email with thunderbird, etc. the web admin panel also didn't let me log in. Since the auth backend is down, that's expected.</p>
<p>I rolled back to a snapshot of this virtual machine, and booted it up... same issue!! Since the old versio behaved the same way, I went back to the newly updated snapshot. I figure if it's failing, I might as well work on the latest version.</p>
<p>After letting it sit for a while during my google research, I received a "new mail" desktop notification from my browser. Uhmmmmm. It started working on its own!</p>
<p>I checked the service status, and it still says it failed:</p>
<p style="padding-left: 30px;">[root@kolab16 ~]# systemctl status dirsrv@service.service<br />● dirsrv@service.service - 389 Directory Server service.<br /> Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled; vendor preset: disabled)<br /> Active: failed (Result: resources)<br /><br />Sep 11 23:10:56 kolab16.sbsllc.local systemd[1]: Failed to load environment files: No such file or directory<br />Sep 11 23:10:56 kolab16.sbsllc.local systemd[1]: dirsrv@service.service failed to run 'start' task: No such file or directory<br />Sep 11 23:10:56 kolab16.sbsllc.local systemd[1]: Failed to start 389 Directory Server service..<br />Sep 11 23:10:56 kolab16.sbsllc.local systemd[1]: dirsrv@service.service failed.<br />Sep 11 23:10:56 kolab16.sbsllc.local systemd[1]: Starting 389 Directory Server service....<br />Sep 11 23:18:16 kolab16.sbsllc.local systemd[1]: Failed to load environment files: No such file or directory<br />Sep 11 23:18:16 kolab16.sbsllc.local systemd[1]: dirsrv@service.service failed to run 'start' task: No such file or directory<br />Sep 11 23:18:16 kolab16.sbsllc.local systemd[1]: Failed to start 389 Directory Server service..<br />Sep 11 23:18:16 kolab16.sbsllc.local systemd[1]: dirsrv@service.service failed.<br />Sep 11 23:18:16 kolab16.sbsllc.local systemd[1]: Starting 389 Directory Server service....</p>
<p>But... the LDAP port is open and listening:</p>
<p style="padding-left: 30px;">[root@kolab16 ~]# netstat -nap | grep 389 | grep "LISTEN "<br />tcp6 0 0 :::389 :::* LISTEN 705/ns-slapd <br />[root@kolab16 ~]# </p>
<p>...and I'm still seeing errors all over the kolab logs.</p>
<p style="padding-left: 30px;">2016-09-11 23:46:54,908 pykolab.auth ERROR Traceback (most recent call last):<br /> File "/usr/lib/python2.7/site-packages/pykolab/auth/ldap/__init__.py", line 3059, in _search<br /> secondary_domains<br /> File "<string>", line 10, in <module><br /> File "/usr/lib/python2.7/site-packages/pykolab/auth/ldap/__init__.py", line 2738, in _persistent_search<br /> resp_ctrl_classes={ecnc.controlType:ecnc}<br /> File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 476, in result4<br /> ldap_result = self._ldap_call(self._l.result4,msgid,all,timeout,add_ctrls,add_intermediates,add_extop)<br /> File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 99, in _ldap_call<br /> result = func(*args,**kwargs)<br />TIMEOUT</p>
<p>There must be something wrong underlying, but the system is working... (I just sent this email!) I'd like to make sure it's working the the right reason and that it'll stay up. Thank you to anyone that can lend me some input.</p>
<div>-- <br />
<p>Best regards,</p>
<p style="margin-bottom: 0in; margin-top: 0in;"><strong>Stephen H. Switzer</strong> <br /><span style="font-size: small;"><em>Technical Consultant & System Engineer</em> <br />- VMware VSP <br />- Microsoft MCP, Desktop/Server</span> <br /> <br /><img src="http://www.switzerbusinesssolutions.com/images/SBS-Logo-139-46.png" alt="" width="140" height="47" name="graphics1" align="BOTTOM" border="0" /><br /><span style="font-family: Lohit Hindi;"><span></span></span><span style="font-size: small;"><strong>Switzer Business Solutions, LLC</strong></span><span style="font-size: small;"><br />- VMware VIP Partner <br />- HP Authorized Business Development Partner <br />- Xorcom Certified Dealer</span></p>
</div>
</body></html>