Sunday, 4 March 2012

Install blueonyx in centos vps (openvz)

1. Install centos 5 or 6 in the vps.
2. Download tar file from http://devel.blueonyx.it/pub/BlueOnyx/TAR/
# mkdir /install
# cd /install

# wget http://devel.blueonyx.it/pub/BlueOnyx/TAR/BlueOnyx-5107R-SL6-CentOS6-RHEL6-i386-20110716.tar.gz
# tar -xzf BlueOnyx-5107R-SL6-CentOS6-RHEL6-i386-20110716.tar.gz




3. run install.sh and remove the folder after installing it.

# ./install.sh
 
The installation has finished!

Please point your browser to http://xxx.xxx.xxx.xxx/login and login with
username 'admin' and password 'blueonyx'

** Your root password is same as admin password.        **
** SSH root logins are disabled by default now!         **
** Use user 'admin' instead for SSH and 'su -' to root! **

# rm -rf /install


4. Load the url http://xxx.xxx.xxx.xxx/login and change the admin password other than blueonyx

6 comments:

  1. # ./install.sh says no such file or directory

    ReplyDelete
    Replies
    1. write cd BlueOnyx-5107R-SL6-CentOS6-RHEL6-i386-20110716

      Delete
  2. He doesn't work for me unfortunately !!

    My VPS with SSH (Putty) is unreachable, i tryed to change port (22 and 444), with new password admin and blueonyx, but it's the same !!

    My VPS and the IP of my VPS (SSH and WEB) is unreachable !!

    ReplyDelete
  3. BlueOnyx needs second level quota enabling on the VPS - add the following two lines to the VPS config file and then restart the VPS:

    QUOTATIME="0"
    DISK_QUOTA=yes

    ReplyDelete
  4. Try this instead: Pre-made official BlueOnyx OpenVZ OS templates. http://devel.blueonyx.it/openvz/

    ReplyDelete
  5. Attempting to install from TAR in CentOS results in /etc/hosts file getting mangled on each reboot.

    "hostname-f" will yield "localhost.localdomain" instead of the fully qualified domain name.

    After installing BlueOnyx using TAR, delete the /etc/hosts file and it will get re-created on next boot when it can be locked with "chattr +i /etc/hosts" setting it's immutable bit.

    If you want to use veth instead of venet in Proxmox OpenVZ then you will need to lock the /etc/sysconfig/network file as well besides creating the ifcfg-eth0 file manually as described in http://forum.proxmox.com/threads/1733-Physical-Host-with-2-NICs-Each-with-Different-Gateways?p=9287#post9287


    ReplyDelete