similar to: Issue with two UPS APC managed from a single PC.

Is that with both UPSes on same machine? A quick guess would be that insufficient data points to identify the device are configured (vendorid, productid, serial...) in ups.conf, so both drivers connect to the first match. I'd expect them to conflict and one would die or both loop reconnecting, if both are running at once, though. Also, which NUT version? Custom build from GitHub or an

On Fri, Aug 7, 2020 at 1:10 PM Erik Skultety <eskultet@redhat.com> wrote: > On Wed, Aug 05, 2020 at 10:13:57PM +0530, Kaushal Shriyan wrote: > > On Wed, Aug 5, 2020 at 1:32 PM Pavel Hrdina <phrdina@redhat.com> wrote: > > > > > On Wed, Aug 05, 2020 at 06:57:11AM +0530, Kaushal Shriyan wrote: > > > > Hi, > > > > > > > > I am

On Wed, Aug 5, 2020 at 1:32 PM Pavel Hrdina <phrdina@redhat.com> wrote: > On Wed, Aug 05, 2020 at 06:57:11AM +0530, Kaushal Shriyan wrote: > > Hi, > > > > I am trying to install kali-linux-2020.2-installer-amd64.iso ( > > https://www.kali.org/downloads/) using KVM virt-install tool > > > > #virt-install --name=kalilinux

Hi, I am trying to install kali-linux-2020.2-installer-amd64.iso ( https://www.kali.org/downloads/) using KVM virt-install tool #virt-install --name=kalilinux --file=/linuxkvmaddgbdisk/kalilinux.img --file-size=50 --nonsparse --vcpu=2 --ram=4096 --network=bridge:br0 --os-type=linux --os-variant=debian9 --graphics none --location=/linuxkvmaddgbdisk/kali-linux-2020.2-installer-amd64.iso

Sounds like some other program is holding the port. Have you stopped other NUT drivers for the device (e.g. via auto-resuscitating services) before starting this one? Does udev, ugen or similar facility have the configuration to hand off this device to NUT run-time user? (BTW, if you are now testing a custom build - was it configured to use same accounts as pre-packaged variant)? On Fri, Mar 24,

Hi Pavel, I am running virt-install version 1.5.0 on CentOS Linux release 7.6.1810 (Core) server. #virt-install --name=kalilinux --file=/linuxkvmaddgbdisk/kalilinux.img --file-size=50 --nonsparse --vcpu=2 --ram=4096 --network=bridge:br0 --os-type=linux --os-variant=debian9 --graphics none --location

Hi Jim, I?m using on Kali Linux. I?m not using a custom version and finally found the issue which was a hidden character staying in the ups.conf file. I rebuilt the file and everything worked out. Issue closed and many thanks for your help. Laurent From: Jim Klimov <jimklimov+nut at gmail.com> Sent: mercredi 29 mars 2023 13:22 To: laurenttaieb at free.fr Cc: nut-upsuser

Read the information from os-release, and make it behave like a Debian distribution (i.e. using dpkg, and apt). --- daemon/inspect_fs.ml | 2 ++ daemon/inspect_fs_unix.ml | 1 + daemon/inspect_types.ml | 2 ++ daemon/inspect_types.mli | 1 + generator/actions_inspection.ml | 4 ++++ 5 files changed, 10 insertions(+) diff --git a/daemon/inspect_fs.ml

The "unknown" fields mean the driver did not get that piece of information from libusb. In case of Manufacturer/Product which are unknown in the later post, but known in the first, I suppose you had another driver running, or the kernel still owned it (udev misbehavior, not handing it off after reconnections, etc.) and so exclusive access was not given to the new (currently reporting)

Here is my output I am getting on my kali machine. I believe that the error is: guestfsd: error while loading shared libraries: libtsk.so.19: cannot open shared object file: No such file or directory I tried to change the LD_LIBRARY_PATH to numerous locations and libtsk.so.19 is inside /usr/lib/x86_64-linux-gnu

I?m making some progress I believe? I switched off and switched on the UPS further to the laptop having started the daemon and I?m not getting the same error message which is probably due to the server working in the background still locking the device I think the daemon starts but gets into an infinite loop and doesn?t finish and hand back control. Here are the updated traces I got by

Hello i have a machine A with 2 disks 1 et 2 running Debian Jessie on 1 is the system and the boot and the swap on 2 different partitions like /home /opt ETC..... i have a machine B with 1 disk running kali-linux and *100G free* Can i clone the disk 1 of machine A on the 100G free on machine B with rsync? If it is possible, how to do that? Many thanks TG -------------- next part --------------

Thanks Larry, I tried. Got the following traces and the driver doesn?t start. 1.036797 [D2] - VendorID: 0463 1.036812 [D2] - ProductID: ffff 1.036826 [D2] - Manufacturer: unknown 1.036840 [D2] - Product: unknown 1.036872 [D2] - Serial Number: unknown 1.036912 [D2] - Bus: 002 1.036942 [D2] - Device: unknown 1.036965 [D2] - Device

I have been running a Samba PDC with Samba version 3.0.0 on Redhat 7.3 for quite some time. My WinXP Pro SP2 system is part of the domain and everything has been working just peachy. And then, of course, I had to tinker with it. I upgraded the linux box to Whitebox Linux 3.0, a derivative of Redhat Enterprise Linux 3.0. It comes with Samba 3.0.7. After installing and updating everything, I

Hi, I remember I had a bootable USB flash drive with few Linux distributions four to five years ago. iso files for Linux distributions and initial ramdisk(copied from extracted iso file) and Linux kernel(copied from extracted iso file) were on the USB flash drive. So I tried to create something similar with latest Ubuntu and in order to keep things simple, I did not add any additional

Followup of commit 70407cd622dda6f088a0876e1e1ae669e9f8a281 for openSUSE Thumbleweed. --- daemon/inspect_fs_unix.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daemon/inspect_fs_unix.ml b/daemon/inspect_fs_unix.ml index 4dd89fa8f..925db06a3 100644 --- a/daemon/inspect_fs_unix.ml +++ b/daemon/inspect_fs_unix.ml @@ -143,7 +143,7 @@ and distro_of_os_release_id = function |

Also, just in case - are you in a virtualized environment? Is there (intentional or not) USB pass-through to the UPSes? My hint is, we had cases where a host or guest grabbed the device but it was not apparent from the part of system running NUT. Jim On Fri, Mar 24, 2023, 23:23 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Sounds like some other program is holding the port. Have

On Fri, Aug 07, 2020 at 05:05:48PM +0530, Kaushal Shriyan wrote: > On Fri, Aug 7, 2020 at 1:10 PM Erik Skultety <eskultet@redhat.com> wrote: > > > On Wed, Aug 05, 2020 at 10:13:57PM +0530, Kaushal Shriyan wrote: > > > On Wed, Aug 5, 2020 at 1:32 PM Pavel Hrdina <phrdina@redhat.com> wrote: > > > > > > > On Wed, Aug 05, 2020 at 06:57:11AM +0530,

On Wed, Aug 05, 2020 at 10:13:57PM +0530, Kaushal Shriyan wrote: > On Wed, Aug 5, 2020 at 1:32 PM Pavel Hrdina <phrdina@redhat.com> wrote: > > > On Wed, Aug 05, 2020 at 06:57:11AM +0530, Kaushal Shriyan wrote: > > > Hi, > > > > > > I am trying to install kali-linux-2020.2-installer-amd64.iso ( > > > https://www.kali.org/downloads/) using KVM

I've several USB <-> RS-232 dongles around. As well as a few embedded devices. They all "Just Work (tm)" on Redhat, CentOS, Fedora, Debian, Raspian and Kali. Knock on wood - never had a problem using any of them. As the drivers are part of the kernel, I'd expect any distro using a recent kernel to do well. On Wed, Jul 8, 2020 at 9:24 AM Leroy Tennison <leroy at