<?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>H&#039;s Blog</title>
	<atom:link href="http://www.hpaschke.de/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hpaschke.de/blog</link>
	<description>A good shell is the best user interface.</description>
	<lastBuildDate>Thu, 26 Apr 2012 22:37:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Precise Pangolin</title>
		<link>http://www.hpaschke.de/blog/2012/04/precise-pangolin/</link>
		<comments>http://www.hpaschke.de/blog/2012/04/precise-pangolin/#comments</comments>
		<pubDate>Thu, 26 Apr 2012 22:37:18 +0000</pubDate>
		<dc:creator>Holger</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.hpaschke.de/blog/?p=365</guid>
		<description><![CDATA[The next LTS release of Ubuntu is ready for download. I really like the long-term releases, even more, if they are so fresh, that they provide the latest packages.]]></description>
			<content:encoded><![CDATA[<p>The next LTS release of Ubuntu is ready for download.</p>
<p>I really like the long-term releases, even more, if they are so fresh, that they provide the latest packages.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hpaschke.de/blog/2012/04/precise-pangolin/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SNMP Warnings in Debian Squeeze</title>
		<link>http://www.hpaschke.de/blog/2012/04/snmp-warnings-in-debian-squeeze/</link>
		<comments>http://www.hpaschke.de/blog/2012/04/snmp-warnings-in-debian-squeeze/#comments</comments>
		<pubDate>Thu, 19 Apr 2012 21:16:02 +0000</pubDate>
		<dc:creator>Holger</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[monitoring]]></category>
		<category><![CDATA[snmp]]></category>
		<category><![CDATA[Squeeze]]></category>

		<guid isPermaLink="false">http://www.hpaschke.de/blog/?p=361</guid>
		<description><![CDATA[The default installation of snmpd in Debian Squeeze will put several warnings into the daemon.log. The reason is the licensing of the MIB files, that is not compatible with Debian. If you are not satisfied with errors on each restart of the snmpd, here are the steps, that solved this problem in my case: Edit /etc/apt/sources.list [...]]]></description>
			<content:encoded><![CDATA[<p>The default installation of <strong>snmpd</strong> in Debian <strong>Squeeze</strong> will put several warnings into the <strong>daemon.log</strong>.</p>
<p>The reason is the licensing of the <strong>MIB</strong> files, that is not compatible with Debian.</p>
<p>If you are not satisfied with errors on each restart of the snmpd, here are the steps, that solved this problem in my case:</p>
<ul>
<li>Edit <strong>/etc/apt/sources.list</strong> and append <strong>contrib</strong> and <strong>non-free</strong> to the standard repositories.</li>
<li><em>apt-get update</em></li>
<li><em>apt-get install snmpd snmp-mibs-downloader</em></li>
<li>Edit <strong>/etc/default/snmpd</strong>:<br />
<em>export MIBS=/usr/share/mibs/netsnmp/</em><em>UCD-SNMP-MIB</em></li>
</ul>
<p>Commenting the original line <em>export MIBS=</em> did not help, also the definition export <em>MIBS=/usr/share/mibs/netsnmp</em> did not work, so I will leave the MIBS reference in the configuration on <strong>UCD-SNMP_MIB</strong>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hpaschke.de/blog/2012/04/snmp-warnings-in-debian-squeeze/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL Query Log</title>
		<link>http://www.hpaschke.de/blog/2012/04/mysql-query-log/</link>
		<comments>http://www.hpaschke.de/blog/2012/04/mysql-query-log/#comments</comments>
		<pubDate>Wed, 11 Apr 2012 21:55:30 +0000</pubDate>
		<dc:creator>Holger</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[Debug]]></category>
		<category><![CDATA[MySQL]]></category>

		<guid isPermaLink="false">http://www.hpaschke.de/blog/?p=354</guid>
		<description><![CDATA[If you need details about whats going on within your MySQL instance, the query log is still very useful, even though it's not good for permanent use, since it costs performance and disk space. But with some luck you already have release 5.1 or later and you can activate the query log on the fly: [...]]]></description>
			<content:encoded><![CDATA[<p>If you need details about whats going on within your MySQL instance, the <strong>query log</strong> is still very useful, even though it's not good for permanent use, since it costs performance and disk space.</p>
<p>But with some luck you already have release 5.1 or later and you can activate the query log on the fly:</p>
<ul>
<li>Log in to your MySQL instance, e.g. <strong>mysql --defaults-file=/etc/mysql/debian.cnf</strong>, if you are using a standard MySQL installation on Debian/Ubuntu.</li>
<li>Set the log target: <strong>set global general_log_file='/var/tmp/mysql.log'</strong></li>
<li>Activate the log file: <strong>set global general_log=1</strong></li>
<li>You can end the logging (and you should really restrict the logging on production systems) with: <strong>set global general_log=0</strong></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.hpaschke.de/blog/2012/04/mysql-query-log/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Java VisualVM</title>
		<link>http://www.hpaschke.de/blog/2012/04/java-visualvm/</link>
		<comments>http://www.hpaschke.de/blog/2012/04/java-visualvm/#comments</comments>
		<pubDate>Tue, 10 Apr 2012 22:28:04 +0000</pubDate>
		<dc:creator>Holger</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Monitoring]]></category>

		<guid isPermaLink="false">http://www.hpaschke.de/blog/?p=348</guid>
		<description><![CDATA[For quick analysis of the options and health of a Java VM I used the jconsole tool, that is part of the Java SDK. Now there is also VisualVM, that not only provides information about the options and health (CPU, Memory), but also a useful overview of the threads including their state and finally easy [...]]]></description>
			<content:encoded><![CDATA[<p>For quick analysis of the options and health of a Java VM I used the <em>jconsole</em> tool, that is part of the Java SDK.</p>
<p>Now there is also <strong>VisualVM</strong>, that not only provides information about the options and health (CPU, Memory), but also a useful overview of the threads including their state and finally easy access to CPU and memory profiling.</p>
<p>See <a href="http://visualvm.java.net/">http://visualvm.java.net/</a> for details. To start this tool use the command <strong>jvisualvm</strong> instead of <strong>jconsole</strong> and select the Java VM that is your object.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hpaschke.de/blog/2012/04/java-visualvm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Alfresco eats Memory &#8211; Yum, Yum</title>
		<link>http://www.hpaschke.de/blog/2012/03/alfresco-eats-memory-yum-yum/</link>
		<comments>http://www.hpaschke.de/blog/2012/03/alfresco-eats-memory-yum-yum/#comments</comments>
		<pubDate>Sat, 10 Mar 2012 23:18:46 +0000</pubDate>
		<dc:creator>Holger</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[Alfresco]]></category>

		<guid isPermaLink="false">http://www.hpaschke.de/blog/?p=345</guid>
		<description><![CDATA[I recently tried to optimize an Alfresco 4 installation in a 1GB Ubuntu VM and reduction of the default 512m for MaxPermSize was too much, the Tomcat instance goes down after startup and first call to /alfresco. Considering the remaining memory for the PostgreSQL database, OpenOffice and the operating system, I thought about reduction of [...]]]></description>
			<content:encoded><![CDATA[<p>I recently tried to optimize an <strong>Alfresco 4</strong> installation in a 1GB Ubuntu VM and reduction of the default 512m for <strong>MaxPermSize</strong> was too much, the Tomcat instance goes down after startup and first call to <em>/alfresco</em>.</p>
<p>Considering the remaining memory for the PostgreSQL database, OpenOffice and the operating system, I thought about reduction of <strong>Heap</strong> and <strong>PermSize</strong> limits for the Tomcat instance included in the Alfresco installation. Setting the Heap Maximum to 512m instead of 1024m was not the problem, but using 128m for MaxPermSize instead of the 512m killed the instance after the first call to <em>/alfresco</em>.</p>
<p>So better don't touch <strong>MaxPermSize</strong> in <em>tomcat/scripts/ctl.sh</em>.</p>
<p>Also 1GB of RAM is not recommended for an Afresco VM, better start with 2GB of RAM. The startup of Alfresco currently takes up to 4-5 minutes, shutdown is not faster, which makes reboots of the VM taking 10 minutes even though the VM is restarted within seconds, it's the Alfresco that gives the delay.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hpaschke.de/blog/2012/03/alfresco-eats-memory-yum-yum/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

