Hi, I figured out what the problem was in my case. It turned out that the mongrel gem hadn't installed the mongrel_rails executable for some reason.
-- Tobi On 22.01.2009, at 19:13, aawilson wrote: > > Hello all, > > I'm having this exact problem (albeit with rails 2.0.2--I can't > upgrade this particular app without breaking things there's no money > to fix). Any ideas? > > Thanks, > > A. Wilson > > On Jan 16, 12:41 pm, Tobias Knaup <[email protected]> wrote: >> Hi all, >> >> I set up a standard Capistrano deployment on a new host. >> To start the Mongrels, "script/spin" calls "script/process/spawner >> mongrel". >> It prints a few lines as if everything were normal, however the >> mongrels are not started and it doesn't create any files in log or >> tmp >> that would give me a clue on what happened. >> If I start Mongrel via script/server -e production everything works >> as >> expected. >> Any hints on where to find debugging output? >> BTW I'm running 2.1.2. >> >> Thanks, >> >> Tobi > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
