[SOLVED] Zentyal 2.3-1 trouble (File Server, Users and Groups)

[martinique]

Not yet knowing about the new release, I did an apt-get upgrade remotely, eagerly waiting for bugfixes to certain packages. I was surprised to see some Kerberos stuff being installed and configured, but entered some dummy data and proceeded, thinking I could easily change it afterwards. Zentyal got really broken, just as promised in the announcement.

I purged Zentyal packages and reinstalled. The setup got stuck at ("Current operation: Setting up zentyal-webserver (2.3.3) ..."), but that was solved with /etc/init.d/zentyal apache restart

User data remained in LDAP from the previous version, but now I can't delete users ("FATAL: Couldn't connect to synchronizer: /var/run/ldb") and trying to start the File Server module fails ("domain MYDOMAIN does not exist").

Here are the essential log bits for the above events:

2012/06/20 08:53:25 ERROR> LDB.pm:214 EBox::LDB::safeConnect - Couldn't connect to LDB server ldapi://%2fvar%2flib%2fsamba%2fprivate%2fldapi, retrying
2012/06/20 08:53:30 DEBUG> LDB.pm:218 EBox::LDB::safeConnect - FATAL: Couldn't connect to LDB server: ldapi://%2fvar%2flib%2fsamba%2fprivate%2fldapi
2012/06/20 08:53:30 ERROR> SambaLdapUser.pm:176 EBox::SambaLdapUser::__ANON__ - FATAL: Couldn't connect to LDB server: ldapi://%2fvar%2flib%2fsamba%2fprivate%2fldapi
2012/06/20 08:53:30 DEBUG> LDB.pm:472 EBox::LDB::enableZentyalModule - Enabling Zentyal LDB module
...
2012/06/20 08:53:45 DEBUG> Sudo.pm:164 EBox::Sudo::_root - sudo commands: status 'zentyal.s4sync'
2012/06/20 08:53:45 ERROR> LDB.pm:183 EBox::LDB::safeConnectSync - Couldn't connect to synchronizer /var/run/ldb, retrying
2012/06/20 08:53:50 DEBUG> LDB.pm:187 EBox::LDB::safeConnectSync - FATAL: Couldn't connect to synchronizer: /var/run/ldb

2012/06/20 08:47:04 DEBUG> Samba.pm:522 EBox::Samba::__ANON__ - domain MYDOMAIN does not exist.
2012/06/20 08:47:04 DEBUG> DomainTable.pm:640 EBox::DNS::Model::DomainTable::_getDomainRow - domain MYDOMAIN does not exist.

Any idea what might have gone wrong?

[jsalamero]

Upgrades between development versions are not supported, and may break, as does the latest packages, some configuration performed when the module is enabled is missing and we have changed some things on the configuration backend too. Purge and reinstall

[kernevil]

Hi,

the synchronizer daemon does not start because samba probably is not correctly provisioned. You can try to purge the module with the following commands:

Code: [Select]

/usr/share/zentyal/unconfigure-module samba
/usr/share/zentyal/purge-module samba

and re-enable the module.

[martinique]

Thanks, kernevil! That worked perfectly to fix the user removal problem.

The File Server problem still remains, although it now logs slightly different errors:

2012/06/21 14:42:54 DEBUG> Samba.pm:522 EBox::Samba::__ANON__ - domain MYDOMAIN does not exist.
2012/06/21 14:42:54 DEBUG> DomainTable.pm:640 EBox::DNS::Model::DomainTable::_getDomainRow - domain MYDOMAIN does not exist.
2012/06/21 14:42:54 DEBUG> Samba.pm:522 EBox::Samba::__ANON__ - domain MYDOMAIN does not exist.
2012/06/21 14:42:54 DEBUG> DNS.pm:277 EBox::DNS::getHostnames - domain MYDOMAIN does not exist.
2012/06/21 14:42:54 ERROR> Samba.pm:304 EBox::Samba::__ANON__ - domain MYDOMAIN does not exist.
2012/06/21 14:42:54 DEBUG> Sudo.pm:82 EBox::Sudo::command - command: rm -f /var/lib/zentyal/conf/configured/samba
2012/06/21 14:42:54 DEBUG> ConfigureModuleController.pm:68 EBox::CGI::ServiceModule::ConfigureModuleController::__ANON__ - Failed to enable: domain MYDOMAIN does not exist.

Any further ideas?

[martinique]

After tinkering with both related and seemingly unrelated settings, File Server finally started, but now it spewed errors about missing sAMAccountName.

2012/07/03 13:56:40 DEBUG> LDB.pm:570 EBox::LDB::getSidById - sAMAccountName mygroup does not exist.

Deleting groups and creating new ones didn't help, so I assumed that the pre-2.3-1 Zentyal version, from which my LDAP data originated, had something missing from the LDAP schema. I ran /usr/share/zentyal-users/reinstall. Unfortunately the script failed to reinstall slapd; Looked a lot like this bug (invoke-rc.d: initscript slapd, action "start" failed).

I'm not quite sure what exactly fixed it, but my last reinstall attempt using aptitude instead of apt-get succeeded.

As both services seem to be working now, I'm marking this as solved.

Edit: The reinstall script failed again. Manually purging and reinstalling slapd along with associated Zentyal modules seems to fix it.