Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perl Encryption Libraries Not Present #130

Closed
rehashedsalt opened this issue Aug 15, 2021 · 3 comments
Closed

Perl Encryption Libraries Not Present #130

rehashedsalt opened this issue Aug 15, 2021 · 3 comments

Comments

@rehashedsalt
Copy link

In an attempt to use this plugin for some simple storage monitoring, I've come across an error:

ERROR: SNMPv3 support is unavailable (Required module Crypt/DES.pm not found). 

To my understanding, this doesn't actually come from my plugin, but instead the SNMP Perl module. In order for that module to work properly with SNMPv3 AuthPriv, the following packages will need to be added to the base container image:

  • libcrypt-des-perl (even if you don't use DES privacy)
  • libdigest-hmac-perl (it's already present, but should be noted as a known dependency)
  • libcrypt-rijndael-perl (for AES privacy support)

Manually installing these packages while the container is live gives me my nice green boxes back.

@tronyx
Copy link

tronyx commented Feb 15, 2022

I created a fork of this repo some time ago to try and keep it up to date and resolve issues for folks: https://github.com/tronyx/Docker-Nagios

I added the two missing libs into my :develop tag if you would like to test it and, if everything works for you, I will merge it into master later today.

@JasonRivers
Copy link
Owner

This is very bad form to comment on every single issue within a repository to tell people to use your fork.

Unfortunately I have been busy and will sort these out, a pull request is often faster than an issue but I still have to look at them and check they are all OK and working.

I'm sorry for the delays.

@tronyx
Copy link

tronyx commented Feb 15, 2022

I meant no malice, disrespect, or ill intent by doing this. When I created the fork some time ago it seemed like your repo was dead. You then came back and did a lot of work on your repo ~7-8 months ago, but have been inactive since then. I understand we're all busy, but it seemed like the repo may have died again so I was simply trying to help folks who had reported issues see their issues resolved so that they could keep enjoying and utilizing the image.

I will refrain from publicly commenting on issues created within your repo in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants