I have a small Rails app deployed on Windows Server 2003 and Mongrel 0.3.13.3. Everything works well, except when the Windows box is rebooted. I have mongrel_service installed and the service is configured to start automatically, however Mongrel consistently fails to start after a reboot. Windows reports the service''s status as "Started", but attempts to access the app fail and checking Task Manager reveals there is no ruby process running. If I manually stop and start the service at that point everything comes up fine. I don''t see anything of note in any of the log files in the Rails "log" directory, or in the Event Viewer. Has anyone else seen this kind of behavior? If so, do you have any suggestions about how to work around it? I understand that work is currently being done to retool mongrel_service. Is this possibly a known issue and something that is being addressed? Thanks, Mark Roghelia
I actually had a worse experience recently. Partly of my own doing. Win 2003 small business server. 1. installed instantrails 2. At one point configured apache to monitor port 3000 in an aborted attempt to set up proxying. 3. gave up on apache for the moment, but got a mongrel_service running monitoring the same port 4. started getting segfaults from mongrel (run in debug mode to see them) 5. updated some other software and restarted Server hung during the login process and never allowed me to sign on. After some digging I discovered the problem, I think. Instant Rails was set to startup and run Apache, which captured port 3000 The mongrel service started and tried to capture the same port, but couldnt. So it failed, and because I had it set to restart the service, this just kept going around in circles. Had to login in safe mode and deactivated the mongrel service. FWIW, I still get segfaults with mongrel as a service (but not if run directly). Haven''t researched it enough to file a bug report yet. _Kevin On 12/8/06, Mark Roghelia <mroghelia at topsailtech.com> wrote:> I have a small Rails app deployed on Windows Server 2003 and Mongrel > 0.3.13.3. Everything works well, except when the Windows box is > rebooted. I have mongrel_service installed and the service is > configured to start automatically, however Mongrel consistently fails > to start after a reboot. Windows reports the service''s status as > "Started", but attempts to access the app fail and checking Task > Manager reveals there is no ruby process running. If I manually stop > and start the service at that point everything comes up fine. I > don''t see anything of note in any of the log files in the Rails "log" > directory, or in the Event Viewer. > > Has anyone else seen this kind of behavior? If so, do you have any > suggestions about how to work around it? > > I understand that work is currently being done to retool > mongrel_service. Is this possibly a known issue and something that > is being addressed? > > Thanks, > > Mark Roghelia > > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-- Kevin Olbrich kevin.olbrich at gmail.com CONFIDENTIAL Unless otherwise indicated or obvious from the nature of the following communication, the information contained herein is a privileged and confidential information/work product. The communication is intended for the use of the individual or entity named above. It the reader of this transmission is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error or are not sure whether it is privileged, please immediately notify us by return e-mail and destroy any copies, electronic, paper, or otherwise, which you may have of this communication.
On 12/8/06, Mark Roghelia <mroghelia at topsailtech.com> wrote:> I have a small Rails app deployed on Windows Server 2003 and Mongrel > 0.3.13.3. Everything works well, except when the Windows box is > rebooted. I have mongrel_service installed and the service is > configured to start automatically, however Mongrel consistently fails > to start after a reboot. Windows reports the service''s status as > "Started", but attempts to access the app fail and checking Task > Manager reveals there is no ruby process running. If I manually stop > and start the service at that point everything comes up fine. I > don''t see anything of note in any of the log files in the Rails "log" > directory, or in the Event Viewer. > > Has anyone else seen this kind of behavior? If so, do you have any > suggestions about how to work around it? >Yes, that behavior happens if mongrel_service tries to start prior the network stack get up (it fails to bind to tcp/ip).> I understand that work is currently being done to retool > mongrel_service. Is this possibly a known issue and something that > is being addressed? >This is something that current and new implementation lack of solution. I''m reworking ServiceFB framework to allow complete control of service dependencies and make it "start" after all network services are up, to solve this issue. -- 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
On 12/8/06, Kevin Olbrich <kevin.olbrich at gmail.com> wrote:> I actually had a worse experience recently. Partly of my own doing. > Win 2003 small business server. > > 1. installed instantrails > 2. At one point configured apache to monitor port 3000 in an aborted > attempt to set up proxying. > 3. gave up on apache for the moment, but got a mongrel_service running > monitoring the same port > 4. started getting segfaults from mongrel (run in debug mode to see them) > 5. updated some other software and restarted > > Server hung during the login process and never allowed me to sign on. > > After some digging I discovered the problem, I think. > > Instant Rails was set to startup and run Apache, which captured port 3000 > The mongrel service started and tried to capture the same port, but > couldnt. So it failed, and because I had it set to restart the > service, this just kept going around in circles. > > Had to login in safe mode and deactivated the mongrel service. >There some changes I''ll implement to mongrel_rails to actually log something in log/mongrel.log about ports already taken. That way you could "see" why the service failed to start...> FWIW, I still get segfaults with mongrel as a service (but not if run > directly). Haven''t researched it enough to file a bug report yet. >That''s because you''re using mongrel_service 0.1.0, which is based on win32-service and currently (guess still will show problems) just crash due mixing of green threads and Service Control Manager handling. The new implementation solves this using a standalone, precompiled binary that just "fire" mongrel_rails in its own ruby process, no more hacking of gem_plugins crashing the service. That also allow me code the cluster implementation, but is delayed due rework on ServiceFB framework.> On 12/8/06, Mark Roghelia <mroghelia at topsailtech.com> wrote:[snip] -- 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
Mark,
I am not sure about your stack, but the following fixed this problem for for
me:
For each of you mongrel services:
In services panel:
set startup type to automatic
Under recovery tab, Set 1st and 2nd failure to restart
In regedit:
under My
computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\{mongrel_servi
ce_name}
right click and add a new string value "DependOnService" set it to
"IIS
Admin Service"
If you are using Apache or lighty, set it to the service name for that web
server.
Shawn Hill
shawn at hillacious.com
-----Original Message-----
From: mongrel-users-bounces at rubyforge.org
[mailto:mongrel-users-bounces at rubyforge.org] On Behalf Of Mark Roghelia
Sent: Friday, December 08, 2006 3:21 PM
To: mongrel-users at rubyforge.org
Subject: [Mongrel] windows service auto start problems
I have a small Rails app deployed on Windows Server 2003 and Mongrel
0.3.13.3. Everything works well, except when the Windows box is rebooted.
I have mongrel_service installed and the service is configured to start
automatically, however Mongrel consistently fails to start after a reboot.
Windows reports the service''s status as "Started", but
attempts to access
the app fail and checking Task Manager reveals there is no ruby process
running. If I manually stop and start the service at that point everything
comes up fine. I don''t see anything of note in any of the log files in
the
Rails "log"
directory, or in the Event Viewer.
Has anyone else seen this kind of behavior? If so, do you have any
suggestions about how to work around it?
I understand that work is currently being done to retool mongrel_service.
Is this possibly a known issue and something that is being addressed?
Thanks,
Mark Roghelia
_______________________________________________
Mongrel-users mailing list
Mongrel-users at rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users