<?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>Server Sitters Tech Corner &#187; Apache</title>
	<atom:link href="http://serversitters.com/technical/category/apache/feed/" rel="self" type="application/rss+xml" />
	<link>http://serversitters.com/technical</link>
	<description>Outsourced Web Hosting Support</description>
	<lastBuildDate>Wed, 15 Dec 2010 12:03:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Disable Trace method &#8211; PCI</title>
		<link>http://serversitters.com/technical/apache/disable-trace-method-pci/</link>
		<comments>http://serversitters.com/technical/apache/disable-trace-method-pci/#comments</comments>
		<pubDate>Wed, 17 Nov 2010 18:05:00 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=200</guid>
		<description><![CDATA[For PCI compliance it&#8217;s often required that you disable the trace method. This can be done by adding the following to your apache config or httpd.conf file: TraceEnable off In cpanel we typically add this entry in the following file: /usr/local/apache/conf/includes/pre_main_global.conf Then restart apache: /etc/init.d/httpd restart Then you can test it: telnet 127.0.0.1 80 Trying [...]]]></description>
			<content:encoded><![CDATA[<p>For PCI compliance it&#8217;s often required that you disable the trace method.  This can be done by adding the following to your apache config or httpd.conf file:</p>
<p>TraceEnable off</p>
<p>In cpanel we typically add this entry in the following file:<br />
/usr/local/apache/conf/includes/pre_main_global.conf </p>
<p>Then restart apache:<br />
/etc/init.d/httpd restart</p>
<p>Then you can test it:<br />
telnet 127.0.0.1 80</p>
<p>Trying 127.0.0.1&#8230;</p>
<p>Connected to 127.0.0.1.</p>
<p>Escape character is &#8216;^]&#8217;.</p>
<p>TRACE / HTTP/1.0</p>
<p>Host: foo</p>
<p>testing&#8230;  <- ENTER twice</p>
<p>You should receive an error &#8211; i.e.</p>
<p>HTTP/1.1 403 Forbidden</p>
<p>Date: Sat, 20 Oct 2007 20:38:31 GMT</p>
<p>Server: Apache/2.2.6 (Debian) PHP/4.4.4-9 mod_ruby/1.2.6 Ruby/1.8.6(2007-06-07)</p>
<p>Content-Length: 320</p>
<p>Connection: close</p>
<p>Content-Type: text/html; charset=iso-8859-1</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/apache/disable-trace-method-pci/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>httpd fullstatus</title>
		<link>http://serversitters.com/technical/apache/httpd-fullstatus/</link>
		<comments>http://serversitters.com/technical/apache/httpd-fullstatus/#comments</comments>
		<pubDate>Wed, 17 Nov 2010 18:00:28 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=198</guid>
		<description><![CDATA[Here&#8217;s a quick apache command that will help you with tracking down apache processes and usage: httpd fullstatus]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s a quick apache command that will help you with tracking down apache processes and usage:</p>
<p>httpd fullstatus</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/apache/httpd-fullstatus/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mod Security Whitelist IP</title>
		<link>http://serversitters.com/technical/security/mod-security-whitelist-ip/</link>
		<comments>http://serversitters.com/technical/security/mod-security-whitelist-ip/#comments</comments>
		<pubDate>Mon, 24 May 2010 14:08:09 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=194</guid>
		<description><![CDATA[Sometimes it&#8217;s necessary to whitelist an IP address so it can get past the mod_security filters. This is a great feature in case you want to open the filters for one visitor while leaving the security features in place. Open the mod_security whitelist file: vi /usr/local/apache/conf/modsec2/whitelist.conf Code: SecRule REMOTE_ADDR "^111\.222\.333\.444" phase:1,nolog,allow,ctl:ruleEngine=off Where 111.222.333.444 would be [...]]]></description>
			<content:encoded><![CDATA[<p>Sometimes it&#8217;s necessary to whitelist an IP address so it can get past the mod_security filters.  This is a great feature in case you want to open the filters for one visitor while leaving the security features in place.</p>
<p>Open the mod_security whitelist file:<br />
vi /usr/local/apache/conf/modsec2/whitelist.conf</p>
<p>Code:<br />
<code><br />
SecRule REMOTE_ADDR "^111\.222\.333\.444" phase:1,nolog,allow,ctl:ruleEngine=off<br />
</code></p>
<p>Where 111.222.333.444 would be replaced with the IP address you wish to whitelist.</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/security/mod-security-whitelist-ip/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disable mod security</title>
		<link>http://serversitters.com/technical/apache/disable-mod-security/</link>
		<comments>http://serversitters.com/technical/apache/disable-mod-security/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 06:55:45 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=183</guid>
		<description><![CDATA[It&#8217;s easy to disable mod security, however the fix varies depending upon the version of mod_security and the way that it has been installed. For mod_security 1.X try the following in a .htaccess within the user&#8217;s home folder: SecFilterEngine Off If that causes a site error or it doesn&#8217;t work you&#8217;re most likely using mod [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s easy to disable mod security, however the fix varies depending upon the version of mod_security and the way that it has been installed.  For mod_security 1.X try the following in a .htaccess within the user&#8217;s home folder:<br />
SecFilterEngine Off</p>
<p>If that causes a site error or it doesn&#8217;t work you&#8217;re most likely using mod security 2.X.  To disable mod security on version 2.X:<br />
First you have to find the path to your whitelist file.  To find this cd into your apache configuration folder.  On cpanel you would run:<br />
cd /usr/local/apache/conf<br />
Then run:<br />
grep whitelist *|grep modsec</p>
<p>This should show you the exact location of your whitelist file.  If the file doesn&#8217;t exist create it using touch or vi.  Once the file has been created add the following:<br />
SecRule SERVER_NAME &#8220;yourdomain.com&#8221; phase:1,nolog,allow,ctl:ruleEngine=off<br />
Be sure to replace yourdomain.com with the domain that you want to disable mod security on.  Then save the file and restart apache.</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/apache/disable-mod-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>critical_create No space left on device</title>
		<link>http://serversitters.com/technical/apache/critical_create-no-space-left-on-device/</link>
		<comments>http://serversitters.com/technical/apache/critical_create-no-space-left-on-device/#comments</comments>
		<pubDate>Wed, 30 Dec 2009 17:29:47 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=167</guid>
		<description><![CDATA[Recently we attempted to restart apache on a client&#8217;s server and we received the following error: critical_create(): semget() failed: No space left on device Although the error hinted at a disk space issue it actually had nothing to do with the available disk space. To resolve this you have two options: 1.) You could reboot [...]]]></description>
			<content:encoded><![CDATA[<p>Recently we attempted to restart apache on a client&#8217;s server and we received the following error:<br />
critical_create(): semget() failed: No space left on device</p>
<p>Although the error hinted at a disk space issue it actually had nothing to do with the available disk space.  To resolve this you have two options:<br />
1.) You could reboot the server which will clear the apache semaphores<br />
2.) Or you can run the following:<br />
<code><br />
killall -9 httpd<br />
for i in $(ipcs|grep httpd|awk '{print $2}');do ipcrm -s $i;done<br />
</code></p>
<p>This will get a list of the semid&#8217;s and shmid&#8217;s and pass them to the ipcrm command.  By using the ipcrm command on each id you will mark System V interprocess communication API kernel entities for removal.  In short it will free up the memory being used by the kernel for these processes so you have enough memory to restart the service.  Once you run this command simply restart apache!</p>
<p><code><br />
/etc/init.d/httpd restart<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/apache/critical_create-no-space-left-on-device/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disable directory indexing</title>
		<link>http://serversitters.com/technical/htaccess/disable-directory-indexing/</link>
		<comments>http://serversitters.com/technical/htaccess/disable-directory-indexing/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 21:45:57 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Htaccess]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=145</guid>
		<description><![CDATA[The easiest way to disable directory indexing is to update/create a .htaccess. Add the following to a .htaccess file within your primary web folder: Options -Indexes]]></description>
			<content:encoded><![CDATA[<p>The easiest way to disable directory indexing is to update/create a .htaccess.  Add the following to a .htaccess file within your primary web folder:<br />
<code>Options -Indexes</code></p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/htaccess/disable-directory-indexing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apache Basics</title>
		<link>http://serversitters.com/technical/apache/apache-basics/</link>
		<comments>http://serversitters.com/technical/apache/apache-basics/#comments</comments>
		<pubDate>Fri, 11 Dec 2009 14:50:46 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=55</guid>
		<description><![CDATA[Secure config file: vi /usr/local/apache-ssl/conf/httpd.conf Normal config file: vi /etc/httpd/conf/httpd.conf This command can be used especially when Apache is already running and you have just made a change in a configuration file. # /usr/local/bin/httpd.reload This command can be used especially if Apache is down and needs to be started up. # /usr/local/bin/httpd.reload &#8211;restart The Apache [...]]]></description>
			<content:encoded><![CDATA[<p>Secure config file:<strong><br />
vi /usr/local/apache-ssl/conf/httpd.conf</strong></p>
<p>Normal config file:<br />
<strong>vi /etc/httpd/conf/httpd.conf</strong></p>
<p>This command can be used especially when Apache is already running and you have just made a change in a configuration file.<br />
<strong># /usr/local/bin/httpd.reload</strong></p>
<p>This command can be used especially if Apache is down and needs to be started up.<br />
<strong># /usr/local/bin/httpd.reload &#8211;restart</strong></p>
<p>The Apache Error Log:<strong><br />
tail -35 /var/log/httpd/error_log</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/apache/apache-basics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>No listening sockets</title>
		<link>http://serversitters.com/technical/apache/no-listening-sockets/</link>
		<comments>http://serversitters.com/technical/apache/no-listening-sockets/#comments</comments>
		<pubDate>Thu, 10 Dec 2009 19:15:05 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=47</guid>
		<description><![CDATA[httpd not running, trying to start no listening sockets available, shutting down Unable to open logs Look for log files greater than 2GB in size.  This usually occurs when a log file grows too large or if the file system has been set to read only due to drive errors.]]></description>
			<content:encoded><![CDATA[<p>httpd not running, trying to start</p>
<p>no listening sockets available, shutting down<br />
Unable to open logs</p>
<p>Look for log files greater than 2GB in size.  This usually occurs when a log file grows too large or if the file system has been set to read only due to drive errors.</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/apache/no-listening-sockets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

