Perhaps the rails gem 2.0.2 is installed for your user but not
systemwide. So its in ~/.gem rather than /usr/lib/ruby/gems/1.8
On Wed, Apr 29, 2009 at 3:51 AM, Alexander Melle wrote:
> Hi,
>
> I'm running a ubuntu 8.04.2 LTS server. Using ruby 1.8.6 and Rails 2.0.2
> I added the mongrel_rails st
Zed Shaw wrote:
> Bradley Taylor shot me this *goldmine* of ugly ugly ugly dogs:
>
> http://www.sonoma-marinfair.org/uglydogvote.shtml
>
> I *have* to use one of these for the Mongrel BUGS Mascot. He'll go on
> our bug list page and replace the little beetles on the left.
>
> Pick the dog you t
James Punteney wrote:
> I've installed pen and mongrel with mongrel_cluster (as gems) on
> Debian sarge. I can run everything from the command line fine
> including starting from the /etc/init.d/mongrel_cluster script
>
> On boot though mongrel_cluster fails with this msg:
> /usr/local/lib/site_ru
On 5/31/06, Alison Rowland <[EMAIL PROTECTED]> wrote:
> Thanks, configuring with -c did the trick!
>
> But now I've got a different problem: I can't get the startup script
> to work at system reboot. It's in /etc/init.d, and it works like a
> charm when I call it from the command line. I'm on Ubunt
Alison Rowland wrote:
> Hi,
>
> I'm trying to setup my mongrel clusters to start on boot. I have
> followed the instructions under the "On Boot Initialization Setup"
> section at http://mongrel.rubyforge.org/docs/mongrel_cluster.html.
>
> When I try to start it up, I get the following error:
James Moore wrote:
> mongrel_rails cluster::start doesn't seem to pay attention to whether or not
> the processes exist or not. If you run it twice, the first set of processes
> are created, then then second run will overwrite the log/{pidfiles} files
> with the new process numbers. Problem is th
