Moved from EE

My Dreamhost server was upgraded awhile ago, and ever since then I have had nothing but issues with my installation of EE.  A lot of other things had issues too, but I was easily able to reinstall and everything worked.  Sadly, that was not an option for EE as my yearly download had expired.  No way was I going to pay just to get things back to where they were.

Needless to say I have been wanting to migrate over, and just never really had the time to do it.

Well, I did it today because I’ve been wanting to post a few things.  I think everything migrated over fairly well, but there are definitely a few issues.  I really wanted to use some rewrite logic to keep all the inbound links working, but I’m afraid that just isn’t going to happen.

Without further ado, hopefully there were be some fun tech updates soon!

links for 2007-01-16

  • An interesting backup solution
    (tags: computers backup software)
  • An interesting light fixture.  If only I could read japanese and it wasn’t in flash.
    (tags: lighting design)

 

Published
Categorized as links

The Site and Other Updates

Ok, so the site is back up.  That was incredibly easy.  As far as I can tell, there was 0 downtime.  The only thing that may have looked strange is that I didn’t have the most current database on the dreamhost server.  But, a simply backup and restore fixed that.  Also, aaron spruit (.com) is up and running on the new host also.  I realized that the two databases could really cause headaches if I didn’t do them both now, especially if I added an entry on both sites.  I’ve updated my registrar with the new name servers, but since that takes awhile to propagate, I updated my current names servers to use the new hosted site, instead of the other one.  That way everyone hits the new site right away, instead of some going one place and others going to another place.

In other news, now that I have this running under Apache, I’m going to start playing with the .htaccess file.  What I’m hoping to accomplish is to get rid of all the extraneous crap on the URLs to this site.  Therefore, if you are reading this through RSS, the feed may go down.  Just come visit the site and grab the new URL of it.  It will probably end up being https://www.rebelpeon.com/rss_2.0/ though, instead of https://www.rebelpeon.com/index.php?/rebelpeon/rss_2.0/.  This should also help with search sites too, since they tend to have a hard time with the URL Query Strings.

Site Downtime

I’m hoping it won’t be for too long, or at all, but I’m going to attempt to finish the migration of my site to dreamhost.  It should progress without any downtime, but knowing my luck, there will be.  However, aaron spruit (.com) will be remain at the same place until everything is working smoothly with this site.  Moving aaron spruit (.com) won’t take much at all as both of these sites run off the same CMS and MySQL database.  It’s just moving the first one that’s a pain.

You’ll know when everything is propagated because there should be dreamhost banner on the bottom of the new site.

ISA 2006 Part 2

I still haven’t found any decent solution to the compression, but I did find a solution to publishing NTLM websites.  Basically, ISA 2004 didn’t have any pre-authentication, where ISA 2006 does.  Why I wasn’t experiencing any of this on my websites was because the ISA machine is on the same domain.  In order to fix this, I had to use LDAP pre-authentication.  I used part of an article posted on isaserver.org.  It got me working to a certain extent, but then I had to play with it a little bit more.  No big deal, it’s all working now. 

Now just to fix the compression part…

ISA 2006 Compression

As I noted over at aaron spruit (.com), I had a few problems with the (new) ISA server.  Last weekend I finally got around to upgrading to ISA 2006.  I’ve had the bits for awhile, but I never actually took the time to install it.

Anyways, there were problems right off the bat.  I successfully backed up all of the ISA 2004 configurations, however, going from ISA 2004 EE to ISA 2006 EE (single box setup) isn’t possible in a nice upgrade path.  The configuration store for ISA has to be completely uninstalled and then reinstalled, but the rest can be simply upgraded.  So a complete uninstall and reinstall was required.  No big deal, as I had the export.

Install ISA 2006, not a problem, and then attempt to import the settings from ISA 2004, no luck.  Well, not a big deal, it’s not like the configuration is that complex.  I get everything setup minus Aaron’s OWA because it’s not cooperating, and then leave it at that.

On Tuesday it appeared as if the internet had gone out at the compound as neither of us were able to access any hosted websites.  When I finally get home, I make sure that our IP address hadn’t changed or anything, and I was able to get out just fine.  It seemed odd, so I logged into the ISA box to find that it was denying people.  I attempt to stop the firewall service, but it hangs in the stopping state, so I just restart the machine.  It comes back online, and all is fine.  Later I look into the event logs and see the following two events repeated whenever someone hit a website starting at around 1PM CST.


Event Type: Warning
Event Source: Microsoft ISA Server Web Proxy
Event Category: None
Event ID: 23001
Date: 11/7/2006
Time: 8:27:02 PM
User: N/A
Computer: RBLPN-ISA
Description:
ISA Server was unable to compress a response body from https://www.rebelpeon.com because the following error occurred: Unspecified error
. This error generally occurs because the available memory is insufficient for completing the compression process.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: Microsoft ISA Server Web Proxy
Event Category: None
Event ID: 23006
Date: 11/7/2006
Time: 8:27:02 PM
User: N/A
Computer: RBLPN-ISA
Description:
The Compression filter cannot handle a response because the allocated memory currently used for compression reached its limit. The memory allocated for compression is specified by the following registry values under the HKLMSoftwareMicrosoftRATStingrayDebugW3Filter key: COMPRESS_MEMORY_ALLOC_MBYTES (by default, 256) and COMPRESS_MEMORY_POOL_BLOCKS (by default, 200).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Does anyone have any idea why this would be happening?  Obviously I could go in and change the default settings, but wouldn’t that just stand to reason it would extend the window that ISA serves website requests?  When creating a web publishing rule, the default is to have compression enabled.  Heck, I want it enabled, since it works with OWA now too.  But why isn’t it releasing any of this memory?  It’s not as though the four or five websites hosted here receive that much traffic.

As of now, compression has been disabled, but there’s still one other problem that remains, Aaron’s OWA.  I can’t get ISA 2006 to function the same as 2004 with respect to his OWA site.  Before, I set up a simple web publishing rule that forwarded requests that hit his OWA external site to the internal one.  He uses Windows Auth on it, and 2004 handled this fine.  Now, with 2006, I can’t get it to do NTLM pass-through.  I can either get it to deny the website because it requires authentication, or I can get it to prompt you with the challenge, but the challenge is for credentials used on the ISA box, not on his OWA box (different domain).  All I want is for it to allow the authentication challenge to pass through.  How else are you supposed to have Windows Auth secured websites sit behind the ISA 2006 box when they’re on a different domain, or a standalone machine?

Published
Categorized as web

links for 2006-09-19

  • (tags: graph government taxes)

 

Published
Categorized as links