similar to: Trying to understand sdorder

Hi! On my FreeBSD 12.0-RELEASE-p7 server I was unable to retrieve the correct information from my two UPS. Every time only the first UPS will returned when I entering "upsc apc900" or "upsc apc901". I don't know why (Bug or configuration issue on my side?!). I have downloaded the latest source code and with my "patch" I was able to get the right information

Hi, I was trying to hack the /etc/rc.d/init.d/halt script under RH 9.0 in a way to achieve a clean shutdown: - commanding the RAID arrays to readonly mode - turning off my hardware watchdog, ... etc. See details below. At the end of all this preparation, and very close to the last lines of the halt script, I would then issue: 1. /usr/bin/belkinunv -x wait /dev/ttyS0 2. (OR, with a smart ups:

Hi, one user found problem with restarting nut. upsdrvctl does not wait for drivers being really terminated. In init scripts we have following: killproc upsmon killproc upsd upsdrvctl stop and then upsdrvctl start upsd upsmon problem is upsdrvctl stop only sends terminating signals but does not wait for driver termination. This makes driver fail to start sometimes when old driver is still

Hi, I've found that upsdrvctl crashes when there is not ports= specified ups.conf #0 __strrchr_sse2 () at ../sysdeps/x86_64/strrchr.S:33 #1 xbasename (file=0x0) at common.c:266 #2 stop_driver (ups=0x1e163e0) at upsdrvctl.c:135 #3 send_all_drivers (command=0x4020f0 <stop_driver>) at upsdrvctl.c:446 #4 main (argc=1, argv=0x7ffff30be9c0) at upsdrvctl.c:565 stop_driver

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

Hello Fabian, > I got my UPS (Belkin F6H350deUNV) to work with the "megatec" driver. > Obviously the de/uk part in the name of these products are > localizations of some sort. So the F6H 350/500/750 UNV Home Office > products should all work with that driver. > > bigone nut # upsc ups@localhost > battery.charge: 95.0 > battery.voltage: 13.50 >

Hello, In order to identify if was some issue regard to the auth api we include some trace logs and we move it to other machine. Bellow is what trace we are generating (date, result, elapsed time in milleseconds, request): [8/29/18 11:49:00 AM] 200 0.3721 action=listener_add&server=r22&port=443&client=2616&mount=/alphafmsp&user=&p

I am trying to make a barplot with a broken axis using gap.barplot (in the indispensable plotrix package). This works well when the data is a vector: > twogrp<-c(rnorm(10)+4,rnorm(10)+20) > gap.barplot(twogrp,gap=c(8,16),xlab="Index",ytics=c(3,6,17,20),ylab="Group values",main="Barplot with gap") But when the data is an array (for a bar plot with multiple

I'm not sure I understand your question. The UPS was running for more than 15 minutes before it went below the battery.charge.low: of 70. Below is my /etc/nut/nut.conf. My goal is that when the UPS report a battery.charge.low of < 70 (or, if possible has been running for 5 minutes) it starts the shutdown process. The shutdown process should take 15 minutes so that proxmox can shutdown

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

>I'm afraid I am just the messenger - @bigon (Laurent Bigonville, on GitHub) is a Debian maintainer of NUT, and he was pointing out the >bug report filed with Debian: >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738122 >With other drivers, we sometimes see the "did not claim interface 0 before use" error if a driver gets out of sync with its PID file, >and

I have NUT server connected to the UPS, several other servers connects to this server, after 5 minutes without power I want all the servers to shutdown without waiting to the UPS batt status. Everything works ok, but I have one issue, the NUT server shutdown the UPS unit too, this is ok in most case but in our case I don't want the UPS to be shutdown. All the servers yes and the NUT server

Processing commands for control at bugs.debian.org: > found 712376 4.1.4-4 Bug #712376 [src:xen] xen FTBFS with current gcc-4.8 Marked as found in versions xen/4.1.4-4. > tags 712376 + sid jessie Bug #712376 [src:xen] xen FTBFS with current gcc-4.8 Added tag(s) sid and jessie. > user debian-gcc at lists.debian.org Setting user to debian-gcc at lists.debian.org (was bigon at debian.org).

Dear all: I have the following codes: Xdata<-c(2,3,8,9,10) Ydata<-1:5 gap.plot(Xdata, Ydata,gap=c(5,6),gap.axis="x",type="o") However, the type='o' seems only work on the first part of gap plot, the second half of the plot always just points, you can not add lines on that part, any help will be highly appreciated. I would like to have these two parts of

Hi, I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified

Dear Charles, Thanks for your quick reply, but I can't install nut_2.7.2 in my raspberry. 1) I create a [nut] directory and use wget to download three files: [nut_2.7.2-1.dsc] [nut_2.7.2.orig.tar.gz] [nut_2.7.2-1.debian.tar.xz] 2)I unpack: dpkg-source -x nut_2.7.2-1.dsc 3) I use command root at pi1:/nut/nut-2.7.2# debuild -us -uc . .. And I have the following error code:

Dear R- list, I have some data to present with histograms. Therefore I used hist(...). I have few values with almost 80% of the frequencies (totaly 800) and some other values with low frequencies ( totaly 5 -10 ) that I want to emphasize. Therefore I want to "cut" the y-axis on 100, but I don't know how to deal with this. Thanks in advance, Michael Graber

Dear Steve, Thanks. Until today I could not install the nut in my raspberry. All installation good, but with my ups " Ovislink Chrome 1000VA" and "nutdrv_atcl_usb" driver, it inform me the following error details. I can startup nut but nutmon don't receive anything only (lost conection). My setup: root at pi1:/nut# lsusb Bus 001 Device 002: ID 0424:9512 Standard

Processing commands for control at bugs.debian.org: > user debian-qa at lists.debian.org Setting user to debian-qa at lists.debian.org (was anbe at debian.org). > affects 774889 + xfswitch-plugin Bug #774889 [gdm3] gdm3: fails to upgrade squeeze -> wheezy -> jessie - trying to overwrite /usr/share/gdm/BuiltInSessions/default.desktop Added indication that 774889 affects xfswitch-plugin

I think I may be of some help in this matter. Since I am running a bunch of Raspberry Pi's with NUT and it took a lot of hacking to make it possible. You could probably copy and paste this right into a shell script and just run it ... # Do an rpi-update FIRST to prevent USB strangeness #some depencies from repo sudo apt-get -y install m4 libtool libudev-dev automake #fixing autoconf for