On Jul 9, 2019, at 12:22 PM, David White wrote:> > So I guess I am wondering if this is related to my problem. I have no idea how the blazer_usb driver works.For the most part, NUT drivers ending in “_usb” (including blazer_usb) do not need a serial device node in /dev. They use libusb to talk directly to the UPS. (If you can reliably read the UPS status with upsc, then the connectivity problem is not at the driver layer.) Can you please run this script to get more information about your setup? I think just gzip'ing the report file should be sufficient to make it small enough to attach to an email reply. (Also, for Ubuntu, you will need to change D="/etc/ups" to D="/etc/nut") http://rogerprice.org/NUT/#NUT_REPORT
Hello, thanks, and sorry for the delay in getting back. I am running the script and have move the comment from one D= line to the other. I am, however, seeing some errors written to the console. They are from line 64-65 of the script. Regarding line 64, I have no /usr/sbin/ups* and suspect the proper location on my Ubuntu install is /sbin/ups*. Is this possible? Here I have upsd and 9 other files. Regarding line 65, I also have and no /etc/ups/*. I would have expected that second location might have been driven by the D variable. Is that what it should be instead of hard-coded to /etc/ups which, as you point out, is the appropriate location for Ubuntu? this is where nut.conf and 5 other files are located. Once I get this straight, I will re-run and post the results. Cheers On 7/9/2019 4:41 PM, Charles Lepple wrote:> On Jul 9, 2019, at 12:22 PM, David White wrote: >> >> So I guess I am wondering if this is related to my problem. I have >> no idea how the blazer_usb driver works. > > For the most part, NUT drivers ending in ???_usb??? (including > blazer_usb) do not need a serial device node in /dev. They use libusb > to talk directly to the UPS. (If you can reliably read the UPS status > with upsc, then the connectivity problem is not at the driver > layer.) > > Can you please run this script to get more information about your > setup? I think just gzip'ing the report file should be sufficient to > make it small enough to attach to an email reply. (Also, for Ubuntu, > you will need to change D="/etc/ups" to D="/etc/nut") > > http://rogerprice.org/NUT/#NUT_REPORT >
On Fri, 12 Jul 2019, David White wrote:> Hello, thanks, and sorry for the delay in getting back. I am running the > script and have move the comment from one D= line to the other. I am, > however, seeing some errors written to the console. They are from line > 64-65 of the script. > > Regarding line 64, I have no /usr/sbin/ups* and suspect the proper > location on my Ubuntu install is /sbin/ups*. Is this possible? Here I > have upsd and 9 other files. > > Regarding line 65, I also have and no /etc/ups/*. I would have expected > that second location might have been driven by the D variable. Is that > what it should be instead of hard-coded to /etc/ups which, as you point > out, is the appropriate location for Ubuntu? this is where nut.conf and > 5 other files are located.Thanks for the report. I confess that the script has not been tested with Ubuntu. I wrongly assumed that it would follow Debian. Could you make the changes to the script you describe, create the report, and send me a list of the directories and files you used? If it's simpler for you, email me the modified script as you used it. I will update the source script to include a variable value suitable for Ubuntu. Thanks again, Roger
On Tue, 9 Jul 2019, Charles Lepple wrote:> Can you please run this script to get more information about your setup? I > think just gzip'ing the report file should be sufficient to make it small > enough to attach to an email reply. (Also, for Ubuntu, you will need to change > D="/etc/ups" to D="/etc/nut") > > http://rogerprice.org/NUT/#NUT_REPORTI have reworked this script so that 1. It tries to autodetect where the configuration files and executables are located. 2. It is easy to add further variations of these directories. The script is still at the same URL. If you want to include a systemd journal report, you will also need script nut-journal to be found at the same URL. The resulting report when gzipped is about 6KBytes. I have tested with openSUSE, but I would much appreciate anyone downloading the script and running it on a different operating system. All comments and corrections are very welcome. Roger
Hi Roger and thanks! I have attached my nut report from the new script (sans journal). 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? On 7/14/2019 7:52 AM, Roger Price wrote:> On Tue, 9 Jul 2019, Charles Lepple wrote: > >> Can you please run this script to get more information about your >> setup? I think just gzip'ing the report file should be sufficient to >> make it small enough to attach to an email reply. (Also, for Ubuntu, >> you will need to change D="/etc/ups" to D="/etc/nut") >> >> http://rogerprice.org/NUT/#NUT_REPORT > > I have reworked this script so that > > 1. It tries to autodetect where the configuration files and executables > are located. > > 2. It is easy to add further variations of these directories. > > The script is still at the same URL. If you want to include a systemd > journal report, you will also need script nut-journal to be found at the > same URL. The resulting report when gzipped is about 6KBytes. > > I have tested with openSUSE, but I would much appreciate anyone > downloading the script and running it on a different operating system. > All comments and corrections are very welcome. > > Roger > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser-------------- next part -------------- NUT configuration 2019-07-14 15:25:25 UTC ########### Operating system ########### 3.0.36+ GNU/Linux NAME="Ubuntu" PRETTY_NAME="Ubuntu 14.04 LTS" ########### /etc/nut/nut.conf ########### MODE=standalone ########### /etc/nut/ups.conf ########### maxretry = 3 [belkinusb] driver = blazer_usb port = auto desc = "Belkin UPS, USB interface" ########### /etc/nut/upsd.conf ########### MAXAGE 15 LISTEN 127.0.0.1 3493 MAXCONN 1024 ########### /etc/nut/upsd.users ########### [local_mon] password = ********* upsmon master ########### /etc/nut/upsmon.conf ########### MONITOR belkinusb at localhost 1 local_mon ********* master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /home/android/nutShutdown.sh POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONBATT EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 ########### /etc/nut/upssched.conf ########### CMDSCRIPT /bin/upssched-cmd ########### <scriptname> ########### Cannot access <scriptname> ########### /etc/hosts.allow ########### ########### ps aux ########### nut 24329 0.0 0.0 3336 660 ? Ss Jul09 1:53 /sbin/upsd root 24346 0.0 0.0 3328 824 ? Ss Jul09 0:00 /sbin/upsmon nut 24349 0.0 0.2 4280 1840 ? S Jul09 1:45 /sbin/upsmon ########### Ownership and permissions of executables ########### -rwxr-xr-x 1 root root 43204 Dec 30 2013 /sbin/upsd* -rwxr-xr-x 1 root root 18224 Dec 30 2013 /sbin/upsdrvctl* -rwxr-xr-x 1 root root 30852 Dec 30 2013 /sbin/upsmon* -rwxr-xr-x 1 root root 22340 Dec 30 2013 /sbin/upssched* -rwxr-xr-x 1 root root 100064 Apr 11 2014 /sbin/upstart-dbus-bridge* -rwxr-xr-x 1 root root 95824 Apr 11 2014 /sbin/upstart-event-bridge* -rwxr-xr-x 1 root root 108140 Apr 11 2014 /sbin/upstart-file-bridge* -rwxr-xr-x 1 root root 104100 Apr 11 2014 /sbin/upstart-local-bridge* -rwxr-xr-x 1 root root 99924 Apr 11 2014 /sbin/upstart-socket-bridge* -rwxr-xr-x 1 root root 58980 Apr 11 2014 /sbin/upstart-udev-bridge* ########### Ownership and permissions of configuration files ########### -rwxrwxrwx 1 root nut 1544 Jul 7 13:12 /etc/nut/nut.conf* -rwxrwxrwx 1 root nut 4653 Jul 9 09:06 /etc/nut/ups.conf* -rwxrwxrwx 1 root nut 4572 Jul 7 13:16 /etc/nut/upsd.conf* -rwxrwxrwx 1 root nut 2177 Jul 7 13:17 /etc/nut/upsd.users* -rwxrwxrwx 1 root nut 15229 Jul 7 16:29 /etc/nut/upsmon.conf* -rwxrwxrwx 1 root nut 3887 Dec 30 2013 /etc/nut/upssched.conf* ########### nut-journal ###########
Roger, I just tried the journal report and it is unable to find journalctl on my system. I am not very expert but this MAY be because my Ubuntu install is actually running chroot'ed on an Android TV computer and the expected systemd may not be there. Could the desired information be elsewhere? Thanks! On 7/14/2019 7:52 AM, Roger Price wrote:> On Tue, 9 Jul 2019, Charles Lepple wrote: > >> Can you please run this script to get more information about your >> setup? I think just gzip'ing the report file should be sufficient to >> make it small enough to attach to an email reply. (Also, for Ubuntu, >> you will need to change D="/etc/ups" to D="/etc/nut") >> >> http://rogerprice.org/NUT/#NUT_REPORT > > I have reworked this script so that > > 1. It tries to autodetect where the configuration files and executables > are located. > > 2. It is easy to add further variations of these directories. > > The script is still at the same URL. If you want to include a systemd > journal report, you will also need script nut-journal to be found at the > same URL. The resulting report when gzipped is about 6KBytes. > > I have tested with openSUSE, but I would much appreciate anyone > downloading the script and running it on a different operating system. > All comments and corrections are very welcome. > > Roger > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser