<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Howto on The Infinite Unknown</title>
    <link>https://www.jaredwatkins.com/tags/howto/</link>
    <description>Recent content in Howto on The Infinite Unknown</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 07 May 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://www.jaredwatkins.com/tags/howto/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fixing MySQL SSL Replication Errors</title>
      <link>https://www.jaredwatkins.com/posts/2013/05/fixing-mysql-ssl-replication-errors/</link>
      <pubDate>Tue, 07 May 2013 00:00:00 +0000</pubDate>
      <author>Jared Watkins</author>
      <guid>https://www.jaredwatkins.com/posts/2013/05/fixing-mysql-ssl-replication-errors/</guid>
      <description>&lt;p&gt;I spent 2 nights trying to get mysql replication over ssl to work.. and kept hitting this generic
error message: connection error 2026. After much searching and trying different things I finally
found the solution that worked for me.  If you are hitting this error here&amp;rsquo;s a short list of
things to check.&lt;/p&gt;
&lt;p&gt;Searching around I found a few key things to look for when you see this error. First.. make sure your certificate
CNs are unique. Some people mistakenly used the same strings when generating server and client
certificates. When generating your CSR and going through all the cert detail questions your CN
would normally be the fully qualified domain name of the host you are generating the cert for.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;openssl x509 -in &amp;lt;cert file&amp;gt; -noout -noout -subject
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Then I would check that you can connect manually from your replication slave to the master.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;mysql -h &amp;lt;master server&amp;gt; --ssl -u &amp;lt;replication user on master&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;After you connect make sure your sesson is using ssl by issuing the command &amp;ldquo;\s&amp;rdquo;. It should
list something like this:
SSL:                    Cipher in use is DHE-RSA-AES256-SHA&lt;/p&gt;
&lt;p&gt;In my case the manual connection was working fine.. but not the replication.&lt;/p&gt;
&lt;p&gt;The problem I had was actually with paths used in the &amp;lsquo;CHANGE MASTER TO&amp;rsquo; line on the slave.
When setting values for MASTER_SSL_CA, MASTER_SSL_CERT, and MASTER_SSL_KEY you should specificy
the complete path to the files.  The docs suggest otherwise.. in combination with MASTER_SSL_CAPATH.
I found that particular setting wasn&amp;rsquo;t used the way I expected.. so I left it out and went with
full path names.&lt;/p&gt;
&lt;p&gt;Hope that&amp;rsquo;s helpful for someone else!&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Keep FreeNAS From Crashing Tweaks</title>
      <link>https://www.jaredwatkins.com/posts/2012/07/keep-freenas-from-crashing-tweaks/</link>
      <pubDate>Sun, 01 Jul 2012 00:00:00 +0000</pubDate>
      <author>Jared Watkins</author>
      <guid>https://www.jaredwatkins.com/posts/2012/07/keep-freenas-from-crashing-tweaks/</guid>
      <description>&lt;p&gt;I found these settings on another site.. reposting here for my future reference and to double the possibility of someone else not having to spend hours trying to figure this out.  My install of FreeNAS kept hanging under even moderate write loads… rendering it unusable until I applied these memory tweaks.  I don’t know nearly as much about BSD internals as I do linux.  You can apply these through the web GUI under System-&amp;gt;Tunables.  When you do they get added to the file /boot/loader.conf.local but should also be backed up with the rest of your config.&lt;/p&gt;
&lt;p&gt;Of course this assumes you have adequate memory… I used these values on a system with 6G total ram.&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;vm.kmem_size=&amp;#34;1536M&amp;#34;
vm.kmem_size_max=&amp;#34;2048M&amp;#34;
vfs.zfs.arc_min=&amp;#34;256M&amp;#34;
vfs.zfs.arc_max=&amp;#34;1024M&amp;#34;
vfs.zfs.txg.timeout=&amp;#34;30&amp;#34;
vfs.zfs.vdev.max_pending=&amp;#34;35&amp;#34;
vfs.zfs.vdev.min_pending=&amp;#34;4&amp;#34;
vfs.zfs.txg.write_limit_override=&amp;#34;1073741824&amp;#34;
&lt;/code&gt;&lt;/pre&gt;</description>
    </item>
    
    <item>
      <title>OSX Mail App Using Tons of Memory and CPU?</title>
      <link>https://www.jaredwatkins.com/posts/2012/01/osx-mail-app-using-tons-of-memory-and-cpu/</link>
      <pubDate>Sat, 07 Jan 2012 00:00:00 +0000</pubDate>
      <author>Jared Watkins</author>
      <guid>https://www.jaredwatkins.com/posts/2012/01/osx-mail-app-using-tons-of-memory-and-cpu/</guid>
      <description>&lt;p&gt;
  &lt;img src=&#34;http://farm1.static.flickr.com/30/44074632_687cc920b9.jpg&#34; alt=&#34;&#34; /&gt;

&lt;/p&gt;
&lt;p&gt;I’ve been using a mac for a while now and I recently decided to dump Entourage and go to using the native Mail.app.  I noticed a problem though.. within minutes of starting up it would consume several hundred megs of ram and have frequent CPU spikes of 80 to 100%.  If Mail was left open, memory usage would climb above 2 gig with continued CPU spikes.  After much digging I finally found the problem and fixed it.&lt;/p&gt;
&lt;p&gt;I’d been using iSync back before I got an iPhone..  and had never thought to disable it.  It looks like what was happening is that mail and other apps (ical, address book) had been building a huge database of stuff that needed to be synced to my old phone.  Once I went in and reset the sync history and disabled iSync.. everything calmed down and now a running instance of Mail.app with 3 imap accounts and an Exchange account is using about 60 MB of ram.. and it’s not steadily climbing as it had been before.  This may have also been the source of the problems I’d been having with Entourage.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Putting the UBEE Cable Modem from Time Warner in Bridge Mode</title>
      <link>https://www.jaredwatkins.com/posts/2011/01/putting-the-ubee-cable-modem-from-time-warner-in-bridge-mode/</link>
      <pubDate>Sat, 22 Jan 2011 00:00:00 +0000</pubDate>
      <author>Jared Watkins</author>
      <guid>https://www.jaredwatkins.com/posts/2011/01/putting-the-ubee-cable-modem-from-time-warner-in-bridge-mode/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;ubee-bridge-mode-e1295698327507.png&#34;&gt;
  &lt;img src=&#34;https://www.jaredwatkins.com/posts/2011/01/putting-the-ubee-cable-modem-from-time-warner-in-bridge-mode/inline_ubee-bridge-mode-e1295698327507.png&#34; width=&#34;170&#34; height=&#34;200&#34; alt=&#34;&#34; /&gt;

&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Time Warner has been offering faster cable modem speeds lately for much the same price as slower speeds a couple years ago.  When I got the new modem I noticed there didn’t seem to be a way to put it in bridge mode to work with the &lt;a href=&#34;http://www.wikinvest.com/concept/Open_Source&#34;&gt;linux&lt;/a&gt; router I already had.  After a little digging I found that the management page for doing this was ‘branded out’ and the link to it was removed from the interface.  The page is still there though… and if you put that url in directly you can still get to it and it still works.  If you can read the image the url would be:  http://[your modem ip]/T|ModeChange.asp    Put that in after you are logged into the management interface which has a default user/pass of ‘user/user’.  Hope that helps…&lt;/p&gt;
&lt;p&gt;FYI: This is a personal blog.. &lt;strong&gt;not a support site&lt;/strong&gt; for this modem. If you have relevant info to share that’s great but &lt;strong&gt;I won’t be approving any more requests for troubleshooting help.&lt;/strong&gt; Do your own troubleshooting and then come share the results of how to fix some situation you encountered if you like.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
