search for: whitedavidp

Roger, Thanks for the idea to add additional items to the notifyflag. That proved the monitor was indeed working as expected and led me to find that my script had myriad issues when run under the nut user. All remedied now. As I progress, I may well end up migrating to the upssched. As a newbie I was simply following the documented "simple" way described here

On Fri, Jul 19, 2019 at 7:37 PM David White <whitedavidp at yahoo.com> wrote: > As a newbie > I was simply following the documented "simple" way described here > <https://networkupstools.org/docs/user-manual.chunked/ar01s07.html> In addition to the NUT documentation above, you may also profit from the excellent work Roger P...

Hi Users NUT, I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a raspberry-pi. In compatibility list, is listed to use the blazer_ser driver. I use a USB adapter to RS-232 conected in to the No-Breake. Follow the comands e confs. root at rasp:/home/pi# lsusb *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* Bus 001 Device 003: ID 0424:ec00 Standard

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

Hi Charles and thanks for your help. 1. I just re-started the Ubuntu/Android system. This runs a root script including "service nut-server start" followed by the same for nut-client. I can check the status on both and they show as running. I can see expected results running "upsc belkinusb". 2. When I check the results from "netstat -t -n" I am NOT finding

I am far from expert on these matters. But have a couple questions: 1. Are you sure that /dev/ttyUSB0 exists and is the result of the Prolific USB->serial converter? For example, if you yank the Prolific and reboot, is /ttyUSB0 there still? It is possible that there is another /dev/ttyUSBx out there.I doubt this but wonder. 2. I have recently been fuddled due to permission problems of

On 1/1/2020 11:49 AM, David White wrote: > > Hi Roger and, as always, thanks! > > I really do not want to wait very long before shutting down things on > this UPS. What I think I am doing (or at least trying to do) is to > execute a script on the host machine when the UPS is detected by NUT to > be on battery power. > > That script sleeps 20 seconds to ensure that this

On 1/1/2020 2:15 PM, grumpy at mailfence.com wrote: > > try upscmd -l > Wow! Thanks, that looks potentially helpful. More testing to be done. Happy new year.

On 1/1/2020 2:15 PM, grumpy at mailfence.com wrote: > try upscmd -l > This is a great suggestion. I was not even aware of this command. I can not turn off that freaking beeping. and the shutdown.stayoff seems to shut the UPS off entirely. It does seem to be one of those commands that are described here <https://networkupstools.org/docs/man/upscmd.html> as "paranoid" and

Something just occurred to me. My kernel does not include USB->Serial code. Long ago, I had to figure out how to build a module for the ch341 USB->Serial adapter I use for running my Heyu home automation system. I never built one for Cypress and that seems to be what the Belkin is using. I know this because I see a line for it using "lsusb" that disappears if I unplug the UPS.

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:

Thanks very much for the help Roger. My ps|grep results almost mirror yours. Only my driver line is different - showing blazer. But I am still seeing: Broadcast Message from nut at loca (somewhere) at 15:25 ... Communications with UPS belkinusb at localhost lost Broadcast Message from nut at loca (somewhere) at 15:25 ... UPS belkinusb at localhost is

Please repsond to me via email if possible to davepwhite@hotmail.com. No access to the list at this time. Thanks. I have 2 machines, one runs Windows NT 4.0 sp5, the other RH Linux 7.0. The Linux box mounts an NT shared drive upon startup. The version number reported by both smbclient and smbmount is 2.0.7. Here is my problem: On the NT box, I create a file in the shared area. I then check its

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>.

Thanks Roger for all your help here. I hope the 2 attachments come through. The .sh is my doctored version of the script and the .report is its output. I welcome any suggestions or ideas about what might be causing my problems with monitoring to the Belkin UPS. Cheers On 7/12/2019 10:12 AM, Roger Price wrote: > On Fri, 12 Jul 2019, David White wrote: > >> Hello, thanks, and sorry

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

Hello all and thanks. I read here <https://mn3m.info/posts/configure-ups-monitor-using-nut-on-debian/> while searching around for my issue's resolution. In this I see that this nut driver is creating and using an entry in /dev (in this case ttyS0). So I "ll tty*" and see nothing with nut. Since this is a USB UPS, I suppose I should be looking for something in /dev/ttyUSB*.

On 1/1/2020 2:21 AM, Roger Price wrote: > On Tue, 31 Dec 2019, David White wrote: > >> ... But it did not actually turn off the UPS at all. The UPS kept >> beeping and I had to turn it off manually. >> >> I thought that NUT would handle this. But perhaps it cannot for my >> unit? Or perhaps I have things improperly configured? Any suggestions? >> Thanks