<?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: 1&amp;1 Internet: Disk quota exceeded (122) error on MYSQL Database apps</title>
	<atom:link href="http://pleasantonwebdesignblog.com/2008/02/1-internet-disk-quota-exceeded-122.html/feed" rel="self" type="application/rss+xml" />
	<link>http://pleasantonwebdesignblog.com/2008/02/1-internet-disk-quota-exceeded-122.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=1-internet-disk-quota-exceeded-122</link>
	<description>Information on Web design, technology, and culture from my vantage point here in Pleasanton, California.</description>
	<lastBuildDate>Tue, 01 May 2012 15:18:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: admin</title>
		<link>http://pleasantonwebdesignblog.com/2008/02/1-internet-disk-quota-exceeded-122.html/comment-page-1#comment-10480</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 11 Jun 2010 04:31:36 +0000</pubDate>
		<guid isPermaLink="false">http://pleasantonwebdesign.tpdevspace.com/?p=135#comment-10480</guid>
		<description>Thanks for visiting. Glad I could help!</description>
		<content:encoded><![CDATA[<p>Thanks for visiting. Glad I could help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rene</title>
		<link>http://pleasantonwebdesignblog.com/2008/02/1-internet-disk-quota-exceeded-122.html/comment-page-1#comment-10409</link>
		<dc:creator>rene</dc:creator>
		<pubDate>Mon, 07 Jun 2010 13:31:14 +0000</pubDate>
		<guid isPermaLink="false">http://pleasantonwebdesign.tpdevspace.com/?p=135#comment-10409</guid>
		<description>it still helped me a year later! tnx!!</description>
		<content:encoded><![CDATA[<p>it still helped me a year later! tnx!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: K</title>
		<link>http://pleasantonwebdesignblog.com/2008/02/1-internet-disk-quota-exceeded-122.html/comment-page-1#comment-3018</link>
		<dc:creator>K</dc:creator>
		<pubDate>Mon, 04 May 2009 22:44:08 +0000</pubDate>
		<guid isPermaLink="false">http://pleasantonwebdesign.tpdevspace.com/?p=135#comment-3018</guid>
		<description>This is over a year after the original post, but a friend of mine had the same issue yesterday and also uses 1&amp;1 for hosting.

This issue was caused by his site being on a shared server and the server&#039;s global php session folder was set to &quot;/tmp&quot;, which he did not have access to.  His access started in a client folder like &quot;/homepages//htdocs&quot;.  So his app didn&#039;t have permissions to the global session folder and was reporting a lack of disk space because it couldn&#039;t write files there.

The fix was one line of code that changed the php session folder to somewhere within his reach in the file system, given his file permissions:

ini_set(&quot;session.save_path&quot;, &quot;/homepages//tmp&quot;);

This needs to be placed in the php code at a point before any sessions are being created.  Change the above path to match your path on the server and create a tmp folder there to serve as the new location for sessions.  Make sure the file permissions allow php full read/write/modify/delete access to the new location.  That immediately fixed our problem.</description>
		<content:encoded><![CDATA[<p>This is over a year after the original post, but a friend of mine had the same issue yesterday and also uses 1&amp;1 for hosting.</p>
<p>This issue was caused by his site being on a shared server and the server&#8217;s global php session folder was set to &#8220;/tmp&#8221;, which he did not have access to.  His access started in a client folder like &#8220;/homepages//htdocs&#8221;.  So his app didn&#8217;t have permissions to the global session folder and was reporting a lack of disk space because it couldn&#8217;t write files there.</p>
<p>The fix was one line of code that changed the php session folder to somewhere within his reach in the file system, given his file permissions:</p>
<p>ini_set(&#8220;session.save_path&#8221;, &#8220;/homepages//tmp&#8221;);</p>
<p>This needs to be placed in the php code at a point before any sessions are being created.  Change the above path to match your path on the server and create a tmp folder there to serve as the new location for sessions.  Make sure the file permissions allow php full read/write/modify/delete access to the new location.  That immediately fixed our problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: monturner</title>
		<link>http://pleasantonwebdesignblog.com/2008/02/1-internet-disk-quota-exceeded-122.html/comment-page-1#comment-40</link>
		<dc:creator>monturner</dc:creator>
		<pubDate>Tue, 11 Mar 2008 13:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://pleasantonwebdesign.tpdevspace.com/?p=135#comment-40</guid>
		<description>Just letting you know, 1&amp;1 database servers kicked the proverbial bucket today at 1.03pm GMT.&lt;br/&gt;&lt;br/&gt;It&#039;s not a one off as the three different servers I using are all (bless them) RIP.&lt;br/&gt;&lt;br/&gt;Just an update for you all, and it&#039;s amazing at how apologetic front line tech support can be.</description>
		<content:encoded><![CDATA[<p>Just letting you know, 1&#038;1 database servers kicked the proverbial bucket today at 1.03pm GMT.</p>
<p>It&#8217;s not a one off as the three different servers I using are all (bless them) RIP.</p>
<p>Just an update for you all, and it&#8217;s amazing at how apologetic front line tech support can be.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

