jarischaefer / docker-librenms

Docker image for LibreNMS
MIT License
115 stars 38 forks source link

Issues with NAS Synology #116

Closed alrodgir closed 4 years ago

alrodgir commented 4 years ago

Hi, In the beginning good job for your project, it works perfect. I'm using it in a Synology NAS DS1019+ I've two little issues that I don't know how can I solve it. Maybe someone can help me.

Maybe you have any idea about my problems, or where I can debug it. (I'm newbie in dockers) Thanks a lot.

jarischaefer commented 4 years ago

E-Mail

Try connecting via command line first to rule out any firewall problems.

You can test alerts using the Webinterface by heading to Alerts -> Alert Transports -> Create alert transport.

Weathermap

Please provide the settings of WEATHERMAP_CRON and WEATHERMAP_ENABLE.

Try running the weathermap script manually to check for errors. The cronjob is located at /etc/cron.d/weathermap.

alrodgir commented 4 years ago

Weathermap

WEATHERMAP_CRON /5 * WEATHERMAP_ENABLE true

The cronjob doesn't exist 😓 maybe I need to create it, I supposed the docker contained it 😅 Captura

E-Mail When I run the command openssl s_client -connect smtp.office365.com:587 -starttls smtp I obtain this, but I can't run the other one Captura1

When I try to test the transport is when I obtain the error Captura3 (Obviously I replace the @domain for my real domain you saw in the first capture of my first post 😅)

Thanks for your time ☺

jarischaefer commented 4 years ago

Weathermap

Please verify that the running container really has the variables set: docker inspect librenms | grep -i weathermap. You have to remove (docker rm) and run (docker run) the container if you change variables.

E-Mail

You have to type EHLO test before the timeout occurs. The server is waiting for your request after the line 250 SMTPUTF8.

alrodgir commented 4 years ago

Weathermap The proble is the map-poller.php, if I run it manually the maps update perfect 👌, but I don't see trafic, Captura1

E-Mail This is the output Captura

😉👌

jarischaefer commented 4 years ago

Either you are waiting too long to enter the EHLO test command or something is interfering with the connection. You have to find a way to verify that your server is actually able to reach the mail server (many providers block ports, quite strict sometimes).

alrodgir commented 4 years ago

Oks, I'm going to study trace the port forwarding.

jarischaefer commented 4 years ago

@alrodgir Maybe you could try setting up a local mail server for testing. It is pretty easy using the docker image from poste.io.

alrodgir commented 4 years ago

Hi @jarischaefer I couldn't try it. I can send mails with other hardware (printers, router...) I'm going to try and answer you ASAP.

Edit: sorry for my ignorance, I'm setting up the poste.io, but I don't know how to send mails by it. I'm using the 'local port' of the '25 docker port' in my network HW. I'm looking for a guide on inet, but the walkthrough doesn't work for me :(

jarischaefer commented 4 years ago

As far as I know, you have to use port 465 or 587 rather than 25: https://poste.io/doc/client-settings

email

The SMTP timeout does not work, it may take a while for errors to show up, see https://stackoverflow.com/a/27406993

alrodgir commented 4 years ago

Finally, it's alive!!!! The only change has been the from mail. Don't ask me anymore. 🤦‍♂️🤷‍♂️ I send the mail direct using office 365 relay servers, and no change the login SMTP auth user. Captura

I'm Thanks for all.

jarischaefer commented 4 years ago

Great to see it's working.