First of all thanks for your reply, the versions im using are: Ruby 1.8.5 RubyGem 0.9.0 Rails 1.2.1 Mongrel_Service 0.3.1 Mongrel 1.0.1
I tryed as you suggested and when i run mongrel via command line mongrel_rails start -p 4000 no problem, running the server version via console took me to the problem as i copy pasted as follows: Errno::EINVAL in Contatti#lista Showing app/views/contatti/lista.rhtml where line #16 raised: Invalid argument Any hints? Thanks On 20 Feb, 14:11, "Luis Lavena" <[EMAIL PROTECTED]> wrote: > On 2/20/07, Fausto <[EMAIL PROTECTED]> wrote: > > > > > I have an odd ( at least for me ) problem with Mongrel running as > > service. > > Im trying to deploy RoR on a Win2003 server using Mongrel as service > > and isapi rewriter for IIS. > > When i run mongrel from shell (ruby script/server -p 4000) i can use > > my application with no problem of any sort. > > When i use mongrel running as service i get a "invalid argument" error > > and when i hit the refresh button the controller works fine. > > Is there any difference in mongrel running in shell mode or service > > mode? > > Fausto, in the future will be really helpful if you provide versions > of the gems (mongrel & rails) you're using. > > In the past, mongrel_service (0.1.0) used to duplicate mongrel_rails > code to implement as service. Since latest release (0.3.1), that is > replaced with original mongrel_rails code (totally DRY). > > My suggestions: > > 1) Since you said you tested your application with webrick, I'll try > doing it with mongrel_rails > > > cd c:\path\to\my\app > > mongrel_rails start -p 4000 > > Check if it works or not. (browse to your app URL > directlyhttp://localhost:4000/). > > 2) If that worked, now perform the same with mongrel_service 'console' > functionality: > > > mongrel_service console single -c "c:\path\to\my\app" -p 4000 > > Please note that: quotes for path are required if spaces to folders > are used. console and single parameter are needed: they inform > mongrel_service that you will simulate the service and single is the > one ruby-process service bundled into the executable. > > 3) If all these things worked, that indicates something is wrong with > the command line of the service itself (called Image Path). > > Check the Services console from the Administrative Tools (or > Start->Run... services.msc). Look for your service name and double > click on it. > > Verify the command line (Executable Path) looks something like this: > > C:\Ruby\bin\mongrel_service.exe single -c "c:\path\to\my\app" -p 4000 > > IMPORTANT NOTE: since you say you're using IIS rewrite, I'll suggest > you check these rules in case all the previous instructions worked. > > Also, you didn't indicate "production" environment, please check your > development database is set in config/database.yml and you're sure to > run it that way. > > > Another question: is there any HowTo for dummies on how to install and > > deploy RoR on a fresh linux based server? > > Not my field of action :-) > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---