<?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> &#187; Plesk Error</title>
	<atom:link href="http://eitwebguru.com/tag/plesk-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://eitwebguru.com</link>
	<description></description>
	<lastBuildDate>Thu, 09 Feb 2012 05:54:15 +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>Unable to Access Plesk &#8211; PSA dead but subsys locked</title>
		<link>http://eitwebguru.com/unable-to-access-plesk-psa-dead-but-subsys-locked/</link>
		<comments>http://eitwebguru.com/unable-to-access-plesk-psa-dead-but-subsys-locked/#comments</comments>
		<pubDate>Wed, 19 Oct 2011 00:12:07 +0000</pubDate>
		<dc:creator>Milind</dc:creator>
				<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Plesk For Linux]]></category>
		<category><![CDATA[Plesk Apache Configuration]]></category>
		<category><![CDATA[Plesk Error]]></category>
		<category><![CDATA[Plesk Error log file]]></category>

		<guid isPermaLink="false">http://eitwebguru.com/?p=736</guid>
		<description><![CDATA[Recently we faced a problem where Plesk was not accessible over Internet i.e. using port 8443 (https) and 8880 (normal). The first thing we checked was the Firewall; it happens sometime that the problem might be with firewall which was blocking port 8443 and 8880 but there was no problem with Firewall. Then we tried [...]]]></description>
			<content:encoded><![CDATA[<!-- google_ad_section_start --><p style="text-align: justify;"><span style="font-family: Verdana; font-size: small;">Recently we faced a problem where Plesk was not accessible over Internet i.e. using port <strong>8443 (https)</strong> and <strong>8880 (normal)</strong>. The first thing we checked was the Firewall; it happens sometime that the problem might be with firewall which was blocking port 8443 and 8880 but there was no problem with Firewall. Then we tried to check the status of Plesk (PSA) Service and got following response</span></p>
<div style="background: url(/wp-content/themes/notepad_second/images/pre_code_bg_blk.png) repeat-y scroll 0% 0% transparent; width: 490px; height: 40px; overflow: auto; line-height: 20px; padding: 20px; font-family: Courier New; font-size: small; color: #ffffff;">[root@server ~]# /etc/init.d/psa status<br /> psa dead but subsys locked</div>
<p><span style="font-family: Verdana; font-size: small;"><br />While checking for logs (Plesk Logs) on <strong>/usr/local/psa/admin/logs/error_log</strong> it was showing following Messages</span></p>
<div style="background: url(/wp-content/themes/notepad_second/images/pre_code_bg_blk.png) repeat-y scroll 0% 0% transparent; width: 490px; height: 40px; overflow: auto; line-height: 20px; padding: 20px; font-family: Courier New; font-size: small; color: #ffffff;">[crit] (98)Address already in use: make_sock: could not bind to port 80</div>
<p><span style="font-family: Verdana; font-size: small;"><br />Now we have used command &#8220;<strong>/usr/sbin/lsof -i | grep http</strong>&#8221; (without quotes) and then killed the process using the ID. After that we have removed the Plesk Lock</span></p>
<div style="background: url(/wp-content/themes/notepad_second/images/pre_code_bg_blk.png) repeat-y scroll 0% 0% transparent; width: 490px; height: 40px; overflow: auto; line-height: 20px; padding: 20px; font-family: Courier New; font-size: small; color: #ffffff;">[root@server ~]# rm -f /var/lock/subsys/psa</div>
<p style="text-align: justify;"><span style="font-family: Verdana; font-size: small;"><br />But starting Plesk service didn&#8217;t fixed the problem. Still we were getting &#8220;<strong>could not bind to port 80</strong>&#8221; Error.</span></p>
<p style="text-align: justify;"><span style="font-family: Verdana; font-size: small;">Now we have opened Plesk Apache Configuration file which include Apache (Web Server) Configuration of Plesk Control Panel.</span></p>
<div style="background: url(/wp-content/themes/notepad_second/images/pre_code_bg_blk.png) repeat-y scroll 0% 0% transparent; width: 490px; height: 20px; overflow: auto; line-height: 20px; padding: 20px; font-family: Courier New; font-size: small; color: #ffffff;">[root@vps ~]# vi /usr/local/psa/admin/conf/httpsd.conf</div>
<p style="text-align: justify;"><span style="font-family: Verdana; font-size: small;"><br />and found that the User has changed the Plesk Port and set it to listen on port 80 which is default port of HTTPD</span></p>
<div style="background: url(/wp-content/themes/notepad_second/images/pre_code_bg_blk.png) repeat-y scroll 0% 0% transparent; width: 490px; height: 200px; overflow: auto; line-height: 20px; padding: 20px; font-family: Courier New; font-size: small; color: #ffffff;"># Listen: Allows you to bind Apache to specific IP addresses and/or<br /> # ports, in addition to the default. See also the <br /> # directive.<br /> #<br /> #Listen 3000<br /> #Listen 12.34.56.78:80<br /> #Listen 8443<br /> #Listen 8880<br /> Listen 80</div>
<p><span style="font-family: Verdana; font-size: small;"><br />So, we have made necessary changes <strong>httpsd.conf</strong> file i.e. disabled Port 80 and allowed 8443 and 8880 in Plesk Apache Configuration and restart PSA.</span></p>
<div style="background: url(/wp-content/themes/notepad_second/images/pre_code_bg_blk.png) repeat-y scroll 0% 0% transparent; width: 490px; height: 240px; overflow: auto; line-height: 20px; padding: 20px; font-family: Courier New; font-size: small; color: #ffffff;">[root@vps ~]# /etc/init.d/psa start<br /> Starting xinetd service&#8230;                                            done<br /> Starting named service&#8230;                                             done<br /> Starting mysqld service&#8230;                                            done<br /> Starting qmail service&#8230;                                             done<br /> Starting courier-imap service&#8230;                                      done<br /> Starting postgresql service&#8230;                                        done<br /> Starting psa-spamassassin service&#8230;                                  done<br /> Starting Plesk&#8230;                                                     done<br /> Starting drwebd service&#8230;                                            done<br /> [root@vps ~]# /etc/init.d/psa status<br /> httpsd (pid 1553 1529 1497 1492) is running&#8230;</div>
<p style="text-align: justify;"><span style="font-family: Verdana; font-size: small;"><strong><br />NOTE:-</strong> Here the problem was with Plesk Apache configuration but there might be some different problems too. I have posted this fix which will help to understand Plesk Error Log file and Plesk Apache Configuration files. If any of the USER face different problem and knows the FIX Let me know through Contact form I will be happy to post here.</span></p>
<!-- google_ad_section_end -->]]></content:encoded>
			<wfw:commentRss>http://eitwebguru.com/unable-to-access-plesk-psa-dead-but-subsys-locked/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>FIX: Unable to get type of handler</title>
		<link>http://eitwebguru.com/fix-unable-to-get-type-of-handler/</link>
		<comments>http://eitwebguru.com/fix-unable-to-get-type-of-handler/#comments</comments>
		<pubDate>Sun, 16 Oct 2011 23:40:31 +0000</pubDate>
		<dc:creator>Milind</dc:creator>
				<category><![CDATA[Plesk]]></category>
		<category><![CDATA[Plesk For Linux]]></category>
		<category><![CDATA[Domain rename Error]]></category>
		<category><![CDATA[handler-type]]></category>
		<category><![CDATA[Plesk Error]]></category>
		<category><![CDATA[Unable to get type of handle]]></category>

		<guid isPermaLink="false">http://eitwebguru.com/?p=27</guid>
		<description><![CDATA[Recently while changing the name of a domain from Plesk (Linux) it thrown following Error: No such parameter 'handler-type' for handler '10-spam-MVquwk' Unable to get type of handler: 10-spam-MVquwk No such parameter 'handler-type' for handler '10-spam-LztqGr' Unable to get type of handler: 10-spam-LztqGr The problem is due to orphaned handlers in /usr/local/psa/handlers Directory. Whenever a [...]]]></description>
			<content:encoded><![CDATA[<!-- google_ad_section_start --><p align="justify"><span style="font-family: Verdana; font-size: small;">Recently while changing the name of a domain from Plesk (Linux) it thrown following Error:</span></p>
<pre style="border: 1px inset; margin: 0px; padding: 6px; overflow: auto; width: 490px; height: 85px; text-align: justify; font-family: Verdana; font-size: small;" dir="ltr"><strong><span style="color: #ff6600;">No such parameter 'handler-type' for handler '10-spam-MVquwk'
Unable to get type of handler: 10-spam-MVquwk

No such parameter 'handler-type' for handler '10-spam-LztqGr'
Unable to get type of handler: 10-spam-LztqGr</span></strong></pre>
<p align="justify"><span style="font-family: Verdana; font-size: small;">The problem is due to orphaned handlers in /usr/local/psa/handlers Directory. Whenever a domain name has been changed whole mail handler system is checked by Plesk. We have created handler directory copy in /usr/local/psa/handlers.copy and removed problem handlers manually. Then executed mail reconfiguration utility:</span></p>
<pre style="border: 1px inset; margin: 0px; padding: 6px; overflow: auto; width: 490px; height: 150px; text-align: justify; font-family: Verdana; font-size: small;" dir="ltr"><strong># /usr/local/psa/admin/sbin/mchk --with-spam
==&gt; Checking for: mail_spam_restore... ok
==&gt; Checking for: mailsrv_conf_init... ok
==&gt; Checking for: mail_mailbox_restore... ok
==&gt; Checking for: mailsrv_entities_dump... ok
==&gt; Checking for: mail_auth_dump... ok
==&gt; Checking for: mailman_lists_dump... ok
==&gt; Checking for: mail_responder_restore... ok
==&gt; Checking for: mail_drweb_restore... ok
==&gt; Checking for: mail_kav_restore... not exsists
==&gt; Checking for: mail_spf_restore... ok
==&gt; Checking for: mail_dk_restore... ok</strong></pre>
<p align="justify"><span style="font-family: Verdana; font-size: small;">After this we were able to rename the domain successfully:</span></p>
<pre style="border: 1px inset; margin: 0px; padding: 6px; overflow: auto; width: 490px; height: 50px; text-align: justify; font-family: Verdana; font-size: small;" dir="ltr"><strong># /usr/local/psa/bin/domain --update supportest123.com -new_name 123testsupport.com
SUCCESS: Update of domain 'supportest123.com' complete.</strong></pre>
<p align="justify"><span style="font-family: Verdana; font-size: small;">If the any problem noted due to the removal of Email Handlers, changes can be reverted using the backup directory which has been created before clearing handlers.</span></p>
<!-- google_ad_section_end -->]]></content:encoded>
			<wfw:commentRss>http://eitwebguru.com/fix-unable-to-get-type-of-handler/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

