Seems to me that the script has two bugs.

First a string/int type bug from cmd_parser.add_option (as default, add_option method enforces the “string” type).
Here are the changes I’ve made :
19,21c19,21
< cmd_parser.add_option(‘-w’, action=’store’, dest=’warning_range’, type=”int”, nargs=1, default=10, help=”Set increment for warning response, default=10″)
< cmd_parser.add_option(‘-c’, action=’store’, dest=’critical_range’, type=”int”, nargs=1, default=20, help=”Set increment for critical response, default=20″)
cmd_parser.add_option(‘-w’, action=’store’, dest=’warning_range’, nargs=1, default=10, help=”Set increment for warning response, default=10″)
> cmd_parser.add_option(‘-c’, action=’store’, dest=’critical_range’, nargs=1, default=20, help=”Set increment for critical response, default=20″)
> cmd_parser.add_option(‘-f’, action=’store’, dest=’check_file’, nargs=1, default=’/tmp/bean_check.txt’,

Second is a math bug. For instance I you have the case where error[1] = options.critical_range, the script will never report the error.
So I’ve done :
82c82
= options.warning_range and error[1] if error[1] > options.warning_range and error[1] < options.critical_range:
87c87
= options.critical_range:
—
> if error[1] > options.critical_range:

Once changed, the script works great. Thanks!