Hi, thank you for your help. I didn't patch anything. There isn't much load on the server. Its something about a call to a label, every 20 or 30 seconds. Threre is enough Ram, that's not the problem. Cpu power is enough. I simply don't know why it stops working.
In an older Mongrel version the error message was, Thread is to old, killing. On Nov 21, 2007 12:58 PM, James Tucker <[EMAIL PROTECTED]> wrote: > I would have expected you to be getting the following on load: > c:/ruby/lib/ruby/gems/1.8/gems/daemons-1.0.9/lib/daemons/daemonize.rb:103:in > `fork': fork() function is unimplemented on this machine > (NotImplementedError) > > The "-d" is not actually supported on Windows, thus the warning: > > ** WARNING: Win32 does not support daemon mode. > > Have you patched something to get this far? > > Oliver Schneider wrote: > > Hi, > > > > I am using a railsapp to call an external app and print some > barcode-labels. > > My problem is, after a while there seems to be a timeout. Then I need to > > stop the Mongrel-Server and restart it. > > Below you can see the error message, when i stop the server. > > > > Has somebody seen this before? > > > > Greetings, > > Oli > > > > C:\etikett>mongrel_rails start -d -e production > > ** WARNING: Win32 does not support daemon mode. > > ** Daemonized, any open files are closed. Look at log/mongrel.pid and > > log/mongrel.log for info. > > ** Starting Mongrel listening at 0.0.0.0:3000 <http://0.0.0.0:3000> > > ** Starting Rails with production environment... > > C:0:Warning: require_gem is obsolete. Use gem instead. > > ** Rails loaded. > > ** Loading any Rails specific GemPlugins > > ** Signals ready. INT => stop (no restart). > > ** Mongrel 1.1.1 available at 0.0.0.0:3000 <http://0.0.0.0:3000> > > ** INT signal received. > > Wed Nov 21 11:21:20 +0100 2007: Reaping 17 threads for slow workers > > because of 'shutdown' > > c:/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.1-mswin32 > /bin/../lib/mongrel.rb:216:in > > `reap_dead_workers': undefined local variable or method `w' for > > #<Mongrel::HttpServer:0x37e5380>(NameError) > > from c:/ruby/lib/ruby/gems/1.8/gems/mongrel- > > 1.1.1-mswin32/bin/../lib/mongrel/configurator.rb:303:in `join' > > from > > c:/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.1-mswin32 > /bin/../lib/mongrel/configurator.rb:303:in > > `join' > > from c:/ruby/lib/ruby/gems/1.8/gems/mongrel- > > 1.1.1-mswin32/bin/../lib/mongrel/configurator.rb:303:in `each' > > from > > c:/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.1-mswin32 > /bin/../lib/mongrel/configurator.rb:303:in > > `join' > > from c:/ruby/lib/ruby/gems/1.8/gems/mongrel- > > 1.1.1-mswin32/bin/mongrel_rails:137:in `run' > > from > > c:/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.1-mswin32 > /bin/../lib/mongrel/command.rb:212:in > > `run' > > from c:/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.1-mswin32 > > /bin/mongrel_rails:281 > > from c:/ruby/bin/mongrel_rails:16:in `load' > > from c:/ruby/bin/mongrel_rails:16 > > Batchvorgang abbrechen (J/N)? j > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users@rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >
_______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
