shgubar
shgubar
I forgot to write about the **error** in the browser (_Chrome's Developer Tools_):
FYI: Protect 2.0.1 does not fixed RTSP stream.
Please try this: wget https://ftp.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.4-1+b1_armhf.deb sudo dpkg -i libseccomp2_2.5.4-1+b1_armhf.deb
> Hi, looked through code and it boiled down to `upssched.c::parse_at()` expecting exactly the upsname from local configuration. > > * https://github.com/networkupstools/nut/blob/master/clients/upssched.c#L1173 > > Try dropping the `@localhost` in `AT`...
Also, I would like to add one more problem related to the fact that the command is not executed - a new status is set: `ups.status: FSD OL BYPASS CHRG`...
> OT: Git has "brAnches". People have "brUnches", if they mix breakfast and lunch. Thanks for pointing out my mistake, it's just a typo.
> Also, since you have a locally built NUT, you can add an `upsdebugx(1, ...)` message in `parse_at` to report the strings it compares for `upsname` and `un`... This is...
> Regarding the status, is it set after a real power outage? Was it long enough to deplete the battery and begin shutdown rituals (raise the FSD flag)? Perhaps it...
> Can you start the `upsmon` primary instances with a higher debug level, to see why they decide to set the FSD nearly right away? Maybe the UPS says "OB...
> Wondering now if you constrained `User=...` in the systemd unit files for NUT? They should normally be left alone (undefined or `root`) and daemons would drop privileges per configuration...