similar to: Question about Tripp-Lite UPS life span

i have a OMNIVS1500XL i have used nut for several years on a full sized pc with no problems i am trying to get nut working with this ups on a raspberry pi i tried with a pi 3b running raspbian stretch i tried with a pi 3b running raspbian buster i tried plugging the usb cable straight into the pi i tried using a powered usb hub i tried rebuilding nut from the source package all caused the pi to

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

Please ignore the previous message as I sent it before it was complete. Hello, I have a Tripplite SMART2200VS that isn't being shut down when the nut master asks it to. My initial test was simply upsmon -c fsd which did cause the system to shut down, however the UPS remained on and providing power to its loads. Looking in the logs (daemon and syslog) it was not clear to me that NUT was

Larry, I have not edited a single file, including anything to do with NUT, on the Synology via ssh.... ever. How is yours configured in the UI? Do you have it set to go into safe mode after a certain number minutes? Earlier, I was just copying and pasting the contents of some files to Roger but did not change anything. -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 8:16 AM -0400,

Thanks Larry, no problem. I appreciate the input. Whenever you get a chance I’d really like to compare notes with someone who has NUT and a Synology to see why the heck mine doesn’t work! ;). I’m also using my Pi as the master like you. Thanks. Todd -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 11:55 AM -0400, Larry Fahnoe <fahnoe at fahnoetech.com>, wrote: > On Fri, Aug

On Fri, 22 May 2020, Tom Cooper wrote: > Sadly I am still seeing a loss of communication. I will check the device number to see if it has changed.  > Not sure what else to look at. I guess I could create a corn job to restart the driver multiple times a day.  If there is a command such as upsc for which the output depends on the driver running correctly, then it might be better to run a

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

Hello I asked Tripplite the serial protocol implemented in the UPS model SU2200RTXLCD2U. The protocol is the 4006, which is not supported by the NUT. I connected my UPS unit to a serial terminal client (both from a Windows machine and a Linux machine), set the communication parameters to those indicated in the protocol spec, and tried to open the communication, unfortunately with no success. I

> > > 2.117586 send_cmd(msg_len=2, type='G') > > 3.219418 libusb_get_interrupt: Connection timed out > > 3.219474 libusb_get_interrupt() returned 0 instead of 8 while > sending 3a 47 b8 0d 00 00 00 00 '.G......' > > 4.219593 libusb_get_interrupt: Connection timed out > > 4.219661 libusb_get_interrupt() returned

Thank you for your answer. I will try to investigate the possibility that the Tripplite serial cable has a different pinout than a standard RS-232 serial cable. I wouldn't use the NUT at this point because I don't think I will be able to write a software update to adapt the NUT to my needs. My idea was first to test the protocol via a serial terminal client directly connected to the UPS,

On Sat, Jul 22, 2017 at 7:48 AM, Charles Lepple <clepple at gmail.com> wrote: > > I also have not used a Synology device, but as I recall, they generally > expect to be the NUT master system. This may cause problems if you need to > do something fancy with upssched. > The Synology boxes work fine as NUT clients, *however* they provide very little ability to configure NUT

On Apr 13, 2018, at 3:55 AM, Jon Bendtsen <jon.bendtsen at jonix.dk> wrote: > > On 13/04/2018 07.56, zefanjas wrote: >> Hi, >> is there a command to get a list of connected slaves you can run on the >> nutserver? I want to monitor the slaves and if their are actually >> connected to server. > > if there is no such command in NUT, then on my Debian

So I finally got a test in after I changed my RPi to the master and everything else (including my Synology) to slaves.  Before I did that though, I timed the shutdown of my Synology since it is the slowest slave to shutdown.  It took 40 seconds to shutdown, so I changed HOSTSYNC in upsmon.conf on the master (“Proton”) to 60.  I then did a test ("sudo upsmon -c fsd”). The slaves shutdown, then

Hey there, Has anyone tackled the best way to shut down a VM running Win10 running in RedHat's (CentOS 7) KVM/QEMU VM manager? I'm looking at this link to follow:

On Mon, 10 Aug 2020, Todd Benivegna wrote: > synoups: https://hastebin.com/xexafofiha.bash Wow! What a mess. It looks as if Synology wanted to write their own "NUT", but decided it would be easier to put their ideas in a script when they saw they could use upssched.conf to call it. NUT intends such a script for timer management. Synology use it for general system management.

On Monday 22 June 2020 15:36:21 Charles Lepple wrote: > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: > > So I just edited /etc/nut/upsd.users to add both the commands it > > claims to have but get this response to either: > > In your original example, you had multiple “instcmd =“ lines for one > user- I think the allowed commands all need to be listed on one >

On 06/11/2017 07:00 AM, Larry Fahnoe wrote: > Hi Ben, > > On RHEL/CentOS 7, libvirt-guests (which comes from libvirt-client) on the host controls the suspend vs. shutdown behavior of the guests. By default the guests suspend, but if you want them to shutdown, change the ON_SHUTDOWN setting in /etc/sysconfig/libvirt-guests. I don't have any Windows guests, but the linux guests work

On Monday 22 June 2020 09:18:29 Charles Lepple wrote: > On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote: > > pi at rpi4:~ $ upscmd myups test.battery.start.quick > > Username (pi): > > Password: > > Unexpected response from upsd: ERR ACCESS-DENIED > > > > Looking at /etc/nut/uspd.users, I (me, pi) should be able to do > > that. ??? > > Hi Gene,

On 28.05.2016 19:46, Larry Fahnoe wrote: > On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru > <mailto:abi at abinet.ru>> wrote: > > However I was unable to shutdown.return it. Maybe protocol is not > fully compatible? > > 0.145757 Initiating UPS shutdown > 0.145760 upsdrv_shutdown... > 0.145763

On Monday 22 June 2020 09:50:50 Larry Fahnoe wrote: > On Mon, Jun 22, 2020 at 8:27 AM Gene Heskett <gheskett at shentel.net> wrote: > > > On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote: > > > > pi at rpi4:~ $ upscmd myups *test.battery.start.quick* > > > > Username (pi): > > > > Password: > > > > Unexpected response from upsd: