The haters crawl out of the woodwork on mod_rails project

There has never been a statue erected to honor a critic.
- Ziglar, Zig

I couldn’t believe that someone would have the gall to actually go on record with grouses as trite as these against the creators of mod_rails … but they did

Basically here are their complaints about Phusion Passenger/mod_rails

- Their product has ‘Enterprise’ in the title
- They shouldn’t be up to version 2.0 already (yes … they actually said that)
- They release FREE products ‘late’ (late being an excruciating 2 weeks)
- They’d like for them them to be more ‘modest’ (like they haven’t heard of DHH)
- The marketing seems too slick and something ‘fishy’ is going on because they’re trying to make money with an Enterprise ready version of Passenger/mod_rails?!?!
- The ‘rails community’ will not embrace mod_rails because of these laughable quibbles … I guess these guys don’t count as part of the ‘rails community’ right?

ridiculous.

PS: Note that the original ‘rant’ appeared on Ruby flow, where it was rightly eviscerated

mod rails Passenger 2.0 RC2 released … even more stable?

The kickass developers over at Phusion have released an update to Phusion passenger (or as I prefer to call it … Apache mod rails).

You can see the list of original improvements here

It seems that this particular problem with mod-rails hanging after a few hours and taking down apache with it (I experienced this in an apache deployment that I tried personally … and its a bit scary) was part of the motivation behind the original mod_rails/Passenger Release Candidate. Continue reading

(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443

I ran into this problem after I installed mod-rails on a cent OS server.

To get my changes to take … I kept running

httpd -k graceful

and it kept working until, all of a sudden, it didn’t.

This was the error I got

[XXXX@XXXXXXXXX]# httpd -k graceful
httpd not running, trying to start
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
unable to open logs

argh!

Then I found this marvellous blog posting on how to fix the “Address already in use: make_sock: could not bind to address – Apache – HTTPD Error”

Here is what I did. (click to enlarge)

worked like a charm too.