On Apr 18, 2017, at 11:05 AM, Karsten Kortenhorn <karstenkortenh...@gmail.com> wrote: > > OK, it works now. I noticed that I also have to start nut-client over > systemctl and that /etc/default/nut is obsolate. > > > Thanks > > > >> Am 18.04.2017 um 14:27 schrieb Charles Lepple: >> [please use Reply-All to keep the list CC'd. Thanks!] >> >>> On Apr 18, 2017, at 3:27 AM, Karsten Kortenhorn >>> <karstenkortenh...@gmail.com> wrote: >>> >>> Hi, >>> >>> I use upsd 2.7.2 on ubuntu 16.04.2 LTS. "ps aux" don't display upsmon! >> That's the first thing to troubleshoot. >> >> The flow of information is: SNMP card -> driver -> upsd -> clients (upsmon, >> upsc, CGI). So if upsc and the CGI scripts show valid data, they are pulling >> it from upsd. >> >> Do you see any log messages related to upsmon startup? (journalctl -t upsmon) >> >> What happens if you start upsmon manually? (sudo upsmon) >> >>> Is it even possible to check two UPS via SNMP in building A and B from one >>> Linux Box (ubuntu-nut-server) to shutdown two datacenter in building A or >>> B if needed? >> Sure, you just need to be certain that when the power goes out, all of the >> network connections between the server and the UPS are still powered on. >> Otherwise, the last status that the server sees is "OL", and then it goes to >> "data stale" when it cannot reach the UPS over SNMP. Likewise, you will need >> to be able to send the shutdown command over the network to those servers. >> >>> My plan is to shutdown all server in building B if power fails in building >>> B and to shutdown all server in building A if power fails in building A. It >>> is not so important to shutdown the ubuntu-nut-server. I can include him in >>> one shutdown-building-script. >> This sounds reasonable. >
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
