Displaying 11 results from an estimated 11 matches for "dicair".
Did you mean:
dicaire
2024 Jul 29
2
Fedora 40 nut-server not starting at boot
On Mon, Jul 29, 2024 at 5:45?PM Tim Dawson <tadawson at tpcsvc.com> wrote:
> OK, looking at this on my RH8 test image . . .
>
> The first thing that I note, is that the *only* thing that needed to be
> set to "enabled" in systemctl (IE "systemctl enable ....") is the
> nut.target entry.
>
Tim, can you show output of systemctl list-unit-files| grep nut
2020 Nov 01
4
ups.test.result meaning
On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote:
> I'm going to guess that since your test runtime of 305 is very close to
> the low limit of 300, that's the warning. Not yet a fail, but very, very
> close.
>
I tried setting
override.battery.runtime.low = 60
in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to
report only
2020 Oct 31
0
ups.test.result meaning
I'm going to guess that since your test runtime of 305 is very close to the low limit of 300, that's the warning. Not yet a fail, but very, very close.
On October 31, 2020 11:41:39 AM CDT, Rick Dicaire <kritek at gmail.com> wrote:
>Hi folks, new to list...
>nut 2.7.2 on Ubuntu 16.04 with Cyberpowersystems CP1350PFCLCD.
>
>After performing upscmd cp1350 at localhost test.battery.start.quick the
>result was "Done and warning". I searched through syslog but could find...
2020 Nov 01
0
ups.test.result meaning
On Saturday 31 October 2020 20:13:48 Rick Dicaire wrote:
> On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote:
> > I'm going to guess that since your test runtime of 305 is very close
> > to the low limit of 300, that's the warning. Not yet a fail, but
> > very, very close.
>
> I tr...
2024 Jul 30
1
Fedora 40 nut-server not starting at boot
On Tue, Jul 30, 2024 at 7:10?AM Bill Gee <bgee at campercaver.net> wrote:
> I wonder if this will get Rick's system running??
>
Tim/Bill, I removed the nut pkg and deps, deleted the nut*.d dirs created
in /etc/systemd/system, then reinstalled nut.
I added the two network objects to Wants and After in system.target,
restored confs in /etc/ups, rebooted, and sure enough upsd and
2000 May 18
0
Failed copying and writing
...ritable = yes
admin users = ardy,root
path = /backup/ms-install
[printers]
comment = All Printers
path = /var/spool/lpd/lp
browseable = no
printable = yes
printer = smb
Any ideas on why this fails?
----------------------------------------------------
Richard Dicaire
Co-owner/Systems Administrator
K&R Information Technologies
http://matrix.linux-help.org/kr/
----------------------------------------------------
Brainbench Certified Master Linux Administrator
http://www.brainbench.com/transcript.jsp?pid=67584
-----------------...
2000 May 22
0
read_socket_data: recv failure for 4
...ritable = yes
admin users = ardy,root
path = /backup/ms-install
[printers]
comment = All Printers
path = /var/spool/lpd/lp
browseable = no
printable = yes
printer = smb
Any ideas on why this fails?
----------------------------------------------------
Richard Dicaire
Co-owner/Systems Administrator
K&R Information Technologies
http://matrix.linux-help.org/kr/
----------------------------------------------------
Brainbench Certified Master Linux Administrator
http://www.brainbench.com/transcript.jsp?pid=67584
-----------------...
2020 Nov 01
1
ups.test.result meaning
>
>
> > battery.voltage: 16.0
> At that voltage, 5 of the 12 cells are shorted
> > output.voltage: 138.0
> too high by about 15 volts
>
> Wow! That battery is beyond toasted, shoulda been replaced months ago.
> And the output voltage is a bit much if its truthfull.
>
Thanks for the response Gene!
I've ordered a replacement unit.
I'm not sure about the
2020 Oct 31
2
ups.test.result meaning
Hi folks, new to list...
nut 2.7.2 on Ubuntu 16.04 with Cyberpowersystems CP1350PFCLCD.
After performing upscmd cp1350 at localhost test.battery.start.quick the
result was "Done and warning". I searched through syslog but could find no
additional information.
What is the warning?
Battery charge was 100% before test was performed.
Here's the full output from upsc after test:
2024 Jul 27
1
Fedora 40 nut-server not starting at boot
Hi folks, I'm having an issue with getting nut-server to start at boot on a
freshly installed Fedora 40 desktop. Seems once the machine is up, I can
manually start with systemctl start nut-server and everythings fine.
dnf info nut
Last metadata expiration check: 2:08:11 ago on Sat 27 Jul 2024 03:48:13 PM
EDT.
Installed Packages
Name : nut
Version : 2.8.2
Release : 1.fc40
2024 Jul 30
0
Fedora 40 nut-server not starting at boot
On Mon, Jul 29, 2024 at 9:01?PM Tim Dawson <tadawson at tpcsvc.com> wrote:
> As I read this, the .target file is used to coordinate the startup of
> other units/services, and as such, is called by systemd when enabled, and
> subsequently starts that which is defined in the .target file.
>
> (And at least on my RH8 VM that I have been testing with, seems to work in
>