search for: amethi

Displaying 20 results from an estimated 20 matches for "amethi".

Did you mean: amet
2016 Dec 10
2
Problem installing NUT on 16.04
...go >> Docs: man:systemd-sysv-generator(8) >> Process: 1886 ExecStart=/etc/init.d/nut-server start (code=exited, status=0/SUCCESS) >> CGroup: /system.slice/nut-server.service >> ??2082 /lib/nut/usbhid-ups -a CyberUPS1 >> >> Dec 09 13:48:33 amethi systemd[1]: Starting LSB: Network UPS Tools initscript... >> Dec 09 13:48:33 amethi nut-server[1886]: * Starting NUT - power devices information server and drivers >> Dec 09 13:48:34 amethi usbhid-ups[2082]: Startup successful >> Dec 09 13:48:34 amethi upsd[2083]: not listening o...
2016 Dec 10
2
Problem installing NUT on 16.04
...vents driver (C) Jiri Kosina [ 1.792323] usbcore: registered new interface driver usbhid [ 1.792324] usbhid: USB HID core driver [ 1.796791] hid-generic 0003:0764:0501.0001: hiddev0,hidraw0: USB HID v1.10 Device [CPS CP1500PFCLCD] on usb-0000:00:14.0-5/input0 journalctl: Dec 09 21:28:49 amethi upsmon[2359]: UPS [CyberUPS1 at localhost]: connect failed: Connection failure: Connection refused Now, I found out that if I do service nut-server stop service nut-server start It works. But this is how it is before those commands: ? nut-server.service - LSB: Network UPS Tools initscript...
2016 Dec 03
2
Problem installing NUT on 16.04
.... ps auxww|grep [/]nut nut 19724 0.0 0.0 27932 516 ? Ss 08:41 0:00 /lib/nut/usbhid-ups -a CyberUPS1 root 20308 0.0 0.0 37844 2632 ? Ss 08:41 0:00 /lib/nut/upsmon nut 20309 0.0 0.0 45632 4884 ? S 08:41 0:00 /lib/nut/upsmon mythuser at amethi:/etc/nut$ grep upsd /var/log/syslog Dec 3 08:38:16 amethi nut-server[18216]: No upsd found running; none killed. 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...
2016 Dec 10
0
Problem installing NUT on 16.04
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 > > > I had a similar issue I think when Ubuntu moved to SystemD with Mythtv > not waiting to start until network was up and then erroring. I will > see if I can recall what I did to fix th...
2016 Dec 03
2
Problem installing NUT on 16.04
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 connect to "upsd", and "upsd" talks to the driver. Looks like you got the driver working before, so that confi...
2016 Dec 03
3
Problem installing NUT on 16.04
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 the logic behind the IPv6 code, but the first line indicate...
2016 Dec 09
2
Problem installing NUT on 16.04
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 de...
2024 Jun 10
3
Permissions error
...standalone nut installation on Ubuntu 22.04.? UPS is a CP1500PFCLCD.? I have gotten as far as eliminating the no connection error that I was being broadcast.? I have the web view viewable at http://192.168.1.105/cgi-bin/nut/upsstats.cgi The problem I have I believe is permissions. 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 I ran chown root:nut upsmon.conf chmod 0640 /etc/nut/upsmon.conf mythuser at amethi:~$ sudo cat /etc/nut/upsd.users [monuser] ? password = X...
2016 Dec 10
0
Problem installing NUT on 16.04
...16-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, status=0/SUCCESS) > CGroup: /system.slice/nut-server.service > ??2082 /lib/nut/usbhid-ups -a CyberUPS1 > > Dec 09 13:48:33 amethi systemd[1]: Starting LSB: Network UPS Tools initscript... > Dec 09 13:48:33 amethi nut-server[1886]: * Starting NUT - power devices information server and drivers > Dec 09 13:48:34 amethi usbhid-ups[2082]: Startup successful > Dec 09 13:48:34 amethi upsd[2083]: not listening on 192.168.0....
2016 Dec 03
0
Problem installing NUT on 16.04
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 listening interface available >> I can't say I fully understand the logic behind the IPv6 code, but >> t...
2024 Jun 11
2
Permissions error
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...
2016 Dec 03
3
Problem installing NUT on 16.04
...: > 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): >> >> UPS CyberUPS1 at localhost is unavailable >> >> I am still unclear on where to set when nut shutdowns system. > The basic configuration is that u...
2024 Jun 11
1
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"; instead check for...
2024 Jun 11
1
Permissions 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 > writepid: fopen /run/nut/usbhid-ups-cyberpowerAmethi.pid: Permission > denied > Using su...
2016 Dec 03
0
Problem installing NUT on 16.04
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 a problem...
2016 Dec 03
2
Problem installing NUT on 16.04
...vent outside systems from accessing NUT). More complicated access control situations (only allow a few hosts from a subnet, for instance) can be handled with TCP-wrappers (/etc/hosts.allow and /etc/hosts.deny) or with kernel firewall rules. > > Maybe still a problem: > > mythuser at amethi:/etc/nut$ sudo upsc CyberUPS1 at localhost ups.status > [sudo] password for mythuser: > Init SSL without certificate database > OL > > But if I read this > https://askubuntu.com/questions/468632/nut-ups-and-ssl-certificates#565740 > correctly, it is just a warning? > But sh...
2016 Dec 03
2
Problem installing NUT on 16.04
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. I had problem initially starting: * *mythuser at amethi:/etc/nut$ sudo upsdrvc...
2016 Dec 03
0
Problem installing NUT on 16.04
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): > > UPS CyberUPS1 at localhost is unavailable > > I am still unclear on where to set when nut shutdowns system. The basic configuration is that upsmon will sh...
2016 Dec 03
0
Problem installing NUT on 16.04
...s 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 a few digits from the end, that's fine. (CyberPower seems to have swapped the model name and serial number strings in the USB descriptor.) mythuser at amethi:/etc/nut$ upsc CyberUPS1 at 192.168.0.105 Init SSL without certificate database battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 3840 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 24.0 battery.voltage.nominal: 24 device.mf...
2016 Dec 03
0
Problem installing NUT on 16.04
> 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. Looks like you got the driver working before, so that configuration...