Author Topic: HTTP module cannot start  (Read 2963 times)

kleung0405

  • Zen Apprentice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
HTTP module cannot start
« on: July 28, 2014, 02:11:08 am »
After upgrading to 3.5, HTTP module cannot start.  If I look at the zentyal.log file, the following error messages appear:

ERROR> LDAP.pm:136 EBox::Module::LDAP::_connectToSchemaMaster - Error binding to schama master LDAP: An error occurred in C<Net::LDAP>
2014/07/28 08:02:34 ERROR> Service.pm:1001 EBox::Module::Service::restartService - Error restarting service: Error binding to schama master LDAP: An error occurred in C<Net::LDAP>
2014/07/28 08:02:34 ERROR> Service.pm:1003 EBox::Module::Service::restartService - Error binding to schama master LDAP: An error occurred in C<Net::LDAP>
2014/07/28 08:02:34 ERROR> RestartService.pm:61 EBox::SysInfo::CGI::RestartService::_process - Restart of HTTP Proxy from dashboard failed: Error binding to schama master LDAP: An error occurred in C<Net::LDAP>

Does anyone has any idea what the problem is?  Thanks.

mtrogg

  • Zen Apprentice
  • *
  • Posts: 12
  • Karma: +4/-0
    • View Profile
Re: HTTP module cannot start
« Reply #1 on: July 28, 2014, 04:51:13 pm »
I didn't roll out that upgrade (yet) but having a swift look at your message I think it might be that ubuntu distribution upgrade not in effect yet (no reboot, running on old core with new scripts?).

Again, never upgraded to different ubuntu server through zentyal dash yet, so I don't know whether It propagates or enforces reboot, in my update processes I always seperately had to reboot (running 3.4.8 now, zentyal for past three months or so).

If you didn't reboot after upgrade, try it manually via dash > system > reboot-halt or via ssh, that might solve your problem!

[edit]It literally means C library NET::LDAP (so the error is connected to your LDAP application) suffers errors while handling calls to it, probably version/compatibility issue, specially since after upgrading. try the reboot. hard C libraries are used p.e. with non statically compiled binaries. statically compiled means that binary includes these libraries in itself instead of relying on the OS for providing them functions.
« Last Edit: July 28, 2014, 04:55:45 pm by mtrogg »