Hello, I''m having an issue with exported resources. I''ve been using stored configs for a while and that all works. But with exported resources, most of the time (but not always), I get the following error: err: Could not retrieve catalog: Puppet::Parser::Compiler failed with error ActiveRecord::StatementInvalid: Mysql::Error: MySQL server has gone away: SELECT * FROM `hosts` WHERE (`hosts`.`name` = ''r...'') LIMIT 1 on node ... This is with Ubuntu 8.04 64-bit, rails 2.0.4, mysql gem 2.7 and passenger 2.0.6, Gary --~--~---------~--~----~------------~-------~--~----~ 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, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
"MySQL server has gone away" means you lost your connection to mysql, most likely because there is a configured idle timeout or the server was restarted. On Jan 15, 2009, at 11:15 PM, gary wrote:> > Hello, > > I''m having an issue with exported resources. I''ve been using stored > configs for a while and that all works. But with exported resources, > most of the time (but not always), I get the following error: > > err: Could not retrieve catalog: Puppet::Parser::Compiler failed with > error ActiveRecord::StatementInvalid: Mysql::Error: MySQL server has > gone away: SELECT * FROM `hosts` WHERE (`hosts`.`name` = ''r...'') > LIMIT 1 on node ... > > This is with Ubuntu 8.04 64-bit, rails 2.0.4, mysql gem 2.7 and > passenger 2.0.6, > > Gary > > >--~--~---------~--~----~------------~-------~--~----~ 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, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hello Jason, My MySQL wait_timeout is set to the default of 8 hours. Through IRC, James and Andrew had looked into it a bit. From what we all read, Puppet should be checking the connection and re-establishing it if necessary. Perhaps I''m missing something in the config. In [puppetmasterd], I have dbsocket set to /var/run/mysqld/mysqld.sock. I also have a rails section without a dbsocket. I forgot what I added that section for, maybe puppetshow or maybe it''s not needed. Gary On Jan 16, 10:41 pm, Jason Kohles <jasonkoh...@gmail.com> wrote:> "MySQL server has gone away" means you lost your connection to mysql, > most likely because there is a configured idle timeout or the server > was restarted. > > On Jan 15, 2009, at 11:15 PM, gary wrote: > > > > > Hello, > > > I''m having an issue with exported resources. I''ve been using stored > > configs for a while and that all works. But with exported resources, > > most of the time (but not always), I get the following error: > > > err: Could not retrieve catalog: Puppet::Parser::Compiler failed with > > error ActiveRecord::StatementInvalid: Mysql::Error: MySQL server has > > gone away: SELECT * FROM `hosts` WHERE (`hosts`.`name` = ''r...'') > > LIMIT 1 on node ... > > > This is with Ubuntu 8.04 64-bit, rails 2.0.4, mysql gem 2.7 and > > passenger 2.0.6, > > > Gary--~--~---------~--~----~------------~-------~--~----~ 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, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Jan 20, 2009, at 3:34 AM, gary wrote:> Hello Jason, > > My MySQL wait_timeout is set to the default of 8 hours. Through IRC, > James and Andrew had looked into it a bit. From what we all read, > Puppet should be checking the connection and re-establishing it if > necessary. > > Perhaps I''m missing something in the config. In [puppetmasterd], I > have dbsocket set to /var/run/mysqld/mysqld.sock. I also have a rails > section without a dbsocket. I forgot what I added that section for, > maybe puppetshow or maybe it''s not needed.I don''t know much about this problem -- Puppet basically just passes these settings on to Rails and doesn''t do anything itself here -- but I can tell you that any Rails section will get ignored in recent releases of Puppet. Only sections named after environments or executables are used at the moment. -- Charm is a way of getting the answer yes without asking a clear question. -- Albert Camus --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Thanks Luke, I commented out [rails] in puppet.conf. I forgot what I was using it anyway. I tried updating all gems to the their newest versions without success. I also tried using postgres but I got the error which the wiki says happens when the gem is not installed. Strange. So I am back to SQLite. :( That works. Gary On Jan 23, 1:59 pm, Luke Kanies <l...@madstop.com> wrote:> On Jan 20, 2009, at 3:34 AM, gary wrote: > > > Hello Jason, > > > My MySQL wait_timeout is set to the default of 8 hours. Through IRC, > > James and Andrew had looked into it a bit. From what we all read, > > Puppet should be checking the connection and re-establishing it if > > necessary. > > > Perhaps I''m missing something in the config. In [puppetmasterd], I > > have dbsocket set to /var/run/mysqld/mysqld.sock. I also have a rails > > section without a dbsocket. I forgot what I added that section for, > > maybe puppetshow or maybe it''s not needed. > > I don''t know much about this problem -- Puppet basically just passes > these settings on to Rails and doesn''t do anything itself here -- but > I can tell you that any Rails section will get ignored in recent > releases of Puppet. Only sections named after environments or > executables are used at the moment. > > -- > Charm is a way of getting the answer yes without asking a clear > question. -- Albert Camus > --------------------------------------------------------------------- > Luke Kanies |http://reductivelabs.com|http://madstop.com--~--~---------~--~----~------------~-------~--~----~ 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, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Jan 23, 2009, at 12:31 AM, Gary wrote:> Thanks Luke, > > I commented out [rails] in puppet.conf. I forgot what I was using it > anyway. > > I tried updating all gems to the their newest versions without > success. I also tried using postgres but I got the error which the > wiki says happens when the gem is not installed. Strange. > > So I am back to SQLite. :( That works.Could it be a problem with multiple ruby installs? It certainly seems like a Ruby issue, anyway. -- No one who cannot rejoice in the discovery of his own mistakes deserves to be called a scholar. --Donald Foster --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Fri, 2009-01-16 at 09:41 -0500, Jason Kohles wrote:> "MySQL server has gone away" means you lost your connection to mysql, > most likely because there is a configured idle timeout or the server > was restarted.Or, more probably the mysql server has crashed, for any reasons (including crashed/corrupted tables). Note that mysql usually run inside a wrapper that relaunches it automatically if it crashes, so that''s easy to not notify mysql is down. I suggest you look into your syslog file to see if there is anything suspect, like errors or backtrace. Hope that helps, -- Brice Figureau My Blog: http://www.masterzen.fr/ --~--~---------~--~----~------------~-------~--~----~ 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, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hello, I''ve tried using mysql on another server as well. No crashes since we use the server for other DBs as well. Luke, you asked about multiple ruby versions. yes there are: one from ubuntu, and 1.8.6-p111 with RailsBench GC patch at /usr/local/bin/ ruby. I made sure that both had all necessary gems. Still a mystery. :) I had also tried to create a fact to say which puppetd (for something else), and it always show /usr/bin/puppetd. Gary On Jan 28, 10:30 pm, Brice Figureau <brice-pup...@daysofwonder.com> wrote:> On Fri, 2009-01-16 at 09:41 -0500, Jason Kohles wrote: > > "MySQLserver has gone away" means you lost your connection tomysql, > > most likely because there is a configured idle timeout or the server > > was restarted. > > Or, more probably themysqlserver has crashed, for any reasons > (including crashed/corrupted tables). Note thatmysqlusually run inside > a wrapper that relaunches it automatically if it crashes, so that''s easy > to not notifymysqlis down. > > I suggest you look into your syslog file to see if there is anything > suspect, like errors or backtrace. > > Hope that helps, > -- > Brice Figureau > My Blog:http://www.masterzen.fr/--~--~---------~--~----~------------~-------~--~----~ 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, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---