similar to: odd messages (apc 500 ls usb)

I'm running a freebsd 6.2 system and built the nut port. I cannot seem to connect to serial com1 or 2 /usr/local/etc/nut> upsc apcBK500 at localhost Error: Connection failure: Connection refused My configs: ups.conf ----------------------- [apcBK500] driver = genericups upstype=20 port = /dev/cuad1 upsmon.conf -------------------------- MONITOR apcBK500 at localhost

Hello world! Please, help me :-) I have a APC RS-800 usb and it don't shutdown. I try every things but nothing: don't shutdown. Uhmmmm My actual situation: tux:/home/effem# uname -a Linux tux 2.6.26-1-686 #1 SMP Wed Aug 20 12:56:41 UTC 2008 i686 GNU/Linux tux:/home/effem# wajig policy nut nut: Installato: 2.2.2-6 Candidato: 2.2.2-6 Tabella versione: 2.2.2-7 0 -20

Dir list! I'm using nut for many years on my home "server" without problems running on Debian 6.x nut version 2.4.3 Now I have decided to move to Debian 10. I have started from zero and install new system on a different disk. I have successfully installed new nut version 2.7.4 I've found one issue, that new version see always "low battery" state. Excerpt from syslog:

Hi friends. Package: nut Version: 2.4.1-1 Depends: libusb, openssl, neon, libgd, net-snmp Status: install user installed Section: admin Architecture: mipsel maintainer: NSLU2 Linux <nslu2-linux at yahoogroups.com> MD5Sum: c8c55a6021fea2b5f194ce4623eb2dfe Size: 1246363 Filename: nut_2.4.1-1_mipsel.ipk Source: http://eu1.networkupstools.org/source/2.4/nut-2.4.1.tar.gz Description: Network UPS

Dear list, I have an APC Smart-UPS 1500 hooked up via the USB port. Recently, when we had a power outage, the only entry in the logs was: Dec 3 14:43:43 afs1 upsmon[3035]: UPS apc at localhost on battery and then the machine seems to have run until the battery was empty. It only notices the "battery low" after I turn the system back on: Dec 3 16:01:39 afs1 usbhid-ups[21973]:

I found their source code for what appears to be the previous version of DSM (their OS), the most recent entry in the NUT Changelog is: 2012-05-31 Arnaud Quette <arnaud.quette at free.fr> * [r3643] NEWS, UPGRADING, configure.in, docs/website/news.txt: Final update for 2.6.4 release Ah ha. Nevermind the above, I tried just running upsmon and that worked (with settings

Short description: when upsmon starts it logs this to /var/log/messages: Jul 11 12:35:55 sorcerer upsmon[23902]: Startup successful Jul 11 12:35:55 sorcerer upsmon[23902]: user monuser not found Near as I can tell upsd is running properly. Long description: Centos 5 system (x86_64), built nut 2.2.2 from stable source with ./configure --with-usb --with-user=nut --with-group-nut make

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 was check out that is the connection between driver-monitor-server-client is working or not. I was put my server directly on power cable, keep control cable connection and use command: $ watch upsc APC600 I was switch to battery, after 2-3 second it show that is on battery OB and after it shutdown because of low battery LO. I think that systemd scripts some what unsynchronized, but after it

OS: Linux BS801-TEC-02 2.6.32-279.22.1.el6.x86_64 #1 SMP Wed Feb 6 03:10:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux CentOS release 6.3 (Final) Nut version: nut-2.6.5 NUT installation method: from source tarball ./configure --with-user=ups --with-group=nut --with-usb --prefix=/ups --localstatedir=/ups/var --with-pidpath=/ups/var/state/ups --with-statepath=/ups/var/state/ups --enable-static UPS

On 2014-02-16 16:36, Elliot Dierksen wrote: > On 2/5/2014 8:24 AM, Charles Lepple wrote: >> On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: >> >>> NUT will complain endlessly about communication errors and never >>> establish SNMP communication with my APC UPS >> Hmm, at first glance, I read the "complain endlessly" part as a figure >> of

Hello, I want to manage my SMART APC with nut 2.0.3 on Fedora Core 4. But i have this output at start of my ups: D?marrage de apcsmart :Network UPS Tools (version 2.0.3) - APC Smart protocol driver Driver version 1.99.7, command table version 2.0 Detected Smart-UPS SC1500 [5S0713T66466] on /dev/ttyS0 [ OK ] D?marrage de upsd

I have an older system which has a simple APC Back-UPS ES 500 connected via USB. I built nut 2.0.2 from source and am attempting to get it to work. I had to manually create the device links and I think it's ok because hidups is recognizing the UPS but any attempts to read data from it fail: [root@server bin]# ./hidups -D -D -D /dev/usb/hid/hiddev0 Network UPS Tools: HID UPS driver 0.13

Good Day Roger Price AA. Hi, Normally one would expect the UPS to disconnect it's power outlets after the default ups.delay.shutdown = 20 seconds. ==> I got it. I tried to command "upsdrvctl shutdown" on both line-mode and battery-mode ==> But ups do not disconnect its outlets power ----------------------------------------------------------------------------------- BB.

[please use reply-all to include the list.] > On Oct 12, 2015, at 4:52 PM, Daniel Green <ddgreen at gmail.com> wrote: > > I recently connected my UPS to my NAS. The NAS detected the UPS, and I checked the "Enable network UPS server" option and added relevant IPs to the "Permitted DiskStation devices" option. The NAS is running DSM 5.2-5592 Update 4, with a NUT

Hello list, I am configuring NUT on a Dell workstation that is connected to an APC Back UPS Pro 1300, and I am running into an issue where starting everything manually seems to be successful, but fails when using the init.d scripts. The short story is that I get the following error when trying to check the status of the UPS: [root at mypc:/etc/nut]# upsc apc_pro1300 at localhost Error:

To try and work through the initial drops, I repeated the previous steps that worked on the physical machine on the CentOS 7.6 virtual machine. The drops continued to occur, but it seems that the driver always reconnects. My initial inclination is to work through and see at what point I get the drops to stop, and I think I will do that next (inputs welcome). From a standpoint of “how much does

Well, after our first real extended power outage, I found out that even though the UPS 1000 RM is recognized okay, it does not work properly. It never seems to see any change in UPS status. It looks very similar to the other issue I reported with the APC CyberFort 350. I never was able to get to the bottom of the CyberFort issue, but I'll bet it's the same issue as we have with the

Hello, I encountered a problem with my APC Smart-UPS 750, connected via USB, using newhidups. Without any reason, nut/upsmon shut down my PC: >>> Oct 13 12:57:08 echo kernel: usb 2-9.1.1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -71 Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost on battery Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost