ValueError: unichr() arg not in range(0x10000) (Status with german Umlauts) about nagstamon HOT 13 CLOSED

Looks like a BeatifulSoup bug but anyways - why is the hostname invalid? Maybe check you DNS? Or look at check_icmp?

from nagstamon.

We had a bigger crash including our DNS. So the check returned that error. Unfortunally we couldn't see any status in Nagstatmon because of this bug.

from nagstamon.

Ouch... well I will look into this after vacation time.

from nagstamon.

Thanks Henri!
If you need any help or testing I can do, please let me know. Enjoy your holidays :-)

from nagstamon.

Do you still have that problem or did you fix your DNS?

from nagstamon.

Can you try latest version 680d6a6?

from nagstamon.

Nagstatmon doesn't shows the error anymore. The Service is shown as down correctly. There is just one flaw: The Status information is beeing cut off after the umlaut. E.g. it should be "check_ping: Ungültiger hostname". Nagstatmon shows "check_ping: Ungo" (see screenshot)

from nagstamon.

Funny... I added a "ignore" to UTF8 decoding, please check f5ec619

from nagstamon.

Unfortunately Nagstatmon now shows again the previous error (ValueError: unichr() arg not in range(0x10000))

from nagstamon.

This is bad... this "ignore" option was thought to ignore such errors... looks like the best thing achievable is the "check_ping: Ungo" - variant. Two soulutions:

• set the locale of your monitoring server to C
• fix your DNS
  I really see no other place where else to handle that UTF trouble. :-(

from nagstamon.

I would prefer the solution as in commit 680d6a6

from nagstamon.

Yes, would be the best option I think too.

from nagstamon.

Please check the latest binaries at http://nagstamon.ifw-dresden.de/files-nagstamon/unstable/ or source from Github.

from nagstamon.