Kolab 3.3, Debian Wheezy (correction ;-))
Matthias Albrecht
matthias.albrecht at tigerbaer.de
Mon Dec 8 11:47:57 CET 2014
Franz,
you certainly pointed me the right direction. This is from
/var/log/kolab/pykolab.log and seems to show, that Kolab can't access
the LDAP-Server any more.
2014-12-06 17:09:37,844 pykolab.conf WARNING Option ldap/auth_cache_uri
does not exist in config file /etc/kolab/kolab.conf, pulling from defaults
2014-12-06 17:09:37,844 pykolab.conf WARNING Option does not exist in
defaults.
2014-12-07 21:29:09,873 pykolab.imap WARNING Could not connect to Cyrus
IMAP server 'imaps://localhost:993'
2014-12-07 21:29:18,392 pykolab.conf WARNING Option ldap/auth_cache_uri
does not exist in config file /etc/kolab/kolab.conf, pulling from defaults
2014-12-07 21:29:18,392 pykolab.conf WARNING Option does not exist in
defaults.
2014-12-07 23:38:35,415 pykolab.auth ERROR An error occured using
_regular_search: SERVER_DOWN({'desc': "Can't contact LDAP server"},)
2014-12-07 23:38:35,416 pykolab.auth ERROR Traceback (most recent call
last):
File
"/usr/lib/python2.7/dist-packages/pykolab/auth/ldap/__init__.py", line
2725, in _search
secondary_domains
File "<string>", line 10, in <module>
File
"/usr/lib/python2.7/dist-packages/pykolab/auth/ldap/__init__.py", line
2623, in _regular_search
attrsonly=attrsonly
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 549,
in search
return
self.search_ext(base,scope,filterstr,attrlist,attrsonly,None,None)
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 541,
in search_ext
timeout,sizelimit,
File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 99,
in _ldap_call
result = func(*args,**kwargs)
SERVER_DOWN: {'desc': "Can't contact LDAP server"}
And this is in /var/log/kolab-webadmin/errors:
[07-Dec-2014 23:32:33 +0100](ham9u49ajk2cfg20g8fafq4b62): PHP Error:
Login failed. Unable to decode response (POST)
[07-Dec-2014 23:35:06 +0100](ham9u49ajk2cfg20g8fafq4b62): PHP Error:
Login failed. Unable to connect to
ssl://sikolab.systematic-investments:443. Error:
php_network_getaddresses: getaddrinfo failed: Name or service not known
(POST)
[07-Dec-2014 23:39:25 +0100](ham9u49ajk2cfg20g8fafq4b62): PHP Error:
Login failed. Unable to connect to
tcp://sikolab.systematic-investments:80. Error:
php_network_getaddresses: getaddrinfo failed: Name or service not known
(POST)
Obviously, more than one thing went wrong when I secured Kolab.
I then followed the section "Apache - Switch to own Certification
Authority" in http://kolab.org/planet?page=1 since this said "Alter
web-server configuration to require valid client certificate, but allow
direct API calls from mail server (omit |internal error| when using
|kolab-admin|).". But no change.
Does anyone know help?
Thanks,
Matthias
-------- Original-Nachricht --------
*Betreff: *Re: Kolab 3.3, Debian Wheezy (correction ;-))
*Von: *Franz Skale <i.bin at dah.am>
*An: *Matthias Albrecht <matthias.albrecht at tigerbaer.de>,
users at lists.kolab.org
*Datum: *08.12.2014 11:34
>
> Hi,
> lost some chars ;-)
> I meant, that /api is not a known service to kolab.
> Refer to the error log.
>
>
> Rgds.
>
> Franz
>
> Am 08.12.14 um 11:29 schrieb Franz Skale:
>> Hi,
>> i have a clean 3.3 setup running on wheezy64 without having the need to
>> add the api_url config option, which is no n service to kolab.
>> Check the logfile: /var/log/kolab-webadmin/errors
>> You should enable debug logging on the kolab services:
>> /etc/default/kolab* or any other kolab service like wallace.
>> Change -l warning to -l debug and restart the services.
>> Then check /var/log/kolab/* etc. for reasonale output.
>>
>>
>> Rgds.
>>
>>
>> Franz
>>
>>
>> Am 07.12.14 um 23:38 schrieb Matthias Albrecht:
>>> Ladies and Gentlemen,
>>>
>>> I have setup Kolab 3.3 on Debian Wheezy and then follow the "secure
>>> your Kolab with SSL". Before I did that, I used the web admin (cn =
>>> Directory Manager) to define my users. Everything worked. After having
>>> secured with SSL, I now get an "Internal System Error". I followed
>>> https://wiki.kolab.org/Kolab3_Troubleshooting to replace
>>>
>>> api_url =https://sikolab.systematic-investments/kolab-webadmin/api
>>>
>>> against
>>>
>>> api_url =http://localhost/kolab-webadmin/api
>>>
>>> in /etc/kolab/kolab.conf under the [kolab_wap] section to no avail.
>>>
>>> Any ideas? Am I in the right forum for these questions?
>>>
>>> Good night,
>>>
>>> Matthias
>>> _______________________________________________
>>> users mailing list
>>> users at lists.kolab.org
>>> https://lists.kolab.org/mailman/listinfo/users
>>
>>
>> _______________________________________________
>> users mailing list
>> users at lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20141208/7b5ad63f/attachment-0001.html>
More information about the users
mailing list