Re: Kolab 389 directory server not responding
Jan Kowalsky <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kroupware |
|---|---|
| Message-ID | <f62002ad-573e-0f9c-9c48-f92a231786ec__2027.43735067106$1536351707$gmane$org@datenkollektiv.net> |
Hi Ramiro, Am 07.09.2018 um 11:47 schrieb Ramiro Aukam: > Hello > Our 389 directory server is freezing after some running time (time > varies , can be multiple days or only few minutes) , even restarting the > computer doesn't work but if i run/service dirsrv@kolab restart/ it > takes ~ 1 min to stop but then works for some time again , also if i > wait for ~ 30 min or longer it also starts working again. we struggle a lot with 389-ds. While a single server runs fine we get performance problems spontaneously hangs and crashes in a multimaster replication environment. > I have no idea where to search, i searched in all Log files there is no > error from the directory server. the error log goes to /var/lib/dirsrv/YOURINSTANCE/error.log > Is there a documentation about the 389 directory server in kolab because > it seems to me that it varies from the standart 389 directory server i maybe depends from your distro. on debian since jessie it's the unchanged 389-ds from repository. > couldn't even find a way to turn debug mode on ? Most of configuraion is done with ldap attributes - some of them are even configurable during runtime via ldapmodify. https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/configuration_command_and_file_reference/core_server_configuration_reference#cnconfig-nsslapd_errorlog_level_Error_Log_Level It's all very well documented in either https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/ or https://directory.fedoraproject.org/ Search the 389-users mailing list https://lists.fedoraproject.org/archives/list/[email protected]/message/ZNZ2ADZKCXFHQKNUTHJ7IC57EGGLCFLJ/ for help. Regards Jan