<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.1.3" -->
<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/"
	>

<channel>
	<title>ThinkSupport.net - 24/7 Webhosting Support, Software support, Ticket support, Live Chat Support, Server Management, FFMPEG &#124; PHPMOTION &#124; CLIPSHARE &#124; RAYZZ &#124; VSHARE &#124; OSTUBE INSTALLATION</title>
	<link>http://thinksupport.net/blog</link>
	<description>24/7 Outsourced WebHosting Support</description>
	<pubDate>Tue, 19 Aug 2008 06:31:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>
	<language>en</language>
			<item>
		<title>Apache - Address already in use: make_sock: could not bind to address</title>
		<link>http://thinksupport.net/blog/apache-address-already-in-use-make_sock-could-not-bind-to-address.html</link>
		<comments>http://thinksupport.net/blog/apache-address-already-in-use-make_sock-could-not-bind-to-address.html#comments</comments>
		<pubDate>Tue, 19 Aug 2008 06:31:21 +0000</pubDate>
		<dc:creator>Sachin</dc:creator>
		
		<category><![CDATA[WHM/cPanel]]></category>

		<category><![CDATA[Linux]]></category>

		<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://thinksupport.net/blog/apache-address-already-in-use-make_sock-could-not-bind-to-address.html</guid>
		<description><![CDATA[This error message can be caused by an improper shut down, the apache processes are still hanging around and apachectl restart won&#8217;t work.
Solution
just kill off the hanging processes:
# fuser 80/tcp
80/tcp: 3010 3702 4088 16754
# kill -n 9 3010
# kill -n 9 3702
# kill -n 9 4088
# kill -n 9 16754
# apachectl start
or if there&#8217;s loads [...]]]></description>
			<content:encoded><![CDATA[<p>This error message can be caused by an improper shut down, the apache processes are still hanging around and apachectl restart won&#8217;t work.</p>
<p><strong>Solution</strong></p>
<p>just kill off the hanging processes:<br />
# fuser 80/tcp<br />
80/tcp: 3010 3702 4088 16754<br />
# kill -n 9 3010<br />
# kill -n 9 3702<br />
# kill -n 9 4088<br />
# kill -n 9 16754<br />
# apachectl start</p>
<p>or if there&#8217;s loads of processes use<br />
# for i in $(fuser 80/tcp);do kill -n 9 $i;done<br />
to kill them all off</p>
]]></content:encoded>
			<wfw:commentRss>http://thinksupport.net/blog/apache-address-already-in-use-make_sock-could-not-bind-to-address.html/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Move domain between clients in Plesk</title>
		<link>http://thinksupport.net/blog/move-domain-between-clients-in-plesk.html</link>
		<comments>http://thinksupport.net/blog/move-domain-between-clients-in-plesk.html#comments</comments>
		<pubDate>Tue, 13 May 2008 18:24:47 +0000</pubDate>
		<dc:creator>Sunil</dc:creator>
		
		<category><![CDATA[Plesk]]></category>

		<guid isPermaLink="false">http://thinksupport.net/blog/move-domain-between-clients-in-plesk.html</guid>
		<description><![CDATA[Moving domains from client to client in Plesk is pretty quick from the command line. Just replace DOMAIN with the domain name you want to move and CLIENTLOGIN with the client’s username:
 /usr/local/psa/bin/domain.sh --update DOMAIN -clogin CLIENTLOGIN
]]></description>
			<content:encoded><![CDATA[<p>Moving domains from client to client in Plesk is pretty quick from the command line. Just replace DOMAIN with the domain name you want to move and CLIENTLOGIN with the client’s username:</p>
<p><strong><code> /usr/local/psa/bin/domain.sh --update DOMAIN -clogin CLIENTLOGIN</code></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://thinksupport.net/blog/move-domain-between-clients-in-plesk.html/feed/</wfw:commentRss>
		</item>
		<item>
		<title>AWStats icons don’t appear in Plesk</title>
		<link>http://thinksupport.net/blog/awstats-icons-don%e2%80%99t-appear-in-plesk.html</link>
		<comments>http://thinksupport.net/blog/awstats-icons-don%e2%80%99t-appear-in-plesk.html#comments</comments>
		<pubDate>Tue, 13 May 2008 14:08:26 +0000</pubDate>
		<dc:creator>Sunil</dc:creator>
		
		<category><![CDATA[Plesk]]></category>

		<guid isPermaLink="false">http://thinksupport.net/blog/awstats-icons-don%e2%80%99t-appear-in-plesk.html</guid>
		<description><![CDATA[The AWStats package in RHEL4/Centos4 and Plesk 8.1 uses an alias directory for the icons called /awstats-icon, but when the AWStats contents is generated, the icon directory is different (/icon). To fix this issue, change this file:
/usr/share/awstats/awstats_buildstaticpages.pl
my $DirIcons='/awstats-icon';
]]></description>
			<content:encoded><![CDATA[<p>The AWStats package in RHEL4/Centos4 and Plesk 8.1 uses an alias directory for the icons called /awstats-icon, but when the AWStats contents is generated, the icon directory is different (/icon). To fix this issue, change this file:</p>
<p><strong>/usr/share/awstats/awstats_buildstaticpages.pl</strong></p>
<p><code>my $DirIcons='/awstats-icon';</code></p>
]]></content:encoded>
			<wfw:commentRss>http://thinksupport.net/blog/awstats-icons-don%e2%80%99t-appear-in-plesk.html/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Can’t find file: ‘horde_sessionhandler.MYI’ in Plesk</title>
		<link>http://thinksupport.net/blog/can%e2%80%99t-find-file-%e2%80%98horde_sessionhandlermyi%e2%80%99-in-plesk.html</link>
		<comments>http://thinksupport.net/blog/can%e2%80%99t-find-file-%e2%80%98horde_sessionhandlermyi%e2%80%99-in-plesk.html#comments</comments>
		<pubDate>Tue, 13 May 2008 13:58:05 +0000</pubDate>
		<dc:creator>Sunil</dc:creator>
		
		<category><![CDATA[Plesk]]></category>

		<guid isPermaLink="false">http://thinksupport.net/blog/can%e2%80%99t-find-file-%e2%80%98horde_sessionhandlermyi%e2%80%99-in-plesk.html</guid>
		<description><![CDATA[If you get this error, you’ve most likely done a file-based MySQL backup restore, and the InnoDB files are hosed. The horde_sessionhandler table isn’t a MyISAM table at all - it’s actually an InnoDB table. The easiest way to fix the issue is to stop MySQL and trash the .frm:
# /etc/init.d/mysqld stop
# rm /var/lib/mysql/horde/horde_sessionhandler.frm
Now start [...]]]></description>
			<content:encoded><![CDATA[<p>If you get this error, you’ve most likely done a file-based MySQL backup restore, and the InnoDB files are hosed. The horde_sessionhandler table isn’t a MyISAM table at all - it’s actually an InnoDB table. The easiest way to fix the issue is to stop MySQL and trash the .frm:</p>
<p><strong><code># /etc/init.d/mysqld stop<br />
# rm /var/lib/mysql/horde/horde_sessionhandler.frm</code></strong></p>
<p>Now start MySQL and re-create the table:</p>
<p><strong><code># /etc/init.d/mysqld start<br />
# mysql -u admin -p`cat /etc/psa/.psa.shadow`</code></strong></p>
<p>Here’s the SQL statements to run:</p>
<p><strong><code>CREATE TABLE horde_sessionhandler (session_id VARCHAR(32) NOT NULL, session_lastmodified INT NOT NULL, session_data LONGBLOB, PRIMARY KEY (session_id)) ENGINE = InnoDB;<br />
GRANT SELECT, INSERT, UPDATE, DELETE ON horde_sessionhandler TO horde@localhost;</code></strong></p>
<p>You’re good to go!</p>
]]></content:encoded>
			<wfw:commentRss>http://thinksupport.net/blog/can%e2%80%99t-find-file-%e2%80%98horde_sessionhandlermyi%e2%80%99-in-plesk.html/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Add SPF records to all domains in Plesk</title>
		<link>http://thinksupport.net/blog/add-spf-records-to-all-domains-in-plesk.html</link>
		<comments>http://thinksupport.net/blog/add-spf-records-to-all-domains-in-plesk.html#comments</comments>
		<pubDate>Tue, 13 May 2008 13:57:26 +0000</pubDate>
		<dc:creator>Sunil</dc:creator>
		
		<category><![CDATA[Plesk]]></category>

		<guid isPermaLink="false">http://thinksupport.net/blog/add-spf-records-to-all-domains-in-plesk.html</guid>
		<description><![CDATA[
If you find yourself in the situation where you need to bulk add SPF records to every domain in Plesk, you can use this huge one-liner:
mysql -u admin -p`cat /etc/psa/.psa.shadow` psa -e &#8220;select dns_zone_id,displayHost from dns_recs GROUP BY dns_zone_id ORDER BY dns_zone_id ASC;&#8221; &#124; awk &#8216;{print &#8220;INSERT INTO dns_recs (type,host,val,time_stamp,dns_zone_id,displayHost,displayVal) VALUES (&#8217;\&#8221;TXT&#8217;\&#8221;,&#8217;\&#8221;&#8221;$2&#8243;&#8216;\&#8221;,&#8217;\&#8221;v=spf1 a mx ~all&#8217;\&#8221;,NOW(),&#8221;$1&#8243;,&#8217;\&#8221;&#8221;$2&#8243;&#8216;\&#8221;,&#8217;\&#8221;v=spf1 [...]]]></description>
			<content:encoded><![CDATA[<p>
If you find yourself in the situation where you need to bulk add SPF records to every domain in Plesk, you can use this huge one-liner:</p>
<p><strong>mysql -u admin -p`cat /etc/psa/.psa.shadow` psa -e &#8220;select dns_zone_id,displayHost from dns_recs GROUP BY dns_zone_id ORDER BY dns_zone_id ASC;&#8221; | awk &#8216;{print &#8220;INSERT INTO dns_recs (type,host,val,time_stamp,dns_zone_id,displayHost,displayVal) VALUES (&#8217;\&#8221;TXT&#8217;\&#8221;,&#8217;\&#8221;&#8221;$2&#8243;&#8216;\&#8221;,&#8217;\&#8221;v=spf1 a mx ~all&#8217;\&#8221;,NOW(),&#8221;$1&#8243;,&#8217;\&#8221;&#8221;$2&#8243;&#8216;\&#8221;,&#8217;\&#8221;v=spf1 a mx ~all&#8217;\&#8221;);&#8221;}&#8217; | mysql -u admin -p`cat /etc/psa/.psa.shadow` psa</strong></p>
<p>Then you’ll need to make Plesk write these changes to the zone files:</p>
<p># <strong>mysql -Ns -uadmin -p`cat /etc/psa/.psa.shadow` -D psa -e &#8217;select name from domains&#8217; | awk &#8216;{print &#8220;/usr/local/psa/admin/sbin/dnsmng update &#8221; $1 }&#8217; | sh</strong></p>
<p>You can check your work by viewing the new entries you made:</p>
<p><strong>mysql -u admin -p`cat /etc/psa/.psa.shadow` psa -e &#8220;SELECT * FROM dns_recs WHERE type=&#8217;TXT&#8217;;&#8221;</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://thinksupport.net/blog/add-spf-records-to-all-domains-in-plesk.html/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Horde refreshes when logging in</title>
		<link>http://thinksupport.net/blog/horde-refreshes-when-logging-in.html</link>
		<comments>http://thinksupport.net/blog/horde-refreshes-when-logging-in.html#comments</comments>
		<pubDate>Tue, 13 May 2008 13:49:53 +0000</pubDate>
		<dc:creator>Sunil</dc:creator>
		
		<category><![CDATA[Plesk]]></category>

		<guid isPermaLink="false">http://thinksupport.net/blog/horde-refreshes-when-logging-in.html</guid>
		<description><![CDATA[If you find that Horde (with Plesk) keeps refreshing when you attempt to log in, and there are no errors logged on the screen or in Apache’s logs, check the session.auto_start variable in /etc/php.ini.
If session.auto_start is set to 1, set it to 0 and Horde will miraculously start working again.
]]></description>
			<content:encoded><![CDATA[<p>If you find that Horde (with Plesk) keeps refreshing when you attempt to log in, and there are no errors logged on the screen or in Apache’s logs, check the session.auto_start variable in /etc/php.ini.</p>
<p>If<strong> session.auto_start is set</strong> to 1, set it to 0 and Horde will miraculously start working again.</p>
]]></content:encoded>
			<wfw:commentRss>http://thinksupport.net/blog/horde-refreshes-when-logging-in.html/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Remove all open_basedir restrictions in Plesk</title>
		<link>http://thinksupport.net/blog/remove-all-open_basedir-restrictions-in-plesk.html</link>
		<comments>http://thinksupport.net/blog/remove-all-open_basedir-restrictions-in-plesk.html#comments</comments>
		<pubDate>Tue, 13 May 2008 13:47:18 +0000</pubDate>
		<dc:creator>Sunil</dc:creator>
		
		<category><![CDATA[Plesk]]></category>

		<guid isPermaLink="false">http://thinksupport.net/blog/remove-all-open_basedir-restrictions-in-plesk.html</guid>
		<description><![CDATA[If you have an open_basedir restriction that is causing issues with a domain, you can remove the restriction easily. First, put the following text in /home/httpd/vhosts/[domain]/conf/vhost.conf:
&#60;Directory /home/httpd/vhosts/[domain]/httpdocs&#62;
php_admin_value open_basedir none
&#60;/Directory&#62;
If there was already a vhost.conf in the directory, then just reload Apache. Otherwise, run the magic wand:
/usr/local/psa/admin/bin/websrvmng -av
Then reload Apache:
/etc/init.d/httpd reload
]]></description>
			<content:encoded><![CDATA[<p>If you have an open_basedir restriction that is causing issues with a domain, you can remove the restriction easily. First, put the following text in /home/httpd/vhosts/[domain]/conf/vhost.conf:</p>
<p><strong>&lt;Directory /home/httpd/vhosts/[domain]/httpdocs&gt;<br />
php_admin_value open_basedir none<br />
&lt;/Directory&gt;</strong></p>
<p>If there was already a vhost.conf in the directory, then just reload Apache. Otherwise, run the magic wand:</p>
<p>/usr/local/psa/admin/bin/websrvmng -av</p>
<p>Then reload Apache:</p>
<p>/etc/init.d/httpd reload</p>
]]></content:encoded>
			<wfw:commentRss>http://thinksupport.net/blog/remove-all-open_basedir-restrictions-in-plesk.html/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Plesk and PHPMyAdmin: Non-static method PMA_Config::isHttps() should not be called statically</title>
		<link>http://thinksupport.net/blog/plesk-and-phpmyadmin-non-static-method-pma_configishttps-should-not-be-called-statically.html</link>
		<comments>http://thinksupport.net/blog/plesk-and-phpmyadmin-non-static-method-pma_configishttps-should-not-be-called-statically.html#comments</comments>
		<pubDate>Tue, 13 May 2008 13:46:37 +0000</pubDate>
		<dc:creator>Sunil</dc:creator>
		
		<category><![CDATA[Plesk]]></category>

		<guid isPermaLink="false">http://thinksupport.net/blog/plesk-and-phpmyadmin-non-static-method-pma_configishttps-should-not-be-called-statically.html</guid>
		<description><![CDATA[If this situation pops up in Plesk, it means that a user has changed their MySQL password outside of Plesk. The password in Plesk’s own database does not match, so the auto-creation of the phpMyAdmin settings fails. You’ll end up seeing this after clicking “DB WebAdmin”:
MySQL said:    Non-static method PMA_Config::isHttps() should not [...]]]></description>
			<content:encoded><![CDATA[<p>If this situation pops up in Plesk, it means that a user has changed their MySQL password outside of Plesk. The password in Plesk’s own database does not match, so the auto-creation of the phpMyAdmin settings fails. You’ll end up seeing this after clicking “DB WebAdmin”:</p>
<p><strong>MySQL said:    Non-static method PMA_Config::isHttps() should not be called statically</strong></p>
<p>The funny thing is that MySQL doesn’t actually say this. It’s a PHP error. To correct the problem, you can manually change the password within Plesk’s database, or you can follow an easier method:</p>
<p>Click Databases<br />
Click Database Users<br />
Click the user that has a password change<br />
In the password fields, enter the new password that they’re using with MySQL</p>
<p>This will force Plesk to change its password in its own database, and it will run the query to change the password in MySQL (but since it’s the same password, no change will be made).</p>
]]></content:encoded>
			<wfw:commentRss>http://thinksupport.net/blog/plesk-and-phpmyadmin-non-static-method-pma_configishttps-should-not-be-called-statically.html/feed/</wfw:commentRss>
		</item>
		<item>
		<title>mchk: Unable to initialize quota settings for someuser@somedomain.com</title>
		<link>http://thinksupport.net/blog/mchk-unable-to-initialize-quota-settings-for-someusersomedomaincom.html</link>
		<comments>http://thinksupport.net/blog/mchk-unable-to-initialize-quota-settings-for-someusersomedomaincom.html#comments</comments>
		<pubDate>Tue, 13 May 2008 13:40:59 +0000</pubDate>
		<dc:creator>Sunil</dc:creator>
		
		<category><![CDATA[Plesk]]></category>

		<guid isPermaLink="false">http://thinksupport.net/blog/mchk-unable-to-initialize-quota-settings-for-someusersomedomaincom.html</guid>
		<description><![CDATA[If you’re working in Plesk and you receive this error:
mchk: Unable to initialize quota settings for someuser@somedomain.com
Run this command to fix the issue, but be patient:
find /var/qmail/mailnames -type d -name '.*' ! -name '.spamassassin' -ls -exec touch '{}'/maildirfolder \; -exec chown popuser:popuser '{}'/maildirfolder \;
]]></description>
			<content:encoded><![CDATA[<p>If you’re working in Plesk and you receive this error:</p>
<p><strong>mchk: Unable to initialize quota settings for someuser@somedomain.com</strong></p>
<p>Run this command to fix the issue, but be patient:</p>
<p><strong><code>find /var/qmail/mailnames -type d -name '.*' ! -name '.spamassassin' -ls -exec touch '{}'/maildirfolder \; -exec chown popuser:popuser '{}'/maildirfolder \;</code></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://thinksupport.net/blog/mchk-unable-to-initialize-quota-settings-for-someusersomedomaincom.html/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Missing HOMEMATCH Config error while creating accounts.</title>
		<link>http://thinksupport.net/blog/missing-homematch-config-error-while-creating-accounts.html</link>
		<comments>http://thinksupport.net/blog/missing-homematch-config-error-while-creating-accounts.html#comments</comments>
		<pubDate>Tue, 13 May 2008 13:29:54 +0000</pubDate>
		<dc:creator>Sunil</dc:creator>
		
		<category><![CDATA[WHM/cPanel]]></category>

		<guid isPermaLink="false">http://thinksupport.net/blog/missing-homematch-config-error-while-creating-accounts.html</guid>
		<description><![CDATA[When creating or restoring a account i get the following error.
Missing HOMEMATCH Config Line in /etc/wwwacct.conf
Solution:
Steps to correct problem.
1. Log into the WHM as root (not a reseller)
2. Click &#8216;Basic cPanel/WHM Setup&#8217;
3. Scroll down to &#8216;Home Directory Prefix&#8217;, and put /home in the text-field.
4. Scroll down and click save
That&#8217;s it, now try to create or [...]]]></description>
			<content:encoded><![CDATA[<p>When creating or restoring a account i get the following error.</p>
<p><strong>Missing HOMEMATCH Config Line in /etc/wwwacct.conf</strong></p>
<p><strong>Solution:</strong></p>
<p>Steps to correct problem.<br />
1. Log into the WHM as root (not a reseller)<br />
2. Click &#8216;Basic cPanel/WHM Setup&#8217;<br />
3. Scroll down to &#8216;Home Directory Prefix&#8217;, and put /home in the text-field.<br />
4. Scroll down and click save</p>
<p>That&#8217;s it, now try to create or restore a account.</p>
]]></content:encoded>
			<wfw:commentRss>http://thinksupport.net/blog/missing-homematch-config-error-while-creating-accounts.html/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
