similar to: mysql connection goe away

Hi, in a production environment we are running into "MySQL server has gone away" errors (see below) when we call rebuild_index in aaf. This happens sporadically. Any suggestions for what might be wrong or workarounds? I guess we try a reconnect before we call rebuild_index? Matthew ActiveRecord::StatementInvalid (Mysql::Error: MySQL server has gone away: SELECT count(*) AS

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

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

Recently I started noticing that after running for a while puppetmaster would freeze after a client called `freshness` which would eventually result in the client getting a timeout and the client dyeing. I tracked the freeze down to the call to ActiveRecord::Base.verify_active_connections! in rails.rb on line 26. After scouring the nets I finally found:

Hi, I''m lost and my mysql connection as well... I got this error in my production.log: ActiveRecord::StatementInvalid (Mysql::Error: Lost connection to MySQL server during query: SET NAMES ''utf8''): Config: Debian Sarge (last updated), Rails 1.1.2, Webrick, mysqld Ver 4.1.11-Debian_4sarge2 for pc-linux-gnu on i386 apache2 with mod_rewrite and webrick as proxy on 8080.

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

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

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

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

My app consists of receiving emails with image attachments from its users so I have been employing the MMS2R gem and Fetcher. Every 60 seconds the app goes to the email server to fetch emails. Under Rails 2.1.1 things worked fine - when I received an email, the email was fetched, parsed and saved to the database. However I needed to upgrade to Rails 2.2.2 for unrelated reasons and now I get the

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 have this model: class LineItem < ActiveRecord::Base belongs_to :quote end in the console: >>l = LineItem.create ActiveRecord::StatementInvalid: Mysql::Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' , , , )'' at line 1: INSERT INTO line_items (`qty`, `quote_id`,

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)

*Hello all ** I am a newbie to R plotting maps. I am trying to plot over a world map a layer of Biogeochemical provinces (BGCP) by A.R. Longhurst. Each ocean region unfortunately are quite irregular in shape (not perfect squares). In GIS this layer of ocean provinces would be a layer of polygons, which I am assuming it cannot be plotted with R. I was wondering If anybody has encounter this

I''m struggling with activerecord and mysql blobs (uploading files)... blobs over 400K-ish cause the below exception... ActiveRecord::StatementInvalid in File#upload Mysql::Error: Lost connection to MySQL server during query: I''ve tried blob, mediumblob, and longblob... I''m using windows xp for development - and have not installed the mysql gem... simlar google

I''m trying to upgrade our production server to rails 2. I''ve already done this on my dev machine (osx) and it worked fine. But now, with everything at the same version, but running in production mode, the production machine - a CentOS5 box - is getting loads of: ActiveRecord::StatementInvalid (Mysql::Error: Lost connection to MySQL server during query errors. i"ve looked

CentOS 5.7 on puppet master, Centos 5.7 or 6.0 on clients. puppet 2.7.5 Storeconfig enabled. activerecord-2.3.5 Time to time i got "MySQL server has gone away". How can i fix it? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group,

hello can anybody help me with this bug, (this sometimes occur sometimes passes) 1) ActiveRecord::StatementInvalid in ''MailReader on Simple Tasks should not accept duplicate email'' Mysql::Error: MySQL server has gone away: ROLLBACK TO SAVEPOINT active_record_1 /home/poldz/.gem/ruby/1.8/gems/activerecord-2.3.5/lib/active_record/connection_adapters/abstract_adapter.rb:219:in

Hi all, Ive been getting this error on one particular query repeatedly for the past few days. ActiveRecord::StatementInvalid: Mysql::Error: Lock wait timeout exceeded; try restarting transaction: UPDATE `posts` SET `updated_at` = ''2010-03-17 05:35:00'', `view_count` = 54 WHERE `id` = 158 Googling around, I found that this is basically because the transaction times out after

Dear Royce; Did ur problem resolved? Because now I am facing same problem. It look like that it happens with IAX trunk only, but does not happen with IAX endpoints that registering (as trunk does not register, it sends the call directly). My initial analysis that one of the following can help to let the trunks talk: if there is an IAX endpoints registering to the machines, then trunk become