To enable Fuse to work inside a OpenVZ container it's very simple (although some people say it can't be done).
Remember that on your HN(HostNode) for OpenVZ, Fuse must be installed and the module must be loaded for this to work. In addition remember that you need the Fuse package installed inside the container of course.
vzctl set 2000 --devices c:10:229:rw --save
vzctl exec 2000 mknod /dev/fuse c 10 229
The part that most people forget when trying to enable Fuse on OpenVZ is that the container must be restarted, otherwise you'll get this message:
fuse: mount failed: No such device
Simply restart the OpenVZ container and then things will work:
vzctl restart 2000 or you can just manually reboot from within the container.
A VPS Server I had just wasn't working right, code that I migrated there just wasn't working. For example, it kept telling me the connection to the database was unsuccessful, halfway through iterating through results it already had.
Then I realized it wasn't my code. Ichecked my /proc/user_beancounters and found this:
cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
2000: kmemsize 2499074 3453079 268435456 268435456 2985
lockedpages 0 8 999999 999999 0
privvmpages 43361 87480 1024000 1024000 0
shmpages 671 1647 65536 65536 0
dummy 0 0 0 0 0
numproc 32 48 999999 999999 0
physpages 10119 24142 0 2147483647 0
vmguarpages 0 0 1024000 1024000 0
oomguarpages 10119 24142 6144 2147483647 0
numtcpsock 6 24 7999992 7999992 0
numflock 8 12 999999 999999 0
numpty 1 1 500000 500000 0
numsiginfo 0 6 999999 999999 0
tcpsndbuf 69316 380120 235713536 235713536 0
tcprcvbuf 98304 1527656 235713536 235713536 0
othersockbuf 8944 175584 235713536 235713536 0
dgramrcvbuf 0 8380 235713536 235713536 0
numothersock 12 32 7999992 7999992 0
dcachesize 220365 274667 2147483646 2147483646 0
numfile 1116 2025 23999976 23999976 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 5 5 128 128 0
Notice the "failcnt" for "kmemsize" is 2985. The value was too low, in this quote it had already been corrected and after that my PHP scripts were working fine.
When things don't make sense and aren't working properly, check your "beancounters" to make sure nothing is failing.
Also remember not to instantly blame your VPS Provider, lots of times people have these problems when running intensive scripts, applications, CPanel/Plesk and it's because your plan does not have enough RAMetc...
This should be something every admin/owner of a VPS checks routinely for inexplicable problems/timeouts with your applications in a VPS Server.
OpenVZ technology is the best for performance, but the settings must be just right to avoid problems, and you must make sure you have a plan that meets your needs. There's no such thing as swapping, if you exceed your limits, connections drop, application/database calls fail without explanation.
So just remember to pick a VPS/Virtual Private Server plan that meets you needs and monitor the beancounters for any signs of failures.
I didn't find any useful information that actually fixed this. My VPS was in the "Running State" and I could not stop or restart it. I kept getting "Container already locked" no matter what Idid (I tried all the suggestions in the Google results for this error).
Most of the suggestions were for Windows but I only use Linux. The other solutioins also said to restart the VZ service or even the entire hostnode and this was not acceptable to me so Iwanted to find a "clean fix".
I tried to "vzctl restart VEID" and "vzctl start VEID --force" and "vzctl stop VEID --fast" with no luck.
Here is how I fixed it:
Delete the /vz/lock/VEID.lck file (where VEID is the number of your VPS).
vzctl chkpnt VEID --kill
That's all there is to it, your VEID can now be restarted successfully.
top - 09:34:12 up 2 days, 20:57, 2 users, load average: 1.83, 1.99, 2.03
Tasks: 59 total, 2 running, 57 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.3%us, 0.0%sy, 0.0%ni, 0.0%id, 99.7%wa, 0.0%hi, 0.0%si, 0.0%st
That 99.7% wa is iowait, it means the server is waiting for a process to complete an IOoperation or in plain English, there is a delay in reading and/or writing data to the hard drive.
Here are some ways to get an idea of what is going on (in RPM based Distros this package is called "sysstat") and contains the very helpful binary called "iostat". There's another package I like called "dstat" that does a great job too.
Run iostat -d 5 (it refreshes the data every 5 seconds):
Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
sda1 2.07 5.27 28.66 1309570 7120384
sda2 0.00 0.03 0.04 7496 8832
Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
sda1 27.15 0.00 357.68 0 1792
sda2 0.00 0.00 0.00 0 0
What we're seeing is that the iowait must be caused primarily by blocks being written to /dev/sda1 which is mounted as / (my root filesystem). So now we know the main cause is by an application constantly writing to the root partition, but we still don't know what process is directly responsible for this.
If you have a newer kernel it's often possible to view processes by io usage, you can test for this by running: cat /proc/self/io
If the file is not found then you don't have io stats enabled in your kernel. Then you can check a suspected process by running cat /proc/13/io (replace the 13 with the PID you want to check).
read_bytes: 0
write_bytes: 0
cancelled_write_bytes: 0
Proxmox has made this free utility to backup running OpenVZ containers. It's a great program which is actually just a PERL script but gets the job done. This program is not 100% required because all it really does is cp -a from your container's path as far as I know but it is still good to have uniformity to how you backup your containers.
For RPM distros such as Centos/RHEL/Fedora etc.. download and install this:
wget http://www.proxmox.com/cms_proxmox/cms/upload/vzdump/vzdump-1.1-2.noarch.rpm; rpm -ivh vzdump-1.1-2.noarch.rpm
For Debian based distros like Ubuntu etc.. download and install this:
wget http://www.proxmox.com/cms_proxmox/cms/upload/vzdump/vzdump_1.1-2_all.deb; dpkg -i vzdump_1.1-2_all.deb
vzdump options
vzdump --help
Unknown option: help
usage: /usr/sbin/vzdump OPTIONS [--all | VPSID]
--exclude VPSID exclude VPSID (assumes --all)
--exclude-path REGEX exclude certain files/directories
--stdexcludes exclude temorary files and logs
--compress compress dump file (gzip)
--dumpdir DIR store resulting files in DIR
--tmpdir DIR store temporary files in DIR
--mailto EMAIL send notification mail to EMAIL.
--quiet be quiet.
--stop stop/start VPS if running
--suspend suspend/resume VPS when running
--snapshot use LVM snapshot when running
--size MB LVM snapshot size
--node CID only run on pve cluster node CID
--lockwait MINUTES maximal time to wait for the global lock
--stopwait MINUTES maximal time to wait until a VM is stopped
--bwlimit KBPS limit I/O bandwidth; KBytes per second
--restore FILENAME restore FILENAME
Real Life Usage To Dump/Backup an OpenVZ Container
*note that since I chose --compress (why not compress right?) that the file will actually be:
vzdump-5000.tgz
vzdump --compress 5000
INFO: Starting new backup job - vzdump --compress 5000
INFO: Starting Backup of VM 2000 (openvz)
INFO: status = CTID 5000 exist mounted running
WARN: online backup without stop/suspend/snapshot
WARN: this can lead to inconsistent data
INFO: creating archive '/vz/dump/vzdump-5000.dat' (/vz/private/5000)
To Restore The OpenVZ Backup
vzrestore /vz/dump/vzdump-5000.tgz 5000
*note that if you specify something different eg. 10000 as the VPSID it will restore to that container.
Ihave no idea how to get the loopback device working in OpenVZ, but what's more frustrating is that I purchased a CPanel license for my VPS and clearly it is not "VPS Optimized". Although everything does seem to work at this point despite that error.
The suggestions here: http://forum.openvz.org/index.php?t=msg&goto=1339 don't seem to work at all. This is an OpenVZ issue, but also a CPanel isue, why on earth would loopback support be expected in a VPS and why would CPanel need this?
It also makes me want to stick with Plesk exclusively, at least they have well designed and thought out Control Panel. I can't believe CPanel looks like it was designed by hackers from the 90's!
cat /proc/user_beancounters produces the following:
kmemsize 1861537 5139870 12752512 12752512 26965041
Notice the failcnt "26965041", that is for kmemsize and at first it confused me. The system had enough guaranteed and enough burst RAM available. kmemsize is a variable indepedent of that, but who cars about the explanation right, let's just make things work. I was installing CPanel and wondered why the install process was taking forever until I checked my beancounters:
The solution is to of course increase kmemsize, in many cases you'll want to double, triple or even quadruple it. Also note it's bad that my barrier and limits are the same, soI've arbitrarily changed the limit in the example below. I can't remember the consequences but I read certain processes will get killed if the server runs out of memory.
vzctl set vpsid --kmemsize $((1275251*4)):$((1875251*4)) --save
The above increased my kmemsize allowances by 4x and should keep everything good. In my opinion tihs is a silly feature and should be more tuned/controlled by the guaranteed memory allocation in OpenVZ.
This can be very annoying and CPanel doesn't seem to document it, or it's not found or made as obvious as it should be. It's always funny when I find it more difficult to work with a control panel than to do everytihng manually without CPanel or even Plesk.
So once again, the default serve path for contents is: /usr/local/apache/htdocs and this is especially applicable when accessing Apache by just an IP which is unbound to any domain at this point.
ping test.com
connect: No buffer space available
/var/log/messages
Oct 18 12:21:03 vps kernel: printk: 177 messages suppressed.
Oct 18 12:21:03 vps kernel: Neighbour table overflow.
Solution in /etc/sysctl.conf:
net.ipv4.neigh.default.gc_thresh1 = 4096
net.ipv4.neigh.default.gc_thresh2 = 8192
net.ipv4.neigh.default.gc_thresh3 = 8192
net.ipv4.neigh.default.base_reachable_time = 86400
net.ipv4.neigh.default.gc_stale_time = 86400
Edit the thresh1,2,3 to higher values if it keeps happening, usually heavy network traffic/torrents will cause this to happen.
Initializing quota ...
Error: Not enough parameters, diskinodes quota not set
vzctl set $veid --diskinodes 90000:91000 --save
New versions of OpenVZ seem to have some strange diskinodes parameter which is required.
This is an SFTP mount that does not work or prompt for password.
Error: DBus error org.freedesktop.DBus.Error.ServiceUnknown: The name :1.1127 was not provided by any .service files
Please select another viewer and try again.
It seems to me that the connection often times out after being opened and the application doesn't know how to handle the disconnection and doesn't realize it needs to kill the instance and restart the connection.
first container would not come up:
Starting CT 2333:
service vz stop
OpenVZ is locked [FAILED]
2010-11-29T23:26:23-0800 vzctl : CT 2333 : Starting container ...
2010-11-29T23:37:21-0800 vzctl : CT 2333 : vzquota on failed [1]
vzquota : (warning) Incorrect quota shutdown for id 2333, recalculating disk usage
vzquota : (error) quota check : lstat `sess_a5078fce5f569e453ab1fb39b0fc69f8': No such file or directory
vzquota on failed [1]
Trying to start it again worked after a long time. The other option is to disable quota, start it and then re-enable quota.
Santrex Review/Scam/Complaint
Santrex never provided any working server, I believe it was just a dummy management Solus server because the server said it was booted but never connected to the console. I complained to them and eventually the support admitted the server was not working and to wait for 24 hours. I waited for 4-days, after which they sent an e-mail saying my service was being disabled for SPAM ...(when SolusVM shows 0kb of traffic). They aren't fazed by threats since their reputation couldn't get any worse. They escalated the PayPal dispute after we provided our evidence and screenshots, along with proof that this case is not unique.
Santrex is widely known as not only a company that does not provide what the customer asks, but when they do provide something it is often out of spec or an extremely poor and unreliable service with fees being stolen due to phony TOS violations.
I thought I'd add it's ironic that they make up phony TOS SPAM notices to steal money and yet they are actually SPAMMERS themselves (if you use RBL's you'll probably find their e-mails blocked):
* 2.5 URIBL_SBL Contains an URL listed in the SBL blocklist
* [URIs: santrex.net]
Here are links to Santrex complaints/reviews/scams that tell a similar story about Santrex:
www.thedave.ca/geek/santrex-net-worst-hosting-company-on-the-planet/comment-page-1/#comment-2350
www.web-hosting-top.com/web-hosting/web-hosting-top.santrex.net/
www.blackhatworld.com/blackhat-seo/shit-list/246599-santrex-webhosting-epic-fail-avoid-all-costs.html
www.freeindex.co.uk/profile%28santrex-internet-services%29_77491.htm
forums.digitalpoint.com/showthread.php
Report Santrex to the local UK government by filling out this simple form (eventually they will be shut down if we all complain):
http://www.tradingstandards.gov.uk/towerhamlets/complain.htm
Santrex Scam Proof
It's weird because I have a nearly identical box and setup and I can update the ovzkernel-PAE* just fine but on this box it doesn't work.
I only get this error with the openvz.repo and not others such as Centos-Base.repo
With my other server it works normally:
================
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package ovzkernel-PAE.i686 0:2.6.18-238.12.1.el5.028stab091.1 set to be installed
---> Package ovzkernel-PAE-devel.i686 0:2.6.18-238.12.1.el5.028stab091.1 set to be installed
--> Finished Dependency Resolution
Dependencies Resolved
=============================================================================================================================================================
Package Arch Version Repository Size
=============================================================================================================================================================
Installing:
ovzkernel-PAE i686 2.6.18-238.12.1.el5.028stab091.1 openvz-kernel-rhel5 21 M
ovzkernel-PAE-devel i686 2.6.18-238.12.1.el5.028stab091.1 openvz-kernel-rhel5 5.4 M
Transaction Summary
=============================================================================================================================================================
Install 2 Package(s)
Upgrade 0 Package(s)
Total download size: 26 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): ovzkernel-PAE-devel-2.6.18-238.12.1.el5.028stab091.1.i686.rpm | 5.4 MB 00:00
(2/2): ovzkernel-PAE-2.6.18-238.12.1.el5.028stab091.1.i686.rpm | 21 MB 00:02
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 9.2 MB/s | 26 MB 00:02
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : ovzkernel-PAE-devel 1/2
Installing : ovzkernel-PAE 2/2
Installed:
ovzkernel-PAE.i686 0:2.6.18-238.12.1.el5.028stab091.1 ovzkernel-PAE-devel.i686 0:2.6.18-238.12.1.el5.028stab091.1
===================================
Openvz kernel cannot update yum error:
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package ovzkernel-PAE.i686 0:2.6.18-238.5.1.el5.028stab085.5 set to be installed
---> Package ovzkernel-PAE-devel.i686 0:2.6.18-238.5.1.el5.028stab085.5 set to be installed
--> Finished Dependency Resolution
--> Running transaction check
---> Package ovzkernel-PAE-devel.i686 0:2.6.18-194.8.1.el5.028stab070.2 set to be erased
--> Finished Dependency Resolution
Dependencies Resolved
=============================================================================================================================================================
Package Arch Version Repository Size
=============================================================================================================================================================
Installing:
ovzkernel-PAE i686 2.6.18-238.5.1.el5.028stab085.5 openvz-kernel-rhel5 21 M
ovzkernel-PAE-devel i686 2.6.18-238.5.1.el5.028stab085.5 openvz-kernel-rhel5 5.4 M
Removing:
ovzkernel-PAE-devel i686 2.6.18-194.8.1.el5.028stab070.2 installed 16 M
Transaction Summary
=============================================================================================================================================================
Install 2 Package(s)
Upgrade 0 Package(s)
Remove 1 Package(s)
Reinstall 0 Package(s)
Downgrade 0 Package(s)
Total download size: 26 M
Is this ok [y/N]: y
Downloading Packages:
http://mirror.ubiquityservers.com/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.steadfast.net/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.trouble-free.net/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://download.openvz.org/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://openvz-mirror1.rapidvps.com/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://openvz.mirror.netriplex.com/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirrors.igsobe.com/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://lnx.apollo-hw.ro/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.duomenucentras.lt/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://openvz.copahost.com/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://openvz.proserve.nl/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.yandex.ru/mirrors/download.openvz.org/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirrors.adnettelecom.ro/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.ihc.ru/download.openvz.org/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.yourconnect.com/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirrors.xservers.ro/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirrors.ircam.fr/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.ellogroup.com/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.europhase.net/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.as24220.net/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://ftp.wicks.co.nz/pub/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.datacenter.by/pub/download.openvz.org/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirrors.thzhost.com/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://ftp.yz.yamagata-u.ac.jp/pub/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://openvz.tsukuba.wide.ad.jp/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.ubiquityservers.com/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.steadfast.net/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.trouble-free.net/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://download.openvz.org/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://openvz-mirror1.rapidvps.com/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://openvz.mirror.netriplex.com/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirrors.igsobe.com/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://lnx.apollo-hw.ro/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.duomenucentras.lt/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://openvz.copahost.com/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://openvz.proserve.nl/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.yandex.ru/mirrors/download.openvz.org/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirrors.adnettelecom.ro/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.ihc.ru/download.openvz.org/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.yourconnect.com/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirrors.xservers.ro/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirrors.ircam.fr/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.ellogroup.com/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.europhase.net/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.as24220.net/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://ftp.wicks.co.nz/pub/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.datacenter.by/pub/download.openvz.org/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirrors.thzhost.com/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://ftp.yz.yamagata-u.ac.jp/pub/openvz/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://openvz.tsukuba.wide.ad.jp/kernel/branches/rhel5-2.6.18/current/ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
Error Downloading Packages:
ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686: failure: ovzkernel-PAE-2.6.18-238.5.1.el5.028stab085.5.i686.rpm from openvz-kernel-rhel5: [Errno 256] No more mirrors to try.
ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686: failure: ovzkernel-PAE-devel-2.6.18-238.5.1.el5.028stab085.5.i686.rpm from openvz-kernel-rhel5: [Errno 256] No more mirrors to try.
======
Here's the problem, yum is looking for an old version of the openvz kernel that isn't on the mirrors, it doesn't know the newest one.
The current one that my other server found was "2.6.18-238.12.1.el5.028stab091.1" but the broken one is looking for "2.6.18-238.5.1.el5.028stab085.5"
I can't update the openvz repo for some reason, I get these errors:
openvz-kernel-rhel5/filelists | 471 kB 00:00
http://mirror.ubiquityservers.com/openvz/kernel/branches/rhel5-2.6.18/current/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
openvz-kernel-rhel5/filelists | 472 kB 00:00
http://mirror.steadfast.net/openvz/kernel/branches/rhel5-2.6.18/current/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
openvz-kernel-rhel5/filelists | 472 kB 00:00
http://mirror.trouble-free.net/openvz/kernel/branches/rhel5-2.6.18/current/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
openvz-kernel-rhel5/filelists | 472 kB 00:00
http://download.openvz.org/kernel/branches/rhel5-2.6.18/current/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
openvz-kernel-rhel5/filelists | 471 kB 00:00
http://openvz-mirror1.rapidvps.com/kernel/branches/rhel5-2.6.18/current/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
openvz-kernel-rhel5/filelists | 472 kB 00:00
http://openvz.mirror.netriplex.com/kernel/branches/rhel5-2.6.18/current/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
openvz-kernel-rhel5/filelists | 471 kB 00:01
http://mirrors.igsobe.com/openvz/kernel/branches/rhel5-2.6.18/current/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
openvz-kernel-rhel5/filelists | 472 kB 00:01
http://mirror.duomenucentras.lt/openvz/kernel/branches/rhel5-2.6.18/current/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
***Solution***
Basically yum has cached some garbage info relating to the OpenVZ repository and the only way to fix it is to rebuild this "metadata" cache.
yum clean metadata
Loaded plugins: fastestmirror
37 metadata files removed
15 sqlite files removed
0 metadata files removed
I did a yum install ovzkernel-PAE* and it got a newer version downloaded succesfully but it's still out of date!
And yum/openvz still don't think it is out of date for some reason.
Even doing a yum update/upgrade didn't work but I tried hours later and it found the latest version. Maybe I hit an old mirror or the old cache of some sort for the latest openvz package was still someone on my system.
CPT ERR: cc4c0800,28000 :Unknown image version: 304. Can't restore.
This happens when you live migrate between OpenVZ servers with different kernels running, at least significantly different by date.
There is no solution except to make sure you're running the same kernels on all machines, or at least not kernels that are much older or different (this is just a guess though, you should ensure all kernels are the same).
Starting online migration of CT 25000 to 192.168.5.1
Preparing remote node
Initializing remote quota
Syncing private
Live migrating container...
Error: Failed to suspend container
CPT ERR: f68cf000,25000 :foreign process 15755/14731(vzctl) inside CT (e.g. vzctl enter or vzctl exec).
CPT ERR: f68cf000,25000 :suspend is impossible now.
CPT ERR: f68cf000,25000 :foreign process 15755/14731(vzctl) inside CT (e.g. vzctl enter or vzctl exec).
CPT ERR: f68cf000,25000 :suspend is impossible now.
CPT ERR: f68cf000,25000 :foreign process 15755/14731(vzctl) inside CT (e.g. vzctl enter or vzctl exec).
CPT ERR: f68cf000,25000 :suspend is impossible now.
This is because you've entered the container using vzctl enter and are still inside it. It should really either kick you out or notice this before starting the migration. The solution is to just get otu and logout.
Error: detected vswap CT config but kernel does not support vswap
This means either old kernel or bad config (physpages NOT set to 0:unlimited)
Solution
vzctl set $veid --physpages 0:unlimited --save
How to Increase The Disk and Partition Size in Windows 2022,2019,11,10,8,7 etc.. Server
1, Enter the command prompt
Start -> cmd
2. Start diskpart
diskpart
3. Find the drive that has the wrong size
list volume
4. Select the volume (in this example we use volume 2)
select volume 2
5. Extend the volume
You'll want to type both commands for it to work. You need to extend the disk partition and also the filesystem
extend filesystem
extend
*Note the "extend filesystem" and not just extend, this is because our space is allocated and just not correctly reported to the NTFS system so it is necessary or you will ge the failure below"
result:
Diskpart successfully extended the volume
failure:
Virtual Disk Service error:
The size of the extent is less than the minimum
*Idon't know why the above error happens,normally it is if the partition cannot extend that far because the next partition or volume is next but this is not the case on this system.
Alternative Way
If you increased the size of the raw disk you will need to do something like this.
select volume 2
extend
Starting container...
vzquota : (error) Quota on syscall for id 4532: No such file or directory
vzquota on failed [3]
Solution
vzquota drop 4532
Then start the container and it should work. It actually happened after migrating the VPS manually to another location (very common).
Another way of doing essentially the same is the following:
https://realtechtalk.com/vzquota_error_Quota_on_syscall_for_id_42131_No_such_file_or_directory_vzquota_on_failed_[3]-1447-articles
If Proxmox won't start a VM with an error like this:
trying to acquire lock...
TASK ERROR: can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout
rm /var/lock/qemu-server/lock-102.conf
Then try to restart the VM and it should be good.
What we did above was find the lock file that is named lock-VMID (in our case 102) and deleted it to release the lock.
If it's stuck and cannot shutdown this normally works:
qm unlock VMID
qm stop VMID
If the above doesn't work, you can forcefully kill the VM:
1.) Find the process ID
#in the example below we see the Process ID is "1137"
ps aux|grep VMID
2.) Kill the process ID
kill ProcessPIDFromAbove
Example of force killing a VM in Proxmox
< a href="/Products/MX72244">
< span class="c-shca-icon-item__body-name-brand">
ADATA
< / span>
XPG SX8200 PCI - E 3.0 x4 M .2 NVMe SSD, 480 GB
< / a>
The problem in the html above is that there is a "span" inside the "a" and this is unusual except for a few products with ADATA.
Otherwise it would print out ADATA with the other product information "XPG SX8200 PCI - E 3.0 x4 M .2 NVMe SSD, 480 GB". So we just want the product info and not the ADATA inside span.
The solution is to use beautifulsoup's "decompose method below".
hddname = prices.find("div", {"class": "c-shca-icon-item__body-name"})
hddname=hddname.find("a")
hddname.span.decompose()
hddname=hddname.get_text().strip()
Once we have the "a" tag contents which contain a "span inside". We just use the decompose() method.
The format is as follows
soupname.tagname.decompose()
By default VMWare Workstation often doesn't work as we would like.
If you create a VM with a default NAT IP it won't work you will find the NIC is disconnected (even though on the VMWare side it says connected including at Power On).
How To Solve It
1.) Create New VMNet for NAT
Click "Edit" -> "Virtual Network Editor"
Click "Add Network"
Select Network To Add "VMNet1" (or the next available name).
Click on "NAT" under "Network Information"
It should by default enable DHCP and a default range of 192.168.*.*
and hit OK.
2.) Edit your VM and assign it the VMNet you created above.
This may sound silly but often on the same machine multiple versions of SQL may be installed due to other applications.
How do we know which one we are running and connected to?
Use the query:
select @@version