<?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>Andryan's Random Notes &#187; Plesk</title>
	<atom:link href="http://blog.nirkabel.org/category/plesk/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nirkabel.org</link>
	<description>This blog is here to stay</description>
	<lastBuildDate>Fri, 20 Jan 2012 03:17:09 +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>iptables port forwarding rules for BattleNET games</title>
		<link>http://blog.nirkabel.org/2007/05/22/iptables-port-forwarding-rules-for-battlenet-games/</link>
		<comments>http://blog.nirkabel.org/2007/05/22/iptables-port-forwarding-rules-for-battlenet-games/#comments</comments>
		<pubDate>Tue, 22 May 2007 04:14:50 +0000</pubDate>
		<dc:creator>Andryan</dc:creator>
				<category><![CDATA[FTP]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Netfilter]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Technical]]></category>

		<guid isPermaLink="false">http://andryan.wordpress.com/2007/05/22/battlenet-games-iptables-rules/</guid>
		<description><![CDATA[This script will create port forwarding rules on port 36xxx to 192.168.1.xxx:36xxx.]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.nirkabel.org/wp-content/uploads/2007/05/script.txt" target="_blank">This script</a> will create port forwarding rules on port 36xxx to 192.168.1.xxx:36xxx.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nirkabel.org/2007/05/22/iptables-port-forwarding-rules-for-battlenet-games/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RHEL Apache (Plesk) rebuild</title>
		<link>http://blog.nirkabel.org/2006/01/23/rhel-apache-plesk-rebuild/</link>
		<comments>http://blog.nirkabel.org/2006/01/23/rhel-apache-plesk-rebuild/#comments</comments>
		<pubDate>Mon, 23 Jan 2006 17:52:21 +0000</pubDate>
		<dc:creator>Andryan</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Technical]]></category>

		<guid isPermaLink="false">http://andryan.wordpress.com/2006/01/23/rhel-apache-plesk-rebuild/</guid>
		<description><![CDATA[By default, Apache distribution shipped with RHEL is compiled with a hard limit of 300 FDs. A busy server requires a lot more..This is how I increased the FD hard limit based on SW-Soft&#8217;s FAQ: http://faq.sw-soft.com/index.php?ToDo=view&#38;questId=172&#38;catId=42 A bit outdated, but that&#8217;ll do! Add the following line to /etc/sysctl.conf: fs.file-max = 131072 Run the following shell [...]]]></description>
			<content:encoded><![CDATA[<p align="left">By default, Apache distribution shipped with RHEL is compiled with a hard limit of 300 FDs. A busy server requires a lot more..This is how I increased the FD hard limit based on SW-Soft&#8217;s FAQ: <a href="http://faq.sw-soft.com/index.php?ToDo=view&amp;questId=172&amp;catId=42" target="_blank">http://faq.sw-soft.com/index.php?ToDo=view&amp;questId=172&amp;catId=42</a><br />
A bit outdated, but that&#8217;ll do! <img src='http://blog.nirkabel.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p align="left">Add the following line to /etc/sysctl.conf:<br />
fs.file-max = 131072</p>
<p align="left">Run the following shell command:<br />
# sysctl -w fs.file-max=131072</p>
<p align="left">Edit __FD_SETSIZE value in /usr/include/bits/typesizes.h to:<br />
#define __FD_SETSIZE 32768<br />
(before, it is 1024)</p>
<p align="left">Find httpd&#8217;s source rpm (try rpmfind or Google) and rebuild the package.<br />
xmlto and pcre-devel are required, install both with up2date.<br />
Other craps will be installed too:<br />
pcre-devel xmlto docbook-dtds docbook-style-xsl passivetex sgml-common tetex xml-common xmltex tetex-fonts tetex-latex<br />
Feel free to remove them once package has been rebuilt.</p>
<p align="left">To rebuild the httpd rpm from the source rpm:<br />
rpmbuild &#8211;rebuild sourcerpmfilehere.src.rpm</p>
<p align="left">Once the custom binary rpm is ready, install it with -Uvh &#8211;force<br />
Although the rebuild process produces 4 rpm files, I think only the httpd rpm is required.</p>
<p align="left">Restart apache with the following commands:<br />
/usr/local/psa/admin/sbin/websrvmng -a -v (not sure why this is needed)<br />
service httpd restart</p>
<p align="left">Valid for Plesk 7.5.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nirkabel.org/2006/01/23/rhel-apache-plesk-rebuild/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PowerDNS with Plesk servers</title>
		<link>http://blog.nirkabel.org/2006/01/23/powerdns-with-plesk-servers/</link>
		<comments>http://blog.nirkabel.org/2006/01/23/powerdns-with-plesk-servers/#comments</comments>
		<pubDate>Mon, 23 Jan 2006 17:51:18 +0000</pubDate>
		<dc:creator>Andryan</dc:creator>
				<category><![CDATA[DNS]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Technical]]></category>

		<guid isPermaLink="false">http://andryan.wordpress.com/2006/01/23/powerdns-with-plesk-servers/</guid>
		<description><![CDATA[Having separate secondary NS for Plesk servers will be difficult to manage. To ease the process, I came up with an idea of using PowerDNS&#8217; supermasters feature. Just shove in the IP of the Plesk server, the name of the secondary NS and the server name to the supermasters table. During initial touch-up of the [...]]]></description>
			<content:encoded><![CDATA[<p align="left">Having separate secondary NS for Plesk servers will be difficult to manage. To ease the process, I came up with an idea of using PowerDNS&#8217; supermasters feature.<br />
Just shove in the IP of the Plesk server, the name of the secondary NS and the server name to the supermasters table.<br />
During initial touch-up of the Plesk server, make sure while modifying the DNS zone template to use THAT Plesk server as the first NS record. Otherwise it would cause problem with wrong SOA name causing PowerDNS not recognizing AXFR sent by the Plesk server.<br />
Also make sure PowerDNS IP is included in the allowed list of AXFR on Plesk!</p>
<p align="left">Some useful queries for PowerDNS&#8217; SQL:<br />
delete records.* from records, domains where records.domain_id = domains.id and domains.account = &#8216;SERVERNAME&#8217;;<br />
delete from domains where account = &#8216;SERVERNAME&#8217;;</p>
<p align="left">Valid for Plesk 7.5.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nirkabel.org/2006/01/23/powerdns-with-plesk-servers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Plesk&#8217;s drwebd issue</title>
		<link>http://blog.nirkabel.org/2006/01/23/plesks-drwebd-issue/</link>
		<comments>http://blog.nirkabel.org/2006/01/23/plesks-drwebd-issue/#comments</comments>
		<pubDate>Mon, 23 Jan 2006 17:48:22 +0000</pubDate>
		<dc:creator>Andryan</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Technical]]></category>

		<guid isPermaLink="false">http://andryan.wordpress.com/2006/01/23/plesks-drwebd-issue/</guid>
		<description><![CDATA[If drwebd doesn&#8217;t want to start, with the following error message: Plesk authorization failed: HTTP request error [6] Error: Plesk Software not running. Make sure localhost is resolving correctly to 127.0.0.1. Check /etc/hosts! Valid for Plesk 7.5.]]></description>
			<content:encoded><![CDATA[<p align="left">If drwebd doesn&#8217;t want to start, with the following error message:<br />
Plesk authorization failed: HTTP request error [6]<br />
Error: Plesk Software not running.</p>
<p align="left">Make sure localhost is resolving correctly to 127.0.0.1. Check /etc/hosts!</p>
<p align="left">Valid for Plesk 7.5.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nirkabel.org/2006/01/23/plesks-drwebd-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Urchin for Plesk</title>
		<link>http://blog.nirkabel.org/2006/01/23/urchin-for-plesk/</link>
		<comments>http://blog.nirkabel.org/2006/01/23/urchin-for-plesk/#comments</comments>
		<pubDate>Mon, 23 Jan 2006 17:45:26 +0000</pubDate>
		<dc:creator>Andryan</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[Urchin]]></category>

		<guid isPermaLink="false">http://andryan.wordpress.com/2006/01/23/urchin-for-plesk/</guid>
		<description><![CDATA[In order to get Urchin working for Plesk. It should run as the same user as the apache. http://help.urchin.com/index.cgi?&#38;id=1243 To do this, the template (urchinwebd.conf.template) should be the one that&#8217;s modified, NOT THE REAL ONE (urchinwebd.conf). Lines that need to be modified should look like this: Before: User nobody Group psaserv After: User psaadm Group [...]]]></description>
			<content:encoded><![CDATA[<p align="left">In order to get Urchin working for Plesk. It should run as the same user as the apache.<br />
<a href="http://help.urchin.com/index.cgi?&amp;id=1243" target="_blank">http://help.urchin.com/index.cgi?&amp;id=1243</a><br />
To do this, the template (urchinwebd.conf.template) should be the one that&#8217;s modified, NOT THE REAL ONE (urchinwebd.conf).</p>
<p align="left">Lines that need to be modified should look like this:<br />
Before:<br />
User nobody<br />
Group psaserv</p>
<p align="left">After:<br />
User psaadm<br />
Group psaserv</p>
<p align="left">Valid for Plesk 7.5.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nirkabel.org/2006/01/23/urchin-for-plesk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Passive FTP workaround for Plesk&#8217;s proftpd</title>
		<link>http://blog.nirkabel.org/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/</link>
		<comments>http://blog.nirkabel.org/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/#comments</comments>
		<pubDate>Mon, 23 Jan 2006 17:35:26 +0000</pubDate>
		<dc:creator>Andryan</dc:creator>
				<category><![CDATA[FTP]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Technical]]></category>

		<guid isPermaLink="false">http://andryan.wordpress.com/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/</guid>
		<description><![CDATA[Add the following line: PassivePorts 49152 65534 to /etc/proftpd.conf NOT /etc/proftpd.include as that file will be overwritten by Plesk regularly. No need to restart xinetd (/etc/init.d/xinetd restart) as proftpd is executed only when a connection has been attempted on the port. Add the following line: /sbin/iptables -A INPUT -p tcp &#8211;dport 49152:65534 -j ACCEPT to [...]]]></description>
			<content:encoded><![CDATA[<p align="left">Add the following line:<br />
PassivePorts 49152 65534<br />
to /etc/proftpd.conf<br />
NOT /etc/proftpd.include as that file will be overwritten by Plesk regularly.</p>
<p align="left">No need to restart xinetd (/etc/init.d/xinetd restart) as proftpd is executed only when a connection has been attempted on the port.</p>
<p align="left">Add the following line:<br />
/sbin/iptables -A INPUT -p tcp &#8211;dport 49152:65534 -j ACCEPT<br />
to /usr/local/psa/var/modules/firewall/firewall-active.sh</p>
<p align="left">That&#8217;s all!<br />
Just need to make sure that the last incoming traffic rule is set to deny all.</p>
<p align="left">Valid for Plesk 7.5.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.nirkabel.org/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

