similar to: A03-OP1000 MS02035C not shutdown

Hello, my Atlantis UPS (model on "subject" line) fails to cycle off the outlet power after a power failure on the mains followed by an automatic shutdown of the computer. The UPS simply remains always on, preventing the computer from restarting. ** Setup: ** Nut version 2.7.2 Nut driver blazer_usb Linux 4.1.1 The config files are pretty default; the peculiar customization is

On 10/14/2015 10:17 AM, Roger Price wrote: > What does "ps aux | grep ups" report? ps aux | grep ups nut 2902 0.0 0.0 20588 1140 ? Ss 00:10 0:02 /lib/nut/nutdrv_qx -a myups nut 2946 0.0 0.0 37632 1428 ? Ss 00:10 0:00 /lib/nut/upsd root 2970 0.0 0.0 37616 1436 ? Ss 00:10 0:00 /lib/nut/upsmon root 2973

I changed the driver from blazer_usb to nutdrv_qx, by editing /etc/nut/ups.conf. To apply changes, I did: # service nut-server restart # service nut-client restart Then I've run a second test, this time simpler than the first one described in my previous email; the test only consists in toggling off/on a wall switch which controls power to the UPS. This way, electric ground remains

On 10/14/2015 12:18 PM, Roger Price wrote: > Is there any command in the list provided by "upscmd -l myups" which is accepted > by this UPS? None of the command sin the list successfully completes, not even beeper.toggle. My list: # upscmd -l myups Instant commands supported on UPS [myups]: beeper.toggle - Toggle the UPS beeper load.off - Turn off the load

On Tue, 13 Oct 2015, Davide Baldini wrote: > Guess I can assume that my OnePower A03-S1001 just doesn't support the > shutdown command. Might this be the case? If the UPS does shut down, then it will have to do so after a delay and not immediately on receiving the shutdown command. Does upsc <ups_name> report anything like ups.delay.shutdown: 30 ups.delay.start: 40

On Wed, 14 Oct 2015, Davide Baldini wrote: > the full output of upsc ${myups} is at https://pastebin.mozilla.org/8849188 ; > in particular: > > ups.delay.shutdown: 30 > ups.delay.start: 180 > > However, the UPS does not shut down, not immediately nor well after the > timeout of the command: upscmd -u admin -p mypass myups shutdown.return 360 What does "ps aux |

On Oct 2, 2015, at 9:01 PM, Davide Baldini <baldiniebaldini at gmail.com> wrote: > > When I manually unplug the mains, the computer waits 3 minutes, shutdowns, and there it stays. As per the above commands, issued from ups_events.sh, it is instead supposed to boot up after 6 minutes (360 / 60 seconds) counted from t?, the moment of the unplug. After 20 seconds from the shutdown, and

Thanks Roger, the full output of upsc ${myups} is at https://pastebin.mozilla.org/8849188 ; in particular: ups.delay.shutdown: 30 ups.delay.start: 180 However, the UPS does not shut down, not immediately nor well after the timeout of the command: upscmd -u admin -p mypass myups shutdown.return 360 -- Davide

On Wed, 14 Oct 2015, Davide Baldini wrote: > upsdrvctl shutdown > ... > instcmd(shutdown.return, [NULL]) > instcmd: FAILED > Shutdown failed! > Driver failed to start (exit status=1) > > This time /var/log/syslog doesn't register anything about the UPS after > issuing the command above. Instead, It logged some errors after a > upscmd -u admin -p mypass

On 10/14/2015 06:11 PM, Roger Price wrote: > Is /etc/init.d/nut-client a Bash/Dash script? Is it possible to add the option to > the call of the driver in this script? Looks like some options can be passed: /etc/init.d/nut-client is a dash script and when it is started or restarted, it executes: start-stop-daemon -S -q -p $upsmon_pid -x $upsmon \ -- $UPSMON_OPTIONS >/dev/null

Guess I can assume that my OnePower A03-S1001 just doesn't support the shutdown command. Might this be the case? -- Davide

Atlantis Land A03-P551(V1.2) battery.charge: 100 battery.voltage: 13.70 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.mfr: device.model: device.type: ups driver.name: blazer_usb driver.parameter.langid_fix: 0x0409 driver.parameter.pollinterval: 2 driver.parameter.port: x driver.version: 2.6.4 driver.version.internal: 0.08 input.current.nominal: 0.0

On Wed, 14 Oct 2015, Davide Baldini wrote: >> Is there any command in the list provided by "upscmd -l myups" which is >> accepted by this UPS? > > None of the command sin the list successfully completes, not even > beeper.toggle. It looks as if the problem is more general than turning off the UPS. The command mechanism is broken. > I added -q and -D to

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

Hi there, I made a new driver, based on blazer, that should work with most of the UPSes manufactured by Voltronic Power - http://www.voltronicpower.com/oCart2/index.php?route=product/category&path=37- and rebranded as Atlantis Land, Cablematic, EPC, FSP, Mustek, SHT, Tuncmatik and many others (they come with a software called Viewpower - http://www.power-software-download.com/viewpower.html )

- OS name and version: Ubuntu 12.04 - exact NUT version: 2.6.3 - NUT installation method: from Ubuntu package "nut 2.6.3-1ubuntu1.1" - exact device name and related information: AtlantisLand Host Power 851 (A03-HP851 rev.1.1) - driver: blazer_usb I have no problems with the operation of NUT. My only problem is that I would like to change the behavior of the NUT driver

Hi! I am trying to get an Atlantis-Land 1501 UPS to work under OpenBSD. The UPS works OK under Linux + megatec_usb driver+nut_2.2.2. What I get under OpenBSD is: root at puffwall:~ # dmesg OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2

Hi! I am trying to get an Atlantis-Land 1501 UPS to work under OpenBSD. The UPS works OK under Linux + megatec_usb driver+nut_2.2.2. What I get under OpenBSD is: root at puffwall:~ # dmesg OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2

Glad you got it working. Denny > On Jul 28, 2018, at 19:02, richjunk at pacbell.net wrote: > > Denny: > > Thank you. Problem solved. > > I switched SHUTDOWNCMD back to the default and added nut.powerfail to > the shutdown runlevel. Now the UPS turns off after the system shutdown, > if the shutdown is caused by lack of power going to the UPS. > > I checked

Roger, Following your guide, it now works great, shutting down the UPS after the system has shutdown. I went with the bash script method. I have noticed, however, that the command to the UPS to do the delayed shutdown comes RIGHT as openSUSE is shutting down. While that is a good thing as far as timing and the potential race is concerned, I have seen it once where the UPS received the command