[BlueOnyx:16562] Re: BlueOnyx 5106R under Centos 5 (latest) on Qube3 - problems

[Michael Stauber]

Hi Andy,

Welcome to BlueOnyx. And no, there are no stupid questions, just stupid
answers. I'll handle those. ;-)

> I'm wanting to evaluate BlueOnyx, and my desired target is a Qube 3
> running Centos 5.11, using the recipe provided by David Thacker;
> http://www.thackernet.com/RaQtoBX/RAQ34_to_BlueOnyx.html, which worked 
> perfectly. The kernel is 2.6.16, from Davids site.

Yeah, that's kinda where the problem starts. I can understand the desire
to run it on the Qube3 hardware. And yes, it's possible (via some work
arounds) to shoe-horn BlueOnyx 5106R onto original Cobalt hardware. But
it's far from being ideal.

BlueOnyx 5106R is the oldest BlueOnyx version and gets the short stick
from us as far as maintenance and fixes goes. It'll get EOL'ed when
CentOS5 stops providing updates. Which will be in a couple of years.

With 5106R you get an old OS that's two versions behind (EL5 instead of
EL7) and it'll run a non-stock kernel which you cannot upgrade when
security holes require it. And you'll be missing out on the shiny new
GUI that we provided BlueOnyx with for the current 5207R and 5208R models.

Lastly, the installation method Tarball-Installer isn't ideal. The best
way is a CD install, which you obviously can't do. The second best
method is an OS template, but that requires OpenVZ, which isn't possible
for you either. That leaves the Tarball-Installer. And I think the
published version that is so far behind that it no longer really works
with any degree of reliability.

> Dovecot SSL-params

Oh yeah. I've seen that one, too. You can open a second terminal and can
kill off the related process to let the install finish. That will throw
a warning, but it's better than to have to sit to wait this one out. It
doesn't hurt to kill it off. Dovecot will work anyway.

> Following that, I saw a number of warnings similar to, and including:
> 
>     No package base-apache-locale-en available

Yeah, that's due to the age of the Tarball-Installer. Please do this and
it should solve the issues:

yum update blueonyx-yumconf

That will install the latest version of the BlueOnyx YUM config files.
If it bitches about "unfinished transactions" or won't let you run it,
try ...

yum update blueonyx-yumconf --skip-broken

... instead.

Once the new "blueonyx-yumconf" is installed (or if it says that you
already have the latest one) do this:

yum clean all

That will clean up the downloaded cache of the YUM repositories.

Then run this:

yum groupinstall blueonyx

That will verify your already downloaded BlueOnyx RPMs with the list of
RPMs that need to be installed in order to give you a fully working
BlueOnyx. It will download and install everything that you are missing.
For those RPMs that the Tarball-Installer already brought aboard you'll
see lines such as this:

Package XXXX already installed and latest version

That is fine and just indicates that there is nothing to do for that RPM
as it's already there and current.

But the important thing is that it'll fetch the bits and pieces that
you're missing at the moment. And I suspect quite a few are indeed
missing and/or outdated.

Once that's done and just for good measure also run this:

yum update

That will fetch any missing updates for both the OS and BlueOnyx. It
might not be necessary or might not find anything to update as you are
already fully current. But either way: It won't hurt to run it.

In any case: If you run into any issues or problems with this, let us
know and we'll take it from there.

-- 
With best regards

Michael Stauber