Modify

Ticket #4337 (closed defect: wontfix)

Opened 13 months ago

Last modified 12 months ago

Cannot enable Users and Groups module after upgrade from 2.0 to 2.2

Reported by: jon.papageorgiou@… Owned by: jamor@…
Milestone: 2.2.X Component: base
Severity: normal Keywords: upgrade from 2.0 to 2.2 module failure Users and Groups
Cc:

Description

I downloaded the migration utility and ran it as specified. During the script the old ebox components were uninstalled and then when the script attempted to install the new components, it could not connect to the repositories. After playing with ifconfig and getting no luck, I rebooted and the computer connected correctly. I reran the script, but after it finished there were no zentyal components installed. I then proceeded to install zentyal-office since I am primarily concerned with file shares. After the installation, none of the previous configurations were present. I attempted to reconfigure, but found the module was not enabled. When I attempted to enable it, the Module Status Configuration page presented an error referencing the following file /var/log/zentyal/zentyal.log. The pertinent information is below:

Command output: . 
Exit value: 1
2012/05/12 18:25:41 ERROR> GlobalImpl.pm:612 EBox::GlobalImpl::__ANON__ - Failed to save changes in module users: root command start 'ebox.slapd' failed. 
Error output: start: Job is already running: ebox.slapd

Command output: . 
Exit value: 1
2012/05/12 18:25:41 ERROR> GlobalImpl.pm:664 EBox::GlobalImpl::saveAllModules - The following modules failed while saving their changes, their state is unknown: users 
2012/05/12 18:25:57 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/05/12 18:25:58 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/05/12 18:25:59 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/05/12 18:26:00 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/05/12 18:26:01 ERROR> Ldap.pm:1107 EBox::Ldap::safeConnect - FATAL: Couldn't connect to LDAP server: ldapi://%2fvar%2frun%2fslapd%2fldapi
2012/05/12 18:26:35 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/05/12 18:26:36 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/05/12 18:26:38 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/05/12 18:26:39 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/05/12 18:26:40 ERROR> Ldap.pm:1107 EBox::Ldap::safeConnect - FATAL: Couldn't connect to LDAP server: ldapi://%2fvar%2frun%2fslapd%2fldapi

So then if I then attempt to enable the File Sharing module, I receive the following:

Trace

    Failed to enable: FATAL: Couldn't connect to LDAP server: ldapi://%2fvar%2frun%2fslapd%2fldapi at /usr/share/perl5/EBox/CGI/ServiceModule/ConfigureModuleController.pm line 74
    EBox::CGI::ServiceModule::ConfigureModuleController::_process('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0x7f...') called at /usr/share/perl5/EBox/CGI/Base.pm line 275
    EBox::CGI::Base::run('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0x7f...') 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(0x7fa71f11ad20)') 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(0x7fa71f1857b8)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
    ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x7fa71f1857b8)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
    ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x7fa71f11ad20)') called at -e line 0
    eval {...} called at -e line 0


Please let me know what steps I need to take to remedy this problem.

Attachments

Change History

comment:1 Changed 12 months ago by jamor@…

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

Hello Jon Papageorgiou,

as you are telling, something incorrect happened on your upgrade process, so now the only thing we can do it is to try to fix the system.

I will try the following:

  • reinstall users and group with "sudo /usr/share/zentyal-users/reinstall"
  • setup again users
  • try to restore the backup from 2.0

The last step could be more problematic and maybe you need to fix by hand your ldif files if it fails. A

Anyway since this a error seems to be caused by the connection on your server, and not a bug of either zentyal or the upgrade-tool it falls outside the scope of the bug fixing. If you need more support please request it in the forum.

Regards,

Javier

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.

 
Note: See TracTickets for help on using tickets.