<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SupportSages &#187; inodes</title>
	<atom:link href="http://www.supportsages.com/blog/tag/inodes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.supportsages.com/blog</link>
	<description>Technical Support and Server Management : Musings in the fox hole.</description>
	<lastBuildDate>Thu, 05 Jan 2012 03:05:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>How to resolve : Internal Server Error when accessing cpanel/WHM/Webmail</title>
		<link>http://www.supportsages.com/blog/2010/06/how-to-resolve-internal-server-error-when-accessing-cpanelwhmwebmail/</link>
		<comments>http://www.supportsages.com/blog/2010/06/how-to-resolve-internal-server-error-when-accessing-cpanelwhmwebmail/#comments</comments>
		<pubDate>Fri, 25 Jun 2010 19:13:12 +0000</pubDate>
		<dc:creator>vince</dc:creator>
				<category><![CDATA[Howtos]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Specials]]></category>
		<category><![CDATA[VPS]]></category>
		<category><![CDATA[cPanel]]></category>
		<category><![CDATA[inode issue]]></category>
		<category><![CDATA[inodes]]></category>
		<category><![CDATA[internal server error]]></category>
		<category><![CDATA[more than 400 attempts to make a session failed]]></category>
		<category><![CDATA[Webmail]]></category>
		<category><![CDATA[WHM]]></category>

		<guid isPermaLink="false">http://www.supportsages.com/blog/?p=927</guid>
		<description><![CDATA[Imagine you are accessing your Website WHM or cPanel or Webmail hosted (in your VPS) and what if you see this

<a href="http://www.supportsages.com/blog/wp-content/uploads/2010/06/cpanel-inode-full-issue.png"><img class="alignnone size-medium wp-image-929" title="cpanel inode full issue" src="http://www.supportsages.com/blog/wp-content/uploads/2010/06/cpanel-inode-full-issue-300x63.png" alt="Image showing the issue" width="300" height="63" /></a><span style="text-decoration: underline;"><strong> </strong></span>

<span style="text-decoration: underline;"><strong>How to solve this</strong></span>

Pre-Requisites : You should have Shell access (as root) to the Node server.

Mostly this happens due to inode issue. The inodes allocated to the server maybe full. <strong>inode</strong> is a data structure on a traditional Unix-style file system such as UFS. An inode stores basic information about a regular file, directory, or other file system object.

<strong>Steps</strong>

Say ...]]></description>
			<content:encoded><![CDATA[<p>Imagine you are accessing your Website WHM or cPanel or Webmail hosted (in your VPS) and what if you see this</p>
<p><a  href="http://www.supportsages.com/blog/wp-content/uploads/2010/06/cpanel-inode-full-issue.png" class="thickbox no_icon" rel="gallery-927" title="cpanel inode full issue"><img class="alignnone size-medium wp-image-929" title="cpanel inode full issue" src="http://www.supportsages.com/blog/wp-content/uploads/2010/06/cpanel-inode-full-issue-300x63.png" alt="Image showing the issue" width="300" height="63" /></a><span style="text-decoration: underline;"><strong> </strong></span></p>
<p><span style="text-decoration: underline;"><strong>How to solve this</strong></span></p>
<p>Pre-Requisites : You should have Shell access (as root) to the Node server.</p>
<p>Mostly this happens due to inode issue. The inodes allocated to the server maybe full. <strong>inode</strong> is a data structure on a traditional Unix-style file system such as UFS. An inode stores basic information about a regular file, directory, or other file system object.</p>
<p><strong>Steps</strong></p>
<p>Say we are logged into the Node Server. There we are going to list all the Containers existing on the Hardware Node. By default, only running Containers are shown.</p>
<pre class="brush: bash; title: ; notranslate">
[root@linuxvps1 ~]# vzlist -a
CTID    NPROC STATUS   IP_ADDR        HOSTNAME
100     18  running    100.20.11.111  WEB.EXAMPLE.COM
101     63  running    100.20.12.203  -
102     169 running    100.20.92.182  server2.example.com
103     81  running    100.20.56.169  example.net
78965   236 running    100.20.77.204  server1.example.com
</pre>
<p>Assume your container is 103. So simply enter into 103 by this command</p>
<pre class="brush: bash; title: ; notranslate">
[root@linuxvps1 ~]# vzctl enter 103
</pre>
<p>Check if the inodes are full in the container</p>
<pre class="brush: bash; title: ; notranslate">
[root@linuxvps1 ~]# df -i
</pre>
<p>Most Probably it should display something like this :</p>
<pre class="brush: bash; title: ; notranslate">
Filesystem      Inodes      IUsed        IFree     IUse%      Mounted on
/dev/vzfs       200000      200000       0         100%       /
none            65536       95           65441     1%         /dev
</pre>
<p>Bang ! The inodes on /dev/vzfs mounted on / are full. You&#8217;ve to go nowhere else to see why that error was delivered. A simple solution will work out, you&#8217;ve to increase the inode limit. You&#8217;ve two options, either through Shell or through the Node Control Panel (like Parallels Infrastructure Manager)</p>
<p>First we will go through Shell mode with this command :</p>
<pre class="brush: bash; title: ; notranslate">$ vzctl set veid --diskinodes softlimit:hardlimit </pre>
<p>Where &#8216;veid&#8217; is the VPS ID</p>
<pre class="brush: bash; title: ; notranslate">root@linuxvps1 ~]# vzctl set 103 --diskinodes 7680100:7680200</pre>
<p>Second we are going for Node Control Panel. In the infrastructure, you will see your VPS with a ! sign. That indicates your VPS is having some sort of issue.</p>
<p><a  href="http://www.supportsages.com/blog/wp-content/uploads/2010/06/cp12.png" class="thickbox no_icon" rel="gallery-927" title="cp1"><img class="alignnone size-full wp-image-934" title="cp1" src="http://www.supportsages.com/blog/wp-content/uploads/2010/06/cp12.png" alt="" width="195" height="159" /></a></p>
<p>So you&#8217;ve seen the Alert. Next access the VPS, go to Resources tab. I&#8217;m sorry to tell you that I grabbed this screenshot after resolving the issue, but it will help you anyway</p>
<p><a  href="http://www.supportsages.com/blog/wp-content/uploads/2010/06/cp2.png" class="thickbox no_icon" rel="gallery-927" title="cp2"><img class="alignnone size-full wp-image-935" title="cp2" src="http://www.supportsages.com/blog/wp-content/uploads/2010/06/cp2.png" alt="" width="616" height="408" /></a></p>
<p>You should see the &#8216;Disk Inodes&#8217; is full under &#8216;Disk Usage&#8217; category (Here it is not !). Next Click Configure to settle this one</p>
<p><a  href="http://www.supportsages.com/blog/wp-content/uploads/2010/06/cp41.png" class="thickbox no_icon" rel="gallery-927" title="cp4"><img class="alignnone size-full wp-image-937" title="cp4" src="http://www.supportsages.com/blog/wp-content/uploads/2010/06/cp41.png" alt="" width="1192" height="394" /></a>See the Highlighted part, the inodes should be limited to some size. Increase it or remove the check mark to make it unlimited.  Make sure you save the changes. Now try again accessing cpanel/WHM/Webmail. It should load with out any issues.That makes a smile in your face, isn&#8217;t it ? <img src='http://www.supportsages.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<div class="tweetthis" style="text-align:left;"><p> <a  class="tt" href="http://twitter.com/home/?status=How+to+resolve+%3A+Internal+Server+Error+when+accessing+cpanel%2FWHM%2FWebmail+http%3A%2F%2Fwww.supportsages.com%2Fblog%2F927" title="Post to Twitter"><img class="nothumb" src="http://www.supportsages.com/blog/wp-content/plugins/tweet-this/icons/en/twitter/tt-twitter3.png" alt="Post to Twitter" /></a> <a  class="tt" href="http://twitter.com/home/?status=How+to+resolve+%3A+Internal+Server+Error+when+accessing+cpanel%2FWHM%2FWebmail+http%3A%2F%2Fwww.supportsages.com%2Fblog%2F927" title="Post to Twitter">Tweet This Post</a></p></div>]]></content:encoded>
			<wfw:commentRss>http://www.supportsages.com/blog/2010/06/how-to-resolve-internal-server-error-when-accessing-cpanelwhmwebmail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

