similar to: evented mongrel dies on USR2

Currently, on deploys we''re sending HUP to the "old" master to reload the config, and then we send it a USR2 to reload the app code. Is this redundant -- i.e. does USR2 reload the unicorn config, or just the application code? I am under the impression that USR2 forks a new master from the old, and only reloads app code, and not the unicorn config, but I just wanted to double

hi i am setting up evented mongrels on one of my servers and i am running into a little confusion. i understand that there is a few diff ways to set this up. one being using the swiftiply gem, setting the env variable to event=1 ( this is one level of confusion on ubuntu ) ( how to do this ) then also setting the require in environment.rb in rails and the other i believe is to overwrite the

I heard about a new mongrel plugin or version that''s single threaded and uses non-blocking IO with events. It''s called something like "swifty fly". Anyone have a link for it? Thanks.

Just a quick question to those of you using merb and sequel or datamapper. How do you setup your merb app? For example: merb -X off -c 5, then run mod_proxy_balancer or nginx to load balance between the 5 (or whatever #) of merb nodes? merb -X off -d, then simply use something like proxypass merb -c 5, keep the mutex lock and cluster it haproxy, swiftiply, evented mongrel...... What

Hi Rui, Not sure if you have seen this problem, but I have been running into this problem when I run the lld tests and the failure occurence is once in 5 times. lld: ../tools/lld/lib/Core/Resolver.cpp:402: void lld::Resolver::deadStripOptimize(): Assertion `symAtom' failed. #0 0x4b05ae llvm::sys::PrintStackTrace(_IO_FILE*)

Has anyone had troubles from Mongrel > 1.0.1? Just curious, because the last time I tried to run Merb it gave me some Mongrel error about the wrong number of arguments, or something like that. I can post the exact message tonight when I get home. -- Cheers, Kevin Williams http://kevwil.com/ http://www.almostserio.us/ http://kevwil.jaiku.com/

Hello, I''m running a Rails application which must sort and manipulate a lot of data which are loaded in memory. The Rails app runs on 2 mongrel processes. When I first load the app, both are 32Mb in memory. After some days, both are between 200Mb and 300Mb. My question is : is there some kind of garbage collector in Mongrel? I never see the two Mongrel processes memory footprint

Just a quick announcement that an update to swiftiplied_mongrel and evented_mongrel which fixes the incompatibility with Mongrels > 1.0.1 has been released. http://swiftiply.swiftcore.org Let me know if you have any problems. Kirk Haines

Hi, I've configured Samba as PDC. It is to serve Windows 98/2000/XP workstations. Firstly everything works fine but with adding new users to the domain there occurs serious trouble. The network printers begin to refuse access. And then I noticed that the workstations begin to refuse access too. smb.conf --- [global] netbios name = OBLR workgroup = X125 server

I'm doing the following from a linux box to a solaris box: rsync_options="-aPvrz --progress --stats --delete --delete-after" rsync $rsync_options -e ssh root@207.156.7.100:/usr2/docs/ /export/export/www/current/www rsync $rsync_options -e ssh root@207.156.7.100:/usr2/was/ /export/export/www/current/www rsync $rsync_options -e ssh root@207.156.7.100:/usr2/soe/

I read this in a previous post ( http://rubyforge.org/pipermail/mongrel-users/2006-December/002354.html) .... First, Mongrel accepts remote clients and creates one Thread for each request. Mongrel also enforces a single request/response using Connect:close headers because Ruby only supports 1024 files (so far). If Mongrel doesn''t do this then people like yourself can write a simple

Thread #<Thread:0xb7ac9dd4 sleep> is too old, killing. Error calling Dispatcher.dispatch #<Mongrel::StopServer: Timed out thread.> I''m getting lockups I''ve seen this too: Shutdown waited 1 for 9 requests, could take 10 seconds.^MThread #<Thread:0xb7815fa8 sleep> is too old, killing. Error calling Dispatcher.dispatch #<Mongrel::StopServer: Timed out

Hi, On os x.3.9, with ruby 1.8.4 installed through darwinports and mongrel through gems, everything works until I restart: mongrel_rails restart adds the logs: ** USR2 signal received. ** Restarting with arguments: ruby /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails start -p 3001 -d /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails:134: in

I cannot find any good example of a unicorn upstart task that works properly for the following: * Upstart will restart if unicorn dies * Can send USR2 signal to unicorn to do a no downtime deploys * Able to stop upstart job, even after a deploy I have tried the following: expect fork respawn setuid www-data chdir /var/www/app/current exec bundle exec unicorn_rails -E production -c

I configure Samba in Share mode, I can see the files but i can't write/delete files in the directory "agenda" The directory /o/aplic/NACSEG/agenda have this permission drwxrwxr-x and the owner and group is agendaglm nobody I have all valid users in the smbpasswd and /etc/passwd This is the smb.conf...........................THANKS! [global] workgroup = GLMSA server

On Zed''s suggestion, I caught two new spinning mongrels and sent a SIGUSR2. The code appears to be stuck in read_multipart for both processes: # kill -USR2 6109 ** USR2 signal received. Thu Sep 21 14:55:39 EDT 2006: Reaping 1 threads for slow workers because of ''shutdown'' Thread #<Thread:0x419d7ce0 run> is too old, killing. Waiting for 1 requests to finish, could

Hi, I''m new to mongrel and so far have liked it a lot during development. I just tried to stand up a production server following the guide here: http://blog.innerewut.de/articles/2006/04/21/scaling-rails-with-apache-2-2-mod_proxy_balancer-and-mongrel This was working well for a few days, until this weekend it crashed with the following stack trace. It''s running on redhat

Hi Today I got an alert mail from my watcher script, telling me that there was no Mongrel running, and that it started one (so the site was down for a few seconds.) This is the first time I got this error (AFAICS), but I''d like to resolve and prevent it for the future. From mongrel.log: ** Starting Mongrel listening at 0.0.0.0:foo ** Starting Rails with production environment... **

Hi, I run a medium-sized website that uses mongrel/rails in the following configuration: -frontend reverse proxy to a cluster of 7 app servers -each app server runs apache 2.2 with mod_proxy_balancer that balancers the requests out into a mongrel cluster of 35 servers. -each mongrel is version 1.0.1 the mongrel cluster config looks like: port: "1620" environment: production address:

Hi all. IF Iam WRITING TO WRONG SAMBA LIST PLEASE TELL ME THAT, I GOT A LITTLE CONFUSED ABOUT THE LIST NAMES I just suscribed to this list and i want to say that i started use samba moustly for file and printer sharing. All ok till now , only two cuestions I need to set up a share folder for two users only , i made some like [folder] valid users usr1 usr2 printable no writable yes