Error Cannot Copy File /etc/hosts Openvz
titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads More... Useful Searches Recent Posts Menu Forums Forums Quick Links Search Forums Recent Posts Members Members Quick Links Notable Members Current Visitors Recent Activity New Profile Posts Menu Log in Sign up Proxmox Support Forum Forums > Proxmox Virtual Environment > Proxmox VE: Installation and configuration > This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More. openvz: startup warnings Discussion in 'Proxmox VE: Installation and configuration' started by mir, May 6, 2013. mir Well-Known Member Proxmox VE Subscriber Joined: Apr 14, 2012 Messages: 3,017 Likes Received: 43 Hi all, When ever I start a CT I get this in the log: /bin/cp: preserving permissions for `/etc/hosts.6': Operation not supported ERROR: Can't copy file /etc/hosts Anything to worry about? #1 mir, May 6, 2013 dietmar Proxmox Staff Member Staff Member Joined: Apr 28, 2005 Messages: 14,410 Likes Received: 85 I guess the container is on NFS? Make sure you use no_root_squash one the NFS server. (Maybe noacl can also help). #2 dietmar, May 7, 2013 mir Well-Known Member Proxmox VE Subscriber Joined: Apr 14, 2012 Messages: 3,017 Likes Received: 43 It is a NFS on a zpool (nexenta) but no_root_squash is set: sharemgr show -vp default nfs=() zfs zfs/vShare/nfs nfs=(anon="-1") nfs:sys=(rw="@172.16.2.0/24" root="@172.16.2.0/24") /volumes/vShare/nfs #3 mir, May 7, 2013 cloudfastservers New Member Joined: Nov 8, 2013 Messages: 3 Likes Received: 0 mir said: ↑ It is a NFS on a zpool (nexenta) but no_root_squash is set: sharemgr show -vp default nfs=() zfs zfs/vShare/nfs nfs=(anon="-1") nfs:sys=(rw="@172.16.2.0/24" root="@172.16.2.0/24") /volumes/vShare/nfsClick to expand... I really need help OpenVz show error and warning because my Nexenta is not accept No Root Squash , how to configure this step by step please help me #4 cloudfastservers, Feb 7, 2014 (You must log in or sign up to post here.) Show Ignored Content Share This Page Tweet Log in with Facebook Log in with Twitter Log in with Google Your name or email address: Do you already have an account? No, create an account now. Yes, my password is: Forgot your password? Stay logged in Proxmox Support Forum Forums > Proxmox Virtual Environment > Proxmox VE: Installation and configuration > Toggle Width Home Contact Us Help Terms and Rules
Start 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 Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network https://forum.proxmox.com/threads/openvz-startup-warnings.13723/ administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top OpenVZ Reboot failed for Ubuntu 12.04 32bit container up vote 0 down vote favorite The container on OpenVZ server was setup using http://serverfault.com/questions/805815/openvz-reboot-failed-for-ubuntu-12-04-32bit-container the template Ubuntu 12.04 32 bit and it was successful.The container fails to load when reboot operation is preformed.Re-installation of the container will only make the server back online.The following error log happens when the container is started after shutdown. [root@openvz ~]# vzctl start 4879 Starting container... Unmounting file system at /vz/root/4879 --- lsof /vz/root/4879 output --- Error in print_output (ploop.c:945): Command lsof exited with status 1 Error in do_umount (ploop.c:983): Failed to umount /vz/root/4879: Device or resource busy Failed to umount image: Error in do_umount (ploop.c:983): Failed to umount /vz/root/4879: Device or resource busy [22] Adding IP address(es): 12.34.56.78 /bin/bash: line 535: /etc/network/interfaces: Read-only file system /bin/bash: line 567: /etc/network/interfaces: Read-only file system /bin/bash: line 574: /etc/network/interfaces: Read-only file system cp: cannot create regular file `/etc/network/interfaces.bak': Read-only file system /bin/bash: line 598: /etc/network/interfaces.bak: Read-only file system mv: cannot stat `/etc/network/interfaces.bak': No such file or directory Setting CPU limit: 100 Setting CPU units: 1000 Setting CPUs: 1 /bin/bash: line 122: /etc/init/console.conf
& Site Management Integration Options Developers eMail Components CloudLinux Extensions Extension Catalog Submit your Extension Plans & Pricing Support Resources FAQs Forums Knowledge Base Documentation Downloads Plesk University Release notes Blog Become a Partner Russian German French Spanish https://kb.plesk.com/en/1015 Chinese Japanese Italian Language English Russian German French Spanish Chinese Japanese Italian any Search My container does not start. What should I check? Article ID: 1015, created on Oct 6, 2008, last review on Jun 17, 2016 Applies to: Operations Automation 5.4 Virtuozzo 6.0 Virtuozzo containers for Linux Virtuozzo hypervisor Resolution Here are the most common causes of a container not starting. The container starts but error cannot shuts down after a few minutes. You probably do not have a valid license installed; it might be expired or the number of containers is exceeded. Please check the output of the vzlicview command. The status of the license should be ACTIVE and the ct_total value in brackets should be not greater than ct_total. More information about licenses can be found in the article How do error cannot copy I check/install a Parallels Virtuozzo Containers license? The container cannot be started because it is locked. Please follow the instructions from this article. The container starts but displays the error /bin/bash: no such file or something similar. The owner of the container could have removed some important package, such as bash or glibc. For containers based on standard templates, you can use the deprecated option of the vzctl command, vzctl recover CTID, to recover the private area of the container. Also, the standard OS template the container is based on may be absent from the Hardware Node; you may check it using vzpkgls CTID and vzpkgls and install the missing OS template if it is needed. For containers based on EZ templates, such an error can appear after migrating the container from another node or after restoring the container from a backup. The pre-migration steps and reparative post-migration steps are described in the article Prepare containers for migration. The container may also be compromised (see below). The container starts but Segmentation fault occurs very soon after its starting. The container may be compromised; please check the article How do I determine that my container is hack