Nagios Support Forum

rkennedy wrote:It looks like the check is running now, but the parameters aren't properly configured now. I would recommend testing over the command line at this point until you can gather the information you're looking for.

As this is a plugin found on our exchange, we do our best to help with it - but, we don't directly support it.

With that said here's a thread I found (in english) with a bit more information about it - https://support.nagios.com/forum/viewto ... =7&t=29459

rkennedy wrote:Sounds good.

Just in case you don't know how to check things over the CLI, you can run the following command -

Code: Select all

/usr/local/nagios/libexec/check_printer <inputhere>

Replace <inputhere> with the variables you're trying to process.

I'll leave this open, let us know if you have any more questions.

Thanks. That's where I get hazy, though. Knowing how to choose the variables and how to input it.

So, if I'm trying to monitor Ricoh printers, does that mean that i need to select option 2, based on the output above?

Going by the command examples given in the last link you provided me with on this plugin, I was able to get some results in the CLI. Are these only limited to toner? Is the examples he gave for option 1, which is not for Ricoh? I realize the parameters set in the example are thresholds, but I don't see the breakdown of each piece.

Papertray:
# paper tray 2
$ check_printer 192.168.123.1 public 1 paper 2

# alerts
$ check_printer 192.168.123.1 public 1 alerts
OK - ( 5 3 10 1 0 1001) ( 5 3 10 1 0 1001)

# pagecounts, just iterate through the argument after counter

$ check_printer 192.168.123.1 public 1 counter 1
OK - Total: 95 | pagecount=95;

# hardware parts
$ check_printer 192.168.123.1 public 1 hardware 1
OK - FS-2100DN Status=2 | data=2;

# hardware parts
$ check_printer 192.168.123.1 public 1 parts 1
OK - Top Cover Status=4

And then, what do I ultimately do with the results? How do I take this info, and turn it into something in the printer.cfg that will check a number of items on those printers?

rkennedy wrote:

Thanks. That's where I get hazy, though. Knowing how to choose the variables and how to input it.

This changes based on what script you're using. With our exchange, comes custom scripts made my people of the community. Most script should have a -h or --help that helps outline which variables are needed for that command in particular.

So, if I'm trying to monitor Ricoh printers, does that mean that i need to select option 2, based on the output above?

Judging from the text above, yes I would think so. However, we do not have a printer here to test with so I can't make that confirmation. The best thing to do is experiment over the command line and find the result you're looking for, and then move it into your check.

Going by the command examples given in the last link you provided me with on this plugin, I was able to get some results in the CLI. Are these only limited to toner? Is the examples he gave for option 1, which is not for Ricoh? I realize the parameters set in the example are thresholds, but I don't see the breakdown of each piece.

I don't believe that they are only limited to the toner, again - this goes with the two answers above. We don't control the flow of how someone writes their scripts, and we do not have a printer here to test with. The best judgement is to experiment with the script. The examples he posted may or may not work on your printer in particular -

Code: Select all

Papertray:
# paper tray 2
$ check_printer 192.168.123.1 public 1 paper 2

# alerts
$ check_printer 192.168.123.1 public 1 alerts
OK - ( 5 3 10 1 0 1001) ( 5 3 10 1 0 1001)

# pagecounts, just iterate through the argument after counter

$ check_printer 192.168.123.1 public 1 counter 1
OK - Total: 95 | pagecount=95;

# hardware parts
$ check_printer 192.168.123.1 public 1 hardware 1
OK - FS-2100DN Status=2 | data=2;

# hardware parts
$ check_printer 192.168.123.1 public 1 parts 1
OK - Top Cover Status=4

And then, what do I ultimately do with the results? How do I take this info, and turn it into something in the printer.cfg that will check a number of items on those printers?

You will want to define a service, and check_command. I've drawn lines to show how the $ARG#$ values correspond, and provided a bit more of detail.

command-service-relationship.png

There were a few links provided in your other thread asking for documentation to help clarify. This is what we have for now, and in the future we may be able to build a more descriptive document that outlines these steps.

Jacktivated wrote:# 'check_printer' command definition
define command{
command_name check_printer
command_line $USER1$/check_printer -H $HOSTADDRESS$ $ARG1$ $ARG2$
}

Jacktivated wrote:check_command check_printer!-C v2c public!1!parts!1 ; The command used to monitor the service

/usr/local/nagios/libexec/check_printer -H 192.168.123.1 -C v2c public 1

check_command check_printer!-C v2c public!1 parts 1

Box293 wrote:

Jacktivated wrote:# 'check_printer' command definition
define command{
command_name check_printer
command_line $USER1$/check_printer -H $HOSTADDRESS$ $ARG1$ $ARG2$
}

Jacktivated wrote:check_command check_printer!-C v2c public!1!parts!1 ; The command used to monitor the service

command_name: check_printer
The exclamation marks separate the arguments:
$ARG1$: -C v2c public
$ARG2$: 1
$ARG3$: parts
$ARG4$: 1

However your check command only has $ARG1$ and $ARG2$ defined, so Nagios is executing:

Code: Select all

/usr/local/nagios/libexec/check_printer -H 192.168.123.1 -C v2c public 1

Try this:

Code: Select all

check_command check_printer!-C v2c public!1 parts 1