BlueOnyx, no longer works

ukhost4u · Oct 27, 2010

Hello.

I have following a guide at:

http://pve.proxmox.com/wiki/BlueOnyx

I have attempted to install BlueOnyx both via a Centos 5 setup and via the openvz template but both do not work.

It seems that for some reason it breaks the network adapter and I loose all network access. I logged into the system via vzctl enter and found that I no longer had a network adapter.

Has anyone else had this issue or is there a work around? I find it odd for Proxmox to have this on there wiki if it does not work.

Thanks,

Paul Hughes
Senior Manager
http://www.ukhost4u.com/

lp86 · Oct 27, 2010

This is a "known" issue I have had since upgrading to Proxmox 1.6. The problem appears to be with the scripts that manage the IP configuration.

My thread about the issue is here, http://forum.proxmox.com/threads/4919-Networking-Issue-with-CentOS-containers-in-1.6

One of my fixes for BlueOnyx was to enclose the gateway in quotes.

Open /etc/sysconfig/network with pico or another text editor, and enclose the 192.0.2.1 on the second line in quotes.
ex

GATEWAY="192.0.2.1"

save the file and restart the network

/sbin/service network restart

give that a try and see what happens.

If it does work, you will have to make the file immutable until this problem is fixed.

chattr +i /etc/sysconfig/network

note: you will be unable to change the host name unless you remove the immutable bit.

apmuthu · Dec 17, 2010

There is no file:
/etc/sysconfig/network
in CentOS / BlueOnyx

BlueOnyx OpenVZ Install just does not recognise any network in ProxMox 1.7

The Wiki states to put in "blueonyx" as the default password since there is no way to build a OpenVZ container in ProxMox without giving a password for the container. The default install for BlueOnyx needs no password at all! All passwords get set from the Web GUI.

apmuthu · Dec 17, 2010

Tried manually creating container with the BlueOnyx Template in vain - for both venet and bridged mode.

Using the OpenVZ.org precreated centos 5.0 standard template (CentOS 5.5) and keeping the root password as "blueonyx", I used the tar ball install and found the following error during the install:

Code:

  Installing     : setserial                                             54/137
  Installing     : cgiwrap                                               55/137
/bin/cp: cannot stat `/etc/proftpd.conf': No such file or directory
error: %pre(proftpd-1.3.3c-1BX1.i386) scriptlet failed, exit status 1
error:   install: %pre scriptlet failed (2), skipping proftpd-1.3.3c-1BX1
  Installing     : pine                                                  57/137
  Installing     : nss_ldap                                              58/137

Code:

  Installing     : nuonce-solarspeed-vbq-constructors                   332/389
error reading information on service kudzu: No such file or directory
  Installing     : base-apache-capstone                                 333/389

Code:

  Installing     : java-1.6.0-sun-fonts                                 365/389
opendir: No such file or directory
  Installing     : base-email-capstone                                  366/389

Code:

  Installing     : base-blueonyx-glue                                   368/389
Could not connect to /usr/sausalito/cced.socket: No such file or directory
Shutting down sm-client: [  OK  ]
Shutting down sendmail: [  OK  ]
Starting sendmail: [  OK  ]
Starting sm-client: [  OK  ]
Could not connect to /usr/sausalito/cced.socket: No such file or directory
error: %trigger(base-blueonyx-glue-5106R-2.20100301BQ99.centos5.noarch) scriptlet failed, exit status 2
  Installing     : xerces-j2                                            369/389
  Installing     : log4j                                                370/389

apmuthu · Dec 17, 2010

Using a precreated CentOS 5.5 template from OpenVZ, a container was created and the BlueOnyx TAR Ball install was initiated that errored with:

Code:

Bad id for repo: BlueOnyx Testing, byte =   8
Bad id for repo: Virtual 5106R, byte =   7

Recently, CentOS stopped supporting Repos with names having spaces in them and this caused the above errors.
The following are the affected RPMs:

Code:

blueonyx-yumconf-1.0.0-4.i386.rpm
solarspeed-blueonyx-repo-1.0.0-SOL2.i386.rpm
solarspeed-virtual-5106R-repo-1.0.1-SOL1.i386.rpm

The repo files were extracted and the spaces hyphenated and uploaded into the /etc/yum.repos.d folder and the rpms commented out in the install.sh file (in the TAR BAll installer file) which was then executed.

It still errors out, but now only at the end:

Code:

  Installing     : libXext                                              286/389
  Installing     : libXrender                                           287/389
/bin/cp: cannot stat `/etc/proftpd.conf': No such file or directory
error: %pre(proftpd-1.3.3c-1BX1.i386) scriptlet failed, exit status 1
error:   install: %pre scriptlet failed (2), skipping proftpd-1.3.3c-1BX1
  Installing     : unixODBC                                             289/389


  Installing     : nuonce-solarspeed-vbq-constructors                   332/389
error reading information on service kudzu: No such file or directory
  Installing     : base-apache-capstone                                 333/389

  Installing     : jakarta-commons-daemon                               364/389
  Installing     : java-1.6.0-sun-fonts                                 365/389
opendir: No such file or directory
  Installing     : base-email-capstone                                  366/389
  Installing     : base-user-capstone                                   367/389
  Installing     : base-blueonyx-glue                                   368/389
Could not connect to /usr/sausalito/cced.socket: No such file or directory
Shutting down sm-client: [  OK  ]
Shutting down sendmail: [  OK  ]
Starting sendmail: [  OK  ]
Starting sm-client: [  OK  ]
Could not connect to /usr/sausalito/cced.socket: No such file or directory
error: %trigger(base-blueonyx-glue-5106R-2.20100301BQ99.centos5.noarch) scriptlet failed, exit status 2
  Installing     : xerces-j2                                            369/389
  Installing     : log4j                                                370/389
  Installing     : xml-commons-resolver                                 371/389
  Installing     : saxon                                                372/389
  Installing     : base-ftp-capstone                                    373/389
  Installing     : base-vsite-capstone                                  374/389
  Installing     : xalan-j2 [###################################      ] 375/389

It then hangs there!

lp86 · Dec 18, 2010

I would recommend using the premade template versus the tarball installer, it has been optimized to run well on OpenVZ.

lp86 · Dec 18, 2010

apmuthu said:
There is no file:
/etc/sysconfig/network
in CentOS / BlueOnyx

BlueOnyx OpenVZ Install just does not recognise any network in ProxMox 1.7

The Wiki states to put in "blueonyx" as the default password since there is no way to build a OpenVZ container in ProxMox without giving a password for the container. The default install for BlueOnyx needs no password at all! All passwords get set from the Web GUI.

Yes there is, at least on a working system there is. It contains this:

FORWARD_IPV4=true
GATEWAY="192.0.2.1"
HOSTNAME="box.domain.tld"
NETWORKING="yes"

lp86 · Dec 18, 2010

I am working on a script that will correct the problems that cause the networking to stop functioning.

apmuthu · Dec 19, 2010

Even the pre-built template on the Wiki and the Aventurine rpm builds also do not work on ProxMox 1.7.

apmuthu · Dec 19, 2010

On a dedicated BlueOnyx built using the ISO, the file /etc/sysconfig/network contains:

Code:

FORWARD_IPV4=false
GATEWAY=192.168.10.1
HOSTNAME=localhost
NETWORKING=yes
NETWORKING_IPV6=no
NOZEROCONF=yes

apmuthu · Dec 19, 2010

View attachment BO-on-VZ-logs.zip attached to enable constructing / bug fixing the BlueOnyx install scripts.

lp86 · Dec 26, 2010

Try enclosing the GATEWAY=192.168.10.1 in quotes like this,
GATEWAY="192.168.10.1"

then do a "/sbin/service network restart"

apmuthu · Dec 27, 2010

Tried the quotes wrapping of the GW IP - still no reprieve.
It just does not have any proper networking - also the udev says it it too old.

lp86 · Dec 27, 2010

Here is the script, what I did was use the old 1.5 scripts and back ported them. I created a custom distribution script so the other centoses are not affected.

cd /tmp
wget http://www.ohiointernet.net/pub/sauce/sauceinstaller.sh
chmod +x /tmp/sauceinstaller.sh
/tmp/sauceinstaller.sh

Then you have to edit your /etc/vz/conf/xxx.conf (xxx=VMID)

edit the "OSTEMPLATE" line, and replace whatever OS was there (most likely centos) replace it with "sauce"

eg mine used to be "OSTEMPLATE="centos-5-blueonyx_5106R-5.4-BXSOL2-20100108_i386"
now it will be "OSTEMPLATE="sauce-5-blueonyx_5106R-5.4-BXSOL2-20100108_i386"

also rename your template in /var/lib/vz/template/cache/ from centos-xxxxxxxx to sauce-xxxxxxxxx

I have been using this now for about 3 weeks, many new containers have been created, even more rebooted with no problems.

Note:
Sauce was the code name of the backend management system, now its called Sausalito.

apmuthu · Dec 27, 2010

Thanks for the script. Will give it a go.

On 18th Dec, 2010, I found the following file (renamed to BlueOnyx Convention) at the site:
http://devel.blueonyx.it/openvz/
blueonyx-5106R-5.5-BXSOL4_20100923_i386.tar.gz

It is now missing.

The latest file there is:
http://devel.blueonyx.it/openvz/blueonyx-5106R-i386-5.5_BXSOL1_20100516.tar.gz

Must the Jan 2010 version be used with your scripts?

lp86 · Dec 27, 2010

It will work with any version, they are just updated versions of the same template.

There was a openvz update about when 1.6 came out that broke bluequartz and blueonyx, this will work with either of them.

Search

Search

BlueOnyx, no longer works

ukhost4u

Member

lp86

Renowned Member

apmuthu

Renowned Member

apmuthu

Renowned Member

apmuthu

Renowned Member

lp86

Renowned Member

lp86

Renowned Member

lp86

Renowned Member

apmuthu

Renowned Member

apmuthu

Renowned Member

apmuthu

Renowned Member

lp86

Renowned Member

apmuthu

Renowned Member

lp86

Renowned Member

apmuthu

Renowned Member

lp86

Renowned Member

We value your privacy