<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    
    <title>Daniel E. Markle's Blog - System Administration</title>
    <link>http://ashtech.net/~dmarkle/blog/</link>
    <description>Blatherings on Technology and Life</description>
    <dc:language>en</dc:language>
    <admin:errorReportsTo rdf:resource="mailto:" />
    <generator>Serendipity 1.5.5 - http://www.s9y.org/</generator>
    <managingEditor>syntax@ashtech.net (Daniel E. Markle)</managingEditor>
<webMaster>syntax@ashtech.net (Daniel E. Markle)</webMaster>

    <image>
        <url>http://ashtech.net/~syntax/blog/uploads/128blackcat.png</url>
        <title>RSS: Daniel E. Markle's Blog - System Administration - Blatherings on Technology and Life</title>
        <link>http://ashtech.net/~dmarkle/blog/</link>
        <width>128</width>
        <height>128</height>
    </image>

<item>
    <title>Liferay 6.0.6 CE Editing Toolbar Bug</title>
    <link>http://ashtech.net/~dmarkle/blog/archives/334-Liferay-6.0.6-CE-Editing-Toolbar-Bug.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~dmarkle/blog/archives/334-Liferay-6.0.6-CE-Editing-Toolbar-Bug.html#comments</comments>
    <wfw:comment>http://ashtech.net/~dmarkle/blog/wfwcomment.php?cid=334</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~dmarkle/blog/rss.php?version=2.0&amp;type=comments&amp;cid=334</wfw:commentRss>
    

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    In Liferay 6.0 GA4 Community Edition there is an error in the CKEditor configuration; different configuration files are used to define the editing toolbar for the web content and other areas depending on the browsing path. This results in an issue where the toolbar changes seemingly at random. This is fixed in the Enterprise Edition and for future versions, but for those of us using the current Community Edition, the following workaround is useful.&lt;br /&gt;
&lt;br /&gt;
The most problematic disappearing item for my use case is the spell checker; the same method can be used to restore other buttons as necessary. Back up, then apply this &lt;a href=&quot;http://ashtech.net/~dmarkle/patches/liferay/ckconfig-spellcheck.patch&quot;&gt;ckconfig.jsp patch&lt;/a&gt; to the Liferay root web app. For the tomcat download this is located in the &lt;code&gt;liferay-portal-6.0.6/tomcat-6.0.29/webapps/ROOT/html/js/editor/ckeditor/&lt;/code&gt; directory. Shut down Liferay, remove the tomcat work directory to clear the cache, then restart Liferay. 
    </content:encoded>

    <pubDate>Wed, 28 Sep 2011 11:39:05 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~dmarkle/blog/archives/334-guid.html</guid>
    
</item>
<item>
    <title>Airprint to an Office Workgroup Printer</title>
    <link>http://ashtech.net/~dmarkle/blog/archives/329-Airprint-to-an-Office-Workgroup-Printer.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~dmarkle/blog/archives/329-Airprint-to-an-Office-Workgroup-Printer.html#comments</comments>
    <wfw:comment>http://ashtech.net/~dmarkle/blog/wfwcomment.php?cid=329</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~dmarkle/blog/rss.php?version=2.0&amp;type=comments&amp;cid=329</wfw:commentRss>
    

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    Although Apple uses standard protocols for Airprint, the service is very picky about the exact broadcast settings before the printer will show up on iOS devices. The easiest way I&#039;ve found to Airprint to an office workgroup printer:&lt;ul&gt;&lt;li&gt;Configure the printer to be printable via a Linux / CUPS server. On Debian install the cups and cups-pdf packages then log in via port 631 and configure the workgroup printer, making sure a test page prints.&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Add &lt;code&gt;ServerAlias *&lt;/code&gt; in /etc/cups.conf; this prevents &quot;Request from x using invalid Host: field&quot; errors.&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Install avahi, on Debian use the avahi-daemon package.&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Run this handy &lt;a href=&quot;https://github.com/tjfontaine/airprint-generate&quot;&gt;airprint-generate script&lt;/a&gt;. Copy the resulting file to /etc/avahi/services/ and restart avahi and cups.&lt;/li&gt;&lt;/ul&gt;Airprint should now be working for your iOS devices on the local network. 
    </content:encoded>

    <pubDate>Tue, 19 Jul 2011 15:55:26 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~dmarkle/blog/archives/329-guid.html</guid>
    
</item>
<item>
    <title>SNMP MIB lookup removed from Debian squeeze</title>
    <link>http://ashtech.net/~dmarkle/blog/archives/322-SNMP-MIB-lookup-removed-from-Debian-squeeze.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~dmarkle/blog/archives/322-SNMP-MIB-lookup-removed-from-Debian-squeeze.html#comments</comments>
    <wfw:comment>http://ashtech.net/~dmarkle/blog/wfwcomment.php?cid=322</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~dmarkle/blog/rss.php?version=2.0&amp;type=comments&amp;cid=322</wfw:commentRss>
    

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    After upgrading to Debian squeeze, snmp output will change; the descriptions are missing.&lt;br /&gt;
&lt;br /&gt;
Before squeeze (i.e. in lenny):&lt;br /&gt;
&lt;code&gt;$ snmpget -v1 -On -c public printer.example.com 1.3.6.1.2.1.25.3.5.1.1.1&lt;br /&gt;
.1.3.6.1.2.1.25.3.5.1.1.1 = INTEGER: idle(3)&lt;/code&gt;&lt;br /&gt;
After squeeze upgrade:&lt;br /&gt;
&lt;code&gt;$ snmpget -v1 -On -c public printer.example.com 1.3.6.1.2.1.25.3.5.1.1.1&lt;br /&gt;
.1.3.6.1.2.1.25.3.5.1.1.1 = INTEGER: 3&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
This is because the MIB files were stripped from squeeze due to &lt;a href=&quot;http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498475&quot;&gt;licensing reasons&lt;/a&gt;. Install the &lt;code&gt;snmp-mibs-downloader&lt;/code&gt; package and comment out  the line in &lt;code&gt;/etc/snmp/snmp.conf&lt;/code&gt; as described in that config file. Non-free will need to be enabled in apt sources if you are not finding the package. See the &lt;a href=&quot;http://wiki.debian.org/SNMP&quot;&gt;Debian wiki section on snmp&lt;/a&gt; for added information. 
    </content:encoded>

    <pubDate>Mon, 07 Feb 2011 18:02:51 -0500</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~dmarkle/blog/archives/322-guid.html</guid>
    
</item>
<item>
    <title>Zimbra 6.0.9 Upgrade Logrotate Issue</title>
    <link>http://ashtech.net/~dmarkle/blog/archives/318-Zimbra-6.0.9-Upgrade-Logrotate-Issue.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~dmarkle/blog/archives/318-Zimbra-6.0.9-Upgrade-Logrotate-Issue.html#comments</comments>
    <wfw:comment>http://ashtech.net/~dmarkle/blog/wfwcomment.php?cid=318</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~dmarkle/blog/rss.php?version=2.0&amp;type=comments&amp;cid=318</wfw:commentRss>
    

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    If receiving e-mails like this from &lt;a href=&quot;http://zimbra.com/&quot;&gt;Zimbra&lt;/a&gt; after upgrading to 6.0.9:&lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
/etc/cron.daily/logrotate:&lt;br /&gt;
error: zimbra:5 unknown user &#039;USER&#039;&lt;br /&gt;
run-parts: /etc/cron.daily/logrotate exited with return code 1&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
See this &lt;a href=&quot;http://www.zimbra.com/forums/administrators/45196-solved-logrotate-issue.html&quot;&gt;forum post on a 6.0.9 logrotate issue&lt;/a&gt;. In a nutshell, edit &lt;code&gt;/etc/logrotate.d/zimbra&lt;/code&gt; and replace &lt;code&gt;USER GROUP&lt;/code&gt; with &lt;code&gt;zimbra zimbra&lt;/code&gt;. 
    </content:encoded>

    <pubDate>Fri, 03 Dec 2010 12:27:36 -0500</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~dmarkle/blog/archives/318-guid.html</guid>
    
</item>
<item>
    <title>Debconf 10</title>
    <link>http://ashtech.net/~dmarkle/blog/archives/314-Debconf-10.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~dmarkle/blog/archives/314-Debconf-10.html#comments</comments>
    <wfw:comment>http://ashtech.net/~dmarkle/blog/wfwcomment.php?cid=314</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~dmarkle/blog/rss.php?version=2.0&amp;type=comments&amp;cid=314</wfw:commentRss>
    

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    In August I attended &lt;a href=&quot;http://debconf10.debconf.org/&quot;&gt;Debconf 10&lt;/a&gt;. My primary goals were to learn more about the current status of the &lt;a href=&quot;http://debian.org/&quot;&gt;Debian&lt;/a&gt; community, particularly in the face of Ubuntu&#039;s rise to popularity, and to fix the &lt;a href=&quot;http://packages.debian.org/search?keywords=xtrkcad&amp;searchon=names&amp;suite=all&amp;section=all&quot;&gt;package xtrkcad for Debian&lt;/a&gt;, which used an outdated library. &lt;br /&gt;&lt;a href=&quot;http://ashtech.net/~dmarkle/blog/archives/314-Debconf-10.html#extended&quot;&gt;Continue reading &quot;Debconf 10&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Wed, 13 Oct 2010 21:20:57 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~dmarkle/blog/archives/314-guid.html</guid>
    
</item>
<item>
    <title>Apache SSL and Combined Certificates</title>
    <link>http://ashtech.net/~dmarkle/blog/archives/281-Apache-SSL-and-Combined-Certificates.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~dmarkle/blog/archives/281-Apache-SSL-and-Combined-Certificates.html#comments</comments>
    <wfw:comment>http://ashtech.net/~dmarkle/blog/wfwcomment.php?cid=281</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~dmarkle/blog/rss.php?version=2.0&amp;type=comments&amp;cid=281</wfw:commentRss>
    

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    Current versions of &lt;a href=&quot;http://httpd.apache.org/&quot;&gt;Apache HTTP Server&lt;/a&gt; support SSL certificates and keys all in one file; it is no longer required to separate them. Point &lt;code&gt;SSLCertificateFile&lt;/code&gt; at the combined file (commonly .pem) and comment out or omit &lt;code&gt;SSLCertificateKeyFile&lt;/code&gt;. &lt;br /&gt;
&lt;br /&gt;
This may not be desirable if you wish to have the certificate publicly available somewhere like &lt;code&gt;/etc/ssl/certs/&lt;/code&gt;, available on the web for verification, or use the certificate for other applications for that domain (it&#039;s important to keep the key, and thus the combined file, private). In many common cases certificates are only used for an SSL secured web server, however. 
    </content:encoded>

    <pubDate>Tue, 04 May 2010 13:52:37 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~dmarkle/blog/archives/281-guid.html</guid>
    
</item>
<item>
    <title>Zimbra 32bit to 64bit Certificate Issue</title>
    <link>http://ashtech.net/~dmarkle/blog/archives/280-Zimbra-32bit-to-64bit-Certificate-Issue.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~dmarkle/blog/archives/280-Zimbra-32bit-to-64bit-Certificate-Issue.html#comments</comments>
    <wfw:comment>http://ashtech.net/~dmarkle/blog/wfwcomment.php?cid=280</wfw:comment>

    <slash:comments>5</slash:comments>
    <wfw:commentRss>http://ashtech.net/~dmarkle/blog/rss.php?version=2.0&amp;type=comments&amp;cid=280</wfw:commentRss>
    

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    When upgrading from 32 to 64 bit &lt;a href=&quot;http://zimbra.com&quot;&gt;Zimbra&lt;/a&gt;, I could not get the zimbra mailbox (mailboxd) to start. It turned out to be a set of borked certificates. Do yourself a favor if you have this problem and just do this:&lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
mv /opt/zimbra/mailboxd/etc/keystore /opt/zimbra/mailboxd/etc/keystore.borked&lt;br /&gt;
sudo /opt/zimbra/bin/zmcertmgr deploycrt self&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
Then re-deploy your certificates using the gui admin interface after restarting Zimbra. &lt;br /&gt;&lt;a href=&quot;http://ashtech.net/~dmarkle/blog/archives/280-Zimbra-32bit-to-64bit-Certificate-Issue.html#extended&quot;&gt;Continue reading &quot;Zimbra 32bit to 64bit Certificate Issue&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sat, 01 May 2010 20:48:14 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~dmarkle/blog/archives/280-guid.html</guid>
    
</item>

</channel>
</rss>
