I successfully switched to using mysql and all the problems relating to sqllite and stored configs, locking issues, etc. went away. However, it seems as if something new has suddenly popped up in my puppetmaster logs and the clients are failing to compile their configurations: info: Found proxy in /etc/puppet/manifests/site.pp err: Puppet::Parser::Interpreter failed with error Mysql::Error: Lost connection to MySQL server during query err: Could not store configs: Lost connection to MySQL server during query I tried restarting puppetmaster and mysql, but the same thing keeps happening. The mysql server is local, and isn''t being used by anything else (puppet is the only database there). I''m not sure what I should do, I can probably drop the database and re-create it to see if that solves the problem, but I''d prefer to leave it how it is to have more of an expert see what the issue is in case it is a bug before destroying any chance of debugging. micah
Micah Anderson wrote:> However, it seems as if something new has suddenly popped up in my puppetmaster > logs and the clients are failing to compile their configurations: > > info: Found proxy in /etc/puppet/manifests/site.pp > err: Puppet::Parser::Interpreter failed with error Mysql::Error: Lost connection > to MySQL server during query > err: Could not store configs: Lost connection to MySQL server during query > > I tried restarting puppetmaster and mysql, but the same thing keeps happening. > The mysql server is local, and isn''t being used by anything else (puppet is the > only database there).As mysteriously as it appeared, the errors have disappeared now... micah
On Jun 29, 2007, at 12:41 AM, Micah Anderson wrote:> As mysteriously as it appeared, the errors have disappeared now...I hate this kind of situation, but at least it''s working now. Let us know if it crops back up, I guess. -- What happens to the hole when the cheese is gone? -- Bertolt Brecht --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Luke Kanies wrote:> On Jun 29, 2007, at 12:41 AM, Micah Anderson wrote: > >> As mysteriously as it appeared, the errors have disappeared now... > > I hate this kind of situation, but at least it''s working now. Let us > know if it crops back up, I guess.Mysql server gone away means exactly that. Either the query is caning mysql or the mysql host is untuned/very overloaded. Dave