Unless I am completely missing something, I am not seeing a problem. If
upsd/upsmon shut down cleanly, the .pid files should *not* exist. Are they
creating correctly on startup? I don't see any errors indicating amproblem with
that . . . (and you don't say whether nutnruns or not).
On June 9,
I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid
fails. I'm running as root, upsmon has root:root permissions as well as the
other daemons and .conf files. I've tried configuring with and without
--prefixpath --prefixaltpath.
Is there something I am missing?
On Jun 9, 2023, at 5:25 AM, Nichole Kaligian via Nut-upsuser
wrote:
>
> Hi,
>
> Every guide I'm finding is connecting their NUT server to the UPS directly.
> Is there no option to monitor a network-attached UPS? On its IP or hostname?
> This was my first assumption when looking at a product
Nichole Kaligian via Nut-upsuser
writes:
> Every guide I'm finding is connecting their NUT server to the UPS directly.
> Is there no option to monitor a network-attached UPS? On its IP or
> hostname? This was my first assumption when looking at a product called
> 'Network UPS Tools', but it
On Fri, Jun 9, 2023, at 05:25, Nichole Kaligian via Nut-upsuser wrote:
> Every guide I'm finding is connecting their NUT server to the UPS directly.
> Is there no option to monitor a network-attached UPS? On its IP or hostname?
> This was my first assumption when looking at a product called
Hi Nichole,
On Fri, 2023-06-09 at 11:25:37 +0200, Nichole Kaligian via Nut-upsuser wrote:
> Hi,
>
> Every guide I'm finding is connecting their NUT server to the UPS directly.
> Is there no option to monitor a network-attached UPS? On its IP or
> hostname? This was my first assumption when
Hi,
Every guide I'm finding is connecting their NUT server to the UPS directly.
Is there no option to monitor a network-attached UPS? On its IP or
hostname? This was my first assumption when looking at a product called
'Network UPS Tools', but it seems I'm misunderstanding? Thanks for any
advice
