Error During Vzctl Chkpnt
Sign in Pricing Blog Support Search GitHub This repository Watch 11 Star 12 Fork 4 opennode/opennode-tui Code Pull requests 1 Projects 0 Pulse Graphs Permalink Branch: master Switch branches/tags Branches Tags ON-476 ON-479 ON-679 ON-712 ON-738 ON-739 ON-749 ON-770 TUI-17 TUI-20 TUI-37 TUI-40 TUI-41 TUI-43 TUI-44 TUI-45 TUI-49 TUI-50 TUI-54 TUI-56 config-propagation-ON-504 kvm-uuid lev-85 lev-134 lev-151 master oms-92 oms-97 oms-99 oms-204 oms-207 oms-210 oms-349 oms-395 oms-396 oms-490 oms-519 oms-524 oms-557 oms-support on-398 on-584 on-721 on-855b on-855 tui-1 tui-18 tui-47 tui-48 tui-52 tui-57 tui-59 tui-62 tui-64 tui-66 tui-67 tui-68 tui-69 tui-70 tui-72 tui-74 tui-75 tui-77 tui-78 tui-82 tui-84 tui-88 tui-89 tui-91 tui-93 tui-94 tui-95 tui-97 tui-98 tui-99 tui-101 tui-103 tui-104 tui-108 tui-110 tui-114 tui-116 tui-117 tui-119 tui-121 tui-123 tui-135 tui-tests Nothing to show Nothing to show Find file Copy path opennode-tui/opennode/cli/actions/openvz_exit_status.py 754a956 Nov 28, 2012 arand Fixed error handling on starting VM with broken values (ON-711), adde… 1 contributor Users who have contributed to this file arand Raw Blame History 127 lines (121 sloc) 6.46 KB OpenVZ_EXIT_STATUS = { 'vzctl': {0: 'Command executed successfully', 1: 'Failed to set a UBC parameter', 2: 'Failed to set a fair scheduler parameter', 3: 'Generic system error', 5: 'The running kernel is not an OpenVZ kernel (or some OpenVZ modules are not loaded)', 6: 'Not enough system resources', 7: 'ENV_CREATE ioctl failed', 8: 'Command executed by vzctl exec returned non-zero exit code', 9: 'Container is locked by another vzctl invocation', 10: 'Global OpenVZ configuration file vz.conf(5) not found', 11: 'A vzctl helper script file not found', 12: 'Permission denied', 13: 'Capability setting failed', 14: 'Container configuration file ctid.conf(5) not found', 15: 'Timeout on vzctl exec', 16: 'Error during vzctl chkpnt', 17: 'Error during vzctl restore', 18: 'Error from setluid() syscall', 20: 'Invalid command line parameter', 21: 'Invalid value for command line parameter', 22: 'Container root directory (VE_ROOT) not set', 23: 'Container private directory (VE_PRIVATE) not set', 24: 'Container template directory (TEMPLATE) not set', 28: 'Not all required UBC parameters are set, unable to start container', 29: 'OS template is not specified, unable to create container', 31: 'Container not running', 32: 'Container already running', 33: 'Unable to stop container', 34: 'Unable to add IP address to container', 40: 'Container not mounted', 41: 'Container already mounted', 43: 'Container private area not found', 44: 'Conta
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Cannot start, stop, enter VE using OpenVZ up vote 0 down vote favorite I'm using Debian Unstable kernel 2.6.32-5-openvz-amd64 (But I don't think it's a problem). After install and run our https://github.com/opennode/opennode-tui/blob/master/opennode/cli/actions/openvz_exit_status.py VEs for several month, our hard disk is nearly full and we add 3 more hard drives to make new RAID 5 Array, format it as ext4 then mount with location /openvz I have a VE with ID 112, I desire to change its configuration to make private area from /var/lib/vz/private/112 (1) to /openvz/112 (2) After syncing all data from (1) to (2), I cannot start VE 112. I revert configuration back to original, but, when I use http://stackoverflow.com/questions/3777042/cannot-start-stop-enter-ve-using-openvz vzctl status 112:, it shows: # vzctl status 112 VEID 112 exist mounted running and cannot enter the ve: # vzctl enter 112 enter into VE 112 failed cannot stop or restart with error: Operation time out. I've tried many ways: try to umount, mount the private area, or use MAKEDEV to make tty or pty, using vzctl chkpnt 112 --kill but it does not work. I dont want to reboot this server, it contains 2 others VEs that are running well without problem. If someone did face with same problem, please let me know your solutions. Thank you very much, --hung openvz share|improve this question asked Sep 23 '10 at 9:38 hungnv 5627 add a comment| 4 Answers 4 active oldest votes up vote 0 down vote Are you able to exec commands within your CT using 'vzctl exec'? If it is possible try vzctl exec 112 ps aux to check what is running within your CT. share|improve this answer answered Nov 25 '10 at 13:38 Michael Gisbers 62643 add a comment| up vote 0 down vote If you cannot login to your CT because of missing /dev/pts you may mount it with 'vzctl exec': vzctl exec 112 mount devpts /dev/pts -t devpts share|improve this answer answered Nov 25 '10 at 13:43 Michael Gisbers 62643 add a comment| up vote 0 down vote The answer for my question is: I reformat new partitio
'General Discussion' started by figjam, Feb 1, 2012. figjam Mega Poster Messages: 111 I have two containers that I cannot migrate to any hardware node online. Both are showing http://forum.odin.com/threads/vzctl-can-not-dump-container-device-or-resource-busy.247446/ very similar errors: vzctl --skiplock --skipowner chkpnt 999 --dump --dumpfile /vz/dump/dumpfile.xEgbdK vzctl : Can not dump Container: Device or resource busy vzctl : Error: error hardlink .cpt_hardlink.00000001, -2 vzctl : Error: deleted reference to existing inode, checkpointing is impossible: -2 vzctl : Checkpointing of Container failed vzctl failed, exitcode=16 can not dump CT#999 : vzctl failed, exitcode=16 vzctl --skiplock --skipowner chkpnt 998 --dump --dumpfile /vz/dump/dumpfile.Bfsgms vzctl : Error: Unable error during open hardlink directory //.cpt_hardlink_dir_a920e4ddc233afddc9fb53d26c392319: No such file or directory vzctl : Checkpointing of Container failed vzctl failed, exitcode=16 can not dump CT#998 : vzctl failed, exitcode=16 Both of these containers were migrated online to the hardware node less than a month ago. Can anyone suggest what I can do to fix the issue? Cheers, Andrew figjam, Feb 1, 2012 #1 MakcyD Odin Team Messages: 66 Hi Andrew, error during vzctl Did you perform any manual operations on template area on the node? The issue is known to occur, when template are was modified, e.g. by copying binaries to /vz/template/OS/VER/ARCH/ while there are containers running, which use binaries from that folder. It was quite a regular troubleshooting step some time ago, to simply copy template area from one node to another in order to prevent various migration issues, but it did not take into account such situation, when we have container running, which uses, let us say, /sbin/rsyslogd, which is a magic link to /vz/template/redhat/el5/x86_64/rsyslog-2.0.6-1.el5.x86_64/sbin/rsyslogd. So now, if we copy template from the other node which might have slightly different /sbin/rsyslogd binary and override the one, currently used in the container. So now if we try to make a dump of container's memory we will inevitably go into non-existing inode (because the file physically is located on the other inodes). The solution in this case is: 1. Never manually sync binaries among template areas (at least, while containers are running) 2. Before the migration synchronize vzpackages using this article: Prepare containers for migration MakcyD, Feb 11, 2012 #2 KristianM Product Expert Messages: 467 MakcyD said: ↑ Did you perform any manual operations on