similar to: reboot of nut managment node resets Tripplite SMX1000LCD

Hi Roger et.al, The shutdown /reset of UPS is near instantaneous after rpi reboots or switches off. FWIW -- It looks like something is off with Ubuntu 20.04 -- I tried with raspbian and arch linux using the same nut configuration on the same hardware and the UPS does not reset. I have repurposed an old rpi2 to act as a nut server. Thanks Roger. Yogesh On Mon, Jun 22, 2020 at 11:33 AM

On Mon, 22 Jun 2020, Yogesh Bhanu wrote: > I'm not sure if it is a bug or a feature. > > I'm running Ubuntu 20.04 on my RPi4 which connects to the UPS over USB. > I have noticed whenever I reboot my RPi4. It resets the UPS ( I can > hear the relay) -- Powerloss. > Any pointers to disable this annoying bug / feature. It looks as if the shutdown part of the reboot is

Hi, This is a newbie post so please bear with me. After loosing my router to a random Subminute outage. I looked around for a fanless UPS and bought Tripp Lite SMX1000LCD The above constellation works. But I have some questions about outputs. Please see attache nut report for the config. upsc output: --8<-- fourpi01:~# upsc tripp Init SSL without certificate database battery.charge: 100

Hi Roger et.al, Following messages are logged by journalctl when powering off. --snip-- Jun 25 11:26:32 fourpi01 containerd[1326]: time="2020-06-25T11:26:32.638781892+10:00" level=info msg="Stop CRI service" Jun 25 11:26:32 fourpi01 systemd[1]: Stopping Network UPS Tools - power device driver controller... Jun 25 11:26:32 fourpi01 upsdrvctl[258149]: Network UPS Tools - UPS

On Fri, 26 Jun 2020, Yogesh Bhanu wrote: > Hi Roger et.al, > > The shutdown /reset of UPS is near instantaneous after rpi reboots or > switches off. > FWIW -- It looks like something is off with Ubuntu 20.04 -- I tried > with raspbian and arch linux using the same nut configuration on the > same hardware and the UPS does not reset. Could you describe the exact procedure

Hi Mauel, No dice. The config does not show up config: --8<-- [tripp] driver = usbhid-ups port = auto vendorid = 09ae productid = 2009 bus = 001 desc = "Tripp Lite SMX1000LCD" runtimecal = 660,100,180,50 -->8-- output: --8<-- upsc tripp Init SSL without certificate database battery.charge: 100 battery.runtime: 736 battery.type: PbAc

Hi Manuel et.al, Going thru the documentation -- it seems this configuration specific to blazer_ups. https://networkupstools.org/docs/man/blazer_usb.html Kind Regards, Yogesh On Fri, May 15, 2020 at 12:53 PM Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > > On 5/15/20 12:13 PM, Yogesh Bhanu wrote: > > [...] > > # Is it possible to calculate /estimate how much

But runs normally if started. On a rpi4 running an uptodate raspbian buster, how do I set it to auto start at boot time? Thanks. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D.

Hi , just starting off with Puppet on Macs. initially we are planning for a small group of machines. If successfull we plan to span it to entire environment in a phased manner. I have a couple of newbie questions. Do i have to use custom script to create and maintain user/group accounts as far as i have read i can manage passwords ? Can i use puppet fileserver also as sourcedir for pushing

Greetings all; Does nut build on an r-pi4b? I have an r-pi4b running one of my cnc machines and the power bump performance due to the size of its psu and the fairly rapid start time of my standby generator, does not allow a full powerdown restart to take place, leaving the pi in a crashed state. I've purchased a factory refurbed cyberpower ups rated at 650 WA which I intend to figure

On Monday 22 June 2020 15:26:23 Larry Fahnoe wrote: > On Mon, Jun 22, 2020 at 12:26 PM Gene Heskett <gheskett at shentel.net> wrote: > > So I just edited /etc/nut/upsd.users to add both the commands it > > claims to have but get this response to either: > > > > pi at rpi4:~ $ upscmd myups test.battery.start.quick > > Username (pi): pi > > Password:

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:

On Wednesday 08 January 2020 09:37:10 Roger Price wrote: > On Tue, 7 Jan 2020, Gene Heskett wrote: > > ● nut-monitor.service - Network UPS Tools - power device monitor and > > shutdown controller > > Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; > > vendor preset: enabled) > > Active: failed (Result: protocol) since Tue 2020-01-07 07:19:19

On Sep 5, 2020, at 5:23 AM, Roger Price wrote: > > On Sat, 5 Sep 2020, Gene Heskett wrote: > >> But runs normally if started. On a rpi4 running an uptodate raspbian buster, how do I set it to auto start at boot time? > > Hello Gene, By "auto start" I assume you mean the automatic power on of a box when wall power returns after a power failure. For this to work,

On 5/19/20 10:39 AM, Yogesh Bhanu wrote: > Hi Manuel et.al, > > Going thru the documentation -- it seems this configuration specific > to blazer_ups. > https://networkupstools.org/docs/man/blazer_usb.html > > Kind Regards, Other drivrs support that option as well. Here is a quote from the same config as before: [guardian]         driver = nutdrv_qx         port = auto

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,

Hi, recently I recognized, that some of the files of my laptop (mostly binary-files, StarCalc, PDF, ...) are corrupted. The files couldn't be viewed or opened (with SO) anymore. The files from older backups, before I used ext3-0.0.5 in ordered mode work still pretty well. I had no fatal crash or something simillar between these dates (OK, I had two times a powerloss of my laptop), but nothing

On Monday 22 June 2020 08:19:15 Charles Lepple wrote: > > On Jun 18, 2020, at 12:39 PM, Mike Dillinger wrote: > > > > ups.test.result: No test initiated > > I’d recommend a battery test. Starting the test via the front panel > should be sufficient, or you might be able to do it with upscmd. from man pi at rpi4:~ $ upscmd -l myups Instant commands supported on UPS

On 5/22/23 03:10, gene heskett wrote: > Which file in the nut I pulled a month ago, should I start with to get > the new version actually running? I still get - -V=2.7.4 The UPGRADING file tsalks about a 2.8.1, but I have started with the autogen 3 times in the usual sequence, winding up with 2.7.4 twice, and while the third time is supposed yo be a charm, now it won't run at all.

Greetings, I'm trying to bring up a alpine rpi aarch64 image within kvm but I'm ended up with a stuck system, here is the xml: <domain type='qemu'> <name>alpine_rpi4_dev_machine</name> <uuid>b1b155fc-cb92-4f22-8904-c934dd24415b</uuid> <memory unit='KiB'>4194304</memory> <currentMemory