similar to: Nut-upsuser Digest, Vol 231, Issue 4

THIS IS systemctl list-units | grep UPS nut-driver at back-ups.service

By side effect, lack of "killpower" touch file works to not-tell the OS shutdown integration on OMV to turn off the UPS. A more proper way about this is generally to change MONITOR back-ups 1 monmaster 4L[p9<0Vi|Z>xKgK master (see my earlier message or docs about primary/master vs. secondary/slave clients), to MONITOR back-ups 1 monmaster 4L[p9<0Vi|Z>xKgK slave and it

As fast as I know, the standard NUT package will not command your power supply off unless customizations are made. Devices like Synology have an option to command the UPS off. What is acting as your NUT server? Your server PC? On Fri, Sep 6, 2024, 11:10 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to > nut-upsuser at

Hallo all. I tried to configure the UPS Trust OXXTRON 1300VA but i didn't succeed. i tried the blazer_usb <http://www.networkupstools.org/docs/man/blazer_usb.html> driver and others but i didn't succeed. My lsusb says Bus 002 Device 005: ID 0925:1234 Lakeview Research Bus 004 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 004 Device 004: ID 0424:2228 Standard

Hello, I had running OpenMediaVault server with NUT 2.4.3 megatec_usb driver. After the OMV upgrade, NUT also upgraded to 2.6.4. I realised that megatec_usb removed in this version. So I have configured to use blazer_usb driver. However NUT behaves incorrectly after switching blazer_usb. System is being halted upon booted up. Is it possible to use megatec_usb driver in the new version? # NUT

On Fri, 11 Oct 2024 15:46:23 +0200 "lnj.sam--- via samba" <samba at lists.samba.org> wrote: > Hi, > > We have a NAS server with OpenMediaVault on a Debian system. > > Mainly we work directly with documents from the LibreOffice and > Office tools. > > Sometimes we note at the opening of a LO document that the file is > corrupted and not repairable.

Hi, We have a NAS server with OpenMediaVault on a Debian system. Mainly we work directly with documents from the LibreOffice and Office tools. Sometimes we note at the opening of a LO document that the file is corrupted and not repairable. We know LO documents are a bunch of files embeded in a compressed ZIP archive. The most of time we can repair them in replacing the corrupted elements

OS: Openmediavault 7.4.7-1 NUT version: 7.0.4-1 Intalled from OMV plugin installer MY UPS: APC BX1200MI-GR connected through USB all of my UPS data are in this screenshot my problem that i need help with is as follow: so what's happening is if my gaming PC / router / switch are connected and power is down the UPS switches normally without issues from AC to battery and vice versa when the

Hi, I'm working hard to setup winbind and openLDAP work together with TLS My networks contains: - a windows server 2008 R2 domain controller - a debian 6 based file server (openmediavault v0.4) running OpenLDAP 2.4.23 and Samba v3.5.6 - a debian 7 computer running winbind 3.6.6 I want to let OpenLDAP store SID <=> uig/gid mapping to ensure constant uid and gid for users on all linux

On Thu, 29 Oct 2015, George Anchev wrote: > Today I experienced something weird. As I was working, the system > started a shutdown and did shut down, then the UPS got powered off and > then back on - an expected behavior for a power fail situation. However > there was no power failure! ... > Oct 29 10:46:46 i7 upsmon[2239]: UPS myups at localhost battery is low > Oct 29

I'm running a single "nut-server" that monitors seven ups units. In upsmon.conf: MONITOR ups-1 0 <User> <Pw> master MONITOR ups-2 0 <User> <Pw> master MONITOR ups-3 0 <User> <Pw> master MONITOR ups-4 0 <User> <Pw> master MONITOR ups-5 1 <User> <Pw> master MONITOR ups-6 1 <User> <Pw> master MONITOR

Hi, I cant seem to get my upssched to get called by upsmon. Upsmon -c fsd just shuts down without the message I set or the one in upssched-cmd /etc/ups/upsmon.conf: MONITOR ups6 at localhost 1 <user> <pass> master MONITOR ups8 at localhost 1 <user> <pass> master SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/sbin/upssched NOTIFYMSG

> If there is no message to NUT, I would consider opening a trouble > ticket with Eaton. It is possible that there is a known issue and/or > a firmware upgrade. What kind of message to NUT? In the log (syslog) there is no other message registered. In nut.log only this appears: > Dec 1 08:10:54 openmediavault upsd[5284]: Data for UPS [ellipsemax] > is stale - check driver >

On 20/05/2019 18:54, Hendrik Friedel wrote: > Hello, > >> Is btrfs becoming more common ? > In my impression: Yes. Also, this problem seems to affect also zfs and > thus all (?) file systems that support checksums and scrubbing in > linux; consequently all filesystems that are the choice of users who > need this for ensuring data consistency. Not from my experience, but,

There's supposedly another way with a custom upsmon.conf: NOTIFYMSG type message upsmon comes with a set of stock messages for various events. You can change them if you like. NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "Someone pulled the plug on %s" Note that %s is replaced with the identifier of the UPS in question. The message must be one

Hi, I want to test the events off my UPS. I define In upsmon.conf: RUN_AS_USER root NOTIFYCMD /sbin/upssched NOTIFYMSG ONLINE "UPS %s on line power" NOTIFYMSG ONBATT "UPS %s on battery" NOTIFYMSG LOWBATT "UPS %s battery is low" # NOTIFYMSG FSD "UPS %s: forced shutdown in progress" NOTIFYMSG COMMOK "Communications with UPS %s established"

I have restored original configuration and enabled the ignorelb flag. I didn't point out in the original e-mail that after every poweroff the battery percentage is reported at 40% instead of 100% and charges slowly again to 100%. Maybe the UPS sends a LB event and shuts down immediatly as suggested in the manual. But the UPS powered off again. The variables reported by upsc can be found

Ok, I am running NUT in dummy mode. I have added a new ups in ups.conf [dummy] driver = dummy-ups port = upsc.dev desc = "dummy ups for testing purposes" upsc.dev has been generated by exporting the Elit configuration. I have added the monitor line in upsmon.conf and the "exec" flags (all the events) MONITOR dummy at artu 1 user pass master SHUTDOWNCMD

P.S.2 Today I experienced something weird. As I was working, the system started a shutdown and did shut down, then the UPS got powered off and then back on - an expected behavior for a power fail situation. However there was no power failure! I ran nut-journal to check what happened: Previous complete boot through shutdown Oct 29 10:09:33 i7 upsdrvctl[1966]: Using subdriver: MGE HID

I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath. Is there something I am missing? Please see attached. Dan -------------- next part -------------- An HTML attachment was