similar to: Process environment requires procfs(5)

Hello all. I''ve recently installed the 0.2.2 pre-release of mongrel_cluster to try out the new --clean option. However, after installing, when I give a simple "mongrel_rails" command, the cluster::status command is not listed. The error I receive when I do try and run the full "mongrel_rails cluster::status" is... ERROR RUNNING

Hey folks. Sorry for the SUPER long email but if you''ve been experiencing the same problems with restarting your mongrel cluster with Capistrano, then I have two solutions that have worked for me and I''m pretty sure will for you as well. THE PROBLEM I was having trouble restarting my clusters using Capistrano. I''ve seen this come up before on the mailing list and

I''m running the latest mongrel (1.0.1) and the latest mongrel_cluster (1.0.1.1) on FreeBSD 6.1. When I use capistrano to try to stop or restart my cluster I get this (partial) output: ps: Process environment requires procfs(5) And my Mongrel processes haven''t stopped. Any ideas? Thanks, Jamie

I''m running FreeBSD 6.1 and installed the 1.0.1.1 mongrel_cluster prerelease. I had a problem with the mongrels not stopping, and it turns out it''s because ps is reporting my processes as just [ruby18] instead of someting more like "mongrel_rails start -d ......." Not sure why it''s doing that, but it is. Any ideas? For the time being I just changed line

The find_pid method no longer returns a nil by default which causes some breakage in cases where the pid can''t be found since the local variable ''pid'' becomes the entire output of the ''ps'' command. Can you add this return back in so that it behaves the way it did earlier? thanks, eric

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:17.procfs Security Advisory The FreeBSD Project Topic: kernel memory disclosure via procfs Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:17.procfs Security Advisory The FreeBSD Project Topic: kernel memory disclosure via procfs Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- ============================================================================= FreeBSD-SA-00:77 Security Advisory FreeBSD, Inc. Topic: Several vulnerabilities in procfs Category: core Module: procfs Announced: 2000-12-18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

I recently did a backport of a couple of networking bug fixes from s10x_u4_b6 to s10x_u3_b10. I patched just /platform/i86pc/kernel/unix and /platform/i86pc/kernel/amd64/unix in my existing u3 OS image and I''m seeing this dtrace problem when running any dtrace script: NODE hcb101 ~ $ ./tcpstat.sh dtrace: failed to compile script /dev/fd/10: "/usr/lib/dtrace/procfs.d", line

Author: peterte Repository: /hg/zfs-crypto/gate Revision: b681de1a640aeda1c2465325a301eec62c555cef Log message: 6324745 vmem memory leak in the procfs PAGEDATA subsystem. 6329403 hrm_init() cannot ever return -1 but in various places we check for that. 6330765 procfs pagedata can panic machine. Files: update: usr/src/uts/common/vm/hat_refmod.c

Hello all... I know its been a while since the last one, but a new prerelease is available with a gratuitous increase in version numbers! gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ This one has some new features in it that need to be tested on all unix platforms. Please run --clean and cluster::status on every *nix you can find. I run linux so the rest are up

Hi all, I am using libvirt:qemu-kvm and I want to access(RO) the procfs of the guest vm. I was trying to use guestfs for the same purpose. I can access /tmp of the guest but not the /proc Is it a known issue? If so, how can I overcome the same? Any pointers? Snippet> [root@hv285 scoreboards]# virsh list Id Name State

Hi all, I am using libvirt:qemu-kvm and I want to access(RO) the procfs of the guest vm. I was trying to use guestfs for the same purpose. I can access /tmp of the guest but not the /proc Is it a known issue? If so, how can I overcome the same? Any pointers? Snippet> [root@hv285 scoreboards]# virsh list Id Name State

Hi, I am using mongrel for a long time... But just now I see a problem. I am running 3 instances using mongrel_cluster and nginx as a reverse proxy. When I start the cluster I have a memory usage of 20MB per instance... In the end of the day this usage is something about 230MB for each instance. It should be a memory leak? Thanks for the help. -- Fernando Lujan -------------- next part

Hello, I''m running mongrel behind apache via proxypass. Every now and then, a spammer tries to proxy traffic through apache, and for some reason, apache forwards the request to mongrel, even though it''s not a site being hosted by me. At times this seems to cause mongrel to become unresponsive, and all requests to the site then fail with a proxy error until mongrel is

Hello, I really can't say if it's rails or fastcgi related, but sometimes rails is not responding. See some output from ./script/process/reaper: ./script/process/reaper Restarting [22804] /usr/local/bin/ruby18 /usr/home/www/public/dispatch.fcgi Restarting [22806] /usr/local/bin/ruby18 /usr/home/www/public/dispatch.fcgi Restarting [22807] /usr/local/bin/ruby18

Hi, I can''t install Mongrel on Ruby 1.8.6 (patchlevel 279), using Windows XP. My environment: C:\ruby18>gem environment RubyGems Environment: - RUBYGEMS VERSION: 1.2.0 - RUBY VERSION: 1.8.6 (2008-07-17 patchlevel 279) [i386-mingw32] - INSTALLATION DIRECTORY: c:/ruby18/lib/ruby/gems/1.8 - RUBY EXECUTABLE: c:/ruby18/bin/ruby.exe - EXECUTABLE DIRECTORY: c:/ruby18/bin -

Hi There, I''ve got a mongrel cluster running on redhat 9 proxied behind an Apache 2.2 installation. I have run into a real stumbling block in that, while the rails app runs in production mode (you get a production.log file, for example, and I see this in the mongrel log: ** Starting Rails with production environment ... ), it always loads the development database configuration