<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: “Broken” Files In VPS Container</title>
	<atom:link href="http://www.thevirtuozzoadmin.com/broken-files-in-vps-container/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thevirtuozzoadmin.com/broken-files-in-vps-container/</link>
	<description>We know stuff about Virtuozzo.</description>
	<lastBuildDate>Tue, 12 Apr 2011 08:56:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Andrew</title>
		<link>http://www.thevirtuozzoadmin.com/broken-files-in-vps-container/comment-page-1/#comment-40</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 19 Aug 2010 05:21:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.thevirtuozzoadmin.com/?p=23#comment-40</guid>
		<description>Hi,

I had exactly the same thing with three different debian and ubuntu containers. It turned out that they were all using older versions of the apache2.2-common package than was on the new server.

If you cat any of the suspect files from outside the container, the contents are just a pointer to the location of the missing files:

    cat /vz/private/137/fs/root/etc/apache2/ports.conf

gave something like:

//ubuntu/9.04/x86/apache2.2-common_2.2.11-2ubuntu2.2_i386/etc/apache2/ports.conf

The package was missing from /vz/template/ubuntu/9.04/x86 on the new server (somehow the migration process had not copied it across). Rsyncing the correct directory from the old server to the new and restarting the VPS fixed the problem on all the problem containers. In the case above I ran the following command on the old server:

    rsync -avz -e &quot;ssh -l root&quot; /vz/template/ubuntu/9.04/x86/apache2.2-common_2.2.11-2ubuntu2.2_i386/ 172.16.1.1:/vz/template/ubuntu/9.04/x86/apache2.2-common_2.2.11-2ubuntu2.2_i386

to copy the required files to the new server.

Cheers,</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I had exactly the same thing with three different debian and ubuntu containers. It turned out that they were all using older versions of the apache2.2-common package than was on the new server.</p>
<p>If you cat any of the suspect files from outside the container, the contents are just a pointer to the location of the missing files:</p>
<p>    cat /vz/private/137/fs/root/etc/apache2/ports.conf</p>
<p>gave something like:</p>
<p>//ubuntu/9.04/x86/apache2.2-common_2.2.11-2ubuntu2.2_i386/etc/apache2/ports.conf</p>
<p>The package was missing from /vz/template/ubuntu/9.04/x86 on the new server (somehow the migration process had not copied it across). Rsyncing the correct directory from the old server to the new and restarting the VPS fixed the problem on all the problem containers. In the case above I ran the following command on the old server:</p>
<p>    rsync -avz -e &#8220;ssh -l root&#8221; /vz/template/ubuntu/9.04/x86/apache2.2-common_2.2.11-2ubuntu2.2_i386/ 172.16.1.1:/vz/template/ubuntu/9.04/x86/apache2.2-common_2.2.11-2ubuntu2.2_i386</p>
<p>to copy the required files to the new server.</p>
<p>Cheers,</p>
]]></content:encoded>
	</item>
</channel>
</rss>

