similar to: ups.delay.shutdown clarification

A client of mine has an APC Back-UPS 350 model (USB connected). His office had a power incident yesterday, where there was an interruption of about 30 seconds. During that time, the server shut down. As soon as it went on battery, the daemon initiated a shutdown. In checking it today, I see the ups.delay.shutdown setting is -1. I tried to adjust it, but could not do so. What does the

Following the recent "trans2" exploit announcement, SuSE released kernel 2.6.5-7.111.5 to deal with it. I've installed the kernel upgrade on my desktop (SuSE 9.1, Samba 3.0.4). However, with this kernel, when I try to save to a share on my server (Samba 2.2.8), I get this set of error messages: Dec 13 22:10:25 p133 kernel: smb_trans2: invalid data, disp=0, cnt=0, tot=0, ofs=0 Dec 13

Hello list! I can't seem to get this running via RS232 monitoring; I've been told that NUT won't support serial connections, and find this hard to verify. Does anyone else have this running on the SU10KRT3U via RS232? If so, what driver did you use? I'm getting no satisfaction from the "tripplite" driver; upon upsdrvctl start, I get "Failed to find UPS - giving

Hello all, I was having this problem and finally found a temp fix for it. The symptoms seem to be this: --> You are on a linux client --> You have mounted a samba drive from you linux client to a linux server. --> When you try to make modifications or copy file from your client to the server, it takes a long time or times-out. --> Your /var/log/mesages file states smb_trans2:

I run a small network at home, with a Linux server, which shares files and a printer. I also have a Linux PC (RH 9, KDE 3.1, CUPS 1.1.17) from which I am trying to share a Lexmark 3200 inkjet. Samba (2.2.7a-security-rollup-fix) seems to be generally configured OK - I can print to the Lexmark from a Windows 98 system, and from another PC running Mandrake 9.1. However, I am unable to print from two

I was testing my new MGE Nova 1100 and I am seeing negative numbers for ups.delay.start and ups.delay.shutdown which seems odd, but also seems to be expected according to examples I have found for MGE Systems. Can someone explain or point me to an explanation of what those numbers mean? The short descriptions don't appear to be compatible with negative numbers.

Hi, My Cyber Power reports these two values. Each pair has the same value. Would they normally be the same thing? Thanks Alan

Thanks On Sat, 16 Mar 2024 at 18:57, Charles Lepple <clepple_at_gmail.com_chribonn at duck.com> wrote: > > On Mar 14, 2024, at 11:41?AM, Alan via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > > Hi, > > > > My Cyber Power reports these two values. Each pair has the same value. > > > > Would they normally be the same thing? >

Hi! I'm using nut to control a ups powerware 9135. All are working, but, in the shutdown, the ups don't poweroff. I did check with upsc, and I can't see a ups.delay.shutdown variable to set the time of automatic poweroff, when I did complete the shutdown of machines. Before, I did use a propietary program to work with this ups, and the daemon did poweroff the ups without problems. But,

On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote: >> The upsrw command was designed for changing variables that are typically >> stored in non-volatile memory on the UPS. Unfortunately, your UPS doesn't >> seem to do that. > > Well, if it doesn't do that, how come upsc reports the changed value? It is > only after I reboot the PC

[when responding, please use reply-all - the list does not mangle the reply-to header] > On Aug 21, 2017, at 12:45 AM, Whiteshell Tech <neil at whiteshell-tech.com> wrote: > > I have attempted to set the delay higher using "upsrw -s ups.delay.shutdown=120 TrippLiteUPS at localhost" and confirmed the value with "upsc TrippLiteUPS at localhost" Still the UPS

On Aug 21, 2017, at 1:35 PM, Whiteshell Tech <neil at whiteshell-tech.com> wrote: > > I ran it again on battery and upsd running, set upsrw ok and then shutdown.return gave an "ERR CMD-NOT-SUPPORTED" Odd thing is after running that I am getting random timed ups powering off for one or two seconds then turns back on even on battery. Server then starts shutting down. Some

On Wed, 4 Jun 2014, Mick wrote: >> Some of the variables (those with HU_FLAG_ABSENT) are apparently not stored >> on the UPS itself-- they are sent to the UPS when the shutdown command is >> executed. Sending the value starts the timer, in some cases, but I think >> the ups.delay.start value should be safe to send at the time when it is >> set. > > I see. So if

On Wednesday 04 Jun 2014 03:07:27 Charles Lepple wrote: > On Jun 3, 2014, at 1:28 AM, Mick wrote: > > On Saturday 05 Apr 2014 16:28:24 Charles Lepple wrote: > >> On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote: > >>> On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote: > >>>>> The upsrw command was designed for changing

On Saturday 05 Apr 2014 16:28:24 Charles Lepple wrote: > On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote: > > On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote: > >>> The upsrw command was designed for changing variables that are > >>> typically stored in non-volatile memory on the UPS. Unfortunately, > >>> your UPS

I'm testing a Powercom UPS (branded as Control System 2 STD80S: http://www.cs2.it/home.php?goto=prodotti&cat=0&idp=2&subid=0) with NUT. It is a USB HID device, with ID 0d9f:0004. I configured nut-server to use driver usbhid-ups and it works almost correctly: upsd communicates right with the device, upsmon catches its events... But when I try to perform a Forced Shutdown, UPS pauses

On Jun 3, 2014, at 1:28 AM, Mick wrote: > On Saturday 05 Apr 2014 16:28:24 Charles Lepple wrote: >> On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote: >>> On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote: >>>>> The upsrw command was designed for changing variables that are >>>>> typically stored in non-volatile memory on

On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote: > On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote: > >>> The upsrw command was designed for changing variables that are typically >>> stored in non-volatile memory on the UPS. Unfortunately, your UPS doesn't >>> seem to do that. >> >> Well, if it doesn't do that,

On Apr 5, 2014, at 7:18 AM, Mick wrote: > $ upsrw -s "ups.delay.shutdown"="30" iDowell at localhost > Username (suzy): admin > Password: > OK This command is sending the value to the UPS (via the usbhid-ups driver). > $ upsc iDowell at localhost ups.delay.shutdown > 30 And this command ends up reading the value back from the UPS. > However, following

Thanks Charles, On Saturday 05 Apr 2014 12:53:06 Charles Lepple wrote: > On Apr 5, 2014, at 7:18 AM, Mick wrote: > > $ upsrw -s "ups.delay.shutdown"="30" iDowell at localhost > > Username (suzy): admin > > Password: > > OK > > This command is sending the value to the UPS (via the usbhid-ups driver). > > > $ upsc iDowell at localhost