<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Error on Evan Hoffman</title><link>https://evan.wtf/tags/error/</link><description>Recent content in Error on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Sun, 18 Sep 2011 12:22:46 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/error/index.xml" rel="self" type="application/rss+xml"/><item><title>Exchange (OWA) CAS crashes with 503 error - again</title><link>https://evan.wtf/2011/09/18/exchange-owa-cas-crashes-with-503-error-again/</link><pubDate>Sun, 18 Sep 2011 12:22:46 +0000</pubDate><guid>https://evan.wtf/2011/09/18/exchange-owa-cas-crashes-with-503-error-again/</guid><description>&lt;p&gt;This just started happening &lt;a href="https://evan.wtf/evan/?p=986"&gt;again&lt;/a&gt;, with these errors appearing in the event viewer:&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;Log Name: System&#10;Source: Microsoft-Windows-WAS&#10;Date: 9/18/2011 11:16:33 AM&#10;Event ID: 5011&#10;Task Category: None&#10;Level: Warning&#10;Keywords: Classic&#10;User: N/A&#10;Computer: exch2010fe1&#10;Description:&#10;A process serving application pool &amp;#39;MSExchangeOWAAppPool&amp;#39; suffered a&#10;fatal communication error with the Windows Process Activation Service.&#10;The process id was &amp;#39;3760&amp;#39;. The data field contains the error number.&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Log Name: System&#10;Source: Microsoft-Windows-WAS&#10;Date: 9/17/2011 6:47:07 AM&#10;Event ID: 5009&#10;Task Category: None&#10;Level: Warning&#10;Keywords: Classic&#10;User: N/A&#10;Computer: exch2010fe1&#10;Description:&#10;A process serving application pool &amp;lsquo;MSExchangeOWAAppPool&amp;rsquo; terminated&#10;unexpectedly. The process id was &amp;lsquo;3108&amp;rsquo;. The process exit code was&#10;&amp;lsquo;0x800703e9&amp;rsquo;.&lt;/p&gt;</description></item><item><title>Amazon SES - "Illegal Header" errors</title><link>https://evan.wtf/2011/05/16/amazon-ses-illegal-header-errors-2/</link><pubDate>Mon, 16 May 2011 12:37:49 +0000</pubDate><guid>https://evan.wtf/2011/05/16/amazon-ses-illegal-header-errors-2/</guid><description>My thoughts on the &amp;ldquo;illegal header&amp;rdquo; error some people are encountering when relaying mail through postfix/SES. Plus some perl code that should help fix it.</description></item><item><title>Integrating Amazon Simple Email Service with postfix for SMTP smarthost relaying.</title><link>https://evan.wtf/2011/04/28/integrating-amazon-simple-email-service-with-postfix-for-smarthost-relaying/</link><pubDate>Thu, 28 Apr 2011 12:23:47 +0000</pubDate><guid>https://evan.wtf/2011/04/28/integrating-amazon-simple-email-service-with-postfix-for-smarthost-relaying/</guid><description>How I configured an EC2 instance to relay mail through Amazon&amp;rsquo;s SES, and some of the bumps I encountered along the way.</description></item><item><title>Going back to FiOS</title><link>https://evan.wtf/2011/04/24/going-back-to-fios/</link><pubDate>Sun, 24 Apr 2011 01:40:05 +0000</pubDate><guid>https://evan.wtf/2011/04/24/going-back-to-fios/</guid><description>&lt;p&gt;I&amp;rsquo;m not sure why these guys operate this way - they&amp;rsquo;re more than happy to lose me as a customer and then throw huge discounts at me to get me back. If they&amp;rsquo;d just give me a good price I&amp;rsquo;d love not to have to go through this rigmarole. But after being with Cablevision for 2 months I checked Verizon&amp;rsquo;s pricing and it beat my current deal with Cablevision.&lt;/p&gt;&#10;&lt;p&gt;FiOS digital voice with number ported for free; 25/25 Mbps internet; HMDVR free &amp;ldquo;forever&amp;rdquo; plus a second HD STB, Showtime, Movie Channel and Flix. Since I already had the battery thing installed last time I had FiOS they gave me a fair discount. Basically the whole package for $87/month + tax, price locked for 2 years, no contract. Not as great of a deal as I&amp;rsquo;d had with FiOS originally, but it&amp;rsquo;s pretty good, and FiOS&amp;rsquo;s service is definitely better than Cablevision&amp;rsquo;s. I&amp;rsquo;ve heard Cablevision was rolling out their &amp;ldquo;DVR plus&amp;rdquo; service with all programs recorded &amp;ldquo;in the cloud&amp;rdquo; rather than on the actual box, but it&amp;rsquo;s been two months and I haven&amp;rsquo;t heard of it coming to Long Island. So basically 2 years later Cablevision&amp;rsquo;s service is exactly the same while Verizon has iPhone apps to control the DVR and use the phone as a remote, plus DVR that&amp;rsquo;s much faster and just generally better service.&lt;/p&gt;</description></item><item><title>How I fixed my Wii's noisy disc drive &amp; read errors.</title><link>https://evan.wtf/2011/02/25/how-i-fixed-my-wii-noisy-disc-drive-read-errors/</link><pubDate>Fri, 25 Feb 2011 00:10:31 +0000</pubDate><guid>https://evan.wtf/2011/02/25/how-i-fixed-my-wii-noisy-disc-drive-read-errors/</guid><description>&lt;p&gt;I got my Wii in late 2006 and around 2009 I noticed it was starting to sound like a circular saw when the disc drive was spinning. This was annoying but it didn&amp;rsquo;t affect the games so I never thought much about it.&lt;/p&gt;&#10;&lt;p&gt;About two weeks ago, however, &lt;a href="http://www.amazon.com/dp/B002BRZ9G0/?tag=evanhoffmasho-20"&gt;New Super Mario Bros. Wii&lt;/a&gt; stopped working:&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://evan.wtf/evan/2011/02/25/how-i-fixed-my-wiis-noisy-disc-drive-read-errors/img_1001/"&gt;&lt;img src="https://evan.wtf/wp-content/uploads/2011/02/IMG_1001-300x225.jpg" alt="" title="IMG_1001"&gt;&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;The Wii basically worked except for the disc drive. As soon as I put a disc in, I&amp;rsquo;d get the error above - even if I didn&amp;rsquo;t start start the game. I tried blowing in the disc slot (the only thing I could think of&amp;hellip; worked for my old NES!) but the problem continued. I figured I had two choices: buy another Wii or attempt to fix mine. Since mine was already essentially useless I figured it couldn&amp;rsquo;t hurt anything to try fixing it.&lt;/p&gt;</description></item><item><title>After switching back to Cablevision, FiOS users can't call us.</title><link>https://evan.wtf/2011/02/24/after-switching-back-to-cablevision-fios-users-cant-call-us-2/</link><pubDate>Thu, 24 Feb 2011 12:39:02 +0000</pubDate><guid>https://evan.wtf/2011/02/24/after-switching-back-to-cablevision-fios-users-cant-call-us-2/</guid><description>&lt;p&gt;So we switched back to Cablevision and it went pretty well, but apparently Verizon users can&amp;rsquo;t call our house number (ported from Verizon to Cablevision). Verizon users have to call from their mobiles in order to complete the call. I&amp;rsquo;m guessing that Verizon hasn&amp;rsquo;t updated their systems to indicate that they no longer &amp;ldquo;own&amp;rdquo; our number and is trying to route the call inside their network. Sucks because I can&amp;rsquo;t imagine Verizon jumping to help fix this since I&amp;rsquo;m not their customer anymore.&lt;/p&gt;</description></item><item><title>VMware Workstation 7 - virtual ethernet fails to start after changing vmnet8 subnet</title><link>https://evan.wtf/2011/02/23/vmware-workstation-7-virtual-ethernet-fails-to-start-after-changing-vmnet8-subnet/</link><pubDate>Wed, 23 Feb 2011 10:29:22 +0000</pubDate><guid>https://evan.wtf/2011/02/23/vmware-workstation-7-virtual-ethernet-fails-to-start-after-changing-vmnet8-subnet/</guid><description>&lt;p&gt;After my recent wipe of my laptop, I reinstalled VMware Workstation and my Win XP VM was working fine. The one wrinkle I faced was that the subnet for the vmnet8 (NAT) vnic had changed from 192.168.250.0/24 to 173.16.132.0/24. The host machine had been 192.168.250.1 so rather than reconfiguring everything on the guest to point to a new IP for the host I figured it would be easier to change the subnet for vmnet8. I went into the Virtual Network Editor and just changed the subnet. Seemed to work correctly, but after doing a release/renew in Win XP I couldn&amp;rsquo;t get an IP.&lt;/p&gt;</description></item><item><title>Wasted time with Exchange 2010, SquirrelMail, and IMAP-SSL</title><link>https://evan.wtf/2010/11/30/wasted-time-with-exchange-2010-squirrelmail-and-imap-ssl/</link><pubDate>Tue, 30 Nov 2010 17:32:11 +0000</pubDate><guid>https://evan.wtf/2010/11/30/wasted-time-with-exchange-2010-squirrelmail-and-imap-ssl/</guid><description>&lt;p&gt;I&amp;rsquo;m setting up SquirrelMail to point to my Exchange 2010 server via IMAP (don&amp;rsquo;t ask) and couldn&amp;rsquo;t get SM to talk to Exchange on port 993 (imaps). Even though the servers on the same subnet, any time passwords are being sent over the network I like to opt for SSL. I found a couple of sites suggesting that the problem was that there was no SSL certificate installed, but I knew for a fact there was a valid certificate because I could get to &lt;a href="https://webmail.example.com/"&gt;https://webmail.example.com/&lt;/a&gt; for OWA.&lt;/p&gt;</description></item><item><title>Ruby/Sinatra part 2</title><link>https://evan.wtf/2010/10/08/ruby-sinatra-part-2/</link><pubDate>Fri, 08 Oct 2010 15:38:19 +0000</pubDate><guid>https://evan.wtf/2010/10/08/ruby-sinatra-part-2/</guid><description>&lt;p&gt;Following up on &lt;a href="https://evan.wtf/2010/10/07/trying-to-teach-myself-ruby-again/"&gt;my previous post&lt;/a&gt;, I decided to go the easier route and just install an older version of Ruby that didn&amp;rsquo;t have the problem with Sinatra, since I wanted a setup I could replicate easily, and editing the server.rb each time I installed wasn&amp;rsquo;t what I was going for. I downloaded 1.9.2-rc2 from &lt;a href="http://ftp.ruby-lang.org//pub/ruby/1.9/"&gt;http://ftp.ruby-lang.org//pub/ruby/1.9/&lt;/a&gt;, compiled it and it works:&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;[evan@evanfc12 ~]$ ruby --version&#10;ruby 1.9.2dev (2010-07-11 revision 28618) [x86_64-linux]&#10;[evan@evanfc12 ~]$ ruby hi.rb ^C&#10;[evan@evanfc12 ~]$ cat hi.rb&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;require &amp;lsquo;sinatra&amp;rsquo;&lt;/p&gt;</description></item><item><title>Trying to teach myself Ruby (again)</title><link>https://evan.wtf/2010/10/07/trying-to-teach-myself-ruby-again/</link><pubDate>Thu, 07 Oct 2010 17:09:28 +0000</pubDate><guid>https://evan.wtf/2010/10/07/trying-to-teach-myself-ruby-again/</guid><description>&lt;p&gt;Now that I have a real web project to work on I figured it&amp;rsquo;s a good time to try and teach myself Ruby again. Sinatra seems to be the new hotness so that&amp;rsquo;s what I&amp;rsquo;m trying, but so far things aren&amp;rsquo;t going quite as I expected. Everything appears to be installed, but when I run the &amp;ldquo;Hello, World!&amp;rdquo; script, the webserver doesn&amp;rsquo;t start as it&amp;rsquo;s apparently supposed to do:&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;[evan@ehoffman 16:59:34 ~]$ ruby --version&#10;ruby 1.9.2p0 (2010-08-18 revision 29036) [x86_64-linux]&#10;[evan@ehoffman 16:59:39 ~]$ irb&#10;irb(main):001:0&amp;gt; require &amp;#39;sinatra&amp;#39;&#10;=&amp;gt; true&#10;irb(main):002:0&amp;gt;&#10;You have new mail in /var/spool/mail/evan&#10;[evan@ehoffman 17:00:20 ~]$ cat hi.rb&#10;#require &amp;#39;rubygems&amp;#39;&#10;require &amp;#39;sinatra&amp;#39;&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;get &amp;lsquo;/&amp;rsquo; do&#10;&amp;ldquo;Hello World&amp;rdquo;&#10;end&#10;[evan@ehoffman 17:00:24 ~]$ ruby hi.rb&#10;[evan@ehoffman 17:00:33 ~]$&lt;/p&gt;</description></item><item><title>Amazon EC2 - ext3 mkfs takes 30+ minutes?</title><link>https://evan.wtf/2010/08/02/amazon-ec2-ext3-mkfs-takes-30-minutes/</link><pubDate>Mon, 02 Aug 2010 11:33:42 +0000</pubDate><guid>https://evan.wtf/2010/08/02/amazon-ec2-ext3-mkfs-takes-30-minutes/</guid><description>&lt;p&gt;I&amp;rsquo;ve been playing around with Amazon EC2 for a new project I&amp;rsquo;m working on and so far I&amp;rsquo;m really impressed. One thing I&amp;rsquo;ve noticed, however, is that it takes forever to create an ext3 filesystem on a new volume. For example, the below command took over 30 minutes to create the filesystem on a 300 GB volume:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;h1 id="mke2fs--j--m0-devsdf1"&gt;mke2fs -j -m0 /dev/sdf1&lt;a class="heading-anchor" href="#mke2fs--j--m0-devsdf1" aria-label="Link to this section"&gt;&#10; &lt;svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2.2"&#10; stroke-linecap="round" stroke-linejoin="round" aria-hidden="true" focusable="false"&gt;&#10; &lt;path d="M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71"/&gt;&#10; &lt;path d="M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71"/&gt;&#10; &lt;/svg&gt;&#10; &lt;/a&gt;&#10;&lt;/h1&gt;&#10;&lt;p&gt;mke2fs 1.40.4 (31-Dec-2007)&#10;Filesystem label=&#10;OS type: Linux&#10;Block size=4096 (log=2)&#10;Fragment size=4096 (log=2)&#10;39321600 inodes, 78642183 blocks&#10;0 blocks (0.00%) reserved for the super user&#10;First data block=0&#10;Maximum filesystem blocks=4294967296&#10;2400 block groups&#10;32768 blocks per group, 32768 fragments per group&#10;16384 inodes per group&#10;Superblock backups stored on blocks:&#10;32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,&#10;4096000, 7962624, 11239424, 20480000, 23887872, 71663616&lt;/p&gt;</description></item><item><title>Outlook 2007 &amp; Exchange 2010 Autodiscover SSL certificate error annoyance</title><link>https://evan.wtf/2010/07/27/outlook-2007-exchange-2010-autodiscover-ssl-certificate-error-annoyance/</link><pubDate>Tue, 27 Jul 2010 11:51:54 +0000</pubDate><guid>https://evan.wtf/2010/07/27/outlook-2007-exchange-2010-autodiscover-ssl-certificate-error-annoyance/</guid><description>&lt;p&gt;One of the more annoying side effects of migrating my mailbox to Exchange 2010 has been the nagging of Outlook 2007&amp;rsquo;s Autodiscovery feature. Now, every time I start Outlook I get hit with a certificate error for autodiscover.domain.com. Now, autodiscover.domain.com is a CNAME to mail.domain.com, which is the OWA URL for the CAS. The SSL certificate is valid - but it&amp;rsquo;s valid for mail.domain.com. I could buy &lt;a href="http://affiliate.godaddy.com/redirect/57C9CDCFC2D9286731DFC80559FF75B02AA47A2EADDA2D5CC2407E21C4FBC792" title="Go Daddy $12.99 SSL Sale!"&gt;a SSL certificate from GoDaddy for $12.99&lt;/a&gt; (an insanely great price, btw) for &amp;ldquo;autodiscover&amp;rdquo; but that would also require using another IP address on the CAS (since you can can only bind one SSL certificate to an IP:port pair), and that seems like a waste of an IP address.&lt;/p&gt;</description></item><item><title>vCenter: Error parsing the server "(server IP)" "clients.xml" file</title><link>https://evan.wtf/2010/06/23/vcenter-error-parsing-the-server-clients-xml-file-2/</link><pubDate>Wed, 23 Jun 2010 12:18:59 +0000</pubDate><guid>https://evan.wtf/2010/06/23/vcenter-error-parsing-the-server-clients-xml-file-2/</guid><description>&lt;p&gt;I got the above error today after running Windows Update on my XP VM a few days ago. A quick search showed that the error is caused by a Microsoft update to the .NET framework. To resolve it, remove update KB980773 (Add/Remove programs, make sure &amp;ldquo;Show Updates&amp;rdquo; is checked; KB980773 is under &amp;ldquo;Microsoft .NET Framework 2.0 Service Pack 2&amp;rdquo;). I removed it and was able to log in without problems.&lt;/p&gt;</description></item><item><title>vCenter: Error parsing the server "(server IP)" "clients.xml" file</title><link>https://evan.wtf/2010/06/23/vcenter-error-parsing-the-server-clients-xml-file/</link><pubDate>Wed, 23 Jun 2010 12:18:59 +0000</pubDate><guid>https://evan.wtf/2010/06/23/vcenter-error-parsing-the-server-clients-xml-file/</guid><description>&lt;p&gt;I got the above error today after running Windows Update on my XP VM a few days ago. A quick search showed that the error is caused by a Microsoft update to the .NET framework. To resolve it, remove update KB980773 (Add/Remove programs, make sure &amp;ldquo;Show Updates&amp;rdquo; is checked; KB980773 is under &amp;ldquo;Microsoft .NET Framework 2.0 Service Pack 2&amp;rdquo;). I removed it and was able to log in without problems.&lt;/p&gt;</description></item></channel></rss>