similar to: Start up script fails

On 1/31/15, Charles Lepple <clepple at gmail.com> wrote: > On Jan 31, 2015, at 9:17 AM, Melvin Call <melvincall979 at gmail.com> wrote: > >> There is no other information provided, and there is nothing in the log to >> help >> either. Can anyone tell me what I need to do to make this output some >> useful >> information that I can use to further

On Jan 31, 2015, at 9:17 AM, Melvin Call <melvincall979 at gmail.com> wrote: > There is no other information provided, and there is nothing in the log to help > either. Can anyone tell me what I need to do to make this output some useful > information that I can use to further trouble-shoot the problem? In general, if a startup script isn't doing what I think it should, I run

On 1/31/15, Charles Lepple <clepple at gmail.com> wrote: > On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote: > >> One last question if you don't mind. I noticed the "default" POWERDOWNFLAG) >> is >> set to /etc/killpower, but I changed that to /tmp and modified my >> umountroot >> script to mount it read only

On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote: > One last question if you don't mind. I noticed the "default" POWERDOWNFLAG is > set to /etc/killpower, but I changed that to /tmp and modified my umountroot > script to mount it read only too, because I know it gets wiped on reboot. Is > there anything that removes /etc/killpower on

On Feb 1, 2015, at 7:04 AM, Melvin Call <melvincall979 at gmail.com> wrote: > Thank you Charles, for the assistance and the information. Everything is > completely functional here now. Not sure if the APC BackUPS ES550 is on the > list of compatible devices, but it works just fine with the usbhid-ups driver, > and supports several basic commands. You're welcome! We do have

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:

On Jan 30, 2015, at 4:22 PM, Melvin Call <melvincall979 at gmail.com> wrote: > At this point I unplugged the UPS and plugged it into a different USP port, but > that did not change the above. Figuring this was likely a udev problem, I > created the following /etc/udev/rules.d/52-nut-usbups.rules (based on an example > on our database server, and changing the vendor and product

Hi, I'm trying to get a sweex ups working with nut on debian sarge. This one: http://www.sweex.com/producten.php?lang=1&%20sectie=&item=59&artikel=95 It's shipped with UPSmart and according to the compatibility list it should work with the genericups upstype=7 driver. But it doesn't. I get: mybox:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl

Hi, I feel that i'm having a small problem with my upsmon configuration (maybe even simply a permissions problem) since I upgrade today to 2.0.2 I have apcsmart set up and talk to my ups no problem (upsc get answer). I have upsd running no problem! But when I try to start upsmon, it's unable to talk to my upsd. Having try a few option I found that saying RUN_AS_USER=root makes my upsmon

Hi, Self-reply ftw, is it something to do with the permissions of the device that is created when the UPS is plugged in? I remember that Debian does have a pretty strict permissions structure, so do I have to fiddle the permissions of something in /dev? I'll try updating nut-server to version 2.6.4-2.3+deb7u1 in wheezy backports and report back - initial attempt to install from wheezy

Hi all, (Keeping this in a separate email from my first one so as to not make it horribly complex) I've connected my Belkin F6C120auUNV UPS to my Debian 7.7.0 host via USB, and found that the usbhid-ups driver will not start unless I use the option '-u root', even when starting this driver as root: root at monitor:/lib/nut# cat /etc/nut/ups.conf [greything] driver =

I got a bunch of configfiles that look like this: mgmt-dev:/etc/nut# grep -v 'niets' * ups.conf:[ups] ups.conf:driver=newhidups ups.conf:port=auto upsd.conf:ACL all 0.0.0.0/0 upsd.conf:ACL localhost 127.0.0.1/32 upsd.conf:ACL remote 192.168.110.0/24 upsd.conf:ACCEPT remote upsd.conf:ACCEPT localhost upsd.conf:REJECT all upsd.users:[monuser] upsd.users:password = mypass upsd.users:allowfrom

I went to the link to test the power off if the battery gets to low. Here is what I got on the command line. root at odroid-u2:/etc/nut# /usr/local/ups/bin/upsdrvctl -t shutdown -bash: /usr/local/ups/bin/upsdrvctl: No such file or directory root at odroid-u2:/etc/nut# find / -name upsdrvctl /sbin/upsdrvctl ^C root at odroid-u2:/etc/nut# /sbin/upsdrvctl -t shutdown Network UPS Tools - UPS driver

Got the: git clone git://github.com/networkupstools/nut.git To work. Had to all so do this: apt-get install autoconf apt-get install libtool Did put driver = usbhid-ups in the /etc/nut/ups.conf file like you said. Here is what I got for it all: root at odroid-u2:~/nut# ./autogen.sh Calling autoreconf... libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying

Here are my permissions and user info. Let me know if there is anything else I should check pi at nutpi:~ $ ls -alt /etc/nut total 56 drwxr-xr-x 87 root root 4096 Jan 26 15:22 .. drwxr-xr-x 2 root nut 4096 Jan 26 13:53 . -rw-r----- 1 root nut 4719 Jan 26 13:15 upssched.conf -rw-r----- 1 root nut 15347 Jan 26 11:25 upsmon.conf -rw-r----- 1 root nut 1543 Jan 26 10:02 nut.conf -rw-r-----

The nut ups daemons seem to be communicating with the UPS but upscmd gives me no joy. Running commands do nothing and produce no output. Using the web interface returns an authentication failure and that is the only clue I have. I believe I have everything setup correctly but it's not working. Can someone review this and give me clues as to what I should research next?

I did just copy and paste on the command line like this: root at odroid-u2:/etc/nut# Shutdown UPS: serverups -bash: Shutdown: command not found root at odroid-u2:/etc/nut# /lib/nut/usbhid-ups -a serverups -k Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.31 Using subdriver: CyberPower HID 0.3 Initiating UPS shutdown root at odroid-u2:/etc/nut# Don't know why

Greetings! I have successfully installed and configured nut package. All i want now is to power off ups. If i run upsmon -c fsd as root - everything goes fine, system and ups gracefully shutting down. If i unplug power cable from an ups, then system is down, but ups still on load. Any help would be appreciated. Debian Lenny x86 ups.conf [ippon] driver = megatec port = /dev/ttyS0

On 5/11/19 3:41 AM, Hadley Wickham wrote: > For what it's worth, I don't think this strategy can work in general, > because a class might have attributes that depend on its data/contents > (e.g. https://vctrs.r-lib.org/articles/s3-vector.html#cached-sum). I > don't think these are particularly common in practice, but it's > dangerous to assume that you can restore a

Here is the output root at nutpi:/etc/nut# ps -elf | grep -E '[n]ut|ups[dms]' 4 S avahi 246 1 0 80 0 - 1472 poll_s Jan26 ? 00:00:31 avahi-daemon: running [nutpi.local] 1 S nut 451 1 0 80 0 - 678 poll_s Jan26 ? 00:03:41 /lib/nut/upscode2 -a deltec-PRA1500 1 S nut 454 1 0 80 0 - 1173 poll_s Jan26 ? 00:00:28 /lib/nut/upsd 1