Cyberpower UPS Not Working Properly On Linux

Message
Author
PlatinumArts
Posts: 55
Joined: Wed Mar 07, 2018 12:08 pm

Cyberpower UPS Not Working Properly On Linux

#1 Post by PlatinumArts »

Hi! I have a Cyberpower CP685AVR and it is not working properly on Linux.
https://www.cyberpowersystems.com/produ ... /cp685avr/

If I am remembering correctly when I switched over to Windows recently it worked when there was a short power outage. Also if I shutdown the computer and pull the plug it still works properly (monitor and motherboard lights still on).

However when the computer is booted and there have been outages the UPS has not properly kicked in and kept the computer on.

I wonder if it would be better to even just remove the USB cable for the UPS. And I wonder, maybe systemd is required?

Here is some info from the terminal:

NOTE the Line Interaction None in the log, status. That's interesting and I couldn't find anything about it in the manual. Also it has said "failed" and rarely "passed" when I've tested in the past. I usually don't run a test because sometimes it has shut the computer off.

sudo pwrstat -status

Code: Select all

The UPS information shows as following:

	Properties:
		Model Name................... CP685AVR-G
		Rating Voltage............... 120 V
		Rating Power................. 390 Watt

	Current UPS status:
		State........................ Normal
		Power Supply by.............. Utility Power
		Utility Voltage.............. 124 V
		Output Voltage............... 124 V
		Battery Capacity............. 100 %
		Remaining Runtime............ 19 min.
		Load......................... 144 Watt(37 %)
		Line Interaction............. None
		Test Result.................. Low Battert at 2024/08/02 16:10:46
		Last Power Event............. Blackout at 2024/05/10 08:57:54
sudo pwrstat -config

Code: Select all

Alarm .............................................. On
Hibernate .......................................... Off
Cloud .............................................. Off

Action for Power Failure:

	Delay time since Power failure ............. 60 sec.
	Run script command ......................... On
	Path of script command ..................... /etc/pwrstatd-powerfail.sh
	Duration of command running ................ 0 sec.
	Enable shutdown system ..................... On

Action for Battery Low:

	Remaining runtime threshold ................ 300 sec.
	Battery capacity threshold ................. 35 %.
	Run script command ......................... On
	Path of command ............................ /etc/pwrstatd-lowbatt.sh
	Duration of command running ................ 0 sec.
	Enable shutdown system ..................... On
Quick System Info for good measure:

Code: Select all

System:
  Kernel: 6.1.0-23-amd64 [6.1.99-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-23-amd64 root=UUID=<filter> ro quiet
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.3_x64 Libretto July 31  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop System: Hewlett-Packard product: HP Z400 Workstation v: N/A
    serial: <superuser required> Chassis: type: 6 serial: <superuser required>
  Mobo: Hewlett-Packard model: 0B4Ch v: D serial: <superuser required> BIOS: Hewlett-Packard
    v: 786G3 v03.61 date: 03/05/2018
CPU:
  Info: model: Intel Xeon W3565 bits: 64 type: MCP arch: Nehalem level: v2 built: 2008-10
    process: Intel 45nm family: 6 model-id: 0x1A (26) stepping: 5 microcode: 0x1D
  Topology: cpus: 1x cores: 4 smt: disabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
    L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 2206 high: 2787 min/max: 1596/3193 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1937 2: 2064 3: 2036 4: 2787 bogomips: 25597
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; RSB filling; PBRSB-eIBRS:
    Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GF106GL [Quadro 2000] vendor: Hewlett-Packard driver: nouveau v: kernel
    non-free: series: 390.xx+ status: legacy-active (EOL~late 2022) arch: Fermi code: GF1xx
    process: 40/28nm built: 2010-16 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports: active: DVI-I-1
    empty: DP-1,DP-2 bus-ID: 0f:00.0 chip-ID: 10de:0dd8 class-ID: 0300 temp: 67.0 C
  Device-2: EMEET HD Webcam C950 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 7-2:3
    chip-ID: 328f:0073 class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: xfwm v: 4.18.0
    driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0.0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: DVI-I-1 model: Asus VW246 serial: <filter> built: 2011 res: 1920x1080 hz: 60 dpi: 92
    gamma: 1.2 size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  API: OpenGL v: 4.3 Mesa 22.3.6 renderer: NVC3 direct-render: Yes
Audio:
  Device-1: Intel 82801JI HD Audio vendor: Hewlett-Packard driver: snd_hda_intel bus-ID: 7-2:3
    v: kernel chip-ID: 328f:0073 bus-ID: 00:1b.0 chip-ID: 8086:3a3e class-ID: 0102 serial: <filter>
    class-ID: 0403
  Device-2: NVIDIA GF106 High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 bus-ID: 0f:00.1 chip-ID: 10de:0be9
    class-ID: 0403
  Device-3: EMEET HD Webcam C950 type: USB driver: snd-usb-audio,uvcvideo
  Device-4: Realtek Audio USB type: USB driver: snd-usb-audio bus-ID: 7-4:4 chip-ID: 0bda:4938
    class-ID: 0102 serial: <filter>
  API: ALSA v: k6.1.0-23-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Broadcom NetXtreme BCM5764M Gigabit Ethernet PCIe vendor: Hewlett-Packard driver: tg3
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 01:00.0 chip-ID: 14e4:1684
    class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: TP-Link Archer T2U PLUS [RTL8821AU] type: USB driver: rtl8821au bus-ID: 1-5:2
    chip-ID: 2357:0120 class-ID: 0000 serial: <filter>
  IF: wlan0 state: up mac: <filter>
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: d0c0 bus-ID: 00:1f.2
    chip-ID: 8086:2822 rev: class-ID: 0104
Drives:
  Local Storage: total: 931.51 GiB used: 109.05 GiB (11.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 3B6Q scheme: MBR
Partition:
  ID-1: / raw-size: 931.51 GiB size: 915.81 GiB (98.31%) used: 109.05 GiB (11.9%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 3 GiB used: 2.2 MiB (0.1%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 49.0 C mobo: N/A gpu: nouveau temp: 67.0 C
  Fan Speeds (RPM): N/A gpu: nouveau fan: 3330
Repos:
  Packages: pm: dpkg pkgs: 2878 libs: 1630 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/librewolf.list
    1: deb [arch=amd64] http://deb.librewolf.net/ bookworm main
  Active apt repos in: /etc/apt/sources.list.d/megasync.list
    1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_12/ ./
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list
    1: deb https://download.onlyoffice.com/repo/debian/ squeeze main
Info:
  Processes: 243 Uptime: 12m wakeups: 1 Memory: 7.74 GiB used: 2.82 GiB (36.4%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Thank you so much for your time and help!
- Mike

User avatar
CharlesV
Global Moderator
Posts: 7078
Joined: Sun Jul 07, 2019 5:11 pm

Re: Cyberpower UPS Not Working Properly On Linux

#2 Post by CharlesV »

Interesting post, I just redid NUT on my machines and worked them over through testing etc..

Check to make sure you have your two files:
/etc/pwrstatd-powerfail.sh
/etc/pwrstatd-lowbatt.sh

verify they have permission to run, and that their contents are doing what you want and are correct.
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

User avatar
artytux
Posts: 398
Joined: Wed Apr 26, 2023 3:58 am

Re: Cyberpower UPS Not Working Properly On Linux

#3 Post by artytux »

@PlatinumArts

Just checked my

Code: Select all

sudo pwrstat -status
and

Code: Select all

sudo pwrstat -config
much the same no difference in there.

Have you looked at the logs in

Daemon Event Log
The daemon will record the power event in pwrstatd.log log file, which can be found on /var/log directory.
could have a clue

Also you do not need to use systemd, My desktop is MXLinux 23.3 KDE with Liquorix kernel 6.9.12-2 and no systemd.

On yours
Also if I shutdown the computer and pull the plug it still works properly (monitor and motherboard lights still on).
are you leaving this (monitor and motherboard lights still on) for a good while 15 minutes and not just for one or two minutes.

option
Something to try
with computer turned off (monitor and motherboard lights still on) don't plug UPS into mains power leave it on battery feed try to startup your computer and the results is, if it does not start read the last line here.

Since the load on battery is way cool on 35 to 40 % don't overload upto 70 to 75 % you have done everything correct.

I would contact Cyberpower and find the nearest service centre in you rarea so 'they' will check the battery condition could be the fault.
" Outside the square , inside the cube "

PlatinumArts
Posts: 55
Joined: Wed Mar 07, 2018 12:08 pm

Re: Cyberpower UPS Not Working Properly On Linux

#4 Post by PlatinumArts »

Wow thank you @artytux for checking your settings with mine! And so you had "Line Interaction None" too?

I'll post the daemon event log below. And also try booting up from the battery, I love that idea!

When I was testing by pulling the plug with the monitor off I did only wait a minute or so but it was functioning properly so I didn't think I needed to wait longer.

Yesterday we did have a quick power failure and the computer stayed on! I wasn't at the computer when it happened and the power failure wasn't long, but long enough that I had to reset the clock on the stove which I think is generally enough for the computer to restart. So it seems like it might have worked! I didn't hear the alarm go off but maybe it wasn't long enough of a power failure.

@CharlesV I do have those files but sadly they are pretty boring and are related to sending out e-mails of the logs. Maybe that'd be good to set up though. I did find a config in there. It seemed to match the output of the config I posted.

Daemon event log:

Code: Select all

2023/09/25 16:06:33 PM	Daemon startups.
2023/09/25 16:06:33 PM	Communication is established.
2023/09/25 23:03:39 PM	Daemon stops its service.
2023/09/25 23:04:32 PM	Daemon startups.
2023/09/25 23:04:32 PM	Communication is established.
2023/09/27 11:22:48 AM	Daemon stops its service.
2023/09/27 11:23:55 AM	Daemon startups.
2023/09/27 11:23:55 AM	Communication is established.
2023/09/29 03:57:01 AM	Daemon stops its service.
2023/09/29 03:58:07 AM	Daemon startups.
2023/09/29 03:58:07 AM	Communication is established.
2023/10/01 07:22:34 AM	Daemon stops its service.
2023/10/01 07:23:47 AM	Daemon startups.
2023/10/01 07:23:47 AM	Communication is established.
2023/10/02 22:47:02 PM	Daemon stops its service.
2023/10/02 22:48:08 PM	Daemon startups.
2023/10/02 22:48:08 PM	Communication is established.
2023/10/10 10:40:58 AM	Daemon stops its service.
2023/10/10 10:42:08 AM	Daemon startups.
2023/10/10 10:42:09 AM	Communication is established.
2023/10/11 11:25:09 AM	Communication is lost.
2023/10/11 11:25:13 AM	Communication is established.
2023/10/12 00:32:57 AM	Communication is lost.
2023/10/12 00:33:01 AM	Communication is established.
2023/10/12 11:59:09 AM	Utility failed.
2023/10/12 11:59:11 AM	Communication is lost.
2023/10/12 11:59:15 AM	Communication is established.
2023/10/12 12:00:09 PM	The settings of system shutdown sustain time is 10 min., 0 sec. which is out of this UPS specification. The UPS will not be turned off.
2023/10/12 12:00:09 PM	Begin to shutdown PC immediately!
2023/10/12 12:00:09 PM	Daemon stops its service.
2023/10/12 15:15:54 PM	Daemon startups.
2023/10/12 15:15:54 PM	Communication is established.
2023/10/15 10:29:49 AM	Daemon stops its service.
2023/10/15 20:12:43 PM	Daemon startups.
2023/10/15 20:12:43 PM	Communication is established.
2023/10/16 10:53:11 AM	Communication is lost.
2023/10/16 10:53:14 AM	Communication is established.
2023/10/16 10:53:16 AM	Communication is lost.
2023/10/16 10:53:19 AM	Communication is established.
2023/10/16 10:53:20 AM	Communication is lost.
2023/10/16 10:53:23 AM	Communication is established.
2023/10/16 10:53:35 AM	Communication is lost.
2023/10/16 10:53:39 AM	Communication is established.
2023/10/19 22:18:11 PM	Daemon stops its service.
2023/10/19 22:19:15 PM	Daemon startups.
2023/10/19 22:19:15 PM	Communication is established.
2023/10/23 14:56:52 PM	Daemon stops its service.
2023/10/23 14:57:59 PM	Daemon startups.
2023/10/23 14:57:59 PM	Communication is established.
2023/10/29 00:10:22 AM	Daemon stops its service.
2023/10/29 04:14:48 AM	Daemon startups.
2023/10/29 04:14:49 AM	Communication is established.
2023/10/29 08:47:52 AM	Daemon stops its service.
2023/10/29 20:28:33 PM	Daemon startups.
2023/10/29 20:28:33 PM	Communication is established.
2023/10/29 22:52:46 PM	Daemon stops its service.
2023/10/30 05:33:43 AM	Daemon startups.
2023/10/30 05:33:43 AM	Communication is established.
2023/10/30 11:03:53 AM	Daemon stops its service.
2023/10/30 11:04:56 AM	Daemon startups.
2023/10/30 11:04:56 AM	Communication is established.
2023/10/31 20:54:15 PM	Daemon stops its service.
2023/10/31 20:55:16 PM	Daemon startups.
2023/10/31 20:55:16 PM	Communication is established.
2023/11/04 03:45:03 AM	Daemon stops its service.
2023/11/04 03:46:05 AM	Daemon startups.
2023/11/04 03:46:05 AM	Communication is established.
2023/11/04 04:00:04 AM	Daemon stops its service.
2023/11/04 04:01:02 AM	Daemon startups.
2023/11/04 04:01:02 AM	Communication is established.
2023/11/06 02:41:08 AM	Daemon stops its service.
2023/11/06 02:42:15 AM	Daemon startups.
2023/11/06 02:42:15 AM	Communication is established.
2023/11/06 03:08:35 AM	Daemon stops its service.
2023/11/06 03:12:52 AM	Daemon startups.
2023/11/06 03:12:53 AM	Communication is established.
2023/11/06 03:16:53 AM	Daemon stops its service.
2023/11/06 03:19:43 AM	Daemon startups.
2023/11/06 03:19:44 AM	Communication is established.
2023/11/06 03:29:49 AM	Daemon stops its service.
2023/11/06 03:30:57 AM	Daemon startups.
2023/11/06 03:30:57 AM	Communication is established.
2023/11/06 03:32:02 AM	Daemon stops its service.
2023/11/06 03:33:12 AM	Daemon startups.
2023/11/06 03:33:12 AM	Communication is established.
2023/11/07 02:18:09 AM	Communication is lost.
2023/11/07 02:18:12 AM	Communication is established.
2023/11/10 07:52:38 AM	Communication is lost.
2023/11/10 07:52:42 AM	Communication is established.
2023/11/14 14:14:45 PM	Daemon stops its service.
2023/11/14 14:15:53 PM	Daemon startups.
2023/11/14 14:15:54 PM	Communication is established.
2023/11/16 23:22:14 PM	Daemon stops its service.
2023/11/20 04:25:55 AM	Daemon startups.
2023/11/20 04:25:55 AM	Communication is established.
2023/11/22 01:04:29 AM	Daemon stops its service.
2023/11/22 03:47:34 AM	Daemon startups.
2023/11/22 03:47:34 AM	Communication is established.
2023/11/24 14:46:56 PM	Daemon startups.
2023/11/24 14:46:56 PM	Communication is established.
2023/11/26 20:48:02 PM	Daemon stops its service.
2023/11/26 20:49:07 PM	Daemon startups.
2023/11/26 20:49:07 PM	Communication is established.
2023/11/27 20:02:27 PM	Daemon stops its service.
2023/11/27 20:03:41 PM	Daemon startups.
2023/11/27 20:03:41 PM	Communication is established.
2023/11/29 17:54:44 PM	Daemon stops its service.
2023/11/29 17:55:54 PM	Daemon startups.
2023/11/29 17:55:54 PM	Communication is established.
2023/11/30 01:03:43 AM	Daemon stops its service.
2023/11/30 05:26:20 AM	Daemon startups.
2023/11/30 05:26:21 AM	Communication is established.
2023/11/30 21:50:07 PM	Daemon startups.
2023/11/30 21:50:08 PM	Communication is established.
2023/11/30 22:17:45 PM	Daemon stops its service.
2023/11/30 22:18:44 PM	Daemon startups.
2023/11/30 22:18:44 PM	Communication is established.
2023/12/02 22:36:39 PM	Daemon stops its service.
2023/12/04 05:28:11 AM	Daemon startups.
2023/12/04 05:28:12 AM	Communication is established.
2023/12/06 05:32:39 AM	Daemon startups.
2023/12/06 05:32:39 AM	Communication is established.
2023/12/08 06:48:07 AM	Daemon stops its service.
2023/12/08 06:49:17 AM	Daemon startups.
2023/12/08 06:49:17 AM	Communication is established.
2023/12/09 03:11:22 AM	Daemon startups.
2023/12/09 03:11:22 AM	Communication is established.
2023/12/09 03:40:12 AM	Daemon stops its service.
2023/12/09 05:22:58 AM	Daemon startups.
2023/12/09 05:22:58 AM	Communication is established.
2023/12/14 06:59:21 AM	Daemon stops its service.
2023/12/14 07:00:30 AM	Daemon startups.
2023/12/14 07:00:31 AM	Communication is established.
2023/12/14 07:07:09 AM	Daemon stops its service.
2023/12/14 08:21:49 AM	Daemon startups.
2023/12/14 08:21:50 AM	Communication is established.
2023/12/14 08:33:27 AM	Daemon startups.
2023/12/14 08:33:27 AM	Communication is established.
2023/12/14 08:37:43 AM	Daemon stops its service.
2023/12/14 11:27:30 AM	Daemon startups.
2023/12/14 11:27:30 AM	Communication is established.
2023/12/14 11:37:46 AM	Daemon startups.
2023/12/14 11:37:46 AM	Communication is established.
2023/12/14 11:42:21 AM	Daemon stops its service.
2023/12/14 11:45:36 AM	Daemon startups.
2023/12/14 11:45:36 AM	Communication is established.
2023/12/14 11:57:36 AM	Daemon stops its service.
2023/12/14 12:00:56 PM	Daemon startups.
2023/12/14 12:00:56 PM	Communication is established.
2023/12/14 12:08:41 PM	Daemon startups.
2023/12/14 12:08:41 PM	Communication is established.
2023/12/14 12:25:07 PM	Daemon stops its service.
2023/12/14 12:26:11 PM	Daemon startups.
2023/12/14 12:26:12 PM	Communication is established.
2023/12/14 12:32:02 PM	Daemon stops its service.
2023/12/14 12:34:21 PM	Daemon startups.
2023/12/14 12:34:21 PM	Communication is established.
2023/12/14 12:40:26 PM	Daemon startups.
2023/12/14 12:40:26 PM	Communication is established.
2023/12/18 05:55:53 AM	Daemon stops its service.
2023/12/18 05:57:16 AM	Daemon startups.
2023/12/18 05:57:17 AM	Communication is established.
2023/12/24 05:58:37 AM	Daemon stops its service.
2023/12/24 05:59:47 AM	Daemon startups.
2023/12/24 05:59:47 AM	Communication is established.
2024/01/05 13:35:04 PM	Daemon stops its service.
2024/01/05 13:36:17 PM	Daemon startups.
2024/01/05 13:36:17 PM	Communication is established.
2024/01/08 13:54:02 PM	Communication is lost.
2024/01/08 13:54:06 PM	Communication is established.
2024/01/10 10:28:06 AM	Communication is lost.
2024/01/10 10:28:10 AM	Communication is established.
2024/01/10 10:28:23 AM	Communication is lost.
2024/01/10 10:28:27 AM	Communication is established.
2024/01/19 13:15:30 PM	Daemon stops its service.
2024/01/19 13:16:31 PM	Daemon startups.
2024/01/19 13:16:31 PM	Communication is established.
2024/01/28 17:09:19 PM	Communication is lost.
2024/01/28 17:09:22 PM	Communication is established.
2024/02/03 06:41:32 AM	Communication is lost.
2024/02/03 06:41:36 AM	Communication is established.
2024/02/05 23:27:05 PM	Daemon stops its service.
2024/02/05 23:28:21 PM	Daemon startups.
2024/02/05 23:28:22 PM	Communication is established.
2024/02/08 09:15:17 AM	Daemon stops its service.
2024/02/08 09:16:28 AM	Daemon startups.
2024/02/08 09:16:29 AM	Communication is established.
2024/02/10 07:26:19 AM	Communication is lost.
2024/02/10 07:26:23 AM	The H2C device can't be used, because the linux system does not support libusb or libusb version is too old.
2024/02/10 07:26:33 AM	Communication is established.
2024/02/10 14:46:27 PM	Daemon stops its service.
2024/02/10 14:47:36 PM	Daemon startups.
2024/02/10 14:47:36 PM	Communication is established.
2024/02/12 18:19:13 PM	Daemon stops its service.
2024/02/12 18:20:25 PM	Daemon startups.
2024/02/12 18:20:25 PM	Communication is established.
2024/02/12 19:00:11 PM	Daemon startups.
2024/02/12 19:00:11 PM	Communication is established.
2024/02/13 14:48:57 PM	Daemon startups.
2024/02/13 14:48:57 PM	Communication is established.
2024/02/16 00:59:49 AM	Daemon stops its service.
2024/02/16 01:00:58 AM	Daemon startups.
2024/02/16 01:00:58 AM	Communication is established.
2024/02/18 08:20:18 AM	Daemon startups.
2024/02/18 08:20:18 AM	Communication is established.
2024/02/18 08:25:34 AM	Daemon stops its service.
2024/02/18 08:26:28 AM	Daemon startups.
2024/02/18 08:26:29 AM	Communication is established.
2024/02/23 18:47:27 PM	Daemon stops its service.
2024/02/23 18:48:36 PM	Daemon startups.
2024/02/23 18:48:36 PM	Communication is established.
2024/03/03 15:49:24 PM	Communication is lost.
2024/03/03 15:49:28 PM	Communication is established.
2024/03/15 18:28:24 PM	Communication is lost.
2024/03/15 18:28:28 PM	Communication is established.
2024/03/15 20:13:22 PM	Communication is lost.
2024/03/15 20:13:26 PM	Communication is established.
2024/03/22 22:56:16 PM	Daemon stops its service.
2024/03/28 00:39:20 AM	Daemon startups.
2024/03/28 00:39:20 AM	Communication is established.
2024/04/02 05:39:32 AM	Communication is lost.
2024/04/02 05:39:35 AM	Communication is established.
2024/04/10 07:29:41 AM	Communication is lost.
2024/04/10 07:29:44 AM	Communication is established.
2024/04/14 13:33:56 PM	Daemon stops its service.
2024/04/14 13:34:59 PM	Daemon startups.
2024/04/14 13:34:59 PM	Communication is established.
2024/04/28 10:51:33 AM	Daemon stops its service.
2024/04/28 10:52:48 AM	Daemon startups.
2024/04/28 10:52:48 AM	Communication is established.
2024/04/30 19:23:07 PM	Communication is lost.
2024/04/30 19:23:10 PM	Communication is established.
2024/05/08 15:41:36 PM	Daemon stops its service.
2024/05/08 15:42:42 PM	Daemon startups.
2024/05/08 15:42:43 PM	Communication is established.
2024/05/10 08:56:41 AM	Communication is lost.
2024/05/10 08:56:44 AM	The H2C device can't be used, because the linux system does not support libusb or libusb version is too old.
2024/05/10 08:56:54 AM	Communication is established.
2024/05/10 08:56:58 AM	Utility failed.
2024/05/10 08:57:01 AM	Communication is lost.
2024/05/10 08:57:04 AM	Communication is established.
2024/05/10 08:57:53 AM	Utility failed.
2024/05/10 08:57:56 AM	Communication is lost.
2024/05/10 08:58:00 AM	Communication is established.
2024/05/10 08:58:00 AM	Communication is lost.
2024/05/10 08:58:04 AM	Communication is established.
2024/05/10 08:58:54 AM	The settings of system shutdown sustain time is 10 min., 0 sec. which is out of this UPS specification. The UPS will not be turned off.
2024/05/10 08:58:54 AM	Begin to shutdown PC immediately!
2024/05/10 08:58:54 AM	Daemon stops its service.
2024/05/10 10:04:21 AM	Daemon startups.
2024/05/10 10:04:21 AM	Communication is established.
2024/05/15 08:01:39 AM	Daemon stops its service.
2024/05/15 08:02:51 AM	Daemon startups.
2024/05/15 08:02:51 AM	Communication is established.
2024/05/17 22:29:55 PM	Daemon stops its service.
2024/05/17 22:31:04 PM	Daemon startups.
2024/05/17 22:31:04 PM	Communication is established.
2024/05/20 20:51:10 PM	Daemon stops its service.
2024/05/20 20:52:19 PM	Daemon startups.
2024/05/20 20:52:19 PM	Communication is established.
2024/05/25 08:08:22 AM	Daemon stops its service.
2024/05/25 08:09:31 AM	Daemon startups.
2024/05/25 08:09:31 AM	Communication is established.
2024/05/26 18:30:27 PM	Communication is lost.
2024/05/26 18:30:31 PM	Communication is established.
2024/05/27 20:48:15 PM	Daemon stops its service.
2024/05/27 20:49:19 PM	Daemon startups.
2024/05/27 20:49:19 PM	Communication is established.
2024/05/29 07:02:54 AM	Utility failed.
2024/05/29 07:02:57 AM	Communication is lost.
2024/05/29 07:03:01 AM	Communication is established.
2024/05/29 07:03:54 AM	The settings of system shutdown sustain time is 10 min., 0 sec. which is out of this UPS specification. The UPS will not be turned off.
2024/05/29 07:03:54 AM	Begin to shutdown PC immediately!
2024/05/29 07:03:54 AM	Daemon stops its service.
2024/05/29 08:02:15 AM	Daemon startups.
2024/05/29 08:02:15 AM	Communication is established.
2024/06/13 23:09:45 PM	Daemon stops its service.
2024/06/13 23:10:56 PM	Daemon startups.
2024/06/13 23:10:56 PM	Communication is established.
2024/06/14 15:55:32 PM	Daemon stops its service.
2024/06/14 15:56:30 PM	Daemon startups.
2024/06/14 15:56:31 PM	Communication is established.
2024/06/15 01:36:28 AM	Daemon stops its service.
2024/06/15 11:14:06 AM	Daemon startups.
2024/06/15 11:14:07 AM	Communication is established.
2024/06/19 14:48:57 PM	Daemon stops its service.
2024/06/19 14:50:05 PM	Daemon startups.
2024/06/19 14:50:05 PM	Communication is established.
2024/06/22 22:15:41 PM	Daemon stops its service.
2024/06/22 22:16:50 PM	Daemon startups.
2024/06/22 22:16:50 PM	Communication is established.
2024/06/25 14:25:42 PM	Communication is lost.
2024/06/25 14:25:45 PM	Communication is established.
2024/06/25 14:37:26 PM	Communication is lost.
2024/06/25 14:37:29 PM	Communication is established.
2024/06/25 14:37:30 PM	Communication is lost.
2024/06/25 14:37:34 PM	Communication is established.
2024/06/25 14:37:46 PM	Communication is lost.
2024/06/25 14:37:50 PM	Communication is established.
2024/06/28 15:32:59 PM	Daemon startups.
2024/06/28 15:32:59 PM	Communication is established.
2024/06/29 13:37:35 PM	Communication is lost.
2024/06/29 13:37:38 PM	Communication is established.
2024/06/30 04:39:38 AM	Communication is lost.
2024/06/30 04:39:41 AM	Communication is established.
2024/07/05 22:22:30 PM	Daemon stops its service.
2024/07/05 22:23:42 PM	Daemon startups.
2024/07/05 22:23:42 PM	Communication is established.
2024/07/08 18:04:54 PM	Daemon stops its service.
2024/07/08 18:05:51 PM	Daemon startups.
2024/07/08 18:05:51 PM	Communication is established.
2024/07/08 19:10:26 PM	Daemon stops its service.
2024/07/09 13:46:45 PM	Daemon startups.
2024/07/09 13:46:45 PM	Communication is established.
2024/07/09 22:09:33 PM	Daemon stops its service.
2024/07/09 22:10:30 PM	Daemon startups.
2024/07/09 22:10:31 PM	Communication is established.
2024/07/09 22:18:59 PM	Daemon stops its service.
2024/07/26 01:03:05 AM	Daemon startups.
2024/07/26 01:03:05 AM	Communication is established.
2024/07/27 17:45:02 PM	Daemon stops its service.
2024/07/27 17:46:14 PM	Daemon startups.
2024/07/27 17:46:14 PM	Communication is established.
2024/07/27 20:35:23 PM	Daemon startups.
2024/07/27 20:35:23 PM	Communication is established.
2024/07/28 21:56:46 PM	Daemon stops its service.
2024/07/28 21:57:51 PM	Daemon startups.
2024/07/28 21:57:51 PM	Communication is established.
2024/07/29 14:22:55 PM	Daemon stops its service.
2024/07/29 14:23:54 PM	Daemon startups.
2024/07/29 14:23:54 PM	Communication is established.
2024/07/29 14:29:56 PM	Daemon stops its service.
2024/07/29 14:30:50 PM	Daemon startups.
2024/07/29 14:30:50 PM	Communication is established.
2024/07/29 14:55:27 PM	Daemon stops its service.
2024/07/29 14:56:21 PM	Daemon startups.
2024/07/29 14:56:21 PM	Communication is established.
2024/07/29 14:57:56 PM	Daemon stops its service.
2024/07/29 15:26:16 PM	Daemon startups.
2024/07/29 15:26:16 PM	Communication is established.
2024/07/29 15:29:04 PM	Daemon stops its service.
2024/07/29 15:31:49 PM	Daemon startups.
2024/07/29 15:31:49 PM	Communication is established.
2024/07/29 15:47:20 PM	Daemon stops its service.
2024/07/29 15:48:15 PM	Daemon startups.
2024/07/29 15:48:15 PM	Communication is established.
2024/07/31 06:00:01 AM	Daemon startups.
2024/07/31 06:00:01 AM	Communication is established.
16:09:04 PM	Daemon startups.
2024/08/02 16:09:05 PM	Communication is established.
2024/08/02 16:10:15 PM	Communication is lost.
2024/08/02 16:10:18 PM	Communication is established.
2024/08/02 16:15:51 PM	Daemon stops its service.
2024/08/02 22:00:42 PM	Daemon startups.
2024/08/02 22:00:43 PM	Communication is established.
2024/08/05 16:24:08 PM	Daemon startups.
2024/08/05 16:24:08 PM	Communication is established.
2024/08/05 18:35:06 PM	Daemon stops its service.
2024/08/05 18:36:01 PM	Daemon startups.
2024/08/05 18:36:01 PM	Communication is established.
2024/08/05 18:38:32 PM	Daemon stops its service.
2024/08/05 18:39:27 PM	Daemon startups.
2024/08/05 18:39:27 PM	Communication is established.
2024/08/06 16:52:51 PM	Utility failed.
2024/08/06 16:52:54 PM	Utility restored.
Thank you all for your help!
- Mike

User avatar
artytux
Posts: 398
Joined: Wed Apr 26, 2023 3:58 am

Re: Cyberpower UPS Not Working Properly On Linux

#5 Post by artytux »

Hello @PlatinumArts
your settings with mine! And so you had "Line Interaction None" too?
yes.
When I was testing by pulling the plug with the monitor off I did only wait a minute or so but it was functioning properly so I didn't think I needed to wait longer.
The lights staying can thou not always have a lingering delay, why I don't , sometimes mine stay on for a bit longer than expected.
Yesterday we did have a quick power failure and the computer stayed on! I wasn't at the computer when it happened and the power failure wasn't long, but long enough that I had to reset the clock on the stove which I think is generally enough for the computer to restart. So it seems like it might have worked!
If in doubt check the last line in terminal result for

Code: Select all

sudo pwrstat -status
, take the guess out of any work in progress.
I didn't hear the alarm go off but maybe it wasn't long enough of a power failure.
What I've done is set-up a small lamp on different circuit so if the power goes out when I'm at the keyboard the light behind me switches off and that part of the room goes dark-ish and 'Oh yeah power is Out'
I could not get the alarm to work anyway don't need it to wake me up I see the light so it's all good.
I reckon you know this and writing this in for anyone else so
Don't overload that circuit is the most important 'thing' that should just be for the computer/moniters if you have any doubts about anything goto the Cyberpower FAQ page(s) https://www.cyberpower.com/au/en/knowledge/faq

Hope this helps
" Outside the square , inside the cube "

Post Reply

Return to “Hardware /Configuration”