similar to: Permissions error

On 6/10/24 19:46, Charles Lepple wrote: > On Jun 10, 2024, at 7:22?PM, Jack McGee wrote: >> mythuser at amethi:~$ upsdrvctl start >> Network UPS Tools - UPS driver controller 2.7.4 >> Can't open /etc/nut/ups.conf: Can't open /etc/nut/ups.conf: Permission denied > If you are sure the driver is not running (unclear from "eliminating the no connection error";

On 6/11/24 18:20, Jack McGee wrote: > > > > I added the user that normally logons onto that machine to the nut > group.? Different error now: > > > mythuser at amethi:~$ upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.4 > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication driver 0.33 > kill: Operation not permitted >

On Jun 10, 2024, at 7:22?PM, Jack McGee wrote: > > mythuser at amethi:~$ upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.4 > Can't open /etc/nut/ups.conf: Can't open /etc/nut/ups.conf: Permission denied If you are sure the driver is not running (unclear from "eliminating the no connection error"; instead check for the absence of the usbhid-ups

On 12/03/2016 10:35 AM, Charles Lepple wrote: > On Dec 3, 2016, at 11:16 AM, Jack McGee <jack at greendesk.net> wrote: >> Dec 3 08:38:16 amethi upsd[18234]: not listening on ::1 port 3493 >> Dec 3 08:38:16 amethi upsd[18234]: listening on 127.0.0.1 port 3493 >> Dec 3 08:38:16 amethi upsd[18234]: no listening interface available > I can't say I fully understand

On 12/03/2016 08:03 AM, Charles Lepple wrote: > On Dec 2, 2016, at 10:23 PM, Jack McGee <jack at greendesk.net> wrote: >> This is new install on Ubuntu 16.04, using packages from Synaptic, >> Network UPS Tools upsd 2.7.2 >> >> I am getting these messages in the terminal: >> Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): >>

On 12/03/2016 10:08 AM, Charles Lepple wrote: >> On Dec 3, 2016, at 11:01 AM, Jack McGee <jack at greendesk.net> wrote: >> >> I did restart those services, no change. >> > $ ps auxww|grep [/]nut > root 13074 0.0 0.0 37844 2628 ? Ss 08:42 0:00 /lib/nut/upsmon > nut 13076 0.0 0.0 45632 5148 ? S 08:42 0:00 /lib/nut/upsmon

On 12/10/2016 07:42 AM, Charles Lepple wrote: >> On Dec 9, 2016, at 10:40 PM, Jack McGee wrote: >> >> ? nut-server.service - LSB: Network UPS Tools initscript >> Loaded: loaded (/etc/init.d/nut-server; bad; vendor preset: enabled) >> Active: active (running) since Fri 2016-12-09 13:48:34 CST; 7h ago >> Docs: man:systemd-sysv-generator(8) >>

On 12/03/2016 09:36 AM, Charles Lepple wrote: >> On Dec 3, 2016, at 9:44 AM, Jack McGee <jack at greendesk.net> wrote: >> >> But doesn't this still indicate an error: >> >> mythuser at amethi:/etc/nut$ upscmd -l CyberPower1 >> Error: Connection failure: Connection refused > Correct - "upsc", "upscmd" and "upsrw" need to

This is new install on Ubuntu 16.04, using packages from Synaptic, *Network UPS Tools upsd 2.7.2 I am getting these messages in the terminal: Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): UPS CyberUPS1 at localhost is unavailable I am still unclear on where to set when nut shutdowns system. I see nut-client and nut server are automatically starting from SystemD.

> On Dec 3, 2016, at 12:31 PM, Jack McGee <jack at greendesk.net> wrote: >> so this is progress. Thanks! Anything else to check to know it is working as it should? http://networkupstools.org/docs/user-manual.chunked/ar01s06.html#Testing_shutdowns The "FSD" test is more for the NUT logic, which isn't too complicated with only one UPS and one server. If you want to

I rebooted machine and nut cannot connect to the UPS. mythuser at amethi:/etc$ sudo /lib/nut/usbhid-ups -DD -a CyberUPS1 Network UPS Tools - Generic HID driver 0.42 (2.7.4.1) USB communication driver (libusb 1.0) 0.02 0.000000 debug level is '2' 0.000499 upsdrv_initups... 0.005722 Checking device (8087/8000) 0.005753 Failed to open device, skipping. (Access

On 12/08/2016 09:38 PM, Charles Lepple wrote: > On Dec 8, 2016, at 7:56 PM, Jack McGee <jack at greendesk.net> wrote: >> I rebooted machine and nut cannot connect to the UPS. > Any messages from the kernel regarding USB HID drivers? (Check dmesg and/or journalctl.) dmesg: [ 1.658554] usb 3-5: new full-speed USB device number 4 using xhci_hcd [ 1.787602] usb 3-5: New USB

On 12/03/2016 10:55 AM, Jack McGee wrote: > On 12/03/2016 10:35 AM, Charles Lepple wrote: >> On Dec 3, 2016, at 11:16 AM, Jack McGee <jack at greendesk.net> wrote: >>> Dec 3 08:38:16 amethi upsd[18234]: not listening on ::1 port 3493 >>> Dec 3 08:38:16 amethi upsd[18234]: listening on 127.0.0.1 port 3493 >>> Dec 3 08:38:16 amethi upsd[18234]: no

On 12/10/2016 08:10 AM, Jack McGee wrote: > e, the path of least resistance would be to listen on 0.0.0.0 and use > a firewall rule to limit connections to that subnet. > > > sorry, after reboot I started seeing this error in terminal: > > Broadcast message from nut at amethi (somewhere) (Sat Dec 10 08:05:01 2016): > > UPS CyberUPS1 at localhost is unavailable > >

On 12/03/2016 11:46 AM, Charles Lepple wrote: > > If you don't mind sending the full output of "upsc" and "upsrw", we can update the DDL page (it only has "upsc" output for an older version of NUT). This UPS provides some sort of serial number (doesn't match the label) in the device.model (and mirrored at ups.model) variables, so if you want to mask off

On Dec 2, 2016, at 10:23 PM, Jack McGee <jack at greendesk.net> wrote: > > This is new install on Ubuntu 16.04, using packages from Synaptic, > Network UPS Tools upsd 2.7.2 > > I am getting these messages in the terminal: > Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): >

> On Dec 3, 2016, at 9:44 AM, Jack McGee <jack at greendesk.net> wrote: > > But doesn't this still indicate an error: > > mythuser at amethi:/etc/nut$ upscmd -l CyberPower1 > Error: Connection failure: Connection refused Correct - "upsc", "upscmd" and "upsrw" need to connect to "upsd", and "upsd" talks to the driver.

> On Dec 9, 2016, at 10:40 PM, Jack McGee wrote: > > ? nut-server.service - LSB: Network UPS Tools initscript > Loaded: loaded (/etc/init.d/nut-server; bad; vendor preset: enabled) > Active: active (running) since Fri 2016-12-09 13:48:34 CST; 7h ago > Docs: man:systemd-sysv-generator(8) > Process: 1886 ExecStart=/etc/init.d/nut-server start (code=exited,

On Dec 3, 2016, at 11:16 AM, Jack McGee <jack at greendesk.net> wrote: > > Dec 3 08:38:16 amethi upsd[18234]: not listening on ::1 port 3493 > Dec 3 08:38:16 amethi upsd[18234]: listening on 127.0.0.1 port 3493 > Dec 3 08:38:16 amethi upsd[18234]: no listening interface available I can't say I fully understand the logic behind the IPv6 code, but the first line indicates

Hello, I was thinking about what could be going wrong here, and a few ideas pop up: 1) If you installed NUT from packaging, there should have been no need to add OS groups/users manually. There is a valid use-case for running different daemons under different accounts, as long as they talk over network and access same files or UNIX sockets at best by sharing a group for that, but it does need