<?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: Plesk install on Ubuntu server &#8211; &#8220;It seems there is a user with UID=110 in this system&#8221; error</title>
	<atom:link href="http://hostechs.com/2009/05/plesk-install-on-ubuntu-server-it-seems-there-is-a-user-with-uid110-in-this-system-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://hostechs.com/2009/05/plesk-install-on-ubuntu-server-it-seems-there-is-a-user-with-uid110-in-this-system-error/</link>
	<description>Yet another Techi blog</description>
	<lastBuildDate>Fri, 10 Feb 2012 10:18:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Florian N</title>
		<link>http://hostechs.com/2009/05/plesk-install-on-ubuntu-server-it-seems-there-is-a-user-with-uid110-in-this-system-error/comment-page-1/#comment-151</link>
		<dc:creator>Florian N</dc:creator>
		<pubDate>Fri, 04 Jun 2010 18:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://hostechs.com/?p=391#comment-151</guid>
		<description>I was expecting that they fixed this issue after so many versions but seems not to be so.

I guess it depends on their testing methods but after a few clients report this bug any company should take measures to fix the reported bugs.</description>
		<content:encoded><![CDATA[<p>I was expecting that they fixed this issue after so many versions but seems not to be so.</p>
<p>I guess it depends on their testing methods but after a few clients report this bug any company should take measures to fix the reported bugs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://hostechs.com/2009/05/plesk-install-on-ubuntu-server-it-seems-there-is-a-user-with-uid110-in-this-system-error/comment-page-1/#comment-150</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 04 Jun 2010 16:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://hostechs.com/?p=391#comment-150</guid>
		<description>This happened to me, installing Plesk 9.5.2 on a stock Ubuntu 8.04 server.  There were a couple of interesting complications...

UID 110 was assigned to the &quot;mysql&quot; user.  I changed it to 111 and tried to run the Plesk install again.  But before I could do that, I had to clean up the package dependencies, since the package install was interrupted (sudo apt-get -f install), and during this process, I was prompted to create a MySQL root password.  So I did.

Then I tried the Plesk install again.  This time, it gave me the same error, so I checked... the bind user was now set to 110.  So I changed it to 112.

Then I tried the Plesk install again.  This time, it started throwing errors about not being able to connect to the MySQL database.  Oops!  Looks like it expects the root password to be blank.  Had to reset that.

Then it finally worked right.

All because they want to use a fixed UID.  I wonder why this didn&#039;t show up during their testing...</description>
		<content:encoded><![CDATA[<p>This happened to me, installing Plesk 9.5.2 on a stock Ubuntu 8.04 server.  There were a couple of interesting complications&#8230;</p>
<p>UID 110 was assigned to the &#8220;mysql&#8221; user.  I changed it to 111 and tried to run the Plesk install again.  But before I could do that, I had to clean up the package dependencies, since the package install was interrupted (sudo apt-get -f install), and during this process, I was prompted to create a MySQL root password.  So I did.</p>
<p>Then I tried the Plesk install again.  This time, it gave me the same error, so I checked&#8230; the bind user was now set to 110.  So I changed it to 112.</p>
<p>Then I tried the Plesk install again.  This time, it started throwing errors about not being able to connect to the MySQL database.  Oops!  Looks like it expects the root password to be blank.  Had to reset that.</p>
<p>Then it finally worked right.</p>
<p>All because they want to use a fixed UID.  I wonder why this didn&#8217;t show up during their testing&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

