Issue #4694 has been updated by Stefan Schulte.
Here is some output from rails.log Failure 01: <pre> D, [2011-10-14T15:23:09.474878 #20802] DEBUG -- : Puppet::Rails::FactName Load (0.3ms) SELECT `fact_names`.* FROM `fact_names` WHERE `fact_names`.`name` = 'clientversion' LIMIT 1 D, [2011-10-14T15:23:09.478551 #20802] DEBUG -- : Puppet::Rails::FactName Load (0.3ms) SELECT `fact_names`.* FROM `fact_names` WHERE `fact_names`.`name` = 'is_virtual' LIMIT 1 D, [2011-10-14T15:23:09.504577 #20802] DEBUG -- : Puppet::Rails::FactName Load (23.0ms) SELECT `fact_names`.* FROM `fact_names` WHERE `fact_names`.`name` = 'virtual' LIMIT 1 D, [2011-10-14T15:23:09.504760 #20802] DEBUG -- : Mysql2::Error: Lost connection to MySQL server during query: SELECT `fact_names`.* FROM `fact_names` WHERE `fact_names`.`name` = 'virtual' LIMIT 1 D, [2011-10-14T15:24:02.412434 #20802] DEBUG -- : Puppet::Rails::Host Load (1.0ms) SELECT `hosts`.* FROM `hosts` WHERE `hosts`.`name` = 'XXX' LIMIT 1 </pre> Failure 02: <pre> D, [2011-10-14T16:16:08.253846 #20856] DEBUG -- : Puppet::Rails::FactName Load (0.2ms) SELECT `fact_names`.* FROM `fact_names` WHERE `fact_names`.`name` = 'ipaddress_nxge3_4' LIMIT 1 D, [2011-10-14T16:16:08.280055 #20856] DEBUG -- : Puppet::Rails::FactName Load (24.3ms) SELECT `fact_names`.* FROM `fact_names` WHERE `fact_names`.`name` = 'kernelrelease' LIMIT 1 D, [2011-10-14T16:16:08.280223 #20856] DEBUG -- : Mysql2::Error: Lost connection to MySQL server during query: SELECT `fact_names`.* FROM `fact_names` WHERE `fact_names`.`name` = 'kernelrelease' LIMIT 1 D, [2011-10-14T16:16:08.359105 #20806] DEBUG -- : Puppet::Rails::ParamValue Load (0.8ms) SELECT `param_values`.* FROM `param_values` WHERE (`param_values`.resource_id = 157) AND (param_name_id = 4) D, [2011-10-14T16:16:08.360513 #20806] DEBUG -- : Puppet::Rails::ParamValue Load (0.3ms) SELECT `param_values`.* FROM `param_values` WHERE (`param_values`.resource_id = 157) AND (param_name_id = 3) </pre> When I search for the error on google I mostly find timeout related problems. But since the error happens during a facts retrieval (as far as I can tell) and after a few successfull queries that does not seem to be the case here. ---------------------------------------- Bug #4694: Storeconfig issue with AR/MySQL https://projects.puppetlabs.com/issues/4694 Author: Andrew Forgue Status: Accepted Priority: Normal Assignee: Category: stored configuration Target version: Affected Puppet version: 0.25.5 Keywords: stored configs Branch: We're having an issue with storeconfigs generating random MySQL disconnect errors. This is not related to #2880 or #2816. Though I suspect that the underlying cause may be the same. First: err: Mysql::Error: MySQL server has gone away: INSERT INTO `fact_values` (...) Second: err: Puppet::Parser::Compiler failed with error ActiveRecord::StatementInvalid: Mysql::Error: Lost connection to MySQL server during query: SELECT * FROM `param_values` WHERE (`param_values`.resource_id = 1136908 AND (param_name_id = 133)) on node xxx. Third: err: Mysql::Error: Lost connection to MySQL server during query: SELECT t.id, t.resource_id, p.name FROM resource_tags as t INNER JOIN resources r ON t.resource_id=r.id INNER JOIN puppet_tags as p ON t.puppet_tag_id=p.id WHERE r.host_id=531 So they're coming from all over the place. I've verified that in the code we're using, reconnect is set to true but it's not reconnecting. Here's the versions: * Puppet 0.25.5 * Rails 2.3.8 * Mongrel 1.1.5 * OS X Leopard (server) * MySQL gem 2.8.1 * MySQL client library 5.0.82 * MySQL server 5.1.48 * Ruby 1.8.7-p22 Here's a summary of a single incident -- puppet server (puppet) to SQL server conversation: Puppet -> SQL: SYN Puppet <- SQL: SYN+ACK Puppet -> SQL: ACK So the TCP connection is open, 1. MySQL Login successful 1. SET NAMES 1. SELECT * FROM HOSTS where hosts.name='hostname' 1. SELECT Facts for host 1. executes a bunch of queries for facts 1. Runs SELECT `param_names`.* FROM `param_names` INNER JOIN `param_values` ON `param_names`.id = `param_values`.param_name_id WHERE ((`param_values`.resource_id = 943831)) 1. Server returns results and then the client issues a quit (!)? 1. Socket is shutdown, client sends FIN+ACK, server responds with FIN+ACK 1. Server sends RST to client twice. I've been working on this for a day or 2 and I have no idea what could be causing this. I don't see any pattern. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
