On Sunday 12 May 2019 06:27:45 pm Charles Lepple wrote:
> On May 12, 2019, at 5:56 PM, Gene Heskett wrote:
> > So I believe I'm in business if systemctl starts it on a reboot.
>
> Cool!
>
> > However I get this at the top of a upsc report:
> >
> > Init SSL without certificate database
> >
> > Whic
On May 12, 2019, at 5:56 PM, Gene Heskett wrote:
>
> So I believe I'm in business if systemctl starts it on a reboot.
Cool!
>
> However I get this at the top of a upsc report:
>
> Init SSL without certificate database
>
> Which I've not recalled seeing in wheezy.
> And the common certs are ins
On Sunday 12 May 2019 03:10:13 pm Charles Lepple wrote:
> On May 12, 2019, at 2:51 PM, Gene Heskett wrote:
> > On Sunday 12 May 2019 02:41:02 pm Charles Lepple wrote:
> >> /lib/nut/usbhid-ups -a myups -DD
> >
> > gene@coyote:~$ /lib/nut/usbhid-ups -a myups -DD
> > Network UPS Tools - Generic HID d
On May 12, 2019, at 2:51 PM, Gene Heskett wrote:
>
> On Sunday 12 May 2019 02:41:02 pm Charles Lepple wrote:
>
>> /lib/nut/usbhid-ups -a myups -DD
> gene@coyote:~$ /lib/nut/usbhid-ups -a myups -DD
> Network UPS Tools - Generic HID driver 0.41 (2.7.4)
> USB communication driver 0.33
> Can't open /
On Sunday 12 May 2019 02:41:02 pm Charles Lepple wrote:
> /lib/nut/usbhid-ups -a myups -DD
gene@coyote:~$ /lib/nut/usbhid-ups -a myups -DD
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
Can't open /etc/nut/ups.conf: Can't open /etc/nut/ups.conf: Permission
denie
On May 12, 2019, at 1:52 PM, Gene Heskett wrote:
>
> On Sunday 12 May 2019 12:07:13 pm Charles Lepple wrote:
>
>> systemctl status nut-driver
> ● nut-driver.service - Network UPS Tools - power device driver controller
> Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor
> p
On Sunday 12 May 2019 12:07:13 pm Charles Lepple wrote:
> systemctl status nut-driver
● nut-driver.service - Network UPS Tools - power device driver controller
Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor
preset: enabled)
Active: failed (Result: exit-code) since Fr
On May 8, 2019, at 8:19 PM, Gene Heskett wrote:
>
> The real problem as I recall from a couple days back, is that the
> usbhid-ups driver was left out of this kernel build. Since this is
> pretty close to an rt kernel, I don't know if the LCNC folks will build
> another kernel with it, and issu
Stuart D. Gathman writes:
On Tue, 7 May 2019, Gene Heskett wrote:
May 07 10:40:21 coyote upsd[12110]: fopen /var/run/nut/upsd.pid: No such
file or directory
Some time ago, Fedora made /var/run a symlink to /run which is a tmpfs
filesystem. Thus, any subdirectories must be created afresh eac
On Wednesday 08 May 2019 05:39:22 pm Stuart D. Gathman wrote:
> On Tue, 7 May 2019, Gene Heskett wrote:
> > May 07 10:40:21 coyote upsd[12110]: fopen /var/run/nut/upsd.pid: No
> > such file or directory
>
> Some time ago, Fedora made /var/run a symlink to /run which is a tmpfs
> filesystem. Thus,
On Tue, 7 May 2019, Gene Heskett wrote:
May 07 10:40:21 coyote upsd[12110]: fopen /var/run/nut/upsd.pid: No such
file or directory
Some time ago, Fedora made /var/run a symlink to /run which is a tmpfs
filesystem. Thus, any subdirectories must be created afresh each boot.
The packager for nut
On Tuesday 07 May 2019 09:49:47 am Charles Lepple wrote:
> On May 7, 2019, at 9:09 AM, Gene Heskett wrote:
> > On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote:
> >> On May 7, 2019, at 5:06 AM, Gene Heskett wrote:
> >>> New testing install(stretch)
> >>> pulled in nut stuff from repo.
> >>>
On May 7, 2019, at 9:09 AM, Gene Heskett wrote:
>
> On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote:
>
>> On May 7, 2019, at 5:06 AM, Gene Heskett wrote:
>>> New testing install(stretch)
>>> pulled in nut stuff from repo.
>>> copied old wheezy configs to /etc/nut, overwriting the resident
On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote:
> On May 7, 2019, at 5:06 AM, Gene Heskett wrote:
> > New testing install(stretch)
> > pulled in nut stuff from repo.
> > copied old wheezy configs to /etc/nut, overwriting the resident
> > files can't talk to ups, missing usbhid-ups file
>
On May 7, 2019, at 5:06 AM, Gene Heskett wrote:
>
> New testing install(stretch)
> pulled in nut stuff from repo.
> copied old wheezy configs to /etc/nut, overwriting the resident files
> can't talk to ups, missing usbhid-ups file
Gene,
What do you have in /etc/nut/ups.conf? (There shouldn't be
New testing install(stretch)
pulled in nut stuff from repo.
copied old wheezy configs to /etc/nut, overwriting the resident files
can't talk to ups, missing usbhid-ups file
Found it in /lib/nut, doesn't modprobe, not in /lib/modules/kernelversion
tree.
I need to fix this, how do I proceed? A dir
16 matches
Mail list logo
