<?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://www.ashtech.net/~dmarkle/blog/</link>
    <description>Blatherings on Technology and Life</description>
    <dc:language>en</dc:language>
    <admin:errorReportsTo rdf:resource="mailto:" />
    <generator>Serendipity 2.1.4 - 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://www.ashtech.net/~dmarkle/blog/</link>
    <width>128</width>
    <height>128</height>
</image>

<item>
    <title>Let's Encrypt SSL Certificates</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/374-Lets-Encrypt-SSL-Certificates.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/374-Lets-Encrypt-SSL-Certificates.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=374</wfw:comment>

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

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    &lt;a href=&quot;https://letsencrypt.org/&quot;&gt;Let&#039;s Encrypt&lt;/a&gt; changes the game for SSL certificates. By combining free certificates with an effective mechanism for ensuring these certificates are legitimately issued, everyone running a site can now have a signed certificate. EFF&#039;s &lt;a href=&quot;https://certbot.eff.org/&quot;&gt;Certbot&lt;/a&gt; is a handy tool for allowing even novice administrators to easily maintain these certificates, with automatic renewal.&lt;br /&gt;
&lt;br /&gt;
For companies with intranets, &lt;a href=&quot;http://security.stackexchange.com/questions/103524/lets-encrypt-for-intranet-websites&quot;&gt;Let&#039;s Encrypt may not be suitable&lt;/a&gt;. The resolution protocol which proves out the site owner requires access to the dns or parent web server for a real domain. Regardless of registration method used, the addresses of these intranet sites are then publicly available via logs which anyone can see, which could be an issue in cases where it is important to keep these private.&lt;br /&gt;
&lt;br /&gt;
Regardless of the caveat for intranets, this new option is a tremendous improvement over the previous state of SSL for many, and has particularly impressive use cases in &lt;a href=&quot;https://www.joyent.com/blog/nginx-and-letsencrypt-on-autopilot&quot;&gt;cloud deployments&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Sat, 21 Jan 2017 00:17:11 -0500</pubDate>
    <guid isPermaLink="false">http://www.ashtech.net/~dmarkle/blog/archives/374-guid.html</guid>
    
</item>
<item>
    <title>Liferay 6.0.6 CE Editing Toolbar Bug</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/334-Liferay-6.0.6-CE-Editing-Toolbar-Bug.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/334-Liferay-6.0.6-CE-Editing-Toolbar-Bug.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=334</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.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://www.ashtech.net/~dmarkle/blog/archives/334-guid.html</guid>
    
</item>
<item>
    <title>Airprint to an Office Workgroup Printer</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/329-Airprint-to-an-Office-Workgroup-Printer.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/329-Airprint-to-an-Office-Workgroup-Printer.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=329</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.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://www.ashtech.net/~dmarkle/blog/archives/329-guid.html</guid>
    
</item>
<item>
    <title>SNMP MIB lookup removed from Debian squeeze</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/322-SNMP-MIB-lookup-removed-from-Debian-squeeze.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/322-SNMP-MIB-lookup-removed-from-Debian-squeeze.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=322</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.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://www.ashtech.net/~dmarkle/blog/archives/322-guid.html</guid>
    
</item>
<item>
    <title>Zimbra 6.0.9 Upgrade Logrotate Issue</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/318-Zimbra-6.0.9-Upgrade-Logrotate-Issue.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/318-Zimbra-6.0.9-Upgrade-Logrotate-Issue.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=318</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.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://www.ashtech.net/~dmarkle/blog/archives/318-guid.html</guid>
    
</item>
<item>
    <title>Debconf 10</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/314-Debconf-10.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/314-Debconf-10.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=314</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.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;a class=&quot;block_level&quot; href=&quot;http://www.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://www.ashtech.net/~dmarkle/blog/archives/314-guid.html</guid>
    
</item>
<item>
    <title>Apache SSL and Combined Certificates</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/281-Apache-SSL-and-Combined-Certificates.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/281-Apache-SSL-and-Combined-Certificates.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=281</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.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://www.ashtech.net/~dmarkle/blog/archives/281-guid.html</guid>
    
</item>
<item>
    <title>Zimbra 32bit to 64bit Certificate Issue</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/280-Zimbra-32bit-to-64bit-Certificate-Issue.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/280-Zimbra-32bit-to-64bit-Certificate-Issue.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=280</wfw:comment>

    <slash:comments>6</slash:comments>
    <wfw:commentRss>http://www.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;a class=&quot;block_level&quot; href=&quot;http://www.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://www.ashtech.net/~dmarkle/blog/archives/280-guid.html</guid>
    
</item>
<item>
    <title>Agile Documentation Thoughts for Small Groups</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/169-Agile-Documentation-Thoughts-for-Small-Groups.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/169-Agile-Documentation-Thoughts-for-Small-Groups.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=169</wfw:comment>

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

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    Working for a small company, our projects tend to be small. Processes and programs are best documented as tasks are first done and over time as improvements are made. Trying to document everything up front is a waste of time, as the requirements change throughout. Waiting until the end, the documentation is never completed as some other urgent project comes along. Humans are frighteningly perishable and can get hit by a bus/meteor/disease at any time.&lt;br /&gt;
 &lt;a class=&quot;block_level&quot; href=&quot;http://www.ashtech.net/~dmarkle/blog/archives/169-Agile-Documentation-Thoughts-for-Small-Groups.html#extended&quot;&gt;Continue reading &quot;Agile Documentation Thoughts for Small Groups&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 30 Jul 2009 23:03:25 -0400</pubDate>
    <guid isPermaLink="false">http://www.ashtech.net/~dmarkle/blog/archives/169-guid.html</guid>
    
</item>
<item>
    <title>Debian 5 Mailutils and Maildir</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/162-Debian-5-Mailutils-and-Maildir.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/162-Debian-5-Mailutils-and-Maildir.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=162</wfw:comment>

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

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    When setting up &lt;a href=&quot;http://en.wikipedia.org/wiki/Maildir&quot;&gt;Maildir&lt;/a&gt; in Debian 5.0, getting the generic &lt;code&gt;mail&lt;/code&gt; applications working correctly can be tricky.&lt;ul&gt;&lt;li&gt;Install the &#039;mailutils&#039; package, not the bsd mailx package.&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Do &lt;strong&gt;not&lt;/strong&gt; touch the mailutils /etc/mail.rc file; there are some promising looking variables here like &lt;code&gt;mailbox-type&lt;/code&gt; but these do not do what is desired. When the MAIL environment variable is set correctly mailutils will automatically detect the maildir box type.&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Do &lt;strong&gt;not&lt;/strong&gt; touch /etc/login.defs; the promising looking lines in here are deprecated.&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Edit files in &lt;code&gt;/etc/pam.d&lt;/code&gt;, changing the pam_mail.so lines as shown (assuming ~/Maildir as the selected location):&lt;br /&gt;
  &lt;ul&gt;&lt;br /&gt;
  &lt;li&gt;login: default login shells&lt;br /&gt;
  &lt;code&gt;session    optional   pam_mail.so dir=~/Maildir standard&lt;/code&gt;&lt;br /&gt;
  &lt;/li&gt;&lt;br /&gt;
  &lt;li&gt;su: set up for proper MAIL when using su; nopen does not show &#039;new mail&#039; message&lt;br /&gt;
  &lt;code&gt;session    optional   pam_mail.so dir=~/Maildir nopen&lt;/code&gt;&lt;br /&gt;
  &lt;/li&gt;&lt;br /&gt;
  &lt;li&gt;sshd: set up MAIL properly when logging in with ssh; this line probably has a noenv by default which needs removed to set this properly&lt;br /&gt;
  &lt;code&gt;session    optional     pam_mail.so dir=~/Maildir standard&lt;/code&gt;&lt;br /&gt;
  &lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt; 
    </content:encoded>

    <pubDate>Wed, 08 Apr 2009 16:32:48 -0400</pubDate>
    <guid isPermaLink="false">http://www.ashtech.net/~dmarkle/blog/archives/162-guid.html</guid>
    
</item>
<item>
    <title>PostgreSQL Upgrade to 8.3 on Debian Encoding Issues</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/160-PostgreSQL-Upgrade-to-8.3-on-Debian-Encoding-Issues.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/160-PostgreSQL-Upgrade-to-8.3-on-Debian-Encoding-Issues.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=160</wfw:comment>

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

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    PostgreSQL has improved its checking for proper locale handling in version 8.3. Due to inconsistencies caused by changing defaults in past versions of Debian, some database clusters contain UTF8 and LATIN1 databases in the same cluster. This can cause problems when trying to restore from a pgdump file with errors similar to:&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;ERROR:  encoding LATIN1 does not match server&#039;s locale en_US.UTF-8&lt;br /&gt;
DETAIL:  The server&#039;s LC_CTYPE setting requires encoding UTF8.&lt;/code&gt; &lt;a class=&quot;block_level&quot; href=&quot;http://www.ashtech.net/~dmarkle/blog/archives/160-PostgreSQL-Upgrade-to-8.3-on-Debian-Encoding-Issues.html#extended&quot;&gt;Continue reading &quot;PostgreSQL Upgrade to 8.3 on Debian Encoding Issues&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Wed, 18 Mar 2009 19:28:36 -0400</pubDate>
    <guid isPermaLink="false">http://www.ashtech.net/~dmarkle/blog/archives/160-guid.html</guid>
    
</item>
<item>
    <title>Cron Uses /usr/sbin/sendmail</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/124-Cron-Uses-usrsbinsendmail.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/124-Cron-Uses-usrsbinsendmail.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=124</wfw:comment>

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

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    On a server running Zimbra on Ubuntu, to get cron job output sent to an e-mail address, make the following link:&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;ln -s /opt/zimbra/postfix/sbin/sendmail /usr/sbin/sendmail&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
Until this is done, crontab output will silently vaporize. &lt;a class=&quot;block_level&quot; href=&quot;http://www.ashtech.net/~dmarkle/blog/archives/124-Cron-Uses-usrsbinsendmail.html#extended&quot;&gt;Continue reading &quot;Cron Uses /usr/sbin/sendmail&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 22 Jan 2009 20:09:33 -0500</pubDate>
    <guid isPermaLink="false">http://www.ashtech.net/~dmarkle/blog/archives/124-guid.html</guid>
    
</item>
<item>
    <title>Be Careful with / in ProxyPass</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/110-Be-Careful-with-in-ProxyPass.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/110-Be-Careful-with-in-ProxyPass.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=110</wfw:comment>

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

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    I use the built-in Apache 2.2 ajp ProxyPass support when deploying Tomcat and JBoss applications via Apache.  When doing so, be careful your slashes match up or you can have subtle problems with applications which use redirects.  For example, I was deploying a &lt;a href=&quot;http://jspwiki.org&quot;&gt;JSPWiki&lt;/a&gt; but having an odd problem with authentication where logins would seem to fail but then work fine if I manually reloaded the page.  I was using this Apache configuration:&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;ProxyPass           /webdevwiki  ajp://127.0.0.1:8009/webdevwiki/&lt;br /&gt;
ProxyPassReverse    /webdevwiki  ajp://127.0.0.1:8009/webdevwiki/&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
This appeared to work fine, but when logging in an extra slash would get added to the Login.jsp redirection page.  This kept the redirect to the main page from working, causing it to reload the Login.jsp infinitely even though login had been successful.  A manual click of the reload button fixed the site, with authentication and all other functions working until trying to log in again.&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;ProxyPass           /webdevwiki  ajp://127.0.0.1:8009/webdevwiki&lt;br /&gt;
ProxyPassReverse    /webdevwiki  ajp://127.0.0.1:8009/webdevwiki&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
Removing the extra slashes as shown fixed this issue. 
    </content:encoded>

    <pubDate>Tue, 05 Feb 2008 18:06:26 -0500</pubDate>
    <guid isPermaLink="false">http://www.ashtech.net/~dmarkle/blog/archives/110-guid.html</guid>
    
</item>
<item>
    <title>Making Apache 2.2 valid-user work with mod_authnz_ldap</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/108-Making-Apache-2.2-valid-user-work-with-mod_authnz_ldap.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/108-Making-Apache-2.2-valid-user-work-with-mod_authnz_ldap.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=108</wfw:comment>

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

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    Apache 2.2&#039;s &lt;a href=&quot;http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html&quot; &gt;mod_authnz_ldap&lt;/a&gt; has significant differences from Apache 2.0&#039;s &lt;a href=&quot;http://httpd.apache.org/docs/2.0/mod/mod_auth_ldap.html&quot; &gt;mod_auth_ldap&lt;/a&gt;.  Moving to 2.2, some significant changes are needed which can be confusing and cause seemingly nonsensical authorization loops if directives are missed.&lt;br /&gt;
&lt;br /&gt;
&lt;h4&gt;Necessary modules&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;auth_basic&lt;/li&gt;&lt;li&gt;authz_user&lt;/li&gt;&lt;li&gt;ldap&lt;/li&gt;&lt;li&gt;authnz_ldap&lt;/li&gt;&lt;/ul&gt;&lt;h4&gt;Directives&lt;/h4&gt;&lt;code&gt;&lt;br /&gt;
        AuthType basic&lt;br /&gt;
        AuthBasicProvider ldap&lt;br /&gt;
        AuthName &quot;My Site&quot;&lt;br /&gt;
        AuthLDAPURL ldap://ldap1.example.com/ou=People,o=Example&lt;br /&gt;
        AuthzLDAPAuthoritative Off&lt;br /&gt;
        Require valid-user&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
&lt;code&gt;AuthBasicProvider ldap&lt;/code&gt; is needed instead of &lt;code&gt;AuthLDAPEnabled on&lt;/code&gt;, which no longer exists as a valid directive.&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;AuthzLDAPAuthoritative Off&lt;/code&gt; is needed to allow the authorization to fall though to &lt;code&gt;Require valid-user&lt;/code&gt;, otherwise you will get &lt;code&gt; auth _ldap authorise: authorisation denied&lt;/code&gt; in your debug messages after it successfully authenticates the user but fails to find an authorization directive to allow access.  These messages will not show up in your logs by default, so it can be confusing if you watch the ldap server, see authentication succeed, and wonder why it keeps requesting a username and password. 
    </content:encoded>

    <pubDate>Thu, 03 Jan 2008 12:46:05 -0500</pubDate>
    <guid isPermaLink="false">http://www.ashtech.net/~dmarkle/blog/archives/108-guid.html</guid>
    
</item>
<item>
    <title>Zimbra Calendar Reminders Not Individually Configurable</title>
    <link>http://www.ashtech.net/~dmarkle/blog/archives/95-Zimbra-Calendar-Reminders-Not-Individually-Configurable.html</link>
            <category>System Administration</category>
    
    <comments>http://www.ashtech.net/~dmarkle/blog/archives/95-Zimbra-Calendar-Reminders-Not-Individually-Configurable.html#comments</comments>
    <wfw:comment>http://www.ashtech.net/~dmarkle/blog/wfwcomment.php?cid=95</wfw:comment>

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

    <author>dmarkle@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    &lt;a href=&quot;http://zimbra.com/&quot;&gt;Zimbra&lt;/a&gt; lacks a calendar feature commonly used by serious Outlook and Entourage users, the ability to configure reminders for individual calendar entries.  The workaround is to create a &#039;reminder&#039; calendar entry, which does not work well as it requires manually changing the reminder if the original appointment changes.  If you are a current or prospective Zimbra user and would like to have this feature added, please &lt;a href=&quot;http://bugzilla.zimbra.com/show_bug.cgi?id=8854&quot; &gt;vote for this bug&lt;/a&gt;.  On a related note, the Zimbra Toaster (which provides popup notification of new mail) does not support calendar reminders, which is documented in &lt;a href=&quot;http://bugzilla.zimbra.com/show_bug.cgi?id=12740&quot; &gt;this bug&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Fri, 06 Jul 2007 10:57:39 -0400</pubDate>
    <guid isPermaLink="false">http://www.ashtech.net/~dmarkle/blog/archives/95-guid.html</guid>
    
</item>

</channel>
</rss>
