Zentyal Forum, Linux Small Business Server
News and Announcements => News and Announcements => Topic started by: javi on February 16, 2010, 09:45:09 am
-
Hi guys,
We are starting the development of our transition branch from Ubuntu Hardy to the next LTS release Ubuntu Lucid. We are glad to announce that we already have a few packages to test.
Please, follow this link for further information:
http://trac.ebox-platform.com/wiki/Document/Announcement/1.5
-
Do you suspect that upgrading from Jaunty then Karmic to get to Lucid will break Ebox since there are no Karmic packages? Is the only reliable upgrade path going to be from Hardy to Lucid?
-
If somebody has time, I would also like to see an answer to this question. I'm looking to install E-Box right now, and the kernel in Hardy is a limitation for the features (wireless) that I want to provide. If Hardy-->Lucid will be an easy upgrade, then I'll install now; else, I'll wait until e-box on Lucid is complete. Thanks!
-
Hardy->Lucid should work. I talked to a guy putting many Drapper machines to Hardy back during that switch, and he said it all worked great. The direct upgrade path should work great unless the Ubuntu devs want to completely lose the credibility of their server and LTS distros.
-
ebox-samba seems to be broken (at least in Lucid Alpha 3). It tries to use /etc/init.d/samba which does not exist anymore. Instead, it should use /etc/init.d/smbd and /etc/init.d/nmbd which are soft links to upstart (I guess).
I would be happy if you fixed that ;)
-
It worked when we uploaded the packages. If that's happening that means the ubuntu guys have uploaded a new samba package.
-
I'll try to fix it during today.
-
Fixed it.
I've uploaded ebox-samba 1.5.1 to our repo. And also I've filed a bug with a patch and asked sponsorship to upload the fix to the ubuntu repo.
-
Cool!
I'll install 2 Virtual Machines and give it a test ;)
-
So the 1.5 people are are only Lucid testers right?
-
Does anyone have any idea +- when the rest of the packages will get posted out to the 1.5 repos? I'd like to give it more of a test but there is not enough there to give it a shot yet.
Arch
-
As soon as possible, but there is no date set.
-
Would it happen to be out by now or can we be sure that by April 29th, things will rev up for 1.5?
-
Yes, after the official launch of 10.04 we will be more focused in 1.5.
-
How is the transition going to work? Is there documentation anywhere?
-
Note that 1.5 is unstable, I don't recommend any transition until 2.0 is out, if by transition you mean upgrading an existing system.
-
I mean in general. Moving from 1.4 to 1.5 for testing purposes or 1.4 to 2.0. How will the OS upgrade work in w/ the eBox upgrade? What should I do to sources.list since I customized it?
-
I am running the latest stable on my home server right now, but would not mind going to 1.5 as this will allow me to run apt-cacher NG on the server (this SHOULD be a module in eBox! It is one of the most useful tools when you have more than one PC in your network running Linux!) among other things.
What is the best way of upgrading to 1.5 and make sure no settings etc. are lost?
-
What is the best way of upgrading to 1.5 and make sure no settings etc. are lost?
As 1.5 is not a stable version, there is no way to assure that everything will be fine after the upgrade...
-
Hi!
I'm new to ebox (and right now I have to find out how to help you) and therefore I'm probably wrong here.
I wanted to test the new 1.5 release - installed ubuntu lucid 64bit server and added the repository - then i installed all things related to ebox (to be sure that nothig is left out).
Theres not Problem enabling the Network in the Modules Status - but whenever I'd like to enable "Users and Groups" (and save the changes made) there is a big error:
A really nasty bug has occurred
Exception
Failed to enable: root command ldapadd -H 'ldapi://' -Y EXTERNAL -c -f /var/lib/ebox/tmp/slapd-master.ldif failed. Error output: SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 ldap_modify: Inappropriate matching (18) additional info: modify/add: olcTLSCACertificateFile: no equality matching rule ldap_modify: Type or value exists (20) additional info: modify/add: olcAccess: value #0 already exists ldap_add: Naming violation (64) ldap_add: Other (e.g., implementation specific) error (80) additional info: olcAttributeTypes: Duplicate attributeType: "0.9.2342.19200300.100.1.2" ldap_add: Other (e.g., implementation specific) error (80) additional info: olcAttributeTypes: Duplicate attributeType: "1.3.6.1.1.1.1.2" ldap_add: Other (e.g., implementation specific) error (80) additional info: olcAttributeTypes: Duplicate attributeType: "2.16.840.1.113730.3.1.1" ldap_modify: Type or value exists (20) additional info: modify/add: olcAccess: value #0 already exists Command output: modifying entry "cn=config" modifying entry "olcDatabase={-1}frontend,cn=config" adding new entry "cn=module{0},cn=config" adding new entry "cn=cosine,cn=schema,cn=config" adding new entry "cn=nis,cn=schema,cn=config" adding new entry "cn=inetorgperson,cn=schema,cn=config" adding new entry "olcDatabase={1}hdb,cn=config" adding new entry "olcOverlay=syncprov,olcDatabase={1}hdb,cn=config" modifying entry "olcDatabase={0}config,cn=config" . Exit value: 20
Trace
Failed to enable: root command ldapadd -H 'ldapi://' -Y EXTERNAL -c -f /var/lib/ebox/tmp/slapd-master.ldif failed.
Error output: SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
ldap_modify: Inappropriate matching (18)
additional info: modify/add: olcTLSCACertificateFile: no equality matching rule
ldap_modify: Type or value exists (20)
additional info: modify/add: olcAccess: value #0 already exists
ldap_add: Naming violation (64)
ldap_add: Other (e.g., implementation specific) error (80)
additional info: olcAttributeTypes: Duplicate attributeType: "0.9.2342.19200300.100.1.2"
ldap_add: Other (e.g., implementation specific) error (80)
additional info: olcAttributeTypes: Duplicate attributeType: "1.3.6.1.1.1.1.2"
ldap_add: Other (e.g., implementation specific) error (80)
additional info: olcAttributeTypes: Duplicate attributeType: "2.16.840.1.113730.3.1.1"
ldap_modify: Type or value exists (20)
additional info: modify/add: olcAccess: value #0 already exists
Command output: modifying entry "cn=config"
modifying entry "olcDatabase={-1}frontend,cn=config"
adding new entry "cn=module{0},cn=config"
adding new entry "cn=cosine,cn=schema,cn=config"
adding new entry "cn=nis,cn=schema,cn=config"
adding new entry "cn=inetorgperson,cn=schema,cn=config"
adding new entry "olcDatabase={1}hdb,cn=config"
adding new entry "olcOverlay=syncprov,olcDatabase={1}hdb,cn=config"
modifying entry "olcDatabase={0}config,cn=config"
.
Exit value: 20 at /usr/share/perl5/EBox/CGI/ServiceModule/ConfigureModuleController.pm line 74
EBox::CGI::ServiceModule::ConfigureModuleController::_process('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0xbc...') called at /usr/share/perl5/EBox/CGI/Base.pm line 262
EBox::CGI::Base::run('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0xbc...') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'ServiceModule/ConfigureModuleController', '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(0xbc046cb0)') 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(0xbc050690)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xbc050690)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xbc046cb0)') called at -e line 0
eval {...} called at -e line 0
please point me to the correct page where to post this "bug?" and help you best in testing 1.5.
Probably I am doing something wrong but it's a standard installation of ubuntu with nothing special.. and only added the ebox repositorys from launchpad and installed ebox ..
So what to do next?
regards
macho
-
Out of all the other threads in the forums, I'd say you picked the best one.
-
The nasty bug is fixed: http://trac.ebox-platform.com/changeset/17358
I will upload new 1.5 packages asap.
-
A new ebox-usersandgroups 1.5.1 package has already been published.
Remember that you can upgrade with:
apt-get update
apt-get install ebox-usersandgroups
-
So, I'll ask again - what is the best way of upgrading an existing system to 1.5?
In the spirit of helping with bug hunting etc. I would like to upgrade my running home-server to 1.5. And I am sure there are more people out there that would like to do it.
I have searched here and on Google without finding any description on how to upgrade.
-
I was wondering about that too. I'm on 1.4 and know you need an OS and application upgrade to 1.5 (or 2.0) so I wanted to know the exact steps to do this especially if eBox is acting as the router for your networking.