Joe McDonagh
2010-May-03 19:33 UTC
[Puppet Users] Issue with naginator and elusive nagios cfg file corruption (#3712)
Hello, I have run into a data corruption problem with naginator that is fairly difficult for me to track down. Hand-written configurations do not suffer from this fate. This was present in .24.8, and still present in .25.4. I''d love to complete this automatic nagios project, if anyone has some ideas on narrowing down the source after reading the bug report (http://projects.reductivelabs.com/issues/3712) please let me know. -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode "When the going gets weird, the weird turn pro." -- 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.
David Schmitt
2010-May-04 19:00 UTC
Re: [Puppet Users] Issue with naginator and elusive nagios cfg file corruption (#3712)
Am 03.05.2010 21:33, schrieb Joe McDonagh:> Hello, I have run into a data corruption problem with naginator that is > fairly difficult for me to track down. Hand-written configurations do > not suffer from this fate. This was present in .24.8, and still present > in .25.4. I''d love to complete this automatic nagios project, if anyone > has some ideas on narrowing down the source after reading the bug report > (http://projects.reductivelabs.com/issues/3712) please let me know.You can try using a hex editor or similar to see what the actual corruption is. Also, can you post a minimal configuration example that causes the problem? From where have you installed puppet? Packages, source? Can you confirm that the installation is pristine? Are you using storeconfigs? Is there maybe something wrong in the database? I''ve used the nagios types from 0.25.4 today and they worked flawlessly. Best regards, David -- dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at Klosterneuburg UID: ATU64260999 FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg -- 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.
Joe McDonagh
2010-May-04 20:38 UTC
Re: [Puppet Users] Issue with naginator and elusive nagios cfg file corruption (#3712)
On 05/04/2010 03:00 PM, David Schmitt wrote:> Am 03.05.2010 21:33, schrieb Joe McDonagh: >> Hello, I have run into a data corruption problem with naginator that is >> fairly difficult for me to track down. Hand-written configurations do >> not suffer from this fate. This was present in .24.8, and still present >> in .25.4. I''d love to complete this automatic nagios project, if anyone >> has some ideas on narrowing down the source after reading the bug report >> (http://projects.reductivelabs.com/issues/3712) please let me know.David, just wanna say thanks for responding to this as it''s driving me absolutely insane and causing a project I want to end to linger forever.> > You can try using a hex editor or similar to see what the actual > corruption is.David, I tried this and got absolutely nowhere. I''m willing to believe I am doing something wrong when analyzing the data, but the tests I''ve tried which I think will narrow down the corruption actually make it more difficult to diagnose. For example, if apt-proxys.cfg was having the problem, and i renamed the hostgroup to ZZZZ, it would then claim the error was in the next alphabetical hostname, say domino-servers, until i get past a few and it runs.> > Also, can you post a minimal configuration example that causes the > problem?Here''s the error: Error: Host '' '' specified in host group ''ad-servers'' is not defined anywhere! Here''s the .cfg file: # HEADER: This file was autogenerated at Mon May 03 13:59:19 -0400 2010 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. define hostgroup { hostgroup_name ad-servers alias Active Directory Servers } Here is a hex dump 0000000 2023 4548 4441 5245 203a 6854 7369 6620 0000020 6c69 2065 6177 2073 7561 6f74 6567 656e 0000040 6172 6574 2064 7461 4d20 6e6f 4d20 7961 0000060 3020 2033 3331 353a 3a39 3931 2d20 3430 0000100 3030 3220 3130 0a30 2023 4548 4441 5245 0000120 203a 7962 7020 7075 6570 2e74 2020 6857 0000140 6c69 2065 7469 6320 6e61 7320 6974 6c6c 0000160 6220 2065 616d 616e 6567 2064 616d 756e 0000200 6c61 796c 202c 7469 230a 4820 4145 4544 0000220 3a52 6920 2073 6564 6966 696e 6574 796c 0000240 6e20 746f 7220 6365 6d6f 656d 646e 6465 0000260 0a2e 6564 6966 656e 6820 736f 6774 6f72 0000300 7075 7b20 090a 6f68 7473 7267 756f 5f70 0000320 616e 656d 2020 2020 2020 2020 2020 2020 0000340 2020 2020 6120 2d64 6573 7672 7265 0a73 0000360 6109 696c 7361 2020 2020 2020 2020 2020 0000400 2020 2020 2020 2020 2020 2020 2020 2020 0000420 6341 6974 6576 4420 7269 6365 6f74 7972 0000440 5320 7265 6576 7372 7d0a 000a 0000453 Now I change the file to this: # HEADER: This file was autogenerated at Mon May 03 13:59:19 -0400 2010 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. define hostgroup { hostgroup_name ZZ alias Active Directory Servers } And I get this: Error: Host '' '' specified in host group ''ZZ'' is not defined anywhere! It indicates to me that the file is fucked somehow. This is written out from an exported and collected resource. Is it possible database encoding comes into play here?> > From where have you installed puppet? Packages, source? Can you > confirm that the installation is pristine? >I make my own packages but they are basically just dsc''s from ftp.ubuntu.org that I build for 8.04 LTS since the 8.04 LTS package is so old. They are installed via apt.> Are you using storeconfigs? Is there maybe something wrong in the > database?That''s what I am wondering but I don''t know what to look for. Things look fine. The file itself, looks fine. There''s corruption at the byte level that isn''t apparent to the human eye. Any idea what to check in the DB?> > I''ve used the nagios types from 0.25.4 today and they worked flawlessly.I know, I think I may have even taken some inspiration from your modules.> > > Best regards, David-- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode "When the going gets weird, the weird turn pro." -- 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.
Joe McDonagh
2010-May-06 15:47 UTC
Re: [Puppet Users] Issue with naginator and elusive nagios cfg file corruption (#3712)
On 05/04/2010 04:38 PM, Joe McDonagh wrote:> On 05/04/2010 03:00 PM, David Schmitt wrote: >> Am 03.05.2010 21:33, schrieb Joe McDonagh: >>> Hello, I have run into a data corruption problem with naginator that is >>> fairly difficult for me to track down. Hand-written configurations do >>> not suffer from this fate. This was present in .24.8, and still present >>> in .25.4. I''d love to complete this automatic nagios project, if anyone >>> has some ideas on narrowing down the source after reading the bug >>> report >>> (http://projects.reductivelabs.com/issues/3712) please let me know. > David, just wanna say thanks for responding to this as it''s driving me > absolutely insane and causing a project I want to end to linger forever. >> >> You can try using a hex editor or similar to see what the actual >> corruption is. > David, I tried this and got absolutely nowhere. I''m willing to believe > I am doing something wrong when analyzing the data, but the tests I''ve > tried which I think will narrow down the corruption actually make it > more difficult to diagnose. For example, if apt-proxys.cfg was having > the problem, and i renamed the hostgroup to ZZZZ, it would then claim > the error was in the next alphabetical hostname, say domino-servers, > until i get past a few and it runs. >> >> Also, can you post a minimal configuration example that causes the >> problem? > Here''s the error: Error: Host '' '' specified in host group ''ad-servers'' > is not defined anywhere! > > Here''s the .cfg file: > > # HEADER: This file was autogenerated at Mon May 03 13:59:19 -0400 2010 > # HEADER: by puppet. While it can still be managed manually, it > # HEADER: is definitely not recommended. > define hostgroup { > hostgroup_name ad-servers > alias Active Directory Servers > } > > Here is a hex dump > > 0000000 2023 4548 4441 5245 203a 6854 7369 6620 > 0000020 6c69 2065 6177 2073 7561 6f74 6567 656e > 0000040 6172 6574 2064 7461 4d20 6e6f 4d20 7961 > 0000060 3020 2033 3331 353a 3a39 3931 2d20 3430 > 0000100 3030 3220 3130 0a30 2023 4548 4441 5245 > 0000120 203a 7962 7020 7075 6570 2e74 2020 6857 > 0000140 6c69 2065 7469 6320 6e61 7320 6974 6c6c > 0000160 6220 2065 616d 616e 6567 2064 616d 756e > 0000200 6c61 796c 202c 7469 230a 4820 4145 4544 > 0000220 3a52 6920 2073 6564 6966 696e 6574 796c > 0000240 6e20 746f 7220 6365 6d6f 656d 646e 6465 > 0000260 0a2e 6564 6966 656e 6820 736f 6774 6f72 > 0000300 7075 7b20 090a 6f68 7473 7267 756f 5f70 > 0000320 616e 656d 2020 2020 2020 2020 2020 2020 > 0000340 2020 2020 6120 2d64 6573 7672 7265 0a73 > 0000360 6109 696c 7361 2020 2020 2020 2020 2020 > 0000400 2020 2020 2020 2020 2020 2020 2020 2020 > 0000420 6341 6974 6576 4420 7269 6365 6f74 7972 > 0000440 5320 7265 6576 7372 7d0a 000a > 0000453 > > Now I change the file to this: > > # HEADER: This file was autogenerated at Mon May 03 13:59:19 -0400 2010 > # HEADER: by puppet. While it can still be managed manually, it > # HEADER: is definitely not recommended. > define hostgroup { > hostgroup_name ZZ > alias Active Directory Servers > } > > And I get this: > > Error: Host '' '' specified in host group ''ZZ'' is not defined anywhere! > > It indicates to me that the file is fucked somehow. This is written > out from an exported and collected resource. Is it possible database > encoding comes into play here? > > >> >> From where have you installed puppet? Packages, source? Can you >> confirm that the installation is pristine? >> > I make my own packages but they are basically just dsc''s from > ftp.ubuntu.org that I build for 8.04 LTS since the 8.04 LTS package is > so old. They are installed via apt. >> Are you using storeconfigs? Is there maybe something wrong in the >> database? > That''s what I am wondering but I don''t know what to look for. Things > look fine. The file itself, looks fine. There''s corruption at the byte > level that isn''t apparent to the human eye. Any idea what to check in > the DB? >> >> I''ve used the nagios types from 0.25.4 today and they worked flawlessly. > I know, I think I may have even taken some inspiration from your modules. >> >> >> Best regards, David > >Anybody else care to chime in on this issue? Any mysql gurus? -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode "When the going gets weird, the weird turn pro." -- 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.
Joe McDonagh
2010-May-18 01:07 UTC
[Puppet Users] Re: Issue with naginator and elusive nagios cfg file corruption (#3712)
On 05/03/2010 03:33 PM, Joe McDonagh wrote:> Hello, I have run into a data corruption problem with naginator that is > fairly difficult for me to track down. Hand-written configurations do > not suffer from this fate. This was present in .24.8, and still present > in .25.4. I''d love to complete this automatic nagios project, if anyone > has some ideas on narrowing down the source after reading the bug report > (http://projects.reductivelabs.com/issues/3712) please let me know. >If anyone was wondering, I traced this back to a custom-compiled nagios package. It must have been compiled against a buggy library or something; the official canonical nagios3 package for 10.04 LTS seems to have rectified the issue. -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode L''ennui est contre-révolutionnaire -- 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.