Nut upsuser - Aug 2019 - Debian 10 nut 2.7.4-8 and APC Back UPS 600i on 940-0020B

Dir list!

I'm using nut for many years on my home "server" without problems
running
on Debian 6.x nut version 2.4.3
Now I have decided to move to Debian 10. I have started from zero and
install new system on a different disk. I have successfully installed new
nut version 2.7.4
I've found one issue, that new version see always "low battery"
state.
Excerpt from syslog:
Aug 27 16:52:52 nusi upsdrvctl[501]: UPS type: APC Back-UPS (940-0020B/C
cable)
Aug 27 16:52:52 nusi upsdrvctl[501]: parse_input_signals: input overrides
specified, but no effective difference - check for typos?
Aug 27 16:52:52 nusi upsdrvctl[501]: Network UPS Tools - UPS driver
controller 2.7.4
Aug 27 16:52:53 nusi upsd[506]: fopen /var/run/nut/upsd.pid: No such file
or directory
Aug 27 16:52:53 nusi upsd[506]: listening on 127.0.0.1 port 3493
Aug 27 16:52:53 nusi upsd[506]: listening on 127.0.0.1 port 3493
Aug 27 16:52:53 nusi upsd[571]: Startup successful
Aug 27 16:52:53 nusi upsmon[776]: fopen /var/run/nut/upsmon.pid: No such
file or directory
Aug 27 16:52:53 nusi upsmon[776]: UPS: APC600 at localhost (master) (power
value 1)
Aug 27 16:52:53 nusi upsmon[776]: Using power down flag file /etc/killpower
Aug 27 16:52:53 nusi upsmon[780]: Startup successful
Aug 27 16:52:53 nusi systemd[1]: nut-monitor.service: Can't open PID file
/run/nut/upsmon.pid (yet?) after start: No such file or directory
Aug 27 16:52:53 nusi upsmon[781]: Init SSL without certificate database
Aug 27 16:52:54 nusi upsd[571]: User monmaster at 127.0.0.1 logged into UPS
[APC600]
Aug 27 16:52:54 nusi upsmon[781]: UPS APC600 at localhost battery is low

Strange thing this message
Aug 27 16:52:53 nusi systemd[1]: nut-monitor.service: Can't open PID file
/run/nut/upsmon.pid (yet?) after start: No such file or directory

Because it is /run/nut/upsmon.pid after login exist (and /var/~run too).
Also all three services are up (nut-driver, nut-monitor and nut-server as
I remember).

Also I've tried
# upsc APC600
device.mfr: APC
device.model: Back-UPS
device.type: ups
driver.name: genericups
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.parameter.synchronous: no
driver.parameter.upstype: 2
driver.version: 2.7.4
driver.version.internal: 1.36
ups.mfr: APC
ups.model: Back-UPS
ups.status: LB OL

On old system (Debian 6.x), every thing is OK:
# upsc APC600
device.mfr: APC
device.model: Back-UPS
device.type: ups
driver.name: genericups
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.parameter.upstype: 2
driver.version: 2.4.3
driver.version.internal: 1.36
ups.mfr: APC
ups.model: Back-UPS
ups.status: OL

I have read many thing in documentation /usr/sharte/doc/nut but does not
find a clue. May be that pid file problem still prevent communication
between driver-monitor-server-clinet?

Any suggestion?
  tovis

On 28.08.19 12:54, tovis r-visor wrote:
>I'm using nut for many years on my home "server" without
problems running
>on Debian 6.x nut version 2.4.3
>Now I have decided to move to Debian 10. I have started from zero and
>install new system on a different disk. I have successfully installed new
>nut version 2.7.4
>Aug 27 16:52:53 nusi upsd[506]: fopen /var/run/nut/upsd.pid: No such file
>or directory
>Aug 27 16:52:53 nusi upsmon[776]: fopen /var/run/nut/upsmon.pid: No such
>file or directory
>Aug 27 16:52:53 nusi systemd[1]: nut-monitor.service: Can't open PID
file
>/run/nut/upsmon.pid (yet?) after start: No such file or directory
>Strange thing this message
>Aug 27 16:52:53 nusi systemd[1]: nut-monitor.service: Can't open PID
file
>/run/nut/upsmon.pid (yet?) after start: No such file or directory
>
>Because it is /run/nut/upsmon.pid after login exist (and /var/~run too).
>Also all three services are up (nut-driver, nut-monitor and nut-server as
>I remember).
FYI, /var/run is symlinked to /run apparently since debian 7, but it's
possible that you don't have this symlink.  You can create it or change
/var/run/ to /run/ in nut's systemd files.

-- 
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Your mouse has moved. Windows NT will now restart for changes to take
to take effect. [OK]

I was check out that is the connection between
driver-monitor-server-client is working or not. I was put my server
directly on power cable, keep control  cable connection and use command:

$ watch upsc APC600

I was switch to battery, after 2-3 second it show that is on battery OB
and after it shutdown because of low battery LO.

I think that systemd scripts some what unsynchronized, but after it connect.

Problem still exist - why low battery?
Low battery sensing is a little tricky on 940-0020B it using DCD as input,
but it driven by CTS and TxD too. I'm afraid that I cannot using -DCD
setting.
Any suggestion?
  tovis
> On 28.08.19 12:54, tovis r-visor wrote:
>>I'm using nut for many years on my home "server" without
problems running
>>on Debian 6.x nut version 2.4.3
>>Now I have decided to move to Debian 10. I have started from zero and
>>install new system on a different disk. I have successfully installed
new
>>nut version 2.7.4
>
>>Aug 27 16:52:53 nusi upsd[506]: fopen /var/run/nut/upsd.pid: No such
file
>>or directory
>>Aug 27 16:52:53 nusi upsmon[776]: fopen /var/run/nut/upsmon.pid: No such
>>file or directory
>>Aug 27 16:52:53 nusi systemd[1]: nut-monitor.service: Can't open PID
file
>>/run/nut/upsmon.pid (yet?) after start: No such file or directory
>
>
>>Strange thing this message
>>Aug 27 16:52:53 nusi systemd[1]: nut-monitor.service: Can't open PID
file
>>/run/nut/upsmon.pid (yet?) after start: No such file or directory
>>
>>Because it is /run/nut/upsmon.pid after login exist (and /var/~run too).
>>Also all three services are up (nut-driver, nut-monitor and nut-server
as
>>I remember).
>
> FYI, /var/run is symlinked to /run apparently since debian 7, but it's
> possible that you don't have this symlink.  You can create it or change
> /var/run/ to /run/ in nut's systemd files.
>
> --
> Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
> Warning: I wish NOT to receive e-mail advertising to this address.
> Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
> Your mouse has moved. Windows NT will now restart for changes to take
> to take effect. [OK]
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser