Pat,

Unfortunately that is an Apache thing, what it does is determine that the service it is connecting to as a proxy is down, and it remembers that it is down.

You would see in the apache error_log (for example)

[Sat Feb 16 11:55:38 2008] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:4485 (xxx.xxxxx.xxx) fad [Sat Feb 16 11:55:38 2008] [error] ap_proxy_connect_backend disabling worker for (xxx.xxxxx.xxx) [Sat Feb 16 11:55:38 2008] [error] proxy: HTTP: disabled connection for (xxx.xxxxx.xxx)

Sometimes, a hard refresh after starting/stopping typo will resolve it without restarting apache. However that is really a limitation of apache and has nothing to do with mongrel or typo. :(

As far as your init script, it looks fine... you might have a case where when you stop apache it doesn't kill all of it's children and the restart fails... not very likely since it's a restart but I've seen it happen.

BTW, I just did that, it disabled it, re-started typo and it started working again without restarting apache... running Apache 2.2.8

Hope that helps.

Scott

On Feb 16, 2008, at 8:17 AM, Pat Ferrel wrote:

I have typo running on mongrel proxied thru apache2. But I have two problems: If a page request comes in while mongrel/typo is down I get an error but when typo comes back up I see it on the port mongrel uses but apachecontinues to give the error. I have to restart apache to get things back in sync. Why? What form should my sysv init.d scripts take? I created the one below to get around my apache restart problem but I see other talk about starting mongrel instead of typo on reboot. Which is right? Can someone point me to a good init.d script that can be used for typo?

#!/bin/bash
# Starts the ruby mongrel server that runs the occamsmachete blog
#

case "$1" in
start)  cd /home/pat/blog
        typo start .
    /etc/init.d/apache2 restart
        ;;
stop)   cd /home/pat/blog
        typo stop .
        ;;
restart)  cd /home/pat/blog
        typo restart .
    /etc/init.d/apache2 restart
        ;;
sweep_cache)  cd /home/pat/blog
        typo sweep_cache .
        ;;
*) log_action_msg "Usage: /etc/init.d/typo {start|stop|restart| sweep_cache}"
        exit 2
        ;;
esac
exit 0


I guess this is a mongrel question but thought I’d try first here in case another typo user has run into this. !DSPAM: 47b71d137561804284693!
_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list

!DSPAM:47b71d137561804284693!

_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list

Reply via email to