search for: mongrel_log

...08.html I had hoped this would go away after a few upgrades but to know avail. Interestingly, the process does not die...it still accepts HTTP requests but does not respond...just sits there deaf. I do a cluster::stop and start and we''re back in action. There is nothing at the tail of mongrel_log..and when I make new connections..nothing gets appended The answers to the previously asked questions are as follows: 1) We do not rotate logs (yet) so we don''t use ruby to rotate 2) ruby script/about About your application''s environment Ruby version 1.8.5 (i68...

...re. * USR1 debugging. If you''re wondering about how Mongrel''s locking of Rails impacts your application, or what is causing BAD CLIENT then just hit your mongrel_rails with USR1 and Mongrel will tell you. * More extensive and accurate memory debugging. Use -B and look at the log/mongrel_log/objects.log to get a good idea of counts of objects, delta changes in counts, and mean+standard deviation lengths of objects with length methods. * Fixes a few places where sockets are closed and left in CLOSE_WAIT. INSTALLING As per usual: sudo gem install mongrel --source=http://mongrel.rubyf...

...xpecting an xml file and obviously isn''t getting what it is supposed to: org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Content is not allowed in prolog. I thought it was unlikely to be helpful but I turned $mongrel_debug_client: kill -USR1 900 This appeared in the mongrel_log but nothing else: ** USR1 received, toggling $mongrel_debug_client to true I''m not able to get the Java program to log any more info about just what request it made until I can get ion touch with the programmer. Somehow I''m stuck thinking there must be a difference in the a...

...re. * USR1 debugging. If you''re wondering about how Mongrel''s locking of Rails impacts your application, or what is causing BAD CLIENT then just hit your mongrel_rails with USR1 and Mongrel will tell you. * More extensive and accurate memory debugging. Use -B and look at the log/mongrel_log/objects.log to get a good idea of counts of objects, delta changes in counts, and mean+standard deviation lengths of objects with length methods. * Fixes a few places where sockets are closed and left in CLOSE_WAIT. INSTALLING As per usual: sudo gem install mongrel --source=http://mongrel.rubyf...

...MON RETVAL=$? diff --git a/conf/ovirt-mongrel-rails b/conf/ovirt-mongrel-rails index e1a6e5c..4050989 100755 --- a/conf/ovirt-mongrel-rails +++ b/conf/ovirt-mongrel-rails @@ -16,7 +16,7 @@ RAILS_ENV="${RAILS_ENV:-production}" OVIRT_DIR="${OVIRT_DIR:-/usr/share/ovirt-server}" MONGREL_LOG="${MONGREL_LOG:-/var/log/ovirt-server/mongrel.log}" MONGREL_PID="${MONGREL_PID:-/var/run/ovirt-server/mongrel.pid}" -MONGREL_LOCKFILE="${MONGREL_LOCKFILE:-/var/lock/subsys/ovirt-server}" +MONGREL_LOCKFILE="${MONGREL_LOCKFILE:-/var/lock/subsys/ovirt-mongrel-rails...