similar to: Mongrel Processes Dying

I tried the mime thing but it did not help. I didn''t think it was that because I can get the mp3 served OK hitting the URL in a browser. I just noticed that I am getting an error in Mongrel when WinAmp make the request for the mp3 file: BAD CLIENT (127.0.0.1): Invalid HTTP format, parsing fails. I don''t think Mongrel has a problem with the URL itself because if a browser

Mongrel 0.3.13.3 Windows XP Rails 1.1.6 I have a rails app that serves up mp3 files via the send_file command. We create a playlist (M3U) with URLs to the mp3s. These play just fine using Windows Media Player. However using WinAmp we get an error "error syncing to stream" when it tries to request the mp3. After playing around I found that if I am running Rails under Webrick WinAmp

Hello, I have mongrel 1.0.1, rails 1.2.2 ruby 1.8.5 running on Centos 4.4. When I execute the mongrel_rails start -d I see that 3 processes are spawned. See below: [root at ccc aaa]# mongrel_rails start -d [root at ccc aaa]# ps -def |grep mong root 2743 1 9 07:14 ? 00:00:01 /usr/bin/ruby /usr/bin/mongrel_rails start -d root 2744 2743 0 07:14 ? 00:00:00

I''m using monit to restart mongrel processes if they go away. With mongrel 0.3 I could issue a start command and the process would start up even if the .pid file existed (though a warning would appear). Now, with mongrel 1.0.1 the warning says I must clear the .pid file and the process is not started. Is there anyway to force it to start without having to clear the .pid? Regards

I have Mongrel Cluster setup with Apache a mod_proxy_balancer. I''ve seen (from time to time) mongrel instances become non-responsive. Is there anyway to configure the balancer so that it "knows" which processes are no longer good and stops trying to use them? _______________________________________________________ The FREE service that prevents junk email

Hi, I''m in the process of moving my blog over from lighttpd -> apache 2.2 + mongrel. Everything works fine as long as I don''t reboot :) On reboot apache comes up but mongrel_cluster doesn''t start up the pooches... I have added the mongrel_cluster call to my startup scripts like so: www:/etc/init.d# update-rc.d mongrel_cluster defaults Adding system startup for

Hi, I''ve got to active project both running on the last Apache 2.2 and on Mongrel 0.3.13.3. One is running perfectly, the other gets (always on the same pages, but not after each request, it seems to be random) a ProxyError every now and then which leads to the mongrel process being called to die and subsequently slowing down the whole web site. I have to restart the mongrel

Hi, I''m running CentOS 4.3 and the latest Mongrel (0.3.13.3) and mongrel_cluster (0.2.0). I have set up a cluster, following the instructions at http://mongrel.rubyforge.org/docs/mongrel_cluster.html . I created a symbolic link in the directory /etc/mongrel_cluster . When I run mongrel_rails cluster::start -c test.yml, the mongrel servers start up. But at boot, the command

Hi all, I encounter timeout errors during file uploads in my Rails application. I think the problem may be in the Mongrel configuration. Here is my setup: * Load balancer (Cisco CSM, my provider''s Catalyst 6509) * Apache 2.2.3 with mod_proxy_balancer * Mongrel 0.3.13.3 * Rails 1.1.6 * Ruby 1.8.4 * MySQL 5.0.22 * file_column I host an application in which users may upload medium files

Yo Zed and everyone else, I''m having a major problem I''m hoping someone can help with. I''ve been running mongrel clusters for a few months with no problems on a couple of my boxes. They both run Debian... I recently moved one of my older Rails apps on a FreeBSD 5.5 box to mongrel as well. Everything runs quickly and wonderfully - when it''s running! My problem

Hi everyone, I''m having a problem starting rails on solaris. I have made the changes suggested in the joyeur article but it doesn''t make any difference. The error is below. Does anyone have any idea? /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in `register'': undefined method `resolve'' for nil:Mongrel::URIClassifier (NoMethodError)

Hi all, I''ve been having problems with the apache 2.2-mod_proxy_balancer- mongrel setup. My setup is: CentOS 4.3 apache 2.2.3 (compiled from source) with mod_proxy_balancer mysql 4.1 ruby 1.8.4 mongrel 0.3.14 (I know I need to update but I think this problem is independent of the mongrel version) mongrel_cluster 0.2.0 rails_machine 0.1.1 I have apache setup as per Coda''s

Hi, I use ferret 0.10.4 whith shared index over NFS directory. There are 2 applications servers. The web server is Mongrel 0.3.13.3 and mongrel_cluster 0.2.0. There are 20 Mongrel processes on each server. Each time my application update a model, Mongrel process stops running with this errro in its log: /usr/lib/ruby/gems/1.8/gems/ferret-0.10.4/lib/ferret/index.rb:663: [BUG] Segmentation fault

First off: Our clusters are LVS balanced Apache 2.2.3 + mod_proxy_balancer + gem mongrel 0.3.13.3 / mongrel_cluster 0.2 + memcached / gem memcache_client + gem rails 1.1.6 on debian boxen, and a pgcluster backend. On 2 of our deployed clusters, we are getting the "spinning mongrel" problem. As the clusters are very low volume right now, it takes days to collect a spinner, making it

Hey guys, I''m running the mongrel server that comes with rails-1.2rc1 for development on a winxp box, anticipating taking it into production on a win2k3 box in the next few weeks. I''ve had a couple of crashes occur during development that give me pause, however. I made a ticket for the last one here: http://dev.rubyonrails.org/ticket/6841 I know, or at least believe, that

We tried to give Mongrel a go running our application which has moderate traffic. We got mongrel up and running easy enough but 3 times in a short period(2hours) mongrel just died with the following error when we went live to production with it. As you can see we are running mongrel-0.3.13.3. /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:576:in`peeraddr'': Transport endpoint

I wanted to be able to specify in my /etc/rc.conf file whether mongrel_cluster should be enabled and the mongrel_cluster_config file for the init script, so I wrote this simple rc.d style script. Just throw it in /usr/local/etc/rc.d/ and do a chmod +x /usr/local/etc/rc.d/mongrel_cluster.sh To enable the script, add mongrel_cluster_enable="YES" to /etc/rc.conf and optionally add

Hello, I have a working mongrel cluster and want to use Lighty as the frontend webserver. I want ligthttpd to deliver the static content. So I did gem install sendfile --remote Everything installed. But if I run the tests like gem check sendfile --test --debug i get the following error message: Exception `Errno::ENOSYS'' at ./test/test_sendfile.rb:75 - Function not implemented -

Hi Guys, I?m getting this error with mongrel_cluster. I am able to start mongrel through mongrel_rails start but the cluster is not working. Initially mongrel_rails wouldn?t work but after I added $ORACLE_HOME and $PD_LIBRARY_PATH variables it worked but mongrel_cluster isn?t working still. The mongrel log file looks like below. Any help is appreciated. Thanks. -----------begin

Hi folks, I''d like to run the Mongrel prerelease (0.3.13.4 prerelease) and mongrel_cluster 0.2.1 on my shared host (which doesn''t want to install prerelease software for all to use). I can install the gems in my own directory, and run mongrel 0.3.13.4 with --prefix just fine. However, I think due to the GemPlugin structure, even my new mongrel_rails loads up