[Locomotive-users] App won't start using mongrel

[Paul Welty]

Yes, but not on OS X. I am going to be using Railsmachine for production and
am trying to get my environment in Locomotive matched-up to make deployment
easier.

The trouble is, because of all the OS X-related problems with Mongrel, now I
can¹t use Mongrel at all anymore within Locomotive. D¹oh!

-Paul



On 9/20/06 4:36 PM, "Steven Talcott Smith" <steve at talcottsystems.com> wrote:

> Does anyone have Mongrel working properly on OS X in production?   I tried and
> gave up temporarily as was under a deadline to go live and I have Apache2
> proxying to Locomotive in "production" mode.  I need to get off this for a
> number of reasons -- not least because I would like more orderly restarts when
> I push code -- to say nothing of the fact that Ryan has stated Loco is not
> intended to be used for production.
> 
> I anticipate a significant increase in traffic over the next few weeks so
> mongrel/capistrano is back on my priority list.
> 
> Paul, I am very keen to hear of your experience...  are you trying mongrel for
> production?
> 
> Best,
> 
> Steven
> 
> 
> On Sep 20, 2006, at 4:09 PM, Paul Welty wrote:
> 
>>  So, I uninstalled the two older versions, and now I get...
>>  
>>  
>> /Applications/Locomotive2/Bundles/rails112rmagick_ppc.locobundle/framework/li
>> b/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/rails.rb:38: uninitialized
>> constant Mongrel::HttpHandler (NameError)
>>          from 
>> /Applications/Locomotive2/Bundles/rails112rmagick_ppc.locobundle/framework/li
>> b/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require'
>>          from 
>> /Applications/Locomotive2/Bundles/rails112rmagick_ppc.locobundle/framework/li
>> b/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:10
>>          from 
>> /Applications/Locomotive2/Bundles/rails112rmagick_ppc.locobundle/framework/bi
>> n/mongrel_rails:18
>>  
>>  
>>  
>>  
>>  On 9/20/06 4:01 PM, "Paul Welty" <ponch at paulwelty.com> wrote:
>>  
>>  
>>> Using ³mongrel_rails start ³ I get this:
>>>  
>>>  
>>> /Applications/Locomotive2/Bundles/rails112rmagick_ppc.locobundle/framework/l
>>> ib/ruby/site_ruby/1.8/rubygems.rb:149:in `activate': can't activate mongrel
>>> (= 0.3.13.3), already activated mongrel-0.3.13.4] (Gem::Exception)
>>>          from 
>>> /Applications/Locomotive2/Bundles/rails112rmagick_ppc.locobundle/framework/l
>>> ib/ruby/site_ruby/1.8/rubygems/custom_require.rb:26:in `require'
>>>          from 
>>> /Applications/Locomotive2/Bundles/rails112rmagick_ppc.locobundle/framework/l
>>> ib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:10
>>>          from 
>>> /Applications/Locomotive2/Bundles/rails112rmagick_ppc.locobundle/framework/l
>>> ib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require'
>>>          from 
>>> /Applications/Locomotive2/Bundles/rails112rmagick_ppc.locobundle/framework/l
>>> ib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:9
>>>          from 
>>> /Applications/Locomotive2/Bundles/rails112rmagick_ppc.locobundle/framework/b
>>> in/mongrel_rails:18
>>>  
>>>  I tried restarting Loco and pushing/not pushing the run button. I always
>>> get the same error.
>>>  
>>>  
>>>  
>>>  
>>>  On 9/20/06 3:15 PM, "Ryan Raaum" <ryan.raaum at gmail.com> wrote:
>>>  
>>>  
>>>> 
>>>>  
>>>>  On 9/20/06, Paul Welty <ponch at paulwelty.com> wrote:
>>>>  
>>>>> I was able to successfully run my loco app with mongrel with the "server:
>>>>> mongrel" addition to locomotive.yml.
>>>>>  
>>>>>  Then I updated the mongrel gem with "sudo gem update mongrel" to 0.3.13.3
>>>>> <http://0.3.13.3> . Then the app wouldn't start. Clicking "run" results in
>>>>> no changes to the window, no app, no logs, no nuttin'.
>>>>>  
>>>>>  I updated the gem again to 0.3.13.4 <http://0.3.13.4> . Same problem. The
>>>>> previous gem, the one in Locomotive to start with, is 0.3.12.4
>>>>> <http://0.3.12.4> .
>>>>>  
>>>>>  When I look at "gem list ‹local", I see version numbers for all three
>>>>> mongrel gems, viz. "mongrel (0.3.13.4 <http://0.3.13.4> , 0.3.13.3
>>>>> <http://0.3.13.3> , 0.3.12.4 <http://0.3.12.4> )".
>>>>>  
>>>>>  This is similar to how rails appears since I updated to 1.1.6.
>>>>> Soooo....I'm wondering if I need to specify the gem version to use in
>>>>> locomotive.yml to get the server to start.
>>>>>  
>>>>>  Or, maybe there is something else I'm missing (a likely possibility!).
>>>>>  
>>>>>  I'd be grateful for any help.
>>>>>  
>>>> 
>>>>  Hi,
>>>>  
>>>>  I suspect that something has changed in the way mongrel is started between
>>>> 0.3.12 and the current versions - but I haven't looked at it in detail.
>>>>   Can you start mongrel ok from the command line?
>>>>  
>>>>  -r
>>>>  
>>>>  
>>>>> -Paul
>>>>>  
>>>>>  _______________________________________________
>>>>>  Locomotive-users mailing list
>>>>>  Locomotive-users at lists.raaum.org
>>>>>  <mailto:Locomotive-users at lists.raaum.org>
>>>>>  http://lists.raaum.org/mailman/listinfo/locomotive-users
>>>>>  
>>>>>  
>>>>>  
>>>> 
>>>>  
>>>>  
>>> 
>>>  
>>>  
>>> 
>>> _______________________________________________
>>>  Locomotive-users mailing list
>>>  Locomotive-users at lists.raaum.org
>>>  http://lists.raaum.org/mailman/listinfo/locomotive-users
>>>  
>> 
>>  
>> _______________________________________________
>> Locomotive-users mailing list
>> Locomotive-users at lists.raaum.org
>> http://lists.raaum.org/mailman/listinfo/locomotive-users
>>  
> 
> 
> 
> _______________________________________________
> Locomotive-users mailing list
> Locomotive-users at lists.raaum.org
> http://lists.raaum.org/mailman/listinfo/locomotive-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://one.textdrive.com/pipermail/locomotive-users/attachments/20060920/0200b00d/attachment-0001.htm