Posterous theme by Cory Watilo

channel 3: open failed: connect failed: Connection refused

Recently I needed to connect to a clients MySQL server on a Debian box to validate some data. I had SSH access to said box so I thought I would just create a SSH tunnel and forward it to a port other than 3306 since I have a local MySQL instance running on the default port. Below is the command I was attempting to use

This would produce the message 'channel 3: open failed: connect failed: Connection refused' in the terminal window that was ssh'd into the remote server when attempting a test connection. After a lot of digging I came across this insightful post that suggested the problem may be that the remote MySQL server was bound to an ip address other than 127.0.0.1. I checked the ip address the MySQL server was bound to and sure enough it was the private server ip address and not 127.0.0.1. A quick change of my command to

ssh -L 3307:10.12.34.567:3306 root@12.345.67.890

and I was in business. The moral of the story? Do not assume your database server is bound to 127.0.0.1. You never know how a particular host will configure the MySQL server.

EntitySpaces On ormbattle.net

We frequently get ask for performance benchmarks on our forums. We typically try to avoid this as performance metrics from the company who is producing the product are dubious at best. We have been looking over ormbattle.net's performance metrics for a while now and we feel they are pretty fair comparison amongst the top .net ORM's. The results should be live pretty soon, however if you want a detailed break down of the EntitySpaces results head on over to our blog and check them out. As you can see EntitySpaces is very fast already and we will be continuing to optimize the areas where we are not at the top of the stack.

Don't forget to reference the 64 bit version of aspnet_isapi.dll if you are running your sites app pool in 64 bit mode.

Yesterday I had a client report an issue that I needed to debug locally. This particular piece of functionality required a wildcard mapping to intercept and inspect all 404 errors. The production site is running on IIS 6 in 32 bit mode. My local development environment has the site running in classic mode on IIS 7. So when attempting to setup the wildcard mapping locally windows will by default open up the aspnet_isapi.dll found int the C:\Windows\Microsoft.NET\Framework\v2.0.50727 folder. This is fine if you are running your site in 32 bit mode, however this is not the aspnet_isapi.dll used if your site is running under 64 bit mode. Instead you should reference the aspnet_isapi.dll found in C:\Windows\Microsoft.NET\Framework64\v2.0.50727. I hope this saves you the time and headache it took me to realize this was my problem.

The EntitySpaces Team Blog - EntitySpaces ORM 2010 Official Release

EntitySpaces ORM 2010 Official Release

We are pleased to announce the release of EntitySpaces 2010. EntitySpaces 2009 and 2010 run side by side just fine, so you can have them both installed. The official release is version 2010.1.0628.0 and is available for purchase now (or download by existing customers).

Glad to get this one out the door, go get it folks!