Displaying 20 results from an estimated 100 matches similar to: "No run cmd /usbhid-ups -k !"
2018 Jul 02
0
No run cmd /usbhid-ups -k !
On Jul 2, 2018, at 9:02 AM, icingaj at gmail.com wrote:
>
> ioctl(12, USBDEVFS_CLAIMINTERFACE, 0xbecf910c) = -1 EBUSY (Resource busy)
> ioctl(12, USBDEVFS_GETDRIVER, 0xbecf9024) = 0
> writev(2, [{"Can't claim USB device [0463:fff"..., 62}, {NULL, 0}], 2Can't
> claim USB device [0463:ffff]: No such file or directory
> ) = 62
> exit_group(1)
2018 Jul 03
1
No run cmd /usbhid-ups -k !
Set with upsrw: ups.delay.shutdown=60 is the same as offdelay = 30.
This time was done correctly by UPS.
Set with upsrw: ups.delay.start=90 is the same as ondelay = 40.
The UPS shut down and reset and forget about the settings.
If I use the program in Win 10 settings in the program from Eaton are stable!?
Jan.
> -----Original Message-----
> From: Nut-upsuser
2007 Jun 26
2
bcmxcp_usb and powerware 5115
Hello, ppl!
I try configure NUT for communicate with my Powerware 5115 UPS.
As root I run '/lib/nut/bcmxcp_usb -DDDD -u root -a ups', but driver
can't connect to my UPS.
Some output:
Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4)
debug level is '4'
usb_set_debug: Setting debugging level to 3 (on)
usb_os_init: Found USB VFS at /dev/bus/usb
usb_os_find_busses: Found 001
2014 Jul 31
0
Re: hang after seabios
Hi Richard thanks for the info.
I took the strace approach and ran into this looping over and over again.
Is it failing to get time?
timer_gettime(0x8, {it_interval={0, 0}, it_value={0, 0}}) = 0
timer_settime(0x8, 0, {it_interval={0, 0}, it_value={0, 250000}}, NULL) = 0
timer_gettime(0x8, {it_interval={0, 0}, it_value={0, 204443}}) = 0
select(16, [0 6 9 13 15], [], [], {1, 0}) = 2 (in [6 13],
2014 Nov 06
0
nutdrv_atcl_usb
On Nov 5, 2014, at 4:39 PM, jani <jani.talikka at gmail.com> wrote:
> The output of the ldd command is:
> root at minime:~# ldd /lib/nut/nutdrv_atcl_usb
> linux-gate.so.1 (0xb7722000)
> libusb-0.1.so.4 => /lib/i386-linux-gnu/libusb-0.1.so.4 (0xb76fe000)
> libpthread.so.0 => /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xb76e2000)
>
2016 Aug 30
1
UPS shutdown
Hi All,
I'm trying to shutdown my UPS using NUT driver version
upsdrvctl -V
Network UPS Tools - UPS driver controller* 1.01-906.*
My UPS details are the following :
battery.charge: 100
battery.charge.low: 5
battery.charge.warning: 50
battery.runtime: 22980
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 26.8
battery.voltage.nominal: 24.0
*device.mfr: American Power Conversion*
2007 Jul 16
1
Tripp Lite OmniSV1500XL
I recently purchased a Tripp Lite OmniSV1500XL and I've had no luck
getting nut to work.
# lsusb
Bus 001 Device 001: ID 0000:0000
Bus 006 Device 002: ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter
Bus 006 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 007 Device 001: ID 0000:0000
Bus 004 Device 009: ID 09ae:0001 Tripp Lite
Bus 004 Device
2009 Jul 14
0
[LLVMdev] "Recursive compilation detected" and signals
Hello,
Platform is RHEL5, GCC 4.2.4, x86-32, and LLVM/LLVM-GCC from subversion
(yesterday evening). I'm compiling C code into bitcode, and then executing
the bitcode using the JIT compiler (lli).
I've managed to reproduce a problem when multiple signals go off around the
same time. A sample program is below. The result is the "recursive
compilation detected" JIT compiler
2023 Jan 14
1
[klibc:time64] time: Use 64-bit time types on all architectures
Commit-ID: df7b02bd5c9af14c6efbe39ee4c313e368dfe967
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=df7b02bd5c9af14c6efbe39ee4c313e368dfe967
Author: Ben Hutchings <ben at decadent.org.uk>
AuthorDate: Sat, 14 Jan 2023 00:17:45 +0100
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 14 Jan 2023 18:10:12 +0100
[klibc] time: Use 64-bit time
2018 Jul 01
0
No run cmd /usbhid-ups -k !
On 01/07/2018 11.53, icingaj at gmail.com wrote:
> Good day.
>
> Can not perform shutdowns Ups. Please help.
>
> Details of our installation are:
> OS: Turris Omnia (TO)
> NUT version: 2.7.4-5
> Installation method: from package
> UPS device: EATON UPS 5SC 500i , 230V, 350W, 500VA, USB bought in jun 2018
>
> If you connect to TO UPS via USB, the /dev/hidraw0
2018 Jul 01
2
No run cmd /usbhid-ups -k !
Good day.
Can not perform shutdowns Ups. Please help.
Details of our installation are:
OS: Turris Omnia (TO)
NUT version: 2.7.4-5
Installation method: from package
UPS device: EATON UPS 5SC 500i , 230V, 350W, 500VA, USB bought in jun 2018
If you connect to TO UPS via USB, the /dev/hidraw0 device will be created.
No any programs from NUT package is not running.
When I run:
/lib/nut/usbhid-ups
2018 Jul 03
2
No run cmd /usbhid-ups -k !
Hi all.
UPS is Eaton 5SC 500i.
I tested three solutions:
1. swap "usbhid-ups -a qnapups" with "usbhid-ups -a qnapups -k"
Result: server shutdown, but ups does not shut off!
2. run prog with params "upsmon -c fsd"
Result: server shutdown, but ups does not shut off!
3. run prog "upscmd -u name -p passwd qnapups shutdown.return"
and next
2004 May 19
0
idmap_ad compile problem
I saw a message on this mailing list about compiling the idmap_ad.c,
back in October of last year... and I'm having the same problem... When
I try to compile it, the message I get is:
gcc -I/usr/include/linux -I/root/samba/samba-3.0.4/source/ubiqx
-I/root/samba/samba-3.0.4/source/popt
-I/root/samba/samba-3.0.4/source/smbwrapper
-I/root/samba/samba-3.0.4/source
2003 Apr 08
0
Panic dereferencing p->p_leader during exit1()
My wife got the following from a system running (effectively)
4.8-RELEASE (I built/installed world just before the kernel version
was updated from 4.8-RC to 4.8-RELEASE). I gather she made a few
attempts to get mozilla to start and then the system panic'd.
According to the crashdump, p->p_leader is NULL but according to
the code, this can never happen. This is a UP Athlon XP-1800
with
2014 Nov 05
2
nutdrv_atcl_usb
The output of the ldd command is:
root at minime:~# ldd /lib/nut/nutdrv_atcl_usb
linux-gate.so.1 (0xb7722000)
libusb-0.1.so.4 => /lib/i386-linux-gnu/libusb-0.1.so.4 (0xb76fe000)
libpthread.so.0 => /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
(0xb76e2000)
libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb7536000)
/lib/ld-linux.so.2
2016 May 26
1
A lot of EAGAIN (Resource temporarily unavailable) using nutdrv_qx
Hello,
I have a Salicru UPS connected by USB using nutdrv_qx driver. As I see
that it was using too much CPU time (or at least, too much for what I
think it should be normal), I used strace to see what is was using,
and got a lot of lines like these:
%<------------%<------------%<------------%<------------
ioctl(4, USBDEVFS_REAPURBNDELAY, 0x7ffdca143278) = -1 EAGAIN (Resource
2016 Oct 28
0
Data Stale at random intervals
Hi Charles,
I've been monitoring for the past few days and NUT has been running solid. Tested and everything's working as it should. Thanks for all of your help on this, great to have it running well again and learned lot.
________________________________
From: Daniel Shields <grungelizard9 at hotmail.com>
Sent: Tuesday, October 25, 2016 8:01 PM
To: Charles Lepple
Subject:
2008 Jan 25
3
Bug#462468: nut: megatec_usb ups not detected since 2.2.1 update anymore
Hi Sven,
2008/1/25, Sven Koch <haegar at sdinet.de>:
> Package: nut
> Version: 2.2.1-1
> Severity: normal
>
> I am using a Mustec PowerMust 1000 USB, connected with a USB cable to
> the PC.
>
> With nut 2.2.0-2.1 everything works without problems - but since the
> 2.2.1-1 update the "upsdrvctl start" from the init script just fails,
> executing the
2017 Apr 08
2
usbhid-ups: Failed to open device, skipping. (Permission denied)
Charles Lepple writes:
> On Sun, Apr 2, 2017 at 2:59 AM, Sam Varshavchik <mrsam at courier-mta.com>
> wrote:
> > Having trouble configuring nut 2.7.4 on Fedora 25, with a new Tripp Lite
> > UPS.
> >
> > I'm running XFCE, and XFCE's Power Manager sees the UPS just fine. lsusb
> > gives:
> >
> > Bus 006 Device 002: ID 09ae:3016 Tripp
2015 May 18
5
kernel/libc uapi changes for y2038
In the patch series I posted recently [1], I introduce new system calls to deal
with modified data structures, but left the question open on how these should
be best accessed from libc. The patches introduce a new __kernel_time64_t type
and based on that five new data structured: struct __kernel_timespec,
struct __kernel_itimerspec, struct __kernel_stat, struct __kernel_rusage,
and struct