search

Tylan / check_snmp_printer

Icinga Plugin for Checking SNMP Printer Status (Trays, Consumables and Pagecounts)
GNU General Public License v3.0
12 stars 4 forks source link

--messages does not show the complete answer #28

Closed Fl33Tr closed 1 year ago

Fl33Tr commented 1 year ago

When using the --messages arguement/field the feedback from the printer is cut off.

This example is from a Lexmark MX511de 0x5a756d205374617274656e2062656c696562696765205461737465206472c3bc636b656e Nicht bereit. Fehlende oder nicht reagi

Tylan commented 1 year ago

Hi apologies for delay. Been out of pocket for a bit.

Can you provide me the following output for the below command:

snmpwalk -Oan -v \<snmp vesion> -c \<community> \<host> .1.3.6.1.2.1.43.16

Tylan commented 1 year ago

Some of this may be fixed already in the next upcoming release. Can you grab it here and let me know. If not working still, please provide the above snmpwalk output for future diagnoses.

https://github.com/Tylan/check_snmp_printer/blob/devel/check_snmp_printer

Fl33Tr commented 1 year ago

Some of this may be fixed already in the next upcoming release. Can you grab it here and let me know. If not working still, please provide the above snmpwalk output for future diagnoses.

https://github.com/Tylan/check_snmp_printer/blob/devel/check_snmp_printer

Some of this may be fixed already in the next upcoming release. Can you grab it here and let me know. If not working still, please provide the above snmpwalk output for future diagnoses.

https://github.com/Tylan/check_snmp_printer/blob/devel/check_snmp_printer

Hi, thanks for your reply. Sadly the newer version does not fix the issue. This is the output of the command you requested. Please note that the output is not complete, as it cuts off a word and the text after. snmpwalk This is how it looks in the web interface when using --messages output

Edit: I did not mean to close the issue

Tylan commented 1 year ago

I made a couple of changes to better sort messages. Can you grab the new devel version and see:

https://github.com/Tylan/check_snmp_printer/blob/devel/check_snmp_printer

Not entirely sure what the "0x5a756d205374617274656e2062656c696562696765205461737465206472c3bc636b656e" is, but could you do the same snmp walk but with -On instead of -Oan:

snmpwalk -On -v \<snmp vesion> -c \<community> \<host> .1.3.6.1.2.1.43.16

and can you run through this snmpwalk and see if the lexmark OID set has any better output for those messages I can use? If you see something, post it here. This has a potential for a lot of output so only share what you feel safe sharing:

snmpwalk -Oan -v \<snmp vesion> -c \<community> \<host> .1.3.6.1.4.1.641

Fl33Tr commented 1 year ago

I made a couple of changes to better sort messages. Can you grab the new devel version and see:

https://github.com/Tylan/check_snmp_printer/blob/devel/check_snmp_printer

Not entirely sure what the "0x5a756d205374617274656e2062656c696562696765205461737465206472c3bc636b656e" is, but could you do the same snmp walk but with -On instead of -Oan:

snmpwalk -On -v -c .1.3.6.1.2.1.43.16

and can you run through this snmpwalk and see if the lexmark OID set has any better output for those messages I can use? If you see something, post it here. This has a potential for a lot of output so only share what you feel safe sharing:

snmpwalk -Oan -v -c .1.3.6.1.4.1.641

This is the output for snmpwalk -On -v -c .1.3.6.1.2.1.43.16 -On The Hex String translates to the text above it, so no luck there.

I also ran the snmpwalk you suggested and did another walk with MIB Browser. Sadly, there was no proper reply for any of the requests.

The output in the Web Interface did not change either.

Tylan commented 1 year ago

Yeah, I figured it was Hex, but the devel build should have resolved that. can you verify from your command line that you are running the new version 1.3.1? ./check_snmp_printer --version

also, can you run the check command from the command line as well using the confirmed 1.3.1 version and let me know results?

Thanks!!

Fl33Tr commented 1 year ago

Yeah, I figured it was Hex, but the devel build should have resolved that. can you verify from your command line that you are running the new version 1.3.1? ./check_snmp_printer --version

also, can you run the check command from the command line as well using the confirmed 1.3.1 version and let me know results?

Thanks!!

You were right. I was still running 1.3.0. After updating to 1.3.1 and double checking the version I get this output: output of 1 3 1 This is looking good, here is the output of the printers webpage: "Keine analoge Telefonleitung an Modem angeschl.; Fax deaktiviert."

Tylan commented 1 year ago

Okay, glad to hear that is working as designed now.

As far as the messages being cut off - It appears as if Lexmark is pushing the current mode (Bereit or Energiesparmodus) on top of what's displayed on the webpage. Perhaps code related on Lexmark's end is causing the "Keine analoge Telefonleitung an Modem angeschl." to be cutoff prematurely. I can only pull what's there and that is why I was hoping somewhere in their Lexmark OID branch they had a better handling of that output (similar to what HP does).

If one day they do create a new OID inside their branch for just this I will gladly add that. Unfortunately for now this is all that can be displayed.

I'll close this out now.