User created but mailbox missing

Wed Oct 7 14:13:11 CEST 2015

Hello Timotheus,
your log file pointed to the problem, thank you!

/var/log/kolab/pykolab.log says:

....
2015-10-07 13:28:54,547 pykolab.auth ERROR An error occured using
_persistent_search: SERVER_DOWN({'desc': "Can't contact LDAP server"},)
2015-10-07 13:28:54,547 pykolab.auth ERROR Traceback (most recent call
last):
  File "/usr/lib/python2.7/dist-packages/pykolab/auth/ldap/__init__.py",
line 2815, in _search
    secondary_domains
  File "<string>", line 10, in <module>
  File "/usr/lib/python2.7/dist-packages/pykolab/auth/ldap/__init__.py",
line 2490, in _persistent_search
    serverctrls=psearch_server_controls
  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"}

...

If I take a look at systemctl, it shows parts of the 389 are not running:

  cyrus-imapd.service                                     loaded active
running   LSB: Init system for Kolab Cyrus IMAP/POP3 daemons.
  dbus.service                                            loaded active
running   D-Bus System Message Bus
  dirsrv-admin.service                                    loaded active
exited    LSB: Start and stop 389 Directory Admin Server
● dirsrv-snmp.service                                     loaded failed
failed    389 Directory Server SNMP Subagent.
● dirsrv at admin.service                                    loaded failed
failed    389 Directory Server admin.
  dirsrv at mail.service                                     loaded active
running   389 Directory Server mail.
  exim4.service                                           loaded active
exited    LSB: exim Mail Transport Agent

root at mail:/home/user# systemctl status dirsrv-snmp.service

*●* dirsrv-snmp.service - 389 Directory Server SNMP Subagent.

   Loaded: loaded (/lib/systemd/system/dirsrv-snmp.service; enabled)

   Active: *failed* (Result: exit-code) since Mi 2015-10-07 14:03:42 CEST;
7s ago

  Process: 1527 ExecStart=/usr/sbin/ldap-agent
/etc/dirsrv/config/ldap-agent.conf *(code=exited, status=1/FAILURE)*

Okt 07 14:03:42 mail.xxx.de ldap-agent[1527]: ldap-agent: No server
instances defined in config file

Okt 07 14:03:42 mail.xxx.de systemd[1]: *dirsrv-snmp.service: control
process exited, code=exited status=1*

Okt 07 14:03:42 mail.xxx.de systemd[1]: *Failed to start 389 Directory
Server SNMP Subagent..*

Okt 07 14:03:42 mail.xxx.de systemd[1]: *Unit dirsrv-snmp.service entered
failed state.*

root at mail:/home/user# systemctl status dirsrv at admin.service says:

*●* dirsrv at admin.service - 389 Directory Server admin.

   Loaded: loaded (/lib/systemd/system/dirsrv at .service; enabled)

   Active: *failed* (Result: exit-code) since Mi 2015-10-07 13:28:45 CEST;
42min ago

  Process: 456 ExecStart=/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-%i -i
/var/run/dirsrv/slapd-%i.pid -w /var/run/dirsrv/slapd-%i.startpid
*(code=exited,
status=1/FAILURE)*

Okt 07 13:28:44 mail.xxx.de ns-slapd[456]: [07/Oct/2015:13:28:44 +0200] dse
- The configuration file /etc/dirsrv/slapd-admin/dse...rror -1

Okt 07 13:28:44 mail.xxx.de ns-slapd[456]: [07/Oct/2015:13:28:44 +0200] dse
- The configuration file /etc/dirsrv/slapd-admin/dse...rror -1

Okt 07 13:28:44 mail.xxx.de ns-slapd[456]: [07/Oct/2015:13:28:44 +0200]
config - The given config file /etc/dirsrv/slapd-admin/d...found.)

Okt 07 13:28:45 mail.xxx.de ns-slapd[456]: [07/Oct/2015:13:28:45 +0200]
schema - No schema files were found in the directory /et.../schema

Okt 07 13:28:45 mail.xxx.de ns-slapd[456]: [07/Oct/2015:13:28:45 +0200] dse
- Please edit the file to correct the reported probl...server.

Okt 07 13:28:45 mail.xxx.de systemd[1]: *dirsrv at admin.service: control
process exited, code=exited status=1*

Okt 07 13:28:45 mail.xxx.de systemd[1]: *Failed to start 389 Directory
Server admin..*

Okt 07 13:28:45 mail.xxx.de systemd[1]: *Unit dirsrv at admin.service entered
failed state.*

Any ideas how to fix this out there?

Sophie

2015-10-07 13:55 GMT+02:00 Timotheus Pokorra <timotheus at kolab.org>:

> Hello Sophie,
>
> You can check /var/log/kolab/pykolab.log
>
> You also can try this:
>
> service kolabd stop
> kolab -d 9 sync 2>&1 | tee kolab-sync.log
> service kolabd start
>
> and see if you get any error messages.
>
> Hope this helps,
>   Timotheus
>
>
>
> On 7 October 2015 at 12:55, Sophie Nellscher
> <sophie.nellscher at googlemail.com> wrote:
> > Hello,
> >
> > I've got a problem (again) that I can't figure out: After my fresh
> install
> > of Kolab on a fresh system I am able to create users through Kolab
> Webadmin
> > but their mailbox is not created. There is no mailserver listed at the
> form
> > and I got an error after login at roundcube.
> >
> > Has anyone dealed with the same issue or is there log on creating users I
> > can consider?
> >
> > Thanks!
> >
> > Best regards
> > Sophie
> >
> > _______________________________________________
> > 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/20151007/b9bb1a2a/attachment.html>