[SOLVED] Upgrade from eBox 1.4.x to 1.5.x

[Svein Wisnaes]

I have been working on upgrading my home server from 1.4.x to 1.5.x and although it has been more or less as expected with a few hiccups here and there, I still have some things left to fix. And as there will be more and more people doing this, I think it is a good thing to gather all experiences regarding this in one thread.

Has anyone worked out a good procedure for the upgrade? This is how I started:

https://help.ubuntu.com/community/LucidUpgrades

There is a section about "Network Upgrade for Ubuntu Servers (Recommended)" there.

I added the eBox 1.5 ppa first as described here:

http://trac.ebox-platform.com/wiki/Document/Documentation/InstallationGuide#eBoxPlatform1.5packages

It would have been nice to be able to "deactivate" the whole eBox part, do the upgrade and then re-activate it again to avoid errors etc.

The eBox ppa got disabled during the 8.04 to 10.04 (Hardy to Lucid) upgrade, but that was expected. All 3rd party repositories get disabled now.

I still need to get ldap fixed so I can start using samba and other things that depend on it...

But the first thing I need to fix is a message I get when I do a console login. After giving username and password, I am told (after a looooooong wait) "Failed to add entry for user xxxxxxxxxx.
"

Does anyone know what this might be?

BTW - a REALLY nice feature would be an export service where you could export a complete setup for eBox to a pendrive and then just do a complete wipe and install. This would save a lot of frustration. Using a CD for the install together with the pendrive could then totally automate the setup.

[christian]

So far, I've no magic answer for you but can share what I experienced 

1 - Pay attention to your mailboxes while performing any changes: reinstalling mail will destroy all messages if it has to recreate virtual domain.
2 - This also apply if you have to reinstall (from scratch) LDAP because of mail depending on LDAP, you're back to above point.
3 - It looks like (but I did not succeed with accurate conclusion while investigating) that migration from 8.04 to 10.04 results in new Postgres (from 8.3 to 8.4) that might impact some services (e.g. webmail tries to access default Postgres port 5432, while mine was 5433 but not reflected in roundcube conf)
4 - I never succeedded to reuse existing accounts (and whatever related to LDAP) after the upgrade and decided to use the "reconfiguration" script, with the side effect (if I can say so) described above 
5 - after complete LDAP reconfiguration and mail services installation, it works except for webmail (under investigation)
6 - I've not been able to reconfigure Mailman properly without preventing postfix to work. I'm investigating this too.

As a matter of conclusion (I know it doesn't really help), migration is not something I would advise. On the other hand, it's 1.5, not 1.6 or even 2.0

[jsalamero]

christian, your mailboxes probably are in /var/vmail/domain/mailbox.bak.

keep in mind that 1.5.x are beta releases intended for testing the upcoming release and migration, should not be used on production and only used if you really know what are you doing and on a testbed machine.

[Svein Wisnaes]

keep in mind that 1.5.x are beta releases intended for testing the upcoming release and migration, should not be used on production and only used if you really know what are you doing and on a testbed machine.

Of course :-) I think this has repeated enough now that everyone should know it. But unless someone actually do stuff like we have done now, nobody will know where there might be problems.

For me, right now, LDAP is a problem. So I need to get that up and running again. Also, I can log in through the web interface, and a lot of things works the way it should.

I noticed one thing that was a big (and positive) difference from 1.4 to 1.5 - PhpMySql is working. Tried it on 1.4 and could never get it to work right.

So if anyone has any good tip on the LDAP part, please let me know. What could have happened here is a mix of settings during the upgrade, or that eBox tries to connect to an old version. Or that the setup of LDAP is not correct for eBox. How to fix?

[Svein Wisnaes]

jsalamero

How can I know if eBox is trying to connect to the wrong LDAP version?

[Svein Wisnaes]

This is what I get when trying to start the filesharing module:

A really nasty bug has occurred
Exception
Can't create ldapi connection
Trace
Can't create ldapi connection at /usr/share/perl5/EBox/Ldap.pm line 175
EBox::Ldap::anonymousLdapCon('EBox::Ldap=HASH(0x230f3d20)') called at /usr/share/perl5/EBox/Ldap.pm line 243
EBox::Ldap::dn('EBox::Ldap=HASH(0x230f3d20)') called at /usr/share/perl5/EBox/SambaLdapUser.pm line 966
EBox::SambaLdapUser::_fetchDomainAttrs('EBox::SambaLdapUser=HASH(0x2470a1d0)', 'AVIDSCHOOL') called at /usr/share/perl5/EBox/SambaLdapUser.pm line 937
EBox::SambaLdapUser::setSambaDomainName('EBox::SambaLdapUser=HASH(0x2470a1d0)', 'AVIDSCHOOL') called at /usr/share/perl5/EBox/Samba.pm line 454
EBox::Samba::_setConf('EBox::Samba=HASH(0x2471b008)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Base.pm line 824
EBox::Module::Base::_regenConfig('EBox::Samba=HASH(0x2471b008)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 607
EBox::Module::Service::_regenConfig('EBox::Samba=HASH(0x2471b008)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 635
EBox::Module::Service::restartService('EBox::Samba=HASH(0x2471b008)') called at /usr/share/perl5/EBox/CGI/EBox/RestartService.pm line 51
EBox::CGI::EBox::RestartService::_process('EBox::CGI::EBox::RestartService=HASH(0x246bb750)') called at /usr/share/perl5/EBox/CGI/Base.pm line 262
EBox::CGI::Base::run('EBox::CGI::EBox::RestartService=HASH(0x246bb750)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'EBox/RestartService', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0x2471b1c8)') 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(0x2473f390)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x2473f390)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x2471b1c8)') called at -e line 0
eval {...} called at -e line 0

[Svein Wisnaes]

As I have a couple of extra system drives for this computer, I decided to use a different drive and install a fresh Ubuntu Server 10.04 plus the 1.5 packages. I will start a different thread about it.