similar to: mongrel_service install error

Hello Users!, Since the pre-release 0.3.18 (last week) Lot of things happen in ruby-land (check the DoS security bulletin, please). Anyway, the win32 folks being left on the side of the road, and cannot provide feedback of stability due lack of binaries for the latest releases. So, I managed to upload the pre-built gem to my host: http://www.mmediasys.com/releases/mongrel-0.3.18-mswin32.gem

i was suffering from a massive memory leak in my application. after searching and testing for quite a while i finally found that it wasn''t my app that had a leak but the win32ole support that was used by the ADO driver in sqlserver adapter. the solution to fix the leak was to install ruby 1.8.5p52 or 1.8.6p36 but sadly as soon i install one of the fixed releases mongrel won''t

Hi folks, For the past weeks I have been working in solve the problems with mongrel_service and its *crazy* behavior related to standard mongrel_rails. Job made this more slow than usual, but here we are: a beta release. * What''s New? - This version of mongrel_service replaces mongrel_service ruby script with a binary, pre-built executable coded using ServiceFB framework [1] in

I just ran into an issue with a new mongrel install on Win32. When trying to run mongrel from RadRails 0.7.2 on win32, I got an error while loading that it couldn''t locate mongrel_service. C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'': no such file to load -- C:/ruby/lib/ruby/gems/1.8/gems/mongrel_service-0.3.1/lib/mongrel_service/init.rb

I am trying to install mongrel_service 0.3.4 on a server that does not have any outside internet connection. It has ruby 1.8.6 and I have been installing gems by copying the source into ..\ruby\lib\ruby\gems\1.8\gems and then doing a gem install --local using the .gem file. I was able to find and install all the gem dependencies of mongrel_service through rubyforge except win32-service which

Hey, I just finished a round of testing my app with mongrel-1.0rc1 (pretty good, four segfaults and a gc error in maybe ten thousands requests) and was moving on to mongrel_service to see if it could cope with said segfaults and gc errors. Sadly, the service will not start. I installed using: mongrel_rails service::install -N nplrails -e development -p 3000 claims to be happy. When I try to

I am trying to run Mongrel 1.1.5 with mongrel_service 0.3.4 on Ruby 1.8.6 with a "normal" user account, i.e. a user which belongs only to the Windows group "Users". The rationale behind this is that running a web server with full administrative rights (e.g. Local System) is not something that I would like to do. Unfortunately, starting the service from the services control

I am trying to install mongrel_service gem on Windows (although this problem seems to hold for any non-compiled gem). I have tried this with Windows Server 2003 and 2008. Also with Ruby version 1.8.7 and 1.9.1 (Luis Lavena''s one click installer). Both with the same result. The error message (full text below) mentions that I have to install development tools first. I have installed MinGW

Hi, why are the gemplugins commented out in mongrel_service? What was the problem with them? I''m curiuos because I''ve used them without problems since the revision 338 (-win32 suffix patch, 31/08). However, my site is a small internal one, so it doesn''t mean any heavy testing. Jano

Thoughts? -------------- next part -------------- An embedded message was scrubbed... From: "Romuald du Song" <rdusong at gmail.com> Subject: [ruby] win32-service : RegisterServiceCtrlHandlerEx Date: Mon, 26 Jun 2006 00:02:10 +0200 Size: 2587 Url: http://rubyforge.org/pipermail/win32utils-devel/attachments/20060628/8f12e8f1/attachment-0001.mht

Hi Luis, Could you make a new build of mongrel_service from trunk and ship it back to me? We''re putting together release candidates. I messed with your Rakefile; in order to sign the gem you''ll have to make yourself a gem certificate and send it to me and I''ll auth it against the official mongrel certificate and send it back. Evan -- Evan Weaver Cloudburst, LLC

Konnichiwa Mongrel users, mongrel_service cannot run as a windows service under my environment, with the windows message : "error 1053 : The service did not respond to the start or control request in a timely fashion." >From a part of "ServiceFB.log" at c:/ruby/bin, mongrel_service failed to get the process name of "service.exe".

All, I am in need of some help. I''ve run into a problem that I am not able to fix or even troubleshoot. I am trying to run Mongrel as a service on Win32. Basically, my problem is that running Mongrel as a service works fine. Fine until I change the configuration (using service::remove and service::install) to use --prefix. I must have this as I am running multiple webapps and app

Hello Mongrels, I know I''ve been promising an update to mongrel_service, I''m working on it, and will shine, I promise. Anyway, for those using mongrel_service with MySQL, 5.x community series, I must inform: There is a bug report at mysql (#25621) [1] that describe the situation with sleeping threads that didn''t respond in timely fashion. That bug causes

Hello Guys, A quick and not so dirty release of mongrel_service. Main issues got fixed: * Strict Gem dependencies for mongrel_service. This version is compatible only with mongrel 1.0.x, 1.1.x and with win32-service 0.5.x. * Fixed issues realted to Win32::Service and gem_plugin being registered with different names due win32-service changes. Also this gem is build with

Hello Mongrel Users! This announce is for Windows users of Mongrel! ;-) I have uploaded a new gem solving a few issues with services. * Services didn''t install on x64 versions of Windows (Server 2003, XP or Vista). * It should no longer depend on Ruby being installed in the PATH * It also allow you have Ruby or your application in any path, including ones with spaces (sorry about

Hi all, If you take a look at the service.rb file in the win32-service repository (the new one in the toplevel repository path), I''ve got this bit of code, which succeeds, but I can''t seem to unpack the data structure properly. Did I pack it wrong to begin with? I should know this but I''m spacing out. proc_status =

I''ve got my application running under Windows with mongrel perfectly, so it was time to convert it to a service. service::install works fine, but service:start gives me some "One moment, start pending" and then lots of "One moment, stopped". After a bit of digging I found this in the service.log: ** Starting Mongrel in production mode at :3000 ** Starting Rails in

Thanks for your reply Luis > Will be very helpful if you provide the logs (servicefb.log and > mongrel_service.log) both located into ruby\bin directory. --------------------------------------------------------------------------------- # Logfile created on 28/03/2007 17:54:32 native/process.bas:44, fb.process.spawn: Spawn() init native/process.bas:50, fb.process.spawn: Success in

Hello Mongrel Users! This is my first post! Is there an expected release date for the fixed version of mongrel_service that will resolve the missing service::start command? I would love to use the much improved features of the new mongrel_service, but I haven''t been able to yet. I haven''t figured out how to follow Zed''s advice on a previous thread to just use the