similar to: NUT Client shuts down when performing runtime calibration on APC UPS

On Wed, 11 Jan 2017, Merk - Oliver wrote: > nas4free: /# more /usr/local/bin/upssched-cmd > #!/bin/sh I would strongly recommend specifying which script interpreter is to be used: dash, bash, csh, ksh, ... For example #!/bin/bash There seem to be too many case statements in this script. > case "${1}" in > shutdown-warning) >

Here are the results from the output of upsc under different conditions from my Debian Test system with NUT 2.7.2 : Normal: ups.status: OL No wall power: ups.status: OB Runtime calibration (started from AP9630 web interface): ups.status: OB CAL So at this stage there is a difference! I then connected to my QNAP and set the UPS settings on the web interface to "Shutdown server if power

I need some help here with getting this thing running. Every time I enable NUT on the server, I get a "on battery" status when I know that it is running on house power. This only occurs when I am monitoring it with FreeBSD(NAS4Free) When i plug the same UPS into CentOS 6.7, It works as expected. I am not sure what the difference between the NUT versions other than the base OS would be.

Hello, I am using an APC UPS (Smart-UPS 2200 RM) to secure my SAN. The SAN runs on FreeBSD 9.1-RELEASE-p5 and is using NUT 2.6.5 version 2. Since the UPS has also a Network card AP9630 I am using the snmp-ups driver to connect the SAN to the UPS for signaling. Last week I need to change the battery pack and then I needed to perform a runtime calibration. I used the web interface of the AP9630

>> >> I need some help here with getting this thing running. Every time I enable NUT on the server, I get a "on battery" status when I know that it is running on house power. This only occurs when I am monitoring it with FreeBSD(NAS4Free) > >Which version of FreeBSD is this based on? I also included the Motherboard and processor so if there is anything those

I'm trying to use a Nas4Free storage system. This same hardware worked fine on Freenas 0.7.2. O/S: Nas4Free 9.0.0.1.148 which comes with nut 2.6.4. UPS is an APC Back UPS RS 800. USB interface. Driver : usbhid-ups Port: auto my NAS is communicating with the UPS, but in testing power failures, I'm not getting the shutdown to be handled properly. When I pull the AC plug on the UPS,

Hello Having the next problem, manually adding via WinSCP in the upsd.users file the user for remote monitoring, saving the file, WinNUT client connects after "upsd -c reload" in NAS4Free console, but if I restart the NAS4Free system, the slave user disappears from upsd.users and remains only the master user. NAS4Free is version 9.1.0.1 rev 724 and NUT is the version what is included.

Thanks, the strange is that I could set in this way the master user. At NAS4Free forum cannot get help, I presented the problem there too, but no real help. On Thu, Aug 22, 2013 at 2:19 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 21, 2013, at 10:41 AM, Incze Andras wrote: > > > Having the next problem, manually adding via WinSCP in the upsd.users > file the

I'm using Nas4Free, and I'm getting the following message all the time in the Daemon log: usbhid-ups[42466]: libusb_get_report: Unknown Error I'm running Nas4Free 9.2.0.1 Shigawire Driver usbhid-ups Nut Version is 2.7.1 Internal verion 0.38 UPS Info from Nas4Free Manufacturer:CP1500PFCLCD Model:CRCA102*AF1 The model UPS I'm running is a Cyber Power CP1500PFCLCD, other

On Aug 21, 2013, at 10:41 AM, Incze Andras wrote: > Having the next problem, manually adding via WinSCP in the upsd.users file the user for remote monitoring, saving the file, WinNUT client connects after "upsd -c reload" in NAS4Free console, but if I restart the NAS4Free system, the slave user disappears from upsd.users and remains only the master user. > NAS4Free is version

Hello, I'm trying to integrate HAST to NAS4Free (FreeBSD 9.1-RC3). Now I have created version 9.1.0.1.531. http://sourceforge.net/projects/nas4free/files/NAS4Free-9.1.0.1/9.1.0.1.531/ Basic CARP + HAST + iSCSI target setup can be done, but very frequently I get hastctl hang when called: /sbin/hastctl status /sbin/hastctl dump Is it better for this method not to call from a script? or

On Aug 22, 2013, at 5:15 AM, Incze Andras wrote: > Thanks, the strange is that I could set in this way the master user. That is odd. The development version of NAS4Free seems to be regenerating the entire upsd.users file: http://sourceforge.net/p/nas4free/code/848/tree/trunk/build/ports/nut/files/nut.sh.in To address your original concern (adding remote users for monitoring), I would

I have gotten the links to the ./configure for NUT for NAS4Free see nas4free build makefile http://sourceforge.net/p/nas4free/code/ ... t/Makefile config files: http://sourceforge.net/p/nas4free/code/ ... nut/files/ I hope this give some insights On Wednesday, August 19, 2015 6:00 AM, Charles Lepple <clepple at gmail.com> wrote: On Aug 19, 2015, at 12:08 AM, Johnny Wong

There is some problem with formatting :( If I paste how was written, the structure is wrong formatted, is putted somewhere right after the end of 1st part with master in the generated file. On Thu, Aug 22, 2013 at 3:32 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 22, 2013, at 5:15 AM, Incze Andras wrote: > > > Thanks, the strange is that I could set in this way

On Jan 9, 2017, at 9:46 AM, Merk - Oliver <oliver.merk at pecon.biz> wrote: > > I then connected to my QNAP and set the UPS settings on the web interface to "Shutdown server if power loss is 5 min", the UPS is configured to an SNMP-Connection with its IP-address. Started runtime calibration and after 5min. the QNAP NAS has shut down. But before that I connected via SSH on

On Aug 23, 2013, at 12:49 PM, Incze Andras wrote: > There is some problem with formatting :( > > If I paste how was written, the structure is wrong formatted, is putted somewhere right after the end of 1st part with master in the generated file. Can you be more specific? You can attach text files if needed. > On Thu, Aug 22, 2013 at 3:32 PM, Charles Lepple <clepple at

OS = NAS4Free (FreeBSD Revision: 199506) NUT Version = 2.7.3 for other parts of NUT version is listed below NUT is part of the NAS4Free distribution Device = Tripp Lite SMART1300LCDT URL http://www.tripplite.com/line-interactive-ups-system-desktop-tower-1300va-120v-usb-port-lcd-screen~SMART1300LCDT/ PROBLEM: NUT is ABLE to see the UPS BUT it is not getting the right(?) descriptor? I am using

> What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) FreeBSD 10.2-RELEASE #0 r286738M the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free.? if you need the ./configure I might have to look for their source on GitHub or something. /usr/local/libexec/nut/usbhid-ups -a

Hello, I would like to use nas4free under xcp 1.6. I install it under full HVM using "other install media". Now I am attaching 4 hdds as external disks. The vm sees at most two hdds, I suppose because of bios support (1 boot + 1 cdrom + 2 hdds= 4 hdds). I need to use more disks, is it possible? If not, it seems to me a serious limit. Mario

Hi all, actually I got a problem with the namespaces in dovecot 1.1 beta11. It occured after purging index files and resynch via imapsync. Dovecot complains about "Unknown namespace", though it worked with versions before. I cannot comfirm for 1.1beta10, but I surely know 1.1beta9 worked with these settings. Example: From Folder [INBOX/Trash] To Folder [___________] To Folder