您所在的组无权查看该日志

OpenVZ Web Panel InstallationTable of contents:IntroductionInstallation of development versionRequirementsManual installation the buildInstallation from Git repositoryUninstallation1. IntroductionMost preferable way to install the panel is to use automatic installer.wget -O - https://raw.githubusercontent.com/sibprogrammer/owp/master/installer/ai.sh | shInstructions below should be used only if you can not use automatic installer due to some reason.2. Installation of development versionTo be able to test the newest features you can install latest development version.This build is not suitable for production and should be used only for testing purposes.wget -O - https://raw.githubusercontent.com/sibprogrammer/owp/master/installer/ai.sh | \ sh -s DOWNLOAD_URL=http://owp.softunity.com.ru/download/ovz-web-panel-latest.tgz3. RequirementsThe following software is required to be installed on server with panel:Ruby 1.8.7+ (1.9 is not supported)RubyGemsRuby SQLite3 supportThe following softwa...

OpenVZ VPS Creation Error – The ploop image can not be used on ext3 or ext4 When i create a VPS, i got error[root@server70 ~]# vzctl create 102 --ostemplate ubuntu-14.04-x86_64 Creating image: /vz/private/102.tmp/root.hdd/root.hdd size=2306867K Creating delta /vz/private/102.tmp/root.hdd/root.hdd bs=2048 size=4614144 sectors v2 Storing /vz/private/102.tmp/root.hdd/DiskDescriptor.xml Error in check_mount_restrictions (ploop.c:1536): The ploop image can not be used on ext3 or ext4 file system without extents Failed to create image: Error in check_mount_restrictions (ploop.c:1536): The ploop image can not be used on ext3 or ext4 file system without extents [21] Destroying container private area: /vz/private/102 Creation of container private area failed [root@server70 ~]# This is because OpenVZ recently started using ploop image for OpenVZ virtual machines. To fix this, edit /etc/vz/vz.confvi /etc/vz/vz.conf Find#VE_LAYOUT=ploop Replace WithVE_LAYOUT=simfs Now you will b...

Quick installationJump to: navigation,searchThis document briefly describes the steps needed to install OpenVZ on your RHEL 6 (CentOS 6, Scientific Linux 6) machine.For Debian based systems, please see Installation on Debian.A commercial version of OpenVZ is available, which simplifies installation with a single disk as well as supports networked installation using PXE boot. To learn more about Parallels Cloud Server and request a free trial, please see http://www.parallels.com/products/pcs/Contents1 Requirements1.1 /vz file system1.2 yum pre-setup2 Kernel installation3 System configuration3.1 sysctl3.2 SELinux4 Tools installation5 Reboot into OpenVZ6 Download OS templates7 Next steps Requirements This guide assumes you are running RHEL (CentOS, Scientific Linux) 6 on your system. Currently, this is a recommended platform to run OpenVZ on. /vz file system It is recommended to use a separate partition for containers (by default /vz) and format it to ext4. yum pre-setup Download open...

您所在的组无权查看该日志

Centos 6.5 _64安装OpenVZ 一 ，首先安装OpenVZ源 cd /etc/yum.repos.dwget http://download.openvz.org/openvz.repo 安装OpenVZ源证书 rpm --import http://download.openvz.org/RPM-GPG-Key-OpenVZ 查看源里面的设置，看下自己的版本，把enabled改为1，其余的改为0，不过这个一般是默认的，所以一般不需要修改，会自动检测到自己安装的是哪个版本，我这里用的是centos 6。 vi openvz.repo [openvz-kernel-rhel5] 设置为 (enabled=0)[openvz-kernel-rhel6] 设置为 (enabled=1) 二，安装OpenVZ yum search vzkernel                        可以列出可安装的内核列表yum -y install vzkernel                       32 位系统安装 yum -y install ovzkernel.x86_64      64 位系统安装本次测试的服务器是64位版本，所以使用下面命令安装。yum -y install ovzkernel....

sysctl -P 报错解决办法sysctl -P 报错解决办法问题症状修改 linux 内核文件 #vi /etc/sysctl.conf后执行sysctl  -P 报错error: "net.bridge.bridge-nf-call-ip6tables" is an unknown keyerror: "net.bridge.bridge-nf-call-iptables" is an unknown keyerror: "net.bridge.bridge-nf-call-arptables" is an unknown key 解决方法如下：modprobe bridgelsmod|grep bridge

RHEL6 虚拟机克隆网络问题解决方法   环境：Virtualbox+RHEL 6 x64用VirtualBox的vboxmanager克隆的虚拟机，操作系统RHEL6，启动后发现网卡不能用了。重启网络服务，报以下错误:Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization.   [FAILED]在RHEL5里也发生类似事情，因为复制虚拟机MAC会重新生成，但是操作系统的MAC却写在ifcfg-ethx里，造成了不一致，所以不能启动网络接口，在RHEL5里可以使用kudzu或者注释网卡配置文件的MAC字段来解决这个问题。但是在RHEL6里，kudzu已经被hal服务取代了。虽然lspci能够正常认到网卡，但是却无法使用/etc/init.d/network restart来启动服务。尝试注释ifcfg-eth0的MAC字段，还是报错。查看了下udev的规则，发现了问题的所在。[root@Oracle ~]# cat /etc/udev/rules.d/70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules# program, run by the persistent-net-generator.rules rules file.## ...

DRBD+Heartbeat+NFS试验手册本实验部署DRBD + HEARDBEAT + NFS 环境，建立一个高可用(HA)的文件服务器集群。在方案中，通过DRBD保证了服务器数据的完整性和一致性。DRBD类似于一个网络RAID-1功能。当你将数据写入本地文件系统时，数据还将会被发送到网络中另一台主机上，以相同的形式记录在一个另文件系统中。主节点与备节点的数据可以保证实时相互同步。当本地主服务器出现故障时，备份服务器上还会保留有一份相同的数据，可以继续使用。在高可用(HA)中使用DRBD功能，可以代替使用一个共享盘阵。因为数据同时存在于本地主服务器和备份服务器上。切换时，远程主机只要使用它上面的那份备份数据，就可以继续提供主服务器上相同的服务，并且client用户对主服务器的故障无感知。 二、实验环境 虚拟机操作系统：Centos 5.5 64bit A: master    计算机名：server1     IP地址：192.168.20.101 B: slave      计算机名：server2     IP地址：192.168.20.102 虚拟IP ： 192.168.20.188 两台服务器将/...

drbd+heartbeat+nfs  测试实验 实验验结构：  Drbd 就是将不同服务器上的不同的分区组合成 /dev/drbd0 这样的块设备，数据实际分布式存储在不同的服务器的存储上，服务器之间通过ip通讯，实际上简单的实现了网络raid的功能，这样，如果损失了单台的服务器也对于数据没有任何损害。Heartbeat 主要是实现Ha的功能，在单点失败的情况下，将资源切换到备用的服务器上。Drbd的conf----------------------------------------------------------------------      global { usage-count yes; }      common { syncer { rate 100M; } }            //同步速率      resource r0 {           protocol C;           net {                cram-hmac-alg sha1;                shared-secret "FooFunFactory&qu...