RailsSpawnMethod per virtual host
7 views
Skip to first unread message
johnsbrn
Dec 19, 2008, 4:11:52 PM12/19/08
to Phusion Passenger Discussions
I have a pressing need for per virtual host assignment of
RailsSpawnMethod. Would this require significant changes? I'd hate to
have to resort to running a couple of mongrels just for image
processing, but there is a serious issue with rmagick and smart
spawning.
RailsSpawnMethod. Would this require significant changes? I'd hate to
have to resort to running a couple of mongrels just for image
processing, but there is a serious issue with rmagick and smart
spawning.
Hongli Lai
Dec 19, 2008, 4:46:16 PM12/19/08
to phusion-...@googlegroups.com
johnsbrn wrote:
> I have a pressing need for per virtual host assignment of
> RailsSpawnMethod. Would this require significant changes?
> I have a pressing need for per virtual host assignment of
> RailsSpawnMethod. Would this require significant changes?
It already is per-virtual host.
--
Phusion | The Computer Science Company
Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)
johnsbrn
Dec 19, 2008, 5:26:13 PM12/19/08
to Phusion Passenger Discussions
Perfect, you might want to update the docs, they list it as a global
option
On Dec 19, 1:46 pm, Hongli Lai <hon...@phusion.nl> wrote:
> johnsbrn wrote:
> > I have a pressing need for per virtual host assignment of
> > RailsSpawnMethod. Would this require significant changes?
>
> It already is per-virtual host.
>
> --
> Phusion | The Computer Science Company
>
> Web:http://www.phusion.nl/
> E-mail: i...@phusion.nl
option
On Dec 19, 1:46 pm, Hongli Lai <hon...@phusion.nl> wrote:
> johnsbrn wrote:
> > I have a pressing need for per virtual host assignment of
> > RailsSpawnMethod. Would this require significant changes?
>
> It already is per-virtual host.
>
> --
> Phusion | The Computer Science Company
>
> Web:http://www.phusion.nl/
Message has been deleted
johnsbrn
Dec 19, 2008, 6:52:40 PM12/19/08
to Phusion Passenger Discussions
Actually, I see it now. Maybe I just missed it.
jeroen houben
Dec 20, 2008, 6:43:11 AM12/20/08
to Phusion Passenger Discussions
just out of interest, could you explain the issue with RMagick? Which
version of RMAgick and passenger are you using?
version of RMAgick and passenger are you using?
johnsbrn
Dec 20, 2008, 10:24:17 AM12/20/08
to Phusion Passenger Discussions
It's covered in this thread
http://groups.google.com/group/phusion-passenger/browse_thread/thread/85a51677c89db7e8/e118444753b4ea7a?lnk=gst&q=rmagick#e118444753b4ea7a
called "frozen processes". Basically in smart spawning mode the rails
process locks up and stops responding. I had a hard time debugging it
because killing it with SIGABRT didn't kill the process or produce a
stack trace in the log. I did get some information which pointed to a
problem with GC.start, but when I modified the code to use the new
rmagick destroy functions the process still froze up. At this point
I'm not even sure how to continue debugging it. It's definitely an
intermittent problem, it doesn't happen every time, but happens often
enough that it will lock up all the Rails processes in a short period
of time.
http://groups.google.com/group/phusion-passenger/browse_thread/thread/85a51677c89db7e8/e118444753b4ea7a?lnk=gst&q=rmagick#e118444753b4ea7a
called "frozen processes". Basically in smart spawning mode the rails
process locks up and stops responding. I had a hard time debugging it
because killing it with SIGABRT didn't kill the process or produce a
stack trace in the log. I did get some information which pointed to a
problem with GC.start, but when I modified the code to use the new
rmagick destroy functions the process still froze up. At this point
I'm not even sure how to continue debugging it. It's definitely an
intermittent problem, it doesn't happen every time, but happens often
enough that it will lock up all the Rails processes in a short period
of time.
Hongli Lai
Dec 20, 2008, 11:13:55 AM12/20/08
to phusion-...@googlegroups.com
johnsbrn wrote:
> It's covered in this thread
> http://groups.google.com/group/phusion-passenger/browse_thread/thread/85a51677c89db7e8/e118444753b4ea7a?lnk=gst&q=rmagick#e118444753b4ea7a
> called "frozen processes". Basically in smart spawning mode the rails
> process locks up and stops responding. I had a hard time debugging it
> because killing it with SIGABRT didn't kill the process or produce a
> stack trace in the log. I did get some information which pointed to a
> problem with GC.start, but when I modified the code to use the new
> rmagick destroy functions the process still froze up. At this point
> I'm not even sure how to continue debugging it. It's definitely an
> intermittent problem, it doesn't happen every time, but happens often
> enough that it will lock up all the Rails processes in a short period
> of time.
> It's covered in this thread
> http://groups.google.com/group/phusion-passenger/browse_thread/thread/85a51677c89db7e8/e118444753b4ea7a?lnk=gst&q=rmagick#e118444753b4ea7a
> called "frozen processes". Basically in smart spawning mode the rails
> process locks up and stops responding. I had a hard time debugging it
> because killing it with SIGABRT didn't kill the process or produce a
> stack trace in the log. I did get some information which pointed to a
> problem with GC.start, but when I modified the code to use the new
> rmagick destroy functions the process still froze up. At this point
> I'm not even sure how to continue debugging it. It's definitely an
> intermittent problem, it doesn't happen every time, but happens often
> enough that it will lock up all the Rails processes in a short period
> of time.
I've noted this problem on the wiki:
http://github.com/FooBarWidget/passenger/wikis/mptnmis-mysterious-problems-that-need-massive-investigations
We'll take a look at this when we have the time.
--
Phusion | The Computer Science Company
Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Reply all
Reply to author
Forward
0 new messages