similar to: "Broken Pipe" FAQ solution a bust

As a follow up from my previous post, I am pondering some changes to my env. I read that with AR I should change the verification timeout to be lower than the MySQL db Interactive_timeout. Now, I have done some performancing tuning to mysql in LAMP env''s but not RoR. MySQL typical set the default interactive_timeout to 8hrs (28800) this has bitten me a few times with sleeping processess

Hi 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 detected by Rails (at least nothing is in the Rails log). Nothing untoward is in the Mongrel log. If you try and visit the application, the request times out

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

Dear ALL, I saw this in article from mongrel faq, Q: Mongrel stops working if it''s left alone for a long time. If you find that Mongrel stops working after a long idle time and you''re using MySQL then you''re hitting a bug in the MySQL driver that doesn''t properly timeout connections. What happens is the MySQL *server* side of the connection times out and

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 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 there, I know this is off-topic or semi off-topic but I really need some help since I am stucked. I'm trying to redirect MariaDB logs to `/var/log/mysql/*.log` files as shown below on the `/etc/my.cnf.d/server.cnf` file: # # These groups are read by MariaDB server. # Use it for options that only the server (but not clients) should see # # See the examples of server

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

On Thu, Mar 12, 2015 at 8:57 AM Tim Dunphy <bluethundr at gmail.com> wrote: > Hey everybody, > > I'm trying to get mysql master/slave replication to work under SSL. I've > created the certs for both the slave and the master. I've configured the > master and slave my.cnf. And it does appear that replication is actually > working. > > Master is actually

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

Hi, > Is anyone else using Dovecot (2.3.8) with MySQL (5.7) seeing a lot of these in MySQL logs? > > 2019-10-28T11:08:20.384428+02:00 58378 [Note] Aborted connection 58378 to db: 'vmail' user: 'vmail' host: 'localhost' (Got an error reading communication packets) > 2019-10-28T11:10:09.821171+02:00 58420 [Note] Aborted connection 58420 to db: 'vmail'

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 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 tried getting our server setup for 400-500 simultaneous calls, calls were going through properly but at around 200-250 calls, mysql (connect ...) statement was taking at least 5-10 sec to connect to the database. I optimized all possible parameters in my.cnf: max_connection=1000 wait_timeout=60 query_cache_type=1 query_cache_limit=4M query_cache_size=512M interactive_timeout=120

Hey everybody, I'm trying to get mysql master/slave replication to work under SSL. I've created the certs for both the slave and the master. I've configured the master and slave my.cnf. And it does appear that replication is actually working. Master is actually MariaDB (version 5.5.41-MariaDB-log, and the slave is MySQL (version 5.5.41-log). But there are two issues I'd like to

We are currntly running mongrel v 1.1.4 mongrel_cluster 1.0.5 mysql gem 2.7.5 (built from source) rails 2.0.2 ruby 1.8.6 mysql version 4.1 this is run on a remote server. We are consistently getting "ActiveRecord::StatementInvalid (Mysql::Error: MySQL server has gone away: SELECT * FROM...." errors. When i then try and stop mongrel some (various) of the mongrels are in error state

> > The mysqld process runs as the mysql user. It's parent which is the > mysqld_safe runs as the root user. That being said the mysql user needs > to have at least read permission to the locations where the ssl files are > > located. By default on Centos the /etc/pki/CA/private directory has its > directory permissions to only allow the root user. If the mysql

Hi everyone, I have been trying to solve this problem for quite some time now and I really don''t have any further clue to investigate. I am running a mongrel_cluster 1.0.5-2 (mongrel verison : 1.1.5-5) on a ubuntu box with apache2 2.2.12-1ubuntu2.1 I have 4 different apps on the same box and each app has two mongrel instances. After a short period of time ( < 2 hours ) some of the

i am using the following comman to fire up mongrel: [sergio@vb_workstation chatlogger]$ mongrel_rails start -d -p 8088 ** You have sendfile installed, will use that to serve files. and everything works fine until some point at night.. i think it is pooping out some time in the middle of the night.. if i try to hit the app in the morning, it just stalls out.. if i restart it, it''s