similar to: can't find UPS on openwrt/arm

Hi Maxime, Quoting Maxime Accadia (2020-02-03 14:20:47) > Hi, > > We have a VM with several USB devices attached. Everything works well, > but sometimes, after a reboot of the host, some usb device get a > different bus/device number and that prevent the reboot of the VM : > ... > Any idea on how to handle this case ? > > We were thinking about using udev, but it

>> On Sun, 23 Feb 2014 19:39:02 +0100, Josu Lazkano <josu.lazkano at gmail.com> wrote: >>> # dmesg >>> ... >>> [181041.636190] usb 4-4: new low-speed USB device number 2 using ohci_hcd >2014-02-25 10:12 GMT+01:00 Virgo P?rna <virgo.parna at mail.ee>: >> I recently read about openwrt (for one of the routers I own). And there was a >>

Greetings, I'm executing an external script when the qemu hook is called with start or release, the script is rather simple, upon start it iterates over the output of lsusb -t and for each device, it looks if it should be added to the vm we started, if so, it attaches it to the vm as follows: virsh --connect qemu:///system "${cmd}" "${domain}" /dev/stdin << END

On Thu, 27 Feb 2014 15:35:06 +0100, Matus UHLAR - fantomas <uhlar at fantomas.sk> wrote: >>> On Sun, 23 Feb 2014 19:39:02 +0100, Josu Lazkano <josu.lazkano at gmail.com> wrote: >>I plug a USB Hub in OpenWRT but there is nothing in "lsusb" and >>"dmesg". In a Debian server I have this: >> >> >># lsusb >>... >>Bus 001

On Thu, Jan 03, 2019 at 18:07:58 +0100, daggs wrote: > Greetings, > > I'm executing an external script when the qemu hook is called with start or release, the script is rather simple, upon start it iterates over the output of lsusb -t and for each device, it looks if it should be added to the vm we started, if so, it attaches it to the vm as follows: > virsh --connect

On 1/4/19 11:27 AM, daggs wrote: > Greetings Peter, > >> Sent: Friday, January 04, 2019 at 4:47 PM >> From: "Peter Krempa" <pkrempa@redhat.com> >> To: daggs <daggs@gmx.com> >> Cc: libvirt-users@redhat.com >> Subject: Re: [libvirt-users] script called from qemu hook freezes. >> >> On Thu, Jan 03, 2019 at 18:07:58 +0100, daggs

On Fri, Jan 04, 2019 at 17:27:48 +0100, daggs wrote: > Greetings Peter, > > > Sent: Friday, January 04, 2019 at 4:47 PM > > From: "Peter Krempa" <pkrempa@redhat.com> > > To: daggs <daggs@gmx.com> > > Cc: libvirt-users@redhat.com > > Subject: Re: [libvirt-users] script called from qemu hook freezes. > > > > On Thu, Jan 03, 2019

Greetings Peter, > Sent: Friday, January 04, 2019 at 4:47 PM > From: "Peter Krempa" <pkrempa@redhat.com> > To: daggs <daggs@gmx.com> > Cc: libvirt-users@redhat.com > Subject: Re: [libvirt-users] script called from qemu hook freezes. > > On Thu, Jan 03, 2019 at 18:07:58 +0100, daggs wrote: > > Greetings, > > > > I'm executing an

Marcus, I did try to do that several days ago, got the email, confirmed my desire to unsubscribe, and wad told that my "request would soon be acted upon" Yet I continue to get these messages. I'd love to have just a way to receive only message chains where I either started the question or am contributing. I don't need to see ALL the comms on the list, however this old-school

I still have two questions: 1) How do I make the nut-server and nut-monitor find the right pid files? They are there but it seems they can't be opened. Permissions are nut/nut. 2) What do these error messages mean? Jan 19 16:14:52 mars nut-monitor[3781]: Init SSL without certificate database Jan 19 16:14:52 mars nut-monitor[3781]: Login on UPS [Eaton at localhost] failed - got [ERR

On 19.01.24 17:02, Stefan Schumacher via Nut-upsuser wrote: >Jan 19 05:50:13 mars nut-monitor[849]: Signal 15: exiting >Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting this looks like someone repeatedly killed nut server. This not a problem of UPS. -- Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this

Hello, could nut clients have its settings file? It would be easier to configure UPSes for upsc, upsmon and nut-monitor with client config file. Maybe ups.conf ? -- Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. My mind is like a steel

Hello, I will thank you all for your support about my network problem on NUT Not it is solved and I will thank you a lot ! Best regards Thierry Le sam. 31 août 2019 à 07:00, <nut-upsuser-request at alioth-lists.debian.net> a écrit : > Send Nut-upsuser mailing list submissions to > nut-upsuser at alioth-lists.debian.net > > To subscribe or unsubscribe via the World

On 19.02.24 14:48, Dan Grostick via Nut-upsuser wrote: >Msmtp is not sending messages when invoked from upssched-cmd. >I can manually invoke it from the command line. where is its config file? >There is a 's' instead of an 'x' in the ls -l. Might this be some sort of >permission problem? Should not be the case. >upsmon.conf has run user as root. msmtp may use

> 1) How do I make the nut-server and nut-monitor find the right pid files? They are there but it seems they can't be opened. Permissions are nut/nut. Actually, if the preceding lifetime of the service was a graceful stop, the exiting daemon should have removed its PID files. Then the newly starting one would check and not find them - as I wrote before - to make sure there is no hung old

Maybe...ish - I haven't seen those for a while, but had few outages either. Can you check if the updated (root) user profile or default profile(s) under /etc mention `mesg n` or similar means of limiting broadcasts? In your manual `wall` executions, do you see them in the same terminal that sent the message, or on all terminals (GUI, SSH sessions)? As root or as any user (as recipient and as

Jan 19 05:50:13 mars nut-monitor[849]: Signal 15: exiting Jan 19 05:50:13 mars nut-monitor[849]: Network UPS Tools upsmon 2.8.0 Jan 19 05:50:13 mars systemd[1]: Stopping nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller... Jan 19 05:50:13 mars systemd[1]: nut-monitor.service: Deactivated successfully. Jan 19 05:50:13 mars systemd[1]: Stopped nut-monitor.service

Hello, I have noticed that (apparensly) since Debian 12 upgrade the WALL commands for upsmon.conf don's seem to work. To test I have configured upsmon-dummy.conf to debug this: NOTIFYCMD /usr/sbin/upssched NOTIFYFLAG ONBATT SYSLOG+EXEC+WALL NOTIFYFLAG ONLINE SYSLOG+EXEC+WALL the /usr/sbin/upssched gets called: /lib/nut/upsmon -D -D -D -D -f /etc/nut/upsmon-dummy.conf and I

Hello, I have tried setting umask 0027 for tftpd, so files are created with permissions 0640. However, tftpd-hpa refused uploading a file with error "must have global write permissions". Looking at the source, I could avoid this issue by using "-p" option. However, it also seems that the umask is not applied when the "-p" option is used. Can anyone explain this

On 19.01.24 16:20, Stefan Schumacher via Nut-upsuser wrote: >This morning at 9:50 the server stopped working unexpectedly - I was >still sleeping until 10:00, so no user intervention took place. > >Jan 19 05:50:17 mars nut-server[1303]: mainloop: Interrupted system call >Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting >Jan 19 05:50:17 mars nut-server[1303]: Network UPS