Modify ↓

Ticket #2038 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

ldap slave module not able to activate

Reported by: snarf77@… Owned by: jsalamero@…
Milestone: Component: users
Severity: normal Keywords: ldap
Cc:

Description

I use two Ebox (one for networking stuff included ldap master) and the second one as mail server which should connect to the master LDAP.

boths boxes can ping each other and password seem ok (as I got this error previsouly but now everything is ok).

I hope the log report attach will help

regards

Snarf

Attachments

ebox.log Download (42.8 KB) - added by snarf77@… 3 years ago.
ldap slave to master sync fail log report

Change History

Changed 3 years ago by snarf77@…

ldap slave to master sync fail log report

comment:1 Changed 3 years ago by jsalamero@…

Make sure hostnames, both for the master and the slave can be resolved from both sides. Configure it on /etc/hosts or using your local DNS.

comment:2 Changed 3 years ago by cperez@…

  • Status changed from new to closed
  • Resolution set to fixed

(In [18848]) NN: merge mslavesync branch (closes #2102 #2238 #2239 #2266 #1958 #2097 #2221 #2160 #1828 #1937 #1940 #2021 #2038 #2042 #2058 #2069 #2070 #2074 #2085 #2103 #2138 #2145 #2220 #2106 #2130 #2176 #2661)

View ↑

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

Attachments ↑
 
Note: See TracTickets for help on using tickets.