similar to: Mongrel stops responding after period of inactivity

Hi I posted this to the Ruby on Rails Talk group but I thought I''d post it here too as it''s probably a more appropriate group. Hope this is ok. I''m running a 2-instance Mongrel cluster behind Apache 2.2.4 with Rails 1.2.3. If no requests are received by the application for several hours (this usually happens overnight) then Mongrel stops responding and no requests are

Hi all, Freshly installed apache 2.2 with httpd-itk (from epel). When I try to access apache's document root from a browser on local network, it always serve me the Apache welcome page, even if I have a index.html and a phpinfo.php file in the /var/www/html folder. If point the browser specifically to http://server/index.html, I get a '404 Not found error'. I'm running CentOS

I forgot to mention it. All the files under /var/html are owned by apache:apache On 15-05-07 04:07 PM, Eric Lehmann wrote: > Have you checked the file rights under your document root ? > Your apache group need reading right. > Am 07.05.2015 21:42 schrieb "John" <tuxfed at gmail.com>: > >> Hi all, Freshly installed apache 2.2 with httpd-itk (from epel). When I

Have you checked the file rights under your document root ? Your apache group need reading right. Am 07.05.2015 21:42 schrieb "John" <tuxfed at gmail.com>: > Hi all, Freshly installed apache 2.2 with httpd-itk (from epel). When I > try to access apache's document root from a browser on local network, it > always serve me the Apache welcome page, even if I have a

I am having issues with setting up my apache/mongrel cluster. I am using FC5, and i currently have 3 mongrels running on port 8000,8001, 8002. I am just testing my apache/mongrel deployment on my development machine and not online. I have apache 2.2.2, and my httpd.conf is pretty much the exact default after i yum installed apache 2.2.2. in my /etc/httdp/conf.d , i have myapp.conf, which

Hello everyone, I have developed several ruby apps which are currently live in production. Recently I have encountered a problem where my apps stop responding after a long period of inactivity. I am using Webrick as the server with Rails 1.1.2 and mysql 5.0.21. I have dug up other issues people have had with mysql dropping connections after 8 hours, and the supposed fix of adding an

Subject: How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to 64-bit CentOS Linux 8.2 (2004) Author of this Guide: Mr. Turritopsis Dohrnii Teo En Ming (TARGETED INDIVIDUAL) Country: Singapore Date: 31 August 2020 Monday Singapore Time Type of Publication: Plain Text Document Version: 20200831.01 SECTION 1 Information Gathering Stage ===================================== Host

I just moved from apache2/fcgi to apache2.2/mongrel and everything seems to work great except for 2 issues, one being major and one minor. the major issue i am experiencing is that after a period of time where my rails apps are not used, typically overnight, the mongrel processes become unresponsive. I currently have 3 apps running behind an apache2.2 proxy. every morning when i come in to

I know this question gets asked a lot but I can''t seem to find the answer when I search through the mailing list. First off here''s my set up. Cent OS 4.3 Apache 2.0 Fast CGI 2.4.0 Rails 1.1 Mysql 5.0 The app starts up fine, but every morning it refuses to start and gives me the dreaded Application error untill I reload Apache. I thought my database was timing out so I added

Greetings, I need some help... please be gentle :-) MY SETUP: Solaris-X86, ruby-1.8.4, Apache-2.2.0, Mongrel-0.3.13.4, MySql-4.1.10a I am using the typical setup with apache proxying request to mongrel with mod_proxy_balancer. Currently, I am only running a single instance of mongrel behind the proxy. I am also using the following gems with this app: capistrano (1.2.0) daemons (1.0.2)

Hi, I have had trouble with mongrel freezing after a period of inactivity. Following the advice from the mongrel FAQ, I added: ActiveRecord::Base.verification_timeout = 14400 to my environment.rb file. Unfortunately, that registered a mongrel error: "uninitialized constant ActiveRecord (NameError)" How do I overcome this one? I tried: require ActiveRecord::Base but that registered

Hi, I have Apache (2.2) setup to proxy requests through to Mongrel (0.3.12.4) for a Rails (1.1.2) application (on ruby 1.8.4). The setup is great, but I''m experiencing some nightly failures. I thought I''d post here before digging in too deeply, but it looks like Rails is going into lala land and Mongrel can''t recover... Seems like everything gets all backed up in

Hi, I''m new to RSpec, so I''m not too sure of the best practises in stubbing. I was thinking along the lines of including a helper method that would stub out a users id and posts to sessions/create. It works fine when speccing SessionsController, but of course it fails when it is included into other controllers specs, because of the post. I''ve tried posting to an

I have this error when trying to het in AppDB. Code: Warning: mysql_connect() [function.mysql-connect]: User winehq already has more than 'max_user_connections' active connections in /home/winehq/opt/appdb/include/query.php on line 82 Database error, please try again soon: User winehq already has more than 'max_user_connections' active connections Is there something wrong with

This isnt totally a rails question; I am using ActiveRecord for storing some simple values into a database. My problem; I keep gettign MySQL Errors. On the Win32 machine it was off and on. Now on the linux machine (ubuntu) I can'' t connect at all. I have all the password settings correct. My only thought, I am working with Threads and thought that might cause the issue, but I

A bit about my environment. Fedora Core 6 httpd 2.2.2 ruby (compiled) 1.8.5 gem 0.9.4 rails 1.2.3 ruby/mysql C library 0.2.6 mysql 5.0.27 interactive_timeout = 28800 wait_timeout = 28800 mongrel 1.0.1 I''ve had this experience in other environments with different versions but this configuration is the most recent attempt I''ve made. I get the "Broken Pipe" error after

According to the mongrel_cluster.yml file you provided, you''re starting only 14 mongrels, but in your proxy balancer config you have 30 mongrels listed on ports 21000 - 21029. In this scenario, if apache tries to proxy to any ports higher than 21014 then you''ll get a proxy error as a mongrel doesn''t exist on that port. Or am I missing something? -----Original

I''ve posted this to rails-deployment as well. I have to administer a medium size rails app (1''5 million requests each day), recently I''ve switched from lighttpd + fcgi to apache + mongrel. In the following lines I am going to describe the platform: All machines are running Debian Etch, with 4 gb ram and dual core intel32 processors. Web server runs debian''s

Good morning everyone, I am running apache 2.2.3 compiled from source and proxy load balancer as described on the mongrel site. I have a total of three sites, this setup works really well for two of them but for one of them, I keep getting "Forbidden" errors and this error in the apache logs: [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of

Hi, Recently i''ve studying puppet by reading and doing the examples from this book: "Pro puppet". books.sysadmins.su/system/files/Pro.Puppet.pdf On page 145 from this book there is example about Exporting Load Balancer Worker Resources. I created the files inside already existing apache module. /etc/puppet/modules/apache/manifests/balancermember.pp define