Roger, I get 4.3.8(1)-release There was good reason, BTW, for the script to NOT fine the journal script on my machine. I had not downloaded it yet. On 7/14/2019 9:06 AM, Roger Price wrote:> On Sun, 14 Jul 2019, David White wrote: > >> ... I saw nothing that looked like a problem with the report save the >> sections <scriptname> "Cannot access <scriptname>. Perhaps this is >> from the missing journal? > > I'm wondering if the =~ operator in Bash is working as expected. What > does command > > echo $BASH_VERSION > > report? > > Roger > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Larry Fahnoe
2019-Jul-14 19:02 UTC
[Nut-upsuser] New improved version of nut-report script
A couple of different issues with the reporting script. First the password masking is not working as intended: I have three different passwords in my ups.users file and only the last one is masked. Here's the first part of the resulting report where I've replaced the unmasked passwords with <PASSWORD-n>. NUT configuration 2019-07-14 16:58:15 UTC ########### Operating system ########### 4.19.57-v7+ GNU/Linux PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_CODENAME=buster ########### /etc/nut/nut.conf ########### MODE=netserver ########### /etc/nut/ups.conf ########### maxretry = 3 [ups] driver = tripplite_usb port = auto desc = "Tripp Lite SMART2200VS" product = ".*SMART2200.*" ########### /etc/nut/upsd.conf ########### LISTEN 0 3493 ########### /etc/nut/upsd.users ########### [admin] password = *<PASSWORD-1>* actions = SET instcmds = ALL [upsmon] password = *<PASSWORD-2>* upsmon master [monuser] password = ********* upsmon slave ########### /etc/nut/upsmon.conf ########### MONITOR ups at localhost 1 upsmon *<PASSWORD-2>* master MINSUPPLIES 1 Second, although CMDSCRIPT is defined in upssched.conf, (and the file exists), it is not being found by the reporting script: ########### /etc/nut/upssched.conf ########### CMDSCRIPT /usr/local/bin/upssched-cmd PIPEFN /var/run/nut/upssched.pipe LOCKFN /var/run/nut/upssched.lock AT ONBATT * START-TIMER shutdown-timer 600 AT ONLINE * CANCEL-TIMER shutdown-timer AT LOWBATT * START-TIMER low-battery-timer 5 AT LOWBATT * START-TIMER shutdown-timer 65 AT ONLINE * EXECUTE ONLINE AT ONBATT * EXECUTE ONBATT AT LOWBATT * EXECUTE LOWBATT AT FSD * EXECUTE FSD AT COMMOK * EXECUTE COMMOK AT COMMBAD * EXECUTE COMMBAD AT SHUTDOWN * EXECUTE SHUTDOWN AT REPLBATT * EXECUTE REPLBATT AT NOCOMM * EXECUTE NOCOMM AT NOPARENT * EXECUTE NOPARENT * ########### <scriptname> ###########* *Cannot access <scriptname>* As you've asked about bash versions, this system provides: GNU bash, version 5.0.3(1)-release (arm-unknown-linux-gnueabihf) --Larry -- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com Minneapolis, Minnesota www.FahnoeTech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20190714/6bba3bec/attachment-0001.html>
On Sun, 14 Jul 2019, Larry Fahnoe wrote:> A couple of different issues with the reporting script. First the password > masking is not working as intended: I have three different passwords in my > ups.users file and only the last one is masked.Hello Larry, Thanks for the report. I've found the password problem. I can't reproduce the <scriptname> problem with openSUSE, so I will have to build a Debian system to do more testing. Thanks again, Roger
On Sun, 14 Jul 2019, Larry Fahnoe wrote:> The issue appears to be caused by my upssched.conf file having the original > commented out declaration of CMDSCRIPT which is what is showing up via the > grep in the script.Oof! Easy to fix. I have just uploaded an updated nut-report script which should fix the multiple password and the <scriptname> bugs. Roger
Larry Fahnoe
2019-Jul-15 11:52 UTC
[Nut-upsuser] New improved version of nut-report script
On Mon, Jul 15, 2019 at 1:01 AM Roger Price <roger at rogerprice.org> wrote:> Oof! Easy to fix. I have just uploaded an updated nut-report script which > should fix the multiple password and the <scriptname> bugs. >Confirming that your fixes are working, thanks Roger. --Larry -- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com Minneapolis, Minnesota www.FahnoeTech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20190715/c98b6bef/attachment.html>
Seemingly Similar Threads
- New improved version of nut-report script
- Tripplite SMART2200VS with tripplite_usb: UPS doesn't shut down
- Tripplite SMART2200VS with tripplite_usb: UPS doesn't shut down
- problem with mailing (nut 2.4.1 and a powermust650 -> megatec_usb)
- Powercom INF-800 support