similar to: Memory error

Hello, I''m just wondering if there could possibly be a memory leak with the latest pre-release? When I run it, the processes keep increasing in memory size and easily pass 200MB and eventually crash due to a lack of memory. Is anybody else having this problem? Thanks, -carl PS, Zed, I sent you two emails directly to your address with logs and other stuff. Let me know if you

Alright, it seems that I am having a bit of a problem with mongrel. My mongrel processes have been crashing pretty often and twice last night. I''m really not sure why, but I really need to fix it. I am running 0.3.13.3. Here is the mongrel.log file. Any ideas, things to look at, etc... is appreciated. Thanks, Carl PS, do all the broken pipe lines mean Mongrel is serving the static

Do you want to get in... ...and got what it takes? I''m working as it-responsible (diplomatic service) for the Republic of Cyprus. Now I want to move on, I know that I have the next big thing in the dot com biz. It all begun from a dream that became a businessplan and also later on was nominated by UN World Summit Awards and won the title as best initiative in category ICT. In a few

Hi Folks, I''ve been getting reports of people with serious stability problems in Mongrel. These problems go away instantly when they remove ruby-sendfile. If your mongrel starts up saying that you have "sendfile installed" and that it is using it then **you are wrong**. Remove the gem and don''t use it. I''ll be investigating why it doesn''t really

Hello, I''m trying to get a new application running with mongrel. I''ve been running a number of applications already using it and it''s been working fine, however now I can''t get mongrel to start. The only difference I can think of is that I''m using postgresql for this and not mysql. However, I am able to run the application using webrick. When

I read in the instructions of Tracks that "upgrading via the rake migrate command is quite a bit more tricky currently with SQLite and SQLite3". Is there any gotcha regarding migrations and SQLite3? -- fxn

Hey guys, Ok, basically I coded a ruby on rails CMS to manage a bunch of media files. I am finding that a lot of people are "hot linking" to these media files and would like to prevent this to save bandwidth. Usually in the past, it hasn''t been a problem, I would add something like the following to my .htaccess file RewriteEngine on RewriteCond %{HTTP_REFERER} !^$

Hi. I''m a fairly new mongrel user and have a scenario that I wanted to run by you all, see if anyone''s synapses connect -- mine def. aren''t! I''m running a fairly simple rails app through a mongrel cluster (2 mongrels). This site is consistently sloooow -- memory on the server is regularly paging (and shouldn''t be). ssh-ing in and running top shows

Hey Folks, I''ve been rather absent lately, but I now have this week slated for full-time Mongrel development. The goal is to get a few big fixes into 0.3.13.4 and release that, and then get a pre-release of 0.4 out for folks to test against. Please make sure you put any outstanding bugs into: http://rubyforge.org/tracker/?atid=5145&group_id=1306&func=browse And any feature

The following is from just two invocations of "mongrel_rails". Is this normal? 57M x 3 seems a little high to me. This is the latest pre-release, Debian sarge, on my VPS. Two Rails apps running against SQLite3, with Pound in front. top - 10:50:12 up 47 days, 12:09, 1 user, load average: 0.06, 0.03, 0.01 Tasks: 52 total, 2 running, 50 sleeping, 0 stopped, 0 zombie Cpu(s):

I hope everyone is getting something out of these recommendations. Today''s recommendation comes from the "Damn Common Sense" dept. of advice. Let''s say you''ve written a really really slow rails application. Best you can get out of the thing is 2 req/sec. What can you possibly do about that? It''s a common problem for new rails developers. Well, the

Hi all, My environment is ruby-1.8.4, rails 1.2.2, mongrel 1.0.1, linux 2.6. Now, i have a problem on memory leaks with mongrel. My site is running 5 mongrel processes on a 2G RAM machine, the memory of each process grows from about 20M to about 250M, but it never recover to the initial 20M, so i had to restart the mongrel processes once per day. The load is about 1M hits per day. Waiting for

Hi all... Hopefully this is the last prelease. If people on non-linux systems could post back any problems with cluster::status, I''d appreciate it. Install with: gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ Note: This is only an update to mongrel_cluster and not Mongrel or other gems. Details about what''s new (if you missed the first

I''m trying to install mongrel and sqlite3 through the gem command on ubuntu. I''m have in the same problem with both. If I try to do sudo gem install sqlite3, it says GemNotFoundException. If I run the same command without sudo, I don''t have permission to some directory: pbarry@pbarry-laptop:~/downloads/rubygems-0.9.0$ sudo gem install sqlite3-ruby ERROR: While

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

Ok, this might sound bad... well, actually it is. I''m my rewrite of mongrel_rails_service and provide a uniform set of commands in the line of gem_plugin commands, found a few issues while stopping the service. Thinking that rails (1.1.2) was responsable, tested against my 1.0.0 rails app, both with the same results. Again, reverted to mongrel 0.3.8, when services was working ok, with

I recently got into using RoR, and the only issue that concerned me was the apparently complexity of deployment. Setting up fastcgi can be a bit of a pain, and I was hoping that the Rails community would come up with something simpler. Mongrel was recommended to me from someone on my local Ruby user group. It was trivial to install as a Gem on my Linux desktop and the FreeBSD server that I am

Hi. A mongrel/rails installation (proxyed through apache) is crashing for some reason with the following error found in the mongrel.log: ERROR: meta.c (179): wmf_header_read: this isn''t a wmf file /root/local/radiant/config/../vendor/rails/activerecord/lib/active_record/base.rb:2068: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24) [i386-linux] Fedora 5 mongrel: 0.3.13.3 Apache/2.2.0

I am having a problem with mongrel just stopping inside a periodically_call_remote function so I ran mongrel with debug enabled Mongrel seg faults after a few minutes The mongrel filelog shows 5 files open when this happens. Same log files that are open all the time. Wed Dec 19 15:10:21 -0700 2007 FILES OPEN BEFORE REQUEST /calibration/ackAdjustDistance --- log/mongrel_debug/objects.log: 2

I''ve been mulling over an idea for a book covering Ruby on Rails application deployment. Obvious topics include using Mongrel by itself and with Apache/Lighttpd, load balancers, memcached, and Capistrano. What other topics would you like to see covered in such a book? Cheers, -- Dave Murphy (Schwuk) http://schwuk.com