Bug 13449 - ctdb -X scriptstatus output is no longer machine readable and nagios plugin has not been updated.
Summary: ctdb -X scriptstatus output is no longer machine readable and nagios plugin h...
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: CTDB (show other bugs)
Version: 4.7.7
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Amitay Isaacs
QA Contact: Samba QA Contact
Depends on:
Reported: 2018-05-25 09:11 UTC by (dead mail address)
Modified: 2018-05-29 06:34 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description (dead mail address) 2018-05-25 09:11:02 UTC
Since 4.7.x (I think) the ctdb command has changed such that many operations are now unable to produce proper machine readable output. This means that the contributed Nagios plugin in the source tree no longer works.

Even with ctdb -X scriptstatus the fields are not whitespace separated (and the date and time fields also contain spaces) which make it much more complex to interpret the results programatically.

Ideally all "ctdb -X" commands should return colon-separated fields as previously or the nagios check should be rewritten to parse fixed-width fields.
Comment 1 Amitay Isaacs 2018-05-29 06:34:38 UTC
ctdb command is primarily designed to for user-interaction with ctdb.  It never produced machine-readable output consistently for all commands.

So it's a design choice to avoid generating any machine-readable output from ctdb command in future.

The real fix is to rewrite nagios plugin using client api instead of trying to parse output of ctdb command.  Unfortunately the nagios plugin is contributed code  and not maintained by the core development team.  

We might fix the nagios plugin, but it's not a priority.

Patches welcome.