<?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>Status Blog</title>
	<atom:link href="http://henleg.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://henleg.net</link>
	<description></description>
	<lastBuildDate>Sat, 01 Jan 2011 20:10:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>cPanel updated to 11.28.60</title>
		<link>http://henleg.net/2011/01/01/cpanel-updated-to-11-28-60/</link>
		<comments>http://henleg.net/2011/01/01/cpanel-updated-to-11-28-60/#comments</comments>
		<pubDate>Sat, 01 Jan 2011 20:10:14 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[cpanel]]></category>
		<category><![CDATA[maintenance]]></category>
		<category><![CDATA[resolved]]></category>

		<guid isPermaLink="false">http://henleg.net/?p=72</guid>
		<description><![CDATA[All cPanel installations has been updated to version 11.28.60. This version mainly contain bugfixes, but also new features and design improvements. If you have any questions, either leave a comment or email info@henleg.com. Change Log for 11.28.60 cPanel X3 Implemented case 40301: Lazy load the email quota warning data to prevent index.html from blocking when [...]]]></description>
			<content:encoded><![CDATA[<p>All cPanel installations has been updated to version 11.28.60. This version mainly contain bugfixes, but also new features and design improvements.</p>
<p>If you have any questions, either leave a comment or email info@henleg.com.</p>
<h3 class="entry-title">Change Log for 11.28.60</h3>
<h4>cPanel X3</h4>
<ul>
<li> Implemented case 40301: Lazy load the  email quota warning data to prevent index.html from blocking when there  are many email accounts</li>
<li> Implemented case 42766: New Latest Visitors UI</li>
<li> Implemented case 44985: Add &#8220;Refresh&#8221; button to Latest Visitors in 11.28</li>
<li> Implemented case 45048: Tidy up Latest Visitors: remove old CSS, do total bytes in template</li>
<li> Implemented case 45474: HTML / CSS for latest visitors page</li>
<li> Fixed case 45079: Refresh of Latest Visitors does not retain resizing of columns</li>
<li> Fixed case 45425: FTP accounts can&#8217;t be created with underscores/hyphens</li>
<li> Fixed case 45619: Fix Back Ground color on pagination for Latest Visitors</li>
</ul>
<h4>Backend</h4>
<ul>
<li> Implemented case 42766: New Latest Visitors UI</li>
<li> Implemented case 44974: Ability to copy and rename databases in cPanel and WHM</li>
<li> Implemented case 44993: Optimize new latest visitors page</li>
<li> Implemented case 45190: Need an XML/JSON-API call to set the update preferences</li>
<li> Fixed case 43186: Unactivated License Error when network restart on boot takes 5+ seconds</li>
<li> Fixed case 45007: dovecotup replaces /etc/rc.subr on FreeBSD</li>
<li> Fixed case 45235: Output for the updateconfig api call should indicate when &#8216;manual&#8217; is specified</li>
<li> Fixed case 45311: phpMyAdmin session fixation between cPanel accounts (originating from the same browser)</li>
<li> Fixed case 45312: Horde icons are missing text</li>
<li> Fixed case 45393: cPBandwd logs bandwidth we don&#8217;t account for</li>
<li> Fixed case 45435: bin/updatephpmyadmin doesn&#8217;t retain BlowFish secret from previous install</li>
<li> Fixed case 45493: CLI setupsiteip: Root user unable to change IP of account owned by reseller</li>
<li> Fixed case 45497: Cpanel::SafeSync::_synclist appears incompatible with FreeBSD</li>
<li> Fixed case 45537: Fix typo in case 45032 changeset</li>
<li> Fixed case 45607: add parse() method to Cpanel::Template::Plugin::JSON.pm</li>
</ul>
<h4>cPanel JavaScript Toolkit</h4>
<ul>
<li> Implemented case 42766: New Latest Visitors UI</li>
<li> Implemented case 45479: Implement â€œfixed_widthâ€  property in YUI DataTable</li>
<li> Implemented case 45529: need generic helper text overlay for text fields</li>
<li> Fixed case 45557: Text_Input_Helper needs to adjust overlay for border/padding</li>
<li> Fixed case 45598: Search becomes unresponsive on large datasets in Latest Visitors UI</li>
</ul>
<h4>WHM UI</h4>
<ul>
<li> Fixed case 44887: WHM menus no longer remember state since 11.28.39</li>
</ul>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;">
<h2 class="entry-title">11.28.60</h2>
</div>
]]></content:encoded>
			<wfw:commentRss>http://henleg.net/2011/01/01/cpanel-updated-to-11-28-60/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Node 1 scheduled maintenance</title>
		<link>http://henleg.net/2010/12/20/node-1-scheduled-maintenance/</link>
		<comments>http://henleg.net/2010/12/20/node-1-scheduled-maintenance/#comments</comments>
		<pubDate>Mon, 20 Dec 2010 12:08:14 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[maintenance]]></category>
		<category><![CDATA[node 1]]></category>
		<category><![CDATA[resolved]]></category>
		<category><![CDATA[status]]></category>

		<guid isPermaLink="false">http://henleg.net/?p=63</guid>
		<description><![CDATA[There will be a scheduled maintenance made tonight, 2010-12-20 starting at 23.00 GMT+1 The reason for this maintenance is that it has been detected that a hard drive in the raid-array is showing signs of being defective. During the scheduled maintenance window, Node 1 will be taken offline and the defective hard drive will be [...]]]></description>
			<content:encoded><![CDATA[<p>There will be a scheduled maintenance made tonight, 2010-12-20 starting at 23.00 GMT+1</p>
<p>The reason for this maintenance is that it has been detected that a hard drive in the raid-array is showing signs of being defective.</p>
<p>During the scheduled maintenance window, Node 1 will be taken offline and the defective hard drive will be replaced. When Node 1 is started up again, the raid-array will be rebuilt and then services should return to normal.</p>
<p>It will take approximately 30 minutes to change hard drive, and then the raid-array has to be rebuilt. It is hard to say how long the rebuild will take, but there will be at least a maintenance window set for 5 hours. However, it will most likely go faster than that.</p>
<p>Thank you for your understanding.</p>
<p>2010-12-20, 23:34 GMT+1<br />
<strong>UPDATE:</strong> All seem to have gone well. The drive has been replaced, the server is back online and the raid-set is being re-synced. If you have any further questions, email info@henleg.com and a customer service representative will get back to you as soon as possible.</p>
<p>2010-12-21, 11:20 GMT+1<br />
<strong>UPDATE:</strong> The raid-set is synced up and checked.</p>
]]></content:encoded>
			<wfw:commentRss>http://henleg.net/2010/12/20/node-1-scheduled-maintenance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Node 1 issues</title>
		<link>http://henleg.net/2010/11/27/node1-issues/</link>
		<comments>http://henleg.net/2010/11/27/node1-issues/#comments</comments>
		<pubDate>Sat, 27 Nov 2010 10:33:46 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[node 1]]></category>
		<category><![CDATA[resolved]]></category>
		<category><![CDATA[status]]></category>

		<guid isPermaLink="false">http://henleg.net/?p=55</guid>
		<description><![CDATA[Node 1 is not accessible due to an error with it&#8217;s filesystem which has gone into read only mode. The datacenter is informed and working on the issue. When further information comes in, it will be posted here. 2010-11-27, 16:11 GMT+1 UPDATE: Services are restored. We have been working with the datacenter to bring the [...]]]></description>
			<content:encoded><![CDATA[<p>Node 1 is not accessible due to an error with it&#8217;s filesystem which has gone into read only mode. The datacenter is informed and working on the issue. When further information comes in, it will be posted here.</p>
<p>2010-11-27, 16:11 GMT+1<br />
<strong>UPDATE:</strong> Services are restored. We have been working with the datacenter to bring the server back up. All services should be operational. If you have any questions, as always feel free to email info@henleg.com and we&#8217;ll answer them and help you when necessary.</p>
]]></content:encoded>
			<wfw:commentRss>http://henleg.net/2010/11/27/node1-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Further issues with Node 3</title>
		<link>http://henleg.net/2010/10/28/further-issues-with-node-3/</link>
		<comments>http://henleg.net/2010/10/28/further-issues-with-node-3/#comments</comments>
		<pubDate>Thu, 28 Oct 2010 19:39:06 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[node 3]]></category>
		<category><![CDATA[status]]></category>

		<guid isPermaLink="false">http://henleg.net/?p=50</guid>
		<description><![CDATA[There has occurred issues with Node 3. This issue is being investigated and an update will be posted when there is more information to present. Note that migration to a new server is starting during week 44. This new server is located in a better network as well as running cPanel as the control panel. [...]]]></description>
			<content:encoded><![CDATA[<p>There has occurred issues with Node 3. This issue is being investigated and an update will be posted when there is more information to present.</p>
<p>Note that migration to a new server is starting during week 44. This new server is located in a better network as well as running cPanel as the control panel. Further information will be posted on here.</p>
<p>Our deep apologies for the inconvenience this outage may cause.</p>
<p>2010-10-28, 23:05 GMT+1<br />
<strong>UPDATE:</strong> Services are restored. Datacenter confirmed DDOS saturating their up-links to the Internet rending the customers&#8217; servers unable to go online.</p>
]]></content:encoded>
			<wfw:commentRss>http://henleg.net/2010/10/28/further-issues-with-node-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Node 3 issues going on</title>
		<link>http://henleg.net/2010/08/11/node-3-issues-going-on/</link>
		<comments>http://henleg.net/2010/08/11/node-3-issues-going-on/#comments</comments>
		<pubDate>Tue, 10 Aug 2010 22:00:00 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[node 3]]></category>
		<category><![CDATA[status]]></category>

		<guid isPermaLink="false">http://henleg.net/?p=45</guid>
		<description><![CDATA[There is an issue going on with node 3. We are working on a solution for this. There is no estimated time on when the issue will be fixed, keep an eye on this space for further information on progress. Your data is safe and sites will be restored. 2010-08-11, 00:38 GMT+1 UPDATE: Services are [...]]]></description>
			<content:encoded><![CDATA[<p>There is an issue going on with node 3. We are working on a solution for this. There is no estimated time on when the issue will be fixed, keep an eye on this space for further information on progress. Your data is safe and sites will be restored.</p>
<p>2010-08-11, 00:38 GMT+1<strong><br />
UPDATE: </strong>Services are restored, however if you experience more issues please email support@henleg.com. Steps are being taken to avoid downtime similar to this.</p>
]]></content:encoded>
			<wfw:commentRss>http://henleg.net/2010/08/11/node-3-issues-going-on/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Spam Assassin Ruleset 2010 Bug &#8211; Fixed</title>
		<link>http://henleg.net/2010/01/02/spam-assassin-ruleset-2010-bug-fixed/</link>
		<comments>http://henleg.net/2010/01/02/spam-assassin-ruleset-2010-bug-fixed/#comments</comments>
		<pubDate>Sat, 02 Jan 2010 10:58:10 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[email]]></category>
		<category><![CDATA[resolved]]></category>
		<category><![CDATA[status]]></category>

		<guid isPermaLink="false">http://henleg.net/?p=39</guid>
		<description><![CDATA[A Y2k10 bug has been found in the SpamAssassin rules causing an additional 3.2 score to be added in all emails. SpamAssassin is a service that protects your mail inbox against spam / junk-mail / UCE. In order to mitigate this bug, manual intervention is necessary and measures has been taken on all servers/services to [...]]]></description>
			<content:encoded><![CDATA[<p>A Y2k10 bug has been found in the SpamAssassin rules causing an additional 3.2 score to be added in all emails. SpamAssassin is a service that protects your mail inbox against spam / junk-mail / UCE.</p>
<p>In order to mitigate this bug, manual intervention is necessary and measures has been taken on all servers/services to fix this issue.</p>
<p>Reference: <a title="SpamAssassin, SA, bugreport from apache foundation. Email, spam, anti-spam, uce, service, daemon, fixed" href="https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6269">Apache Foundation bugreport</a></p>
]]></content:encoded>
			<wfw:commentRss>http://henleg.net/2010/01/02/spam-assassin-ruleset-2010-bug-fixed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Status-blog downtime</title>
		<link>http://henleg.net/2009/11/06/status-blog-downtime/</link>
		<comments>http://henleg.net/2009/11/06/status-blog-downtime/#comments</comments>
		<pubDate>Fri, 06 Nov 2009 15:58:47 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[resolved]]></category>
		<category><![CDATA[status]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://henleg.net/?p=35</guid>
		<description><![CDATA[This status blog had some downtime due to our provider doing a server migration. The blog is now up and running as it should at the new location however.]]></description>
			<content:encoded><![CDATA[<p>This status blog had some downtime due to our provider doing a server migration. The blog is now up and running as it should at the new location however.</p>
]]></content:encoded>
			<wfw:commentRss>http://henleg.net/2009/11/06/status-blog-downtime/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Network issues with Node 3</title>
		<link>http://henleg.net/2009/03/14/network-issues-with-node-3-2/</link>
		<comments>http://henleg.net/2009/03/14/network-issues-with-node-3-2/#comments</comments>
		<pubDate>Sat, 14 Mar 2009 12:47:11 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[network]]></category>
		<category><![CDATA[node 3]]></category>
		<category><![CDATA[status]]></category>

		<guid isPermaLink="false">http://henleg.net/?p=28</guid>
		<description><![CDATA[Right now there is what looks to be a network issue going on in the datacenter where Node 3 is located. We have contacted the datacenter for further information and will update this post when we have more information to provide for you. We apologize for the inconvenience. 2009-03-14, 13:46 GMT+1 UPDATE: The network seem [...]]]></description>
			<content:encoded><![CDATA[<p>Right now there is what looks to be a network issue going on in the datacenter where Node 3 is located. We have contacted the datacenter for further information and will update this post when we have more information to provide for you.</p>
<p>We apologize for the inconvenience.</p>
<p>2009-03-14, 13:46 GMT+1<strong><br />
UPDATE: </strong>The network seem to have been stabilized now. If you experience any issues apart from what is posted above, please email support@henleg.com</p>
<p>2009-03-14, 14:46 GMT+1<strong><br />
UPDATE: </strong>There are still some lingering network issues to certain locations, we do know that the datacenter is working on it. We have not received an ETA on when this issue will be totally over, but it shouldn&#8217;t take too much time. Once again we apologize for any inconvenience this might have caused you. We will keep this post updated as we get to know more.</p>
<p>2009-03-14, 15:10 GMT+1<strong><br />
</strong><strong>UPDATE: </strong>Network connectivity seems to have been restored to <span style="text-decoration: underline;">all</span> locations now. We&#8217;ll update this post as further information comes in. Naturally, getting the network up and running is the biggest priority for the technicians on site at the datacenter and a RFO (Reason For Outage) takes lower priority. To verify the server status from different locations than your own, go to <a title="uptime status check host tracker hosttracker host-tracker ajax monitoring" href="http://host-tracker.com">http://host-tracker.com</a> and put in your website&#8217;s full domain name there. Also see the <a title="pingdom server status check henleg.com henleg.net node 3" href="http://www.pingdom.com/reports/gsp9lyjn948q/check_overview/?name=Node+3">Pingdom Status page</a> for Node 3 to see if there are any issues currently. If you have any questions, please email support@henleg.com and your inquiry will be answered as soon as possible.</p>
]]></content:encoded>
			<wfw:commentRss>http://henleg.net/2009/03/14/network-issues-with-node-3-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Node 2: Issues with web server</title>
		<link>http://henleg.net/2009/03/03/node-2-issues-with-web-server/</link>
		<comments>http://henleg.net/2009/03/03/node-2-issues-with-web-server/#comments</comments>
		<pubDate>Tue, 03 Mar 2009 21:18:34 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[node 2]]></category>
		<category><![CDATA[resolved]]></category>
		<category><![CDATA[status]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://henleg.net/?p=24</guid>
		<description><![CDATA[Right now there is an issue opened due to an update of the software PHP used on Node 2 going wrong. We are working on the issue and will update this blog post when the issue at hand is solved. Thank you for your patience. 2009-03-03, 22:28 GMT+1 UPDATE: The web server is now functioning [...]]]></description>
			<content:encoded><![CDATA[<p>Right now there is an issue opened due to an update of the software PHP used on Node 2 going wrong. We are working on the issue and will update this blog post when the issue at hand is solved.</p>
<p>Thank you for your patience.</p>
<p>2009-03-03, 22:28 GMT+1<br />
<strong>UPDATE: </strong>The web server is now functioning normally. If you experience any errors apart from this, please email support@henleg.com</p>
]]></content:encoded>
			<wfw:commentRss>http://henleg.net/2009/03/03/node-2-issues-with-web-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Network issues with Node 3</title>
		<link>http://henleg.net/2009/02/13/network-issues-with-node-3/</link>
		<comments>http://henleg.net/2009/02/13/network-issues-with-node-3/#comments</comments>
		<pubDate>Fri, 13 Feb 2009 18:37:07 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[network]]></category>
		<category><![CDATA[node 3]]></category>
		<category><![CDATA[resolved]]></category>
		<category><![CDATA[status]]></category>

		<guid isPermaLink="false">http://henleg.net/?p=19</guid>
		<description><![CDATA[There is currently a network issue going on at the Datacenter where Node 3 is located. When this is fixed, this post will be updated. We apologize for any inconvenience this has caused. 2009-02-13, 21:42 GMT+1 UPDATE: The reason to this outage was a so called DDOS attack against the Datacenter where Node 3 is [...]]]></description>
			<content:encoded><![CDATA[<p>There is currently a network issue going on at the Datacenter where Node 3 is located. When this is fixed, this post will be updated.</p>
<p>We apologize for any inconvenience this has caused.</p>
<p>2009-02-13, 21:42 GMT+1<br />
<strong>UPDATE: </strong>The reason to this outage was a so called <a title="ddos attack distributed denial of service wikipedia explanation what is definition resolved" href="http://en.wikipedia.org/wiki/Denial-of-service_attack">DDOS</a> attack against the Datacenter where Node 3 is located in. The issue is now labelled as resolved. Thank you for your patience</p>
]]></content:encoded>
			<wfw:commentRss>http://henleg.net/2009/02/13/network-issues-with-node-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

