similar to: heel 0.2.0 - simple directory webserving with mongrel

Sorry if this is the wrong place to ask, but when I run mongrel evented using swiftiply and then send it the USR2 signal to restart it, it dies. Without eventing, USR2 restarts mongrel as expected. Anyone else seen this? Here''s a dump: $ EVENT=1 mongrel_rails start -d -P /tmp/m.pid -p 4321 Using Evented Mongrel ** Ruby version is up-to-date; cgi_multipart_eof_fix was not loaded $ kill

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 Just a few minutes back I came across a post about autotest/zentest and that post reignited the feeling I get when I look at RDoc, RoR documentation. The main thing that is lacking in RoR and to some extent Ruby''s RDoc is showing method names in HTML is not documentation. The arguments to method, exception/errors raised by method, return value and a usage example completes the

Hi all, I''m playing around with mongrel handlers and I came across a behaviour that seems abnormal to me with regard to the Configurator#uri calls. It appears that order matters. For instance: ... listener do uri "/icons", :handler => DirHandler.new("/var/www/icons") uri "/", :handler =>

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

I was pushing out a new version of a site I have that I think was last generated with webgen 0.4.1. Since my gems are updated to 0.4.4 I''m getting this error when running ''webgen''. I''ve reverted back to 0.4.2 and that is the version where this custom vertical menu plugin starts breaking. So I''m not sure what has changed to cause this. I get this

Hi there, Even though I am running Mongrel in development mode, I have to manually restart Mongrel to load any changes that I have made to controller or model code. This is the output when I start Mongrel: $ script/server start ./script/../config/boot.rb:29:Warning: require_gem is obsolete. Use gem instead. => Booting Mongrel (use ''script/server webrick'' to force WEBrick)

Hi, I have some problem with mongrel server. While I am trying access http://localhost:3000, getting the following error message mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). **

Hi, I'm in the process of setting up a backup server for a somewhat antiquated NT4 server. Backup server is CentOS-4 (~ RHEL-4), kernel-2.6.9-11.EL, samba-client-3.0.10-1.4E, rsync-2.6.3-1, LANG=en_US.UTF-8. NT4 shares are mounted on the server and rsynced to local disk. This setup is working pretty well, however on the NT box there are some files with names containing odd characters like

Hello, I don''t know if this is really relevant anymore because a new version is about to be released it seems, however I''ve been trying to run mongrel 0.3.12.4 on a development server in development mode (simply with mongrel_rails start). I try to access the server and the first page (static file) loads, but then the server dies and I get this in the logs. I''m

On Sat, 20 Oct 2001, Jack Moffitt wrote: > I changed the libshout2 and thread module apis. This broke everything. > If you are tracking CVS, make sure to update your libshout2 and the > thread module. Ices2 and Icecast2 already uses these new changes, which > were implemented as part of general cleanup and getting Solaris builds > out of clean tarballs. > > If anyone is

I''m trying to deploy a rails app for development on slicehost and I can''t seem to get mongrel to work correctly. When I run mongrel_rails start I get: ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop

https://bugzilla.samba.org/show_bug.cgi?id=5040 Summary: multiple mount point directory sources aren't completely recursive Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

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*)

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/

Hello! Run problems after upgrading to mongrel 1.0.3 from 1.0.1: # uname -sr FreeBSD 7.0-BETA1 # mongrel_rails start ** Starting Mongrel listening at :3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload

[ Asked on -questions on Friday; re-asking now on -stable without cross-post] I recently upgraded a 4.11-REL machine to 6.0-REL and have run into some snags. While the installation from CD went fine, after configuring and enabling my ed0 NIC, bad things start to happen. FWIW, this machine is an ancient (hardware circa 1991, BIOS circa 1994) dual-Pentium 133 MHz machine, with EISA/PCI and

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

Dear list members, I get the following error when using the glht function to perform a post hoc analysis for an ANOVA with repeated measures: require(nlme) lme_H2H_musicians = lme(H2H ~ Emotion*Material, data=musicians, random = ~1|Subject) require(multcomp) summary(glht(lme_H2H_musicians, linfct=mcp(Type = "Tukey")), test = adjusted(type = "bonferroni")) Error in

Hello everybody, problem solved, there was a typo. I wrote Type instead of Material Best ----Messaggio originale---- Da: angelo.arcadi@virgilio.it Data: 22-giu-2012 11.05 A: <r-help@r-project.org> Ogg: Error with glht function: Error in mcp2matrix(model, linfct = linfct) : Variable(s) 'Type' have been specified in 'linfct' but cannot be found in 'model'!