similar to: Mongrel Service 0.3.1, basic process monitoring

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

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

Hello Guys, Been testing fastthread (known on previous releases as optimized_locking) for soon to be released 0.3.18 mswin32 gems (official ones). Attached to this message is the ruby script I used for the test results shown on graphics [1] and [2] The idea of the script is simulate what Mongrel do with threads creating a simple workload for testing Ruby VM stability. [1] refers to normal,

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

64bit Intel 8 CPU server Windows 2003 Server Service set to run as LocalSystem, doesn''t work as user account either The error we see is: "Service failed to start in a timely..." Which I have seen in the past email trails as working The app works from mongrel_rails start and from mongrel_service console -N servicename -p 3000 -c c:\rails_apps\appname -e production We upgraded

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

Hello Mongrels around the world! Been thinking a way to unify the issue I described in the subject. For those who aren''t aware, mongrel (actually, mongrel_rails) only generate the log file if daemonize was used (-d) That means no log file under windows, due his lack of fork/daemonization capabilities. Now, users that need to run mongrel on windows cannot report and fill the empty

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

Hi all, I''ve forwarded this from the Mongrel mailing list to see if anyone has any thoughts. In summary, Luis is hitting broken pipe errors on occasion when he tries to stop a service. In a later email Luis mentions that simply ignoring them might not always be the best idea, since sometimes the service seems to no longer respond, even though it still appears to be running fine. Dan

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 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

Just so you know, I''ve read the manual :) http://mongrel.rubyforge.org/docs/choosing_deployment.html No php or ssl needed - that is me - simple. So I should be good to go but thought I''d ask. BTW, sorry about the stupid subject. Listening to BNL, you know ;) On 6/27/06, mongrel-users-request at rubyforge.org <mongrel-users-request at rubyforge.org> wrote: > Send

Hello List! I''m glad to announce the update of Rails Plugin Fossilize (0.3.0): Fossilize ========= Allow you distribute your rails application as a Gem. It add a "fossilize" generator and a package task to rake. What it offer ============= Fossilize offer you two ways of using your distributable rails application: * a ''unpack'' method (by default):

Hi Luis, answers in CAPS. -----Original Message----- From: Luis Lavena [mailto:luislavena at gmail.com] Sent: Tuesday, December 26, 2006 5:39 PM To: mongrel-users at rubyforge.org Subject: [Mongrel] no log/mongrel.log file on win32, looking for suggestions... Hello Mongrels around the world! Been thinking a way to unify the issue I described in the subject. For those who aren''t

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

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".

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

Hello list! I have mongrel service 0.1.0 working on my current production machine. Upgrading to a new server and also moving to mongrel service 0.3.1 has not worked yet. I am hoping someone will have an idea as to why. I have mongrel installed properly (I think): C:\rails\igacc>gem list --local *** LOCAL GEMS *** ... mongrel (1.0.1) A small fast HTTP library and server that runs

Hello Guys, Doing conversion of some test for some controllers, still with integrated views. Anyway, I have this: it "should not see Join This Group button on profile page as member" do get "show", :id => @group.id response.should be_success response.should_not have_text(/Join This Group/) end But running with spec (0.9.4), drop me the folling error: