Ticket #5015 (closed defect: worksforme)
master/slave: Failed to enable: FATAL: Couldn't connect to LDAP server: ldap://207.61.225.18
| Reported by: | dimasf@… | Owned by: | jamor@… |
|---|---|---|---|
| Milestone: | 2.2.X | Component: | users |
| Severity: | normal | Keywords: | |
| Cc: |
Description (last modified by jamor@…) (diff)
Setup a connection to master (Users and Groups) and when tying to enabled the module the error of "FATAL: Couldn't connect to LDAP server: ldap://207.61.225.18" appeared.
Note: The slave and master are able to communicate with ping. hey can ping each other with no problem.
Error
Failed to enable: FATAL: Couldn't connect to LDAP server: ldap://207.61.225.18
Trace
Failed to enable: FATAL: Couldn't connect to LDAP server: ldap://207.61.225.18 at /usr/share/perl5/EBox/CGI/ServiceModule/ConfigureModuleController.pm line 74
EBox::CGI::ServiceModule::ConfigureModuleController::_process('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0x24...') called at /usr/share/perl5/EBox/CGI/Base.pm line 275
EBox::CGI::Base::run('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0x24...') called at /usr/share/perl5/EBox/CGI/Run.pm line 129
EBox::CGI::Run::run('EBox::CGI::Run', 'ServiceModule/ConfigureModuleController', 'EBox') called at /usr/share/zentyal/cgi/ebox.cgi line 34
ModPerl::ROOT::ModPerl::Registry::usr_share_zentyal_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0x24893ed8)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x24893be8)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x24893be8)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x24893ed8)') called at -e line 0
eval {...} called at -e line 0
Attachments
Change History
Changed 9 months ago by anonymous
-
attachment
zentyal.log
added
comment:1 follow-up: ↓ 2 Changed 9 months ago by jamor@…
- Status changed from new to closed
- Resolution set to worksforme
- Component changed from base to users
- Description modified (diff)
- Summary changed from Bug report from Zentyal Server to master/slave: Failed to enable: FATAL: Couldn't connect to LDAP server: ldap://207.61.225.18
Hello Dimasf,
this is surely a configuration error. Since we have a connection error message and you say they can ping each other, I would check your firewall first.
Regards,
Javier
comment:2 in reply to: ↑ 1 Changed 9 months ago by dimasf@…
Thank you Javier. I haven't indeed done anything with the master's firewall. I assume the firewall is set to Zentyal default. Any suggestion on which port/protocol I need to setup on the master's?
Thanks,
Dimas Replying to jamor@…:
Hello Dimasf,
this is surely a configuration error. Since we have a connection error message and you say they can ping each other, I would check your firewall first.
Regards,
Javier
comment:3 Changed 9 months ago by dimasf@…
Hi Javier,
I set the master's firewall so that it allows an ldap connection from slave. By doing that, I was able to enable the Users & Groups module. Another problem then occured when I tried to save the changes.
I attached a new log for diagnosis purposes.
Thanks,
Dimas
zentyal.log