Issue #2437 has been updated by Luke Kanies.

Status changed from Unreviewed to Accepted
Priority changed from Normal to High

You're correct, looks like a problem with the regex.
----------------------------------------
Bug #2437: nagios commands containing a semicolon (in quoted string) cause 
rewriting of config on each run
http://projects.reductivelabs.com/issues/2437

Author: Sven Mueller
Status: Accepted
Priority: High
Assigned to: 
Category: nagios
Target version: 
Complexity: Unknown
Affected version: 0.24.8
Keywords: 


When I have a nagios command defined in puppet like this:

<pre>
nagios_command {
    "nagios_table_size":
    command_line => '$USER3$/check_mysql_health --hostname localhost --username 
nagioschecks --password nagiosCheckPWD --mode sql --name "SELECT 
ROUND(Data_length/1024) as Data_kBytes from INFORMATION_SCHEMA.TABLES where 
TABLE_NAME=\"$ARG1$\";" --name2 "table size" --units kBytes -w $ARG2$ -c 
$ARG3$',
}
</pre>

It causes the nagios config to be re-written (and thus nagios restarted) each 
time puppetd runs. It writes the configuration correctly, but it reads the 
command_line part of the nagios config back only up to the semicolon ";" before 
--name2
This is quite annoying when you get a notification about a changed nagios 
configuration every time puppetd runs ;-)
I assume this is caused by the (too simple?) regexp that is searching for 
inline comments in nagios configuration lines, but I'm not sure.


-- 
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://reductivelabs.com/redmine/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
-~----------~----~----~----~------~----~------~--~---

Reply via email to