From rochkind at jhu.edu  Mon Nov  2 12:43:43 2009
From: rochkind at jhu.edu (Jonathan Rochkind)
Date: Mon, 02 Nov 2009 12:43:43 -0500
Subject: [Mongrel] mongrel, prefix, and latest versions of Rails?
In-Reply-To: <7d3c3deca05ee04044aa954de4409386@ruby-forum.com>
References: <3a96987f0809031617n7bfb33a1kd80ca8c51ec516cf@mail.gmail.com>
	<4ebd6478ed2a2c5a210b0b58987a03de@ruby-forum.com>
	<5801C7961B62634F9D3513FBFC860C6C03073922@CCHSCLEXMB55.cc.ad.cchs.net>
	<7d3c3deca05ee04044aa954de4409386@ruby-forum.com>
Message-ID: <4AEF1A4F.3040800@jhu.edu>

Is there a version of mongrel out yet that has a --prefix that works 
with latest versions of Rails?

When I do a "gem install mongrel", I get mongrel 1.1.5.

Using Rails 2.3.4, if I try launching mongrel with "--prefix 
/something", I get an error about:

 uninitialized constant ActionController::AbstractRequest


As this problem was first reported a year ago, I'm hoping there's a 
version of mongrel that handles it, that I just haven't managed to 
actually install with a naive "gem install mongrel", it's hiding 
somewhere else?

Or is this really not fixed in a mongrel release yet?

Any advice welcome.  (I know how to set the prefix in environment.rb 
_instead of_ mongrel command line; but I really want to do it in the 
mongrel command line sometimes).

Jonathan

From lists at ruby-forum.com  Thu Nov 12 05:04:18 2009
From: lists at ruby-forum.com (Geetha Sg)
Date: Thu, 12 Nov 2009 11:04:18 +0100
Subject: [Mongrel] mulitiple rails application with different domain name
Message-ID: <267325d50efe403d753a24902ad2ad23@ruby-forum.com>

I am using Slackware 12.1 OS, I need to deploy two rails applications
(mongrel) with two different domain name with single ip.

for example,

maths.exam.info  -  path is /srv/maths.com/www/

grammar.exam.info  -  path is /srv/grammar.com/www


Herewith I've attached the apache conf files, please find it.

The problem is both the domain goes to maths.exam.info
we could get both sites where mention the port number.

maths.exam.info:8000

grammar.exam.info:8003

How can i get the both sides with out port numbers.

The dns has registered properly.

Thanks
sg..

Attachments:
http://www.ruby-forum.com/attachment/4228/apache1.conf.rtf

-- 
Posted via http://www.ruby-forum.com/.

From rgo at aspgems.com  Thu Nov 12 08:08:37 2009
From: rgo at aspgems.com (Rafael G.)
Date: Thu, 12 Nov 2009 14:08:37 +0100
Subject: [Mongrel] mulitiple rails application with different domain name
In-Reply-To: <267325d50efe403d753a24902ad2ad23@ruby-forum.com>
References: <267325d50efe403d753a24902ad2ad23@ruby-forum.com>
Message-ID: <4AFC08D5.4010505@aspgems.com>

More or less you like it:
  Apache with proxy pass - http://gist.github.com/232869
  Apache with proxy balancer - http://gist.github.com/232872

Choose one and modify to your needs :)

Geetha Sg wrote:
> I am using Slackware 12.1 OS, I need to deploy two rails applications
> (mongrel) with two different domain name with single ip.
>
> for example,
>
> maths.exam.info  -  path is /srv/maths.com/www/
>
> grammar.exam.info  -  path is /srv/grammar.com/www
>
>
> Herewith I've attached the apache conf files, please find it.
>
> The problem is both the domain goes to maths.exam.info
> we could get both sites where mention the port number.
>
> maths.exam.info:8000
>
> grammar.exam.info:8003
>
> How can i get the both sides with out port numbers.
>
> The dns has registered properly.
>
> Thanks
> sg..
>
> Attachments:
> http://www.ruby-forum.com/attachment/4228/apache1.conf.rtf
>
>   


-- 
Rafa


From hassan.schroeder at gmail.com  Thu Nov 12 07:58:26 2009
From: hassan.schroeder at gmail.com (Hassan Schroeder)
Date: Thu, 12 Nov 2009 04:58:26 -0800
Subject: [Mongrel] mulitiple rails application with different domain name
In-Reply-To: <267325d50efe403d753a24902ad2ad23@ruby-forum.com>
References: <267325d50efe403d753a24902ad2ad23@ruby-forum.com>
Message-ID: <4eedb92a0911120458j2d9368e2j2b6f35d6b6a5e942@mail.gmail.com>

On Thu, Nov 12, 2009 at 2:04 AM, Geetha Sg <lists at ruby-forum.com> wrote:
> I am using Slackware 12.1 OS, I need to deploy two rails applications
> (mongrel) with two different domain name with single ip.

> The problem is both the domain goes to maths.exam.info
> we could get both sites where mention the port number.
>
> maths.exam.info:8000
>
> grammar.exam.info:8003
>
> How can i get the both sides with out port numbers.

Configure your virtual hosts properly; ServerName should be e.g.
maths.exam.info and grammer.exam.info.

Also, both vhosts are forwarding to the same mongrel cluster, so
nothing will ever get to the application on port 8003.

HTH,
-- 
Hassan Schroeder ------------------------ hassan.schroeder at gmail.com
twitter: @hassan

From lists at ruby-forum.com  Fri Nov 13 04:32:55 2009
From: lists at ruby-forum.com (Geetha Sg)
Date: Fri, 13 Nov 2009 10:32:55 +0100
Subject: [Mongrel] mulitiple rails application with different domain name
In-Reply-To: <4eedb92a0911120458j2d9368e2j2b6f35d6b6a5e942@mail.gmail.com>
References: <267325d50efe403d753a24902ad2ad23@ruby-forum.com>
	<4eedb92a0911120458j2d9368e2j2b6f35d6b6a5e942@mail.gmail.com>
Message-ID: <2274ba02d33e050cde564dbbd3c46cdd@ruby-forum.com>

Hassan Schroeder wrote:
> On Thu, Nov 12, 2009 at 2:04 AM, Geetha Sg <lists at ruby-forum.com> wrote:
>> I am using Slackware 12.1 OS, I need to deploy two rails applications
>> (mongrel) with two different domain name with single ip.
> 
>> The problem is both the domain goes to maths.exam.info
>> we could get both sites where mention the port number.
>>
>> maths.exam.info:8000
>>
>> grammar.exam.info:8003
>>
>> How can i get the both sides with out port numbers.
> 
> Configure your virtual hosts properly; ServerName should be e.g.
> maths.exam.info and grammer.exam.info.
> 
> Also, both vhosts are forwarding to the same mongrel cluster, so
> nothing will ever get to the application on port 8003.
> 
> HTH,

hi,

let me know how to do that.. i am very basic of ruby hosting..
-- 
Posted via http://www.ruby-forum.com/.

From rgo at aspgems.com  Fri Nov 13 05:44:14 2009
From: rgo at aspgems.com (Rafael G.)
Date: Fri, 13 Nov 2009 11:44:14 +0100
Subject: [Mongrel] mulitiple rails application with different domain name
In-Reply-To: <2274ba02d33e050cde564dbbd3c46cdd@ruby-forum.com>
References: <267325d50efe403d753a24902ad2ad23@ruby-forum.com>	<4eedb92a0911120458j2d9368e2j2b6f35d6b6a5e942@mail.gmail.com>
	<2274ba02d33e050cde564dbbd3c46cdd@ruby-forum.com>
Message-ID: <4AFD387E.5060509@aspgems.com>

Geetha Sg wrote:
> Hassan Schroeder wrote:
>   
>> On Thu, Nov 12, 2009 at 2:04 AM, Geetha Sg <lists at ruby-forum.com> wrote:
>>     
>>> I am using Slackware 12.1 OS, I need to deploy two rails applications
>>> (mongrel) with two different domain name with single ip.
>>>       
>>> The problem is both the domain goes to maths.exam.info
>>> we could get both sites where mention the port number.
>>>
>>> maths.exam.info:8000
>>>
>>> grammar.exam.info:8003
>>>
>>> How can i get the both sides with out port numbers.
>>>       
>> Configure your virtual hosts properly; ServerName should be e.g.
>> maths.exam.info and grammer.exam.info.
>>
>> Also, both vhosts are forwarding to the same mongrel cluster, so
>> nothing will ever get to the application on port 8003.
>>
>> HTH,
>>     
>
> hi,
>
> let me know how to do that.. i am very basic of ruby hosting..
>   
I give you two templates that you can use to configure your server 
replacing "foo" with your data, and the ports with your mongrel ports.

If you don't understand something it's explained in apache documentation 
very well: http://httpd.apache.org/docs/2.2/

Regards!


-- 
Rafa


From lists at ruby-forum.com  Fri Nov 13 06:57:29 2009
From: lists at ruby-forum.com (Geetha Sg)
Date: Fri, 13 Nov 2009 12:57:29 +0100
Subject: [Mongrel] mulitiple rails application with different domain name
In-Reply-To: <4AFD387E.5060509@aspgems.com>
References: <267325d50efe403d753a24902ad2ad23@ruby-forum.com>
	<4eedb92a0911120458j2d9368e2j2b6f35d6b6a5e942@mail.gmail.com>
	<2274ba02d33e050cde564dbbd3c46cdd@ruby-forum.com>
	<4AFD387E.5060509@aspgems.com>
Message-ID: <e6c9b6a72c3302b760ef5d2c4ebdddc4@ruby-forum.com>

Rafael Garc?a wrote:
> Geetha Sg wrote:
>>>> maths.exam.info:8000
>>>
>>> HTH,
>>>     
>>
>> hi,
>>
>> let me know how to do that.. i am very basic of ruby hosting..
>>   
> I give you two templates that you can use to configure your server
> replacing "foo" with your data, and the ports with your mongrel ports.
> 
> If you don't understand something it's explained in apache documentation
> very well: http://httpd.apache.org/docs/2.2/
> 
> Regards!
> 
> 
> --
> Rafa

should i create the  apache_vhost_mongrel_cluster.conf   for both 
applications

I'm using slackware os.

pls help
-- 
Posted via http://www.ruby-forum.com/.

From rgo at aspgems.com  Fri Nov 13 08:04:50 2009
From: rgo at aspgems.com (Rafael G.)
Date: Fri, 13 Nov 2009 14:04:50 +0100
Subject: [Mongrel] mulitiple rails application with different domain name
In-Reply-To: <e6c9b6a72c3302b760ef5d2c4ebdddc4@ruby-forum.com>
References: <267325d50efe403d753a24902ad2ad23@ruby-forum.com>	<4eedb92a0911120458j2d9368e2j2b6f35d6b6a5e942@mail.gmail.com>	<2274ba02d33e050cde564dbbd3c46cdd@ruby-forum.com>	<4AFD387E.5060509@aspgems.com>
	<e6c9b6a72c3302b760ef5d2c4ebdddc4@ruby-forum.com>
Message-ID: <4AFD5972.8020401@aspgems.com>

Geetha Sg wrote:
> Rafael Garc?a wrote:
>   
>> Geetha Sg wrote:
>>     
>>>>> maths.exam.info:8000
>>>>>           
>>>> HTH,
>>>>     
>>>>         
>>> hi,
>>>
>>> let me know how to do that.. i am very basic of ruby hosting..
>>>   
>>>       
>> I give you two templates that you can use to configure your server
>> replacing "foo" with your data, and the ports with your mongrel ports.
>>
>> If you don't understand something it's explained in apache documentation
>> very well: http://httpd.apache.org/docs/2.2/
>>
>> Regards!
>>
>>
>> --
>> Rafa
>>     
>
> should i create the  apache_vhost_mongrel_cluster.conf   for both 
> applications
>
> I'm using slackware os.
>
> pls help
>   


I recommend you to try the simple vhost example gist, after I you need 
more try the other "complex" gist.

I suposse that you're using this file as vhost configuration file(I find 
it there in my slackware):

        /etc/httpd/extra/httpd-vhosts.conf

You can paste this code ( I don't tested it but you get the idea and 
perhaps works fine):

NameVirtualHost *:80

<VirtualHost *:80>
   ServerName maths.exam.info
   DocumentRoot /srv/maths.com/www
 
   ProxyPass / http://127.0.0.1:8000/  
</VirtualHost>

<VirtualHost *:80>
   ServerName grammar.exam.info
   DocumentRoot /srv/grammar.com/www
 
 
   ProxyPass / http://127.0.0.1:8003/
 
</VirtualHost>


I personally (and many people) separate vhosts for domains or applications.
But in your case do it when you understand how it works and what do 
every directive(apache doc for it).

Remember: www directory should be a rails_root/public link

-- 
Rafa


From mliebelt at web.de  Sun Nov 15 07:21:47 2009
From: mliebelt at web.de (Markus Liebelt)
Date: Sun, 15 Nov 2009 13:21:47 +0100
Subject: [Mongrel] Problems with mongrel_service and used account
Message-ID: <op.u3frale6869msv@w4de3gsy0000435.t-systems.com>

Hi everybody,

I try to use in a rails application that is installed with mongrel_service
on windows the win32ole API to access Outlook appointments. This works
well when started from the command line, but does not work when started as
a service.

What should I check in which order to trap down the error?

Bye
	Markus

From luislavena at gmail.com  Sun Nov 15 17:32:02 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Sun, 15 Nov 2009 19:32:02 -0300
Subject: [Mongrel] Problems with mongrel_service and used account
In-Reply-To: <op.u3frale6869msv@w4de3gsy0000435.t-systems.com>
References: <op.u3frale6869msv@w4de3gsy0000435.t-systems.com>
Message-ID: <71166b3b0911151432q660b2bf5hde563895dc6c81e9@mail.gmail.com>

On Sun, Nov 15, 2009 at 9:21 AM, Markus Liebelt <mliebelt at web.de> wrote:
> Hi everybody,
>
> I try to use in a rails application that is installed with mongrel_service
> on windows the win32ole API to access Outlook appointments. This works
> well when started from the command line, but does not work when started as
> a service.
>
> What should I check in which order to trap down the error?
>

Hello Markus,

Services run without privileges for certain things, like create
objects and such.

Since you're executing from the command line and work, means that your
user has access to these OLE objects.

There are two options:

1) Configure the service to run under the same user account (that can
be done from the services management interface)

2) Determine the issue using psexec.

Try to lower the privileges of the prompt and execute the exact same
command line.

The tools you need are psexec, as I mentioned here:

http://rubyforge.org/pipermail/mongrel-users/2007-February/003006.html

See that thread for details.

Please also include in your reply information about your OS (32bits or
64bits), versions of Ruby and the gems installed too.

There is a known issue with 64bits Windows that was solved in latest
gem release, just in case.

Cheers,
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From thomas.allen at litsoftllc.com  Wed Nov 18 12:31:38 2009
From: thomas.allen at litsoftllc.com (Thomas Allen)
Date: Wed, 18 Nov 2009 12:31:38 -0500
Subject: [Mongrel] Requests that make calls from XMLRPC::Client tie up
	Mongrel
Message-ID: <d2a166b00911180931n1da7b049mb324f44e5284f4c6@mail.gmail.com>

Hi Everyone,

I'm running a Rails site on Mongrel and I can't figure out why a
particular type of request ties up Mongrel easily. The requests that
tie up Mongrel call an XML-RPC server like so:

# In the controller
def site_start
  if params[:id]
    @site = Site.find(params[:id])
    @site.site_start
    render :json=>{:success=>true}
  end
end

# In the model
def site_start
  RpcTask.manage(self, 'start')
end

# In RpcTask
def manage(site, task)
  run('manage_task', {
    :site => site.name,
    :site_id => site.id,
    :task => task
  })
end

# which calls
def run(task, task_params = {})
  begin
    server = XMLRPC::Client.new2('http://localhost:9192/')
    result = server.call_async(task,task_params)
    return result
  rescue XMLRPC::FaultException => err
    logger = ActiveRecord::Base.logger
    logger.error(err.faultCode)
    logger.error(err.faultString)
    logger.error(result)
  end
  false
end

If I call the model method directly from the console, the RPC side
responds very quickly:

>> start = Time.now; Site.first.site_start; (Time.now - start).to_s
=> "0.493253"

Removing the body of RpcTask.run results in comparable performance.
Also, by switching from a single mongrel to a four-mongrel cluster, I
was able to get the these actions to perform acceptably but I imagine
that I'm doing something very wrong here to require so much power. Any
ideas?

Thanks,
Thomas Allen

From rochkind at jhu.edu  Wed Nov 18 12:53:22 2009
From: rochkind at jhu.edu (Jonathan Rochkind)
Date: Wed, 18 Nov 2009 12:53:22 -0500
Subject: [Mongrel] Requests that make calls from XMLRPC::Client tie up
 Mongrel
In-Reply-To: <d2a166b00911180931n1da7b049mb324f44e5284f4c6@mail.gmail.com>
References: <d2a166b00911180931n1da7b049mb324f44e5284f4c6@mail.gmail.com>
Message-ID: <4B043492.1040605@jhu.edu>

Do the RpcTask task methods end up using ruby threads to do their 
work?   That call_async  method definitely sounds suspiciously like it 
might.

I've found that ruby threads under mongrel (although I don't think it's 
neccesarily an issue specific to mongrel) sometimes block when you don't 
think they ought to be, or end up in wait state for long periods when it 
doesn't seem like they ought to be.

When I have actual control over my ruby threads, I've found that 
explicitly setting the thread priority of 'background' threads to be 
lower than 0 generally frees things up.   If RpcTask is creating threads 
and you don't want to hack it's code to set thread priorities...  is 
there a synchronous method you can use instead of call_async to make 
your rpc?

Jonathan

Thomas Allen wrote:
> Hi Everyone,
>
> I'm running a Rails site on Mongrel and I can't figure out why a
> particular type of request ties up Mongrel easily. The requests that
> tie up Mongrel call an XML-RPC server like so:
>
> # In the controller
> def site_start
>   if params[:id]
>     @site = Site.find(params[:id])
>     @site.site_start
>     render :json=>{:success=>true}
>   end
> end
>
> # In the model
> def site_start
>   RpcTask.manage(self, 'start')
> end
>
> # In RpcTask
> def manage(site, task)
>   run('manage_task', {
>     :site => site.name,
>     :site_id => site.id,
>     :task => task
>   })
> end
>
> # which calls
> def run(task, task_params = {})
>   begin
>     server = XMLRPC::Client.new2('http://localhost:9192/')
>     result = server.call_async(task,task_params)
>     return result
>   rescue XMLRPC::FaultException => err
>     logger = ActiveRecord::Base.logger
>     logger.error(err.faultCode)
>     logger.error(err.faultString)
>     logger.error(result)
>   end
>   false
> end
>
> If I call the model method directly from the console, the RPC side
> responds very quickly:
>
>   
>>> start = Time.now; Site.first.site_start; (Time.now - start).to_s
>>>       
> => "0.493253"
>
> Removing the body of RpcTask.run results in comparable performance.
> Also, by switching from a single mongrel to a four-mongrel cluster, I
> was able to get the these actions to perform acceptably but I imagine
> that I'm doing something very wrong here to require so much power. Any
> ideas?
>
> Thanks,
> Thomas Allen
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
>   

From thomas.allen at litsoftinc.com  Wed Nov 18 14:13:39 2009
From: thomas.allen at litsoftinc.com (Thomas Allen)
Date: Wed, 18 Nov 2009 14:13:39 -0500
Subject: [Mongrel] Requests that make calls from XMLRPC::Client tie up
	Mongrel
In-Reply-To: <4B043492.1040605@jhu.edu>
References: <d2a166b00911180931n1da7b049mb324f44e5284f4c6@mail.gmail.com>
	<4B043492.1040605@jhu.edu>
Message-ID: <d2a166b00911181113qef10918jb3a70cbfbf9e7c97@mail.gmail.com>

Hi Jonathan,

I thought that maybe using 'call_async' rather than simply 'call'
might improve the situation but the behavior is the same with either
call.

Thomas Allen

On Wed, Nov 18, 2009 at 12:53 PM, Jonathan Rochkind <rochkind at jhu.edu> wrote:
> Do the RpcTask task methods end up using ruby threads to do their work?
> That call_async ?method definitely sounds suspiciously like it might.
>
> I've found that ruby threads under mongrel (although I don't think it's
> neccesarily an issue specific to mongrel) sometimes block when you don't
> think they ought to be, or end up in wait state for long periods when it
> doesn't seem like they ought to be.
>
> When I have actual control over my ruby threads, I've found that explicitly
> setting the thread priority of 'background' threads to be lower than 0
> generally frees things up. ? If RpcTask is creating threads and you don't
> want to hack it's code to set thread priorities... ?is there a synchronous
> method you can use instead of call_async to make your rpc?
>
> Jonathan
>
> Thomas Allen wrote:
>>
>> Hi Everyone,
>>
>> I'm running a Rails site on Mongrel and I can't figure out why a
>> particular type of request ties up Mongrel easily. The requests that
>> tie up Mongrel call an XML-RPC server like so:
>>
>> # In the controller
>> def site_start
>> ?if params[:id]
>> ? ?@site = Site.find(params[:id])
>> ? ?@site.site_start
>> ? ?render :json=>{:success=>true}
>> ?end
>> end
>>
>> # In the model
>> def site_start
>> ?RpcTask.manage(self, 'start')
>> end
>>
>> # In RpcTask
>> def manage(site, task)
>> ?run('manage_task', {
>> ? ?:site => site.name,
>> ? ?:site_id => site.id,
>> ? ?:task => task
>> ?})
>> end
>>
>> # which calls
>> def run(task, task_params = {})
>> ?begin
>> ? ?server = XMLRPC::Client.new2('http://localhost:9192/')
>> ? ?result = server.call_async(task,task_params)
>> ? ?return result
>> ?rescue XMLRPC::FaultException => err
>> ? ?logger = ActiveRecord::Base.logger
>> ? ?logger.error(err.faultCode)
>> ? ?logger.error(err.faultString)
>> ? ?logger.error(result)
>> ?end
>> ?false
>> end
>>
>> If I call the model method directly from the console, the RPC side
>> responds very quickly:
>>
>>
>>>>
>>>> start = Time.now; Site.first.site_start; (Time.now - start).to_s
>>>>
>>
>> => "0.493253"
>>
>> Removing the body of RpcTask.run results in comparable performance.
>> Also, by switching from a single mongrel to a four-mongrel cluster, I
>> was able to get the these actions to perform acceptably but I imagine
>> that I'm doing something very wrong here to require so much power. Any
>> ideas?
>>
>> Thanks,
>> Thomas Allen
>> _______________________________________________
>> Mongrel-users mailing list
>> Mongrel-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>
>>
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>

From thomas.allen at litsoftinc.com  Wed Nov 18 14:50:37 2009
From: thomas.allen at litsoftinc.com (Thomas Allen)
Date: Wed, 18 Nov 2009 14:50:37 -0500
Subject: [Mongrel] Requests that make calls from XMLRPC::Client tie up
	Mongrel
In-Reply-To: <d2a166b00911181113qef10918jb3a70cbfbf9e7c97@mail.gmail.com>
References: <d2a166b00911180931n1da7b049mb324f44e5284f4c6@mail.gmail.com>
	<4B043492.1040605@jhu.edu>
	<d2a166b00911181113qef10918jb3a70cbfbf9e7c97@mail.gmail.com>
Message-ID: <d2a166b00911181150g642ac402h83f18f540e7fa14e@mail.gmail.com>

Thanks for suggesting that the problem may be related to threading. At
least on this Debian box, changing RpcTask.run to the following seems
to do the trick:

def run(task, task_params = {})
  Thread.new {
    server = XMLRPC::Client.new2('http://localhost:9192/')
    server.call(task,task_params)
  }.value
end

Thomas

On Wed, Nov 18, 2009 at 2:13 PM, Thomas Allen
<thomas.allen at litsoftinc.com> wrote:
> Hi Jonathan,
>
> I thought that maybe using 'call_async' rather than simply 'call'
> might improve the situation but the behavior is the same with either
> call.
>
> Thomas Allen
>
> On Wed, Nov 18, 2009 at 12:53 PM, Jonathan Rochkind <rochkind at jhu.edu> wrote:
>> Do the RpcTask task methods end up using ruby threads to do their work?
>> That call_async ?method definitely sounds suspiciously like it might.
>>
>> I've found that ruby threads under mongrel (although I don't think it's
>> neccesarily an issue specific to mongrel) sometimes block when you don't
>> think they ought to be, or end up in wait state for long periods when it
>> doesn't seem like they ought to be.
>>
>> When I have actual control over my ruby threads, I've found that explicitly
>> setting the thread priority of 'background' threads to be lower than 0
>> generally frees things up. ? If RpcTask is creating threads and you don't
>> want to hack it's code to set thread priorities... ?is there a synchronous
>> method you can use instead of call_async to make your rpc?
>>
>> Jonathan
>>
>> Thomas Allen wrote:
>>>
>>> Hi Everyone,
>>>
>>> I'm running a Rails site on Mongrel and I can't figure out why a
>>> particular type of request ties up Mongrel easily. The requests that
>>> tie up Mongrel call an XML-RPC server like so:
>>>
>>> # In the controller
>>> def site_start
>>> ?if params[:id]
>>> ? ?@site = Site.find(params[:id])
>>> ? ?@site.site_start
>>> ? ?render :json=>{:success=>true}
>>> ?end
>>> end
>>>
>>> # In the model
>>> def site_start
>>> ?RpcTask.manage(self, 'start')
>>> end
>>>
>>> # In RpcTask
>>> def manage(site, task)
>>> ?run('manage_task', {
>>> ? ?:site => site.name,
>>> ? ?:site_id => site.id,
>>> ? ?:task => task
>>> ?})
>>> end
>>>
>>> # which calls
>>> def run(task, task_params = {})
>>> ?begin
>>> ? ?server = XMLRPC::Client.new2('http://localhost:9192/')
>>> ? ?result = server.call_async(task,task_params)
>>> ? ?return result
>>> ?rescue XMLRPC::FaultException => err
>>> ? ?logger = ActiveRecord::Base.logger
>>> ? ?logger.error(err.faultCode)
>>> ? ?logger.error(err.faultString)
>>> ? ?logger.error(result)
>>> ?end
>>> ?false
>>> end
>>>
>>> If I call the model method directly from the console, the RPC side
>>> responds very quickly:
>>>
>>>
>>>>>
>>>>> start = Time.now; Site.first.site_start; (Time.now - start).to_s
>>>>>
>>>
>>> => "0.493253"
>>>
>>> Removing the body of RpcTask.run results in comparable performance.
>>> Also, by switching from a single mongrel to a four-mongrel cluster, I
>>> was able to get the these actions to perform acceptably but I imagine
>>> that I'm doing something very wrong here to require so much power. Any
>>> ideas?
>>>
>>> Thanks,
>>> Thomas Allen
>>> _______________________________________________
>>> Mongrel-users mailing list
>>> Mongrel-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>>
>>>
>>
>> _______________________________________________
>> Mongrel-users mailing list
>> Mongrel-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>
>

From rochkind at jhu.edu  Wed Nov 18 14:56:13 2009
From: rochkind at jhu.edu (Jonathan Rochkind)
Date: Wed, 18 Nov 2009 14:56:13 -0500
Subject: [Mongrel] Requests that make calls from XMLRPC::Client tie up
 Mongrel
In-Reply-To: <d2a166b00911181150g642ac402h83f18f540e7fa14e@mail.gmail.com>
References: <d2a166b00911180931n1da7b049mb324f44e5284f4c6@mail.gmail.com>
	<4B043492.1040605@jhu.edu>
	<d2a166b00911181113qef10918jb3a70cbfbf9e7c97@mail.gmail.com>
	<d2a166b00911181150g642ac402h83f18f540e7fa14e@mail.gmail.com>
Message-ID: <4B04515D.9090304@jhu.edu>

Cool, glad you solved it. Threading in ruby has all sorts of gotchas. 
Although I can't possibly explain why your new way works, it seems odd 
to me, although it does seem to confirm that _something_ about threading 
is what was causing you problems.  Out of curiosity, what was 
RpcTask.run defined as before?  Did it involve threads already?

Might be interesting to try your code under Passenger instead of Mongrel 
and see if the same problem occurs. I am trying to switch all my stuff 
out of mongrel to passenger, mongrel's continued development seems... 
not something I am confident in.

Jonathan

Thomas Allen wrote:
> Thanks for suggesting that the problem may be related to threading. At
> least on this Debian box, changing RpcTask.run to the following seems
> to do the trick:
>
> def run(task, task_params = {})
>   Thread.new {
>     server = XMLRPC::Client.new2('http://localhost:9192/')
>     server.call(task,task_params)
>   }.value
> end
>
> Thomas
>
> On Wed, Nov 18, 2009 at 2:13 PM, Thomas Allen
> <thomas.allen at litsoftinc.com> wrote:
>   
>> Hi Jonathan,
>>
>> I thought that maybe using 'call_async' rather than simply 'call'
>> might improve the situation but the behavior is the same with either
>> call.
>>
>> Thomas Allen
>>
>> On Wed, Nov 18, 2009 at 12:53 PM, Jonathan Rochkind <rochkind at jhu.edu> wrote:
>>     
>>> Do the RpcTask task methods end up using ruby threads to do their work?
>>> That call_async  method definitely sounds suspiciously like it might.
>>>
>>> I've found that ruby threads under mongrel (although I don't think it's
>>> neccesarily an issue specific to mongrel) sometimes block when you don't
>>> think they ought to be, or end up in wait state for long periods when it
>>> doesn't seem like they ought to be.
>>>
>>> When I have actual control over my ruby threads, I've found that explicitly
>>> setting the thread priority of 'background' threads to be lower than 0
>>> generally frees things up.   If RpcTask is creating threads and you don't
>>> want to hack it's code to set thread priorities...  is there a synchronous
>>> method you can use instead of call_async to make your rpc?
>>>
>>> Jonathan
>>>
>>> Thomas Allen wrote:
>>>       
>>>> Hi Everyone,
>>>>
>>>> I'm running a Rails site on Mongrel and I can't figure out why a
>>>> particular type of request ties up Mongrel easily. The requests that
>>>> tie up Mongrel call an XML-RPC server like so:
>>>>
>>>> # In the controller
>>>> def site_start
>>>>  if params[:id]
>>>>    @site = Site.find(params[:id])
>>>>    @site.site_start
>>>>    render :json=>{:success=>true}
>>>>  end
>>>> end
>>>>
>>>> # In the model
>>>> def site_start
>>>>  RpcTask.manage(self, 'start')
>>>> end
>>>>
>>>> # In RpcTask
>>>> def manage(site, task)
>>>>  run('manage_task', {
>>>>    :site => site.name,
>>>>    :site_id => site.id,
>>>>    :task => task
>>>>  })
>>>> end
>>>>
>>>> # which calls
>>>> def run(task, task_params = {})
>>>>  begin
>>>>    server = XMLRPC::Client.new2('http://localhost:9192/')
>>>>    result = server.call_async(task,task_params)
>>>>    return result
>>>>  rescue XMLRPC::FaultException => err
>>>>    logger = ActiveRecord::Base.logger
>>>>    logger.error(err.faultCode)
>>>>    logger.error(err.faultString)
>>>>    logger.error(result)
>>>>  end
>>>>  false
>>>> end
>>>>
>>>> If I call the model method directly from the console, the RPC side
>>>> responds very quickly:
>>>>
>>>>
>>>>         
>>>>>> start = Time.now; Site.first.site_start; (Time.now - start).to_s
>>>>>>
>>>>>>             
>>>> => "0.493253"
>>>>
>>>> Removing the body of RpcTask.run results in comparable performance.
>>>> Also, by switching from a single mongrel to a four-mongrel cluster, I
>>>> was able to get the these actions to perform acceptably but I imagine
>>>> that I'm doing something very wrong here to require so much power. Any
>>>> ideas?
>>>>
>>>> Thanks,
>>>> Thomas Allen
>>>> _______________________________________________
>>>> Mongrel-users mailing list
>>>> Mongrel-users at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>>>
>>>>
>>>>         
>>> _______________________________________________
>>> Mongrel-users mailing list
>>> Mongrel-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>>
>>>       
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
>   

From thomas.allen at litsoftinc.com  Wed Nov 18 16:16:24 2009
From: thomas.allen at litsoftinc.com (Thomas Allen)
Date: Wed, 18 Nov 2009 16:16:24 -0500
Subject: [Mongrel] Requests that make calls from XMLRPC::Client tie up
	Mongrel
In-Reply-To: <4B04515D.9090304@jhu.edu>
References: <d2a166b00911180931n1da7b049mb324f44e5284f4c6@mail.gmail.com>
	<4B043492.1040605@jhu.edu>
	<d2a166b00911181113qef10918jb3a70cbfbf9e7c97@mail.gmail.com>
	<d2a166b00911181150g642ac402h83f18f540e7fa14e@mail.gmail.com>
	<4B04515D.9090304@jhu.edu>
Message-ID: <d2a166b00911181316j232b60femf1c2abbe7a963e88@mail.gmail.com>

I didn't want to shoot off another email so soon, but it turns out
that code did not fix the problem. It seemed to because I was running
the mongrel on another port and this revealed the real problem: The
task being invoked on the other side logs certain information both to
a file and via HTTP (coming back to these same mongrel(s)). The
start_site task, for instance, would immediately send six requests to
the single mongrel, bogging it down (one request for each log message,
each one indicating a different service that had just been started).

So I have three options:
* Re-work the other side so that it batches the log messages
* Run enough mongrels to handle this sort of traffic (four seems to do it)
* Tweak mongrel somehow...maybe that's where you guys would have the
best advice :^)

Thomas

On Wed, Nov 18, 2009 at 2:56 PM, Jonathan Rochkind <rochkind at jhu.edu> wrote:
> Cool, glad you solved it. Threading in ruby has all sorts of gotchas.
> Although I can't possibly explain why your new way works, it seems odd to
> me, although it does seem to confirm that _something_ about threading is
> what was causing you problems. ?Out of curiosity, what was RpcTask.run
> defined as before? ?Did it involve threads already?
>
> Might be interesting to try your code under Passenger instead of Mongrel and
> see if the same problem occurs. I am trying to switch all my stuff out of
> mongrel to passenger, mongrel's continued development seems... not something
> I am confident in.
>
> Jonathan
>
> Thomas Allen wrote:
>>
>> Thanks for suggesting that the problem may be related to threading. At
>> least on this Debian box, changing RpcTask.run to the following seems
>> to do the trick:
>>
>> def run(task, task_params = {})
>> ?Thread.new {
>> ? ?server = XMLRPC::Client.new2('http://localhost:9192/')
>> ? ?server.call(task,task_params)
>> ?}.value
>> end
>>
>> Thomas
>>
>> On Wed, Nov 18, 2009 at 2:13 PM, Thomas Allen
>> <thomas.allen at litsoftinc.com> wrote:
>>
>>>
>>> Hi Jonathan,
>>>
>>> I thought that maybe using 'call_async' rather than simply 'call'
>>> might improve the situation but the behavior is the same with either
>>> call.
>>>
>>> Thomas Allen
>>>
>>> On Wed, Nov 18, 2009 at 12:53 PM, Jonathan Rochkind <rochkind at jhu.edu>
>>> wrote:
>>>
>>>>
>>>> Do the RpcTask task methods end up using ruby threads to do their work?
>>>> That call_async ?method definitely sounds suspiciously like it might.
>>>>
>>>> I've found that ruby threads under mongrel (although I don't think it's
>>>> neccesarily an issue specific to mongrel) sometimes block when you don't
>>>> think they ought to be, or end up in wait state for long periods when it
>>>> doesn't seem like they ought to be.
>>>>
>>>> When I have actual control over my ruby threads, I've found that
>>>> explicitly
>>>> setting the thread priority of 'background' threads to be lower than 0
>>>> generally frees things up. ? If RpcTask is creating threads and you
>>>> don't
>>>> want to hack it's code to set thread priorities... ?is there a
>>>> synchronous
>>>> method you can use instead of call_async to make your rpc?
>>>>
>>>> Jonathan
>>>>
>>>> Thomas Allen wrote:
>>>>
>>>>>
>>>>> Hi Everyone,
>>>>>
>>>>> I'm running a Rails site on Mongrel and I can't figure out why a
>>>>> particular type of request ties up Mongrel easily. The requests that
>>>>> tie up Mongrel call an XML-RPC server like so:
>>>>>
>>>>> # In the controller
>>>>> def site_start
>>>>> ?if params[:id]
>>>>> ? @site = Site.find(params[:id])
>>>>> ? @site.site_start
>>>>> ? render :json=>{:success=>true}
>>>>> ?end
>>>>> end
>>>>>
>>>>> # In the model
>>>>> def site_start
>>>>> ?RpcTask.manage(self, 'start')
>>>>> end
>>>>>
>>>>> # In RpcTask
>>>>> def manage(site, task)
>>>>> ?run('manage_task', {
>>>>> ? :site => site.name,
>>>>> ? :site_id => site.id,
>>>>> ? :task => task
>>>>> ?})
>>>>> end
>>>>>
>>>>> # which calls
>>>>> def run(task, task_params = {})
>>>>> ?begin
>>>>> ? server = XMLRPC::Client.new2('http://localhost:9192/')
>>>>> ? result = server.call_async(task,task_params)
>>>>> ? return result
>>>>> ?rescue XMLRPC::FaultException => err
>>>>> ? logger = ActiveRecord::Base.logger
>>>>> ? logger.error(err.faultCode)
>>>>> ? logger.error(err.faultString)
>>>>> ? logger.error(result)
>>>>> ?end
>>>>> ?false
>>>>> end
>>>>>
>>>>> If I call the model method directly from the console, the RPC side
>>>>> responds very quickly:
>>>>>
>>>>>
>>>>>
>>>>>>>
>>>>>>> start = Time.now; Site.first.site_start; (Time.now - start).to_s
>>>>>>>
>>>>>>>
>>>>>
>>>>> => "0.493253"
>>>>>
>>>>> Removing the body of RpcTask.run results in comparable performance.
>>>>> Also, by switching from a single mongrel to a four-mongrel cluster, I
>>>>> was able to get the these actions to perform acceptably but I imagine
>>>>> that I'm doing something very wrong here to require so much power. Any
>>>>> ideas?
>>>>>
>>>>> Thanks,
>>>>> Thomas Allen
>>>>> _______________________________________________
>>>>> Mongrel-users mailing list
>>>>> Mongrel-users at rubyforge.org
>>>>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>>>>
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Mongrel-users mailing list
>>>> Mongrel-users at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>>>
>>>>
>>
>> _______________________________________________
>> Mongrel-users mailing list
>> Mongrel-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>
>>
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>

From thomas.allen at litsoftinc.com  Wed Nov 18 16:43:46 2009
From: thomas.allen at litsoftinc.com (Thomas Allen)
Date: Wed, 18 Nov 2009 16:43:46 -0500
Subject: [Mongrel] Requests that make calls from XMLRPC::Client tie up
	Mongrel
In-Reply-To: <d2a166b00911181316j232b60femf1c2abbe7a963e88@mail.gmail.com>
References: <d2a166b00911180931n1da7b049mb324f44e5284f4c6@mail.gmail.com>
	<4B043492.1040605@jhu.edu>
	<d2a166b00911181113qef10918jb3a70cbfbf9e7c97@mail.gmail.com>
	<d2a166b00911181150g642ac402h83f18f540e7fa14e@mail.gmail.com>
	<4B04515D.9090304@jhu.edu>
	<d2a166b00911181316j232b60femf1c2abbe7a963e88@mail.gmail.com>
Message-ID: <d2a166b00911181343sdc58398h58f3fed8d784fd90@mail.gmail.com>

Then again, this test (against a single mongrel started with the
production env) demonstrates that the site can handle a great number
of these logging requests:

% siege "http://localhost:9191/sites/log?site_id=1&msg=Memcached%3A+Starting&levelname=INFO"
** SIEGE 2.68
** Preparing 10 concurrent users for battle.
The server is now under siege...
Lifting the server siege..      done.
Transactions:		        3362 hits
Availability:		      100.00 %
Elapsed time:		       19.64 secs
Data transferred:	        0.15 MB
Response time:		        0.06 secs
Transaction rate:	      171.18 trans/sec
Throughput:		        0.01 MB/sec
Concurrency:		        9.99
Successful transactions:        3362
Failed transactions:	           0
Longest transaction:	        0.18
Shortest transaction:	        0.03

>> Site.first.log_entries.length
=> 3372

The hanging requests I've observed have all been in the browser as
Ajax requests...but I officially have no idea as to what is causing
this issue.

Thomas

On Wed, Nov 18, 2009 at 4:16 PM, Thomas Allen
<thomas.allen at litsoftinc.com> wrote:
> I didn't want to shoot off another email so soon, but it turns out
> that code did not fix the problem. It seemed to because I was running
> the mongrel on another port and this revealed the real problem: The
> task being invoked on the other side logs certain information both to
> a file and via HTTP (coming back to these same mongrel(s)). The
> start_site task, for instance, would immediately send six requests to
> the single mongrel, bogging it down (one request for each log message,
> each one indicating a different service that had just been started).
>
> So I have three options:
> * Re-work the other side so that it batches the log messages
> * Run enough mongrels to handle this sort of traffic (four seems to do it)
> * Tweak mongrel somehow...maybe that's where you guys would have the
> best advice :^)
>
> Thomas
>
> On Wed, Nov 18, 2009 at 2:56 PM, Jonathan Rochkind <rochkind at jhu.edu> wrote:
>> Cool, glad you solved it. Threading in ruby has all sorts of gotchas.
>> Although I can't possibly explain why your new way works, it seems odd to
>> me, although it does seem to confirm that _something_ about threading is
>> what was causing you problems. ?Out of curiosity, what was RpcTask.run
>> defined as before? ?Did it involve threads already?
>>
>> Might be interesting to try your code under Passenger instead of Mongrel and
>> see if the same problem occurs. I am trying to switch all my stuff out of
>> mongrel to passenger, mongrel's continued development seems... not something
>> I am confident in.
>>
>> Jonathan
>>
>> Thomas Allen wrote:
>>>
>>> Thanks for suggesting that the problem may be related to threading. At
>>> least on this Debian box, changing RpcTask.run to the following seems
>>> to do the trick:
>>>
>>> def run(task, task_params = {})
>>> ?Thread.new {
>>> ? ?server = XMLRPC::Client.new2('http://localhost:9192/')
>>> ? ?server.call(task,task_params)
>>> ?}.value
>>> end
>>>
>>> Thomas
>>>
>>> On Wed, Nov 18, 2009 at 2:13 PM, Thomas Allen
>>> <thomas.allen at litsoftinc.com> wrote:
>>>
>>>>
>>>> Hi Jonathan,
>>>>
>>>> I thought that maybe using 'call_async' rather than simply 'call'
>>>> might improve the situation but the behavior is the same with either
>>>> call.
>>>>
>>>> Thomas Allen
>>>>
>>>> On Wed, Nov 18, 2009 at 12:53 PM, Jonathan Rochkind <rochkind at jhu.edu>
>>>> wrote:
>>>>
>>>>>
>>>>> Do the RpcTask task methods end up using ruby threads to do their work?
>>>>> That call_async ?method definitely sounds suspiciously like it might.
>>>>>
>>>>> I've found that ruby threads under mongrel (although I don't think it's
>>>>> neccesarily an issue specific to mongrel) sometimes block when you don't
>>>>> think they ought to be, or end up in wait state for long periods when it
>>>>> doesn't seem like they ought to be.
>>>>>
>>>>> When I have actual control over my ruby threads, I've found that
>>>>> explicitly
>>>>> setting the thread priority of 'background' threads to be lower than 0
>>>>> generally frees things up. ? If RpcTask is creating threads and you
>>>>> don't
>>>>> want to hack it's code to set thread priorities... ?is there a
>>>>> synchronous
>>>>> method you can use instead of call_async to make your rpc?
>>>>>
>>>>> Jonathan
>>>>>
>>>>> Thomas Allen wrote:
>>>>>
>>>>>>
>>>>>> Hi Everyone,
>>>>>>
>>>>>> I'm running a Rails site on Mongrel and I can't figure out why a
>>>>>> particular type of request ties up Mongrel easily. The requests that
>>>>>> tie up Mongrel call an XML-RPC server like so:
>>>>>>
>>>>>> # In the controller
>>>>>> def site_start
>>>>>> ?if params[:id]
>>>>>> ? @site = Site.find(params[:id])
>>>>>> ? @site.site_start
>>>>>> ? render :json=>{:success=>true}
>>>>>> ?end
>>>>>> end
>>>>>>
>>>>>> # In the model
>>>>>> def site_start
>>>>>> ?RpcTask.manage(self, 'start')
>>>>>> end
>>>>>>
>>>>>> # In RpcTask
>>>>>> def manage(site, task)
>>>>>> ?run('manage_task', {
>>>>>> ? :site => site.name,
>>>>>> ? :site_id => site.id,
>>>>>> ? :task => task
>>>>>> ?})
>>>>>> end
>>>>>>
>>>>>> # which calls
>>>>>> def run(task, task_params = {})
>>>>>> ?begin
>>>>>> ? server = XMLRPC::Client.new2('http://localhost:9192/')
>>>>>> ? result = server.call_async(task,task_params)
>>>>>> ? return result
>>>>>> ?rescue XMLRPC::FaultException => err
>>>>>> ? logger = ActiveRecord::Base.logger
>>>>>> ? logger.error(err.faultCode)
>>>>>> ? logger.error(err.faultString)
>>>>>> ? logger.error(result)
>>>>>> ?end
>>>>>> ?false
>>>>>> end
>>>>>>
>>>>>> If I call the model method directly from the console, the RPC side
>>>>>> responds very quickly:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>
>>>>>>>> start = Time.now; Site.first.site_start; (Time.now - start).to_s
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>> => "0.493253"
>>>>>>
>>>>>> Removing the body of RpcTask.run results in comparable performance.
>>>>>> Also, by switching from a single mongrel to a four-mongrel cluster, I
>>>>>> was able to get the these actions to perform acceptably but I imagine
>>>>>> that I'm doing something very wrong here to require so much power. Any
>>>>>> ideas?
>>>>>>
>>>>>> Thanks,
>>>>>> Thomas Allen
>>>>>> _______________________________________________
>>>>>> Mongrel-users mailing list
>>>>>> Mongrel-users at rubyforge.org
>>>>>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mongrel-users mailing list
>>>>> Mongrel-users at rubyforge.org
>>>>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>>>>
>>>>>
>>>
>>> _______________________________________________
>>> Mongrel-users mailing list
>>> Mongrel-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>>
>>>
>>
>> _______________________________________________
>> Mongrel-users mailing list
>> Mongrel-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>
>

From mliebelt at web.de  Sat Nov 21 04:24:55 2009
From: mliebelt at web.de (Markus Liebelt)
Date: Sat, 21 Nov 2009 10:24:55 +0100
Subject: [Mongrel] Problems with mongrel_service and used account
In-Reply-To: <71166b3b0911151432q660b2bf5hde563895dc6c81e9@mail.gmail.com>
References: <op.u3frale6869msv@w4de3gsy0000435.t-systems.com>
	<71166b3b0911151432q660b2bf5hde563895dc6c81e9@mail.gmail.com>
Message-ID: <op.u3qm3uqp869msv@w4de3gsy0000435.t-systems.com>

Hi Luis,

On Sun, 15 Nov 2009 23:32:02 +0100, Luis Lavena <luislavena at gmail.com>  
wrote:

> On Sun, Nov 15, 2009 at 9:21 AM, Markus Liebelt <mliebelt at web.de> wrote:
>> Hi everybody,
>>
>> I try to use in a rails application that is installed with  
>> mongrel_service
>> on windows the win32ole API to access Outlook appointments. This works
>> well when started from the command line, but does not work when started  
>> as
>> a service.
>>
>> What should I check in which order to trap down the error?
>>
>
> Hello Markus,
>
> Services run without privileges for certain things, like create
> objects and such.
>
> Since you're executing from the command line and work, means that your
> user has access to these OLE objects.
>
> There are two options:
>
> 1) Configure the service to run under the same user account (that can
> be done from the services management interface)

I just tried that. See my question on Stackoverflow  
(http://stackoverflow.com/questions/1737135/error-when-reading-outlook-calendar-from-rails-application-when-started-as-a-mong)  
and the hint of Mr. Doggen that this may not work with Outlook.

I have tested it again with the correct user account and it did not work  
either. So I found the workaround:

Start a small script like

ruby script\runner 'AppointmentController.new.refresh_no_redirect'

> 2) Determine the issue using psexec.
>
> Try to lower the privileges of the prompt and execute the exact same
> command line.
>
> The tools you need are psexec, as I mentioned here:
>
> http://rubyforge.org/pipermail/mongrel-users/2007-February/003006.html
>
> See that thread for details.

I did not tried that, thank's anyway for the recommendation.

> Please also include in your reply information about your OS (32bits or
> 64bits), versions of Ruby and the gems installed too.

Well, I don't think that they matter here. I use Windows XP (32bit), ruby  
1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]

> There is a known issue with 64bits Windows that was solved in latest
> gem release, just in case.
>
> Cheers,

Thank's a lot for your hints.

Bye
	Markus

From x.meglio at gmail.com  Sat Nov 21 17:20:45 2009
From: x.meglio at gmail.com (Anton Andriyevskyy)
Date: Sun, 22 Nov 2009 00:20:45 +0200
Subject: [Mongrel] Using mongrel_rails: Can't install Redmine as win2003
	service
Message-ID: <1154274a0911211420s6065e7f7ja264d093300ffd66@mail.gmail.com>

Hello everyone.

After stugging 3+ hours installing redmine I got success but still
can't install redmine as service (windows 2003).

So here is my problem. I successfully installed redmine and mapped it
to mysql, created database and initialized it with default values.
Last thing I'm trying to do is to install it as service on windows
2003, and for this I'm running in cmd mode this instruction:

mongrel_rails service::install -N Redmine -c [your redmine folder] -p
[portno] -e production

and I get this error:
C:/ruby/lib/ruby/gems/1.8/gems/win32-service-0.7.0-x86-mswin32-60/lib/
win32/service.rb:282:in `initialize': no options provided
(ArgumentError)

When I try without params:
mongrel_rails service::install
... it just says that name (-N) is obligatory.

But when I try with name only (-N), I get the same error.

Any help appreciated.
Thanks,
Anton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/mongrel-users/attachments/20091122/520f0ef9/attachment.html>

From luislavena at gmail.com  Sat Nov 21 17:47:50 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Sat, 21 Nov 2009 19:47:50 -0300
Subject: [Mongrel] Using mongrel_rails: Can't install Redmine as win2003
	service
In-Reply-To: <1154274a0911211420s6065e7f7ja264d093300ffd66@mail.gmail.com>
References: <1154274a0911211420s6065e7f7ja264d093300ffd66@mail.gmail.com>
Message-ID: <71166b3b0911211447s6a37eec2r32faa9283f677056@mail.gmail.com>

On Sat, Nov 21, 2009 at 7:20 PM, Anton Andriyevskyy <x.meglio at gmail.com> wrote:
> Hello everyone.
>
> After stugging 3+ hours installing redmine I got success but still
> can't install redmine as service (windows 2003).
>
> So here is my problem. I successfully installed redmine and mapped it
> to mysql, created database and initialized it with default values.
> Last thing I'm trying to do is to install it as service on windows
> 2003, and for this I'm running in cmd mode this instruction:
>
> mongrel_rails service::install -N Redmine -c [your redmine folder] -p
> [portno] -e production
>
> and I get this error:
> C:/ruby/lib/ruby/gems/1.8/gems/win32-service-0.7.0-x86-mswin32-60/lib/
> win32/service.rb:282:in `initialize': no options provided
> (ArgumentError)
>
> When I try without params:
> mongrel_rails service::install
> ... it just says that name (-N) is obligatory.
>
> But when I try with name only (-N), I get the same error.
>

Please uninstall win32-service 0.7.0

mongrel_service has been linked to an specific version of
win32-service due API changes.

gem install win32-service -v 0.5.2

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From x.meglio at gmail.com  Sat Nov 21 18:58:52 2009
From: x.meglio at gmail.com (Anton Andriyevskyy)
Date: Sun, 22 Nov 2009 01:58:52 +0200
Subject: [Mongrel] Using mongrel_rails: Can't install Redmine as win2003
	service
In-Reply-To: <71166b3b0911211447s6a37eec2r32faa9283f677056@mail.gmail.com>
References: <1154274a0911211420s6065e7f7ja264d093300ffd66@mail.gmail.com> 
	<71166b3b0911211447s6a37eec2r32faa9283f677056@mail.gmail.com>
Message-ID: <1154274a0911211558u69cca894ve99a212ef00722e@mail.gmail.com>

Hi Luis. Thanks for help, it worked with old version of win32-service.

Does this mean I'll be not able to run both win32-service versions together
to keep another ruby-applications working which requires win32-service 0.6+
?

Anton


On Sun, Nov 22, 2009 at 12:47 AM, Luis Lavena <luislavena at gmail.com> wrote:

> On Sat, Nov 21, 2009 at 7:20 PM, Anton Andriyevskyy <x.meglio at gmail.com>
> wrote:
> > Hello everyone.
> >
> > After stugging 3+ hours installing redmine I got success but still
> > can't install redmine as service (windows 2003).
> >
> > So here is my problem. I successfully installed redmine and mapped it
> > to mysql, created database and initialized it with default values.
> > Last thing I'm trying to do is to install it as service on windows
> > 2003, and for this I'm running in cmd mode this instruction:
> >
> > mongrel_rails service::install -N Redmine -c [your redmine folder] -p
> > [portno] -e production
> >
> > and I get this error:
> > C:/ruby/lib/ruby/gems/1.8/gems/win32-service-0.7.0-x86-mswin32-60/lib/
> > win32/service.rb:282:in `initialize': no options provided
> > (ArgumentError)
> >
> > When I try without params:
> > mongrel_rails service::install
> > ... it just says that name (-N) is obligatory.
> >
> > But when I try with name only (-N), I get the same error.
> >
>
> Please uninstall win32-service 0.7.0
>
> mongrel_service has been linked to an specific version of
> win32-service due API changes.
>
> gem install win32-service -v 0.5.2
>
> --
> Luis Lavena
> AREA 17
> -
> Perfection in design is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.
> Antoine de Saint-Exup?ry
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/mongrel-users/attachments/20091122/73326aee/attachment.html>

From luislavena at gmail.com  Sat Nov 21 19:55:16 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Sat, 21 Nov 2009 21:55:16 -0300
Subject: [Mongrel] Using mongrel_rails: Can't install Redmine as win2003
	service
In-Reply-To: <1154274a0911211558u69cca894ve99a212ef00722e@mail.gmail.com>
References: <1154274a0911211420s6065e7f7ja264d093300ffd66@mail.gmail.com> 
	<71166b3b0911211447s6a37eec2r32faa9283f677056@mail.gmail.com> 
	<1154274a0911211558u69cca894ve99a212ef00722e@mail.gmail.com>
Message-ID: <71166b3b0911211655w7afae85agf0cf6f2dc2c20ea1@mail.gmail.com>

On Sat, Nov 21, 2009 at 8:58 PM, Anton Andriyevskyy <x.meglio at gmail.com> wrote:
> Hi Luis. Thanks for help, it worked with old version of win32-service.
> Does this mean I'll be not able to run both win32-service versions together
> to keep another ruby-applications working which requires win32-service 0.6+
> ?

mongrel_service uses "gem" method to lock to one specific version of
win32-service.

Seems is not working as expected, which could be due an old RubyGems version.

Please update to latest RubyGems 1.3.5.

I don't have too much time now to update mongrel_service, but if you
want make it API compatible with latest win32-service, I'll happily
apply the patches and make a new release.

The repository is here:

http://github.com/fauna/mongrel_service
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From x.meglio at gmail.com  Sat Nov 21 20:09:32 2009
From: x.meglio at gmail.com (Anton Andriyevskyy)
Date: Sun, 22 Nov 2009 05:09:32 +0400
Subject: [Mongrel] Using mongrel_rails: Can't install Redmine as win2003
	service
In-Reply-To: <71166b3b0911211655w7afae85agf0cf6f2dc2c20ea1@mail.gmail.com>
References: <1154274a0911211420s6065e7f7ja264d093300ffd66@mail.gmail.com>
	<71166b3b0911211447s6a37eec2r32faa9283f677056@mail.gmail.com>
	<1154274a0911211558u69cca894ve99a212ef00722e@mail.gmail.com>
	<71166b3b0911211655w7afae85agf0cf6f2dc2c20ea1@mail.gmail.com>
Message-ID: <1154274a0911211709k34f3ed74r1c4fb8433fbe5069@mail.gmail.com>

Luis, thanks for your comments.

Unfortunately i'm not ror coder and i'm zero familiar with it, so i'm
not able to fix. I just needet it for redmine, and finally it worked.

Thanks for help!

Kind Regards,
Anton

2009/11/22, Luis Lavena <luislavena at gmail.com>:
> On Sat, Nov 21, 2009 at 8:58 PM, Anton Andriyevskyy <x.meglio at gmail.com>
> wrote:
>> Hi Luis. Thanks for help, it worked with old version of win32-service.
>> Does this mean I'll be not able to run both win32-service versions
>> together
>> to keep another ruby-applications working which requires win32-service
>> 0.6+
>> ?
>
> mongrel_service uses "gem" method to lock to one specific version of
> win32-service.
>
> Seems is not working as expected, which could be due an old RubyGems
> version.
>
> Please update to latest RubyGems 1.3.5.
>
> I don't have too much time now to update mongrel_service, but if you
> want make it API compatible with latest win32-service, I'll happily
> apply the patches and make a new release.
>
> The repository is here:
>
> http://github.com/fauna/mongrel_service
> --
> Luis Lavena
> AREA 17
> -
> Perfection in design is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.
> Antoine de Saint-Exup?ry
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>

-- 
????????? ? ???? ?????????? ????????

Anton

From x.meglio at gmail.com  Mon Nov 23 07:16:27 2009
From: x.meglio at gmail.com (Anton Andriyevskyy)
Date: Mon, 23 Nov 2009 14:16:27 +0200
Subject: [Mongrel] An error occurred while sending mail (530 5.7.0 Must
	issue a STARTTLS command first. 15sm1058080bwz.0 )
Message-ID: <1154274a0911230416l18adb06sc52d3fc3514ae46b@mail.gmail.com>

I get an error after configured everything as in this tutorial:
http://redmineblog.com/articles/setup-redmine-to-send-email-using-gmail/

*My email.yml:*

# Outgoing email settings

meglio:
  delivery_method: :smtp
  smtp_settings:
    tls: true
    address: "smtp.gmail.com"
    port: '587'
    domain: "smtp.gmail.com"
    authentication: :plain
    user_name: "xxxxx at gmail.com"
    password: "xxxxx"


My RoR:

*>rails -v
Rails 2.2.2

>ruby -v
ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32]*



Any ideas?

Thanks,
Anton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/mongrel-users/attachments/20091123/45b139d7/attachment-0001.html>

From david at vrensk.com  Mon Nov 23 08:02:47 2009
From: david at vrensk.com (David Vrensk)
Date: Mon, 23 Nov 2009 14:02:47 +0100
Subject: [Mongrel] An error occurred while sending mail (530 5.7.0 Must
	issue a STARTTLS command first. 15sm1058080bwz.0 )
In-Reply-To: <1154274a0911230416l18adb06sc52d3fc3514ae46b@mail.gmail.com>
References: <1154274a0911230416l18adb06sc52d3fc3514ae46b@mail.gmail.com>
Message-ID: <81b453920911230502h542889ava188cc545a97a7ae@mail.gmail.com>

On Mon, Nov 23, 2009 at 13:16, Anton Andriyevskyy <x.meglio at gmail.com>wrote:

> Any ideas?
>
>
Well, I'd suggest two alternatives:

1. Tell us what makes this a *mongrel* problem.  (It looks like a rails or
email problem, and those are bound to be ignored without comment on this
list.)
2. Try one of the rails lists or a rails group on IRC.  You are more likely
to get email help there.

HTH,

/David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/mongrel-users/attachments/20091123/13c1b83b/attachment.html>

From x.meglio at gmail.com  Mon Nov 23 10:41:08 2009
From: x.meglio at gmail.com (Anton Andriyevskyy)
Date: Mon, 23 Nov 2009 17:41:08 +0200
Subject: [Mongrel] An error occurred while sending mail (530 5.7.0 Must
	issue a STARTTLS command first. 15sm1058080bwz.0 )
In-Reply-To: <81b453920911230502h542889ava188cc545a97a7ae@mail.gmail.com>
References: <1154274a0911230416l18adb06sc52d3fc3514ae46b@mail.gmail.com> 
	<81b453920911230502h542889ava188cc545a97a7ae@mail.gmail.com>
Message-ID: <1154274a0911230741m65ae9b85h8ca3cdb6bb1367ba@mail.gmail.com>

Thanks, David, I'll try option #2.
Anton


On Mon, Nov 23, 2009 at 3:02 PM, David Vrensk <david at vrensk.com> wrote:

> On Mon, Nov 23, 2009 at 13:16, Anton Andriyevskyy <x.meglio at gmail.com>wrote:
>
>> Any ideas?
>>
>>
> Well, I'd suggest two alternatives:
>
> 1. Tell us what makes this a *mongrel* problem.  (It looks like a rails or
> email problem, and those are bound to be ignored without comment on this
> list.)
> 2. Try one of the rails lists or a rails group on IRC.  You are more likely
> to get email help there.
>
> HTH,
>
> /David
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/mongrel-users/attachments/20091123/e60c7876/attachment.html>

From lists at ruby-forum.com  Wed Nov 25 20:56:24 2009
From: lists at ruby-forum.com (Roger Pack)
Date: Thu, 26 Nov 2009 02:56:24 +0100
Subject: [Mongrel] update gem
Message-ID: <14931c826dcfd9c7ebd3a9b85e152c3b@ruby-forum.com>

Could somebody please update the gem version?

we've got 1.1.5
and 1.1.6 (1.9 compatible) only available through

gem install mongrel --source http://gems.rubyinstaller.org

Thanks.
-r
-- 
Posted via http://www.ruby-forum.com/.

From luislavena at gmail.com  Thu Nov 26 05:01:08 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 26 Nov 2009 07:01:08 -0300
Subject: [Mongrel] update gem
In-Reply-To: <14931c826dcfd9c7ebd3a9b85e152c3b@ruby-forum.com>
References: <14931c826dcfd9c7ebd3a9b85e152c3b@ruby-forum.com>
Message-ID: <71166b3b0911260201r2d3c6138id3d2ed5c2b59acf2@mail.gmail.com>

On Wed, Nov 25, 2009 at 10:56 PM, Roger Pack <lists at ruby-forum.com> wrote:
> Could somebody please update the gem version?
>
> we've got 1.1.5
> and 1.1.6 (1.9 compatible) only available through
>
> gem install mongrel --source http://gems.rubyinstaller.org
>

Is not that easy. The gem available at gems.rubyinstaller.org is only
"build compatible" with 1.9, and is not taking advantage of it.

A safer bet will be integrate Unicorn and make it work with
non-posix/fork() environments.

Patches are welcome.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry