similar to: udevd can't reach LDAP-server during boot

On Sunday 20 March 2016 12:30:58 Richard W.M. Jones wrote: > This is useful for debugging (but we can't print it unconditionally > since we cannot run grep etc yet). It also allows us to identify > when udevd is invoked so we can time it for boot analysis. > --- I just sent a patch to make use of bash functionalities for string matching in /proc/cmdline. This way, the verbosity

This is useful for debugging (but we can't print it unconditionally since we cannot run grep etc yet). It also allows us to identify when udevd is invoked so we can time it for boot analysis. --- appliance/init | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/appliance/init b/appliance/init index f6fe9b9..657943c 100755 --- a/appliance/init +++ b/appliance/init @@

Bonjour, Depuis que j'ai pass? une machine de Squeeze ? Wheezy, j'ai toutes les secondes dans /var/log/syslog, ce message : udevd[374]: timeout: killing '/sbin/modprobe -b

I upgraded my container from CentOS 6.4 to CentOS 6.5. Everything looks good after upgrade until reboot. When rebooted to container I'm getting the following errors.. Any help would be greatly appreciated /bin/mknod: `/dev/lp2': Operation not permitted /bin/chown: cannot access `/dev/lp2': No such file or directory /bin/mknod: `/dev/lp3': Operation not permitted /bin/chown: cannot

On Apr 23, 2014, at 3:47 AM, Frantz de Germain wrote: > I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP > 1.6/Centos 5.7) to manage a Dell UPS 2700W. > > Here is my ups.conf : > > [SU27003U-08] > driver = usbhid-ups > port = auto > desc = "SU27003U-08" > > 52-nut-usbups.rules have well been installed in

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ -------------- next part -------------- >From 879508c96941daf5dc01dca5fc0d0880107adb70 Mon Sep 17 00:00:00 2001 From: Richard Jones <rjones at

Wrong list, wrong language : double appologize for my previous message .. Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20140128/ebe37a27/attachment.html>

Commit a6330e9d3af0f5286f1d53d909fd868387b67f69 enabled /run for systemd-tmpfiles: while this works fine in most of the cases, there are few tmpfiles configurations that still references /var/run instead of /run. As result, include also /var/run in the systemd-tmpfiles execution. --- appliance/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appliance/init

I suppose it would help if I posted relevant version info (sorry about that...) CentOS Linux release 7.4.1708 (Core) @ 3.10.0-693.11.6.el7.x86_64 systemd-219-42.el7_4.4.x86_64 $ modinfo virtio_scsi filename: /lib/modules/3.10.0-693.11.6.el7.x86_64/kernel/drivers/scsi/virtio_scsi.ko.xz license: GPL description: Virtio SCSI HBA driver rhelversion: 7.4 srcversion:

Hi, today I updated the glibc packages on some CentOS machines. After the Update I checked which services/processes I have to restart "yum -C ps" or "needs-restarting" At the most machines I get no information about necessary restarts, but at two machines a long listing : 1 : /sbin/init 386 : /sbin/udevd-d 659 : /sbin/udevd-d 999 : /usr/sbin/vmtoolsd 1103 : auditd 1128 :

Hello list. My server: Gentoo 2.6.21-xen dom0 xen-tools 3.2.1 lvm 2.02.28-r2 udev-115-r1 Symptoms: normally I run 4 domUs. About once a week I have a need to restart a domU. Sometimes it works just fine, but other times it does not and I''ll get a message back saying "Error: Device 0 (vif) could not be connected. Hotplug scripts not working". The domU config file has not

Hi everyone, I have a udev rule file that contains a singular rule: SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_VENDOR}=="*Google*", ENV{DEVTYPE}=="disk", ATTR{queue/scheduler}:="noop" When I use a Google Cloud instance and boot it, things work as expected and /dev/sda (a persistent disk) uses the noop scheduler. If the instance also has a

Hello, I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP 1.6/Centos 5.7) to manage a Dell UPS 2700W. Here is my ups.conf : [SU27003U-08] driver = usbhid-ups port = auto desc = "SU27003U-08" 52-nut-usbups.rules have well been installed in /lib/udev/rules.d/. I've put it in /etc/udev/rules.d/ too. I've rebooted the machine.

USB sticks and cameras used to pop right up on my desktop. Now they don't. I've checked the Gnome "Drives and Media Preferences" and nothing has changed -- I have "Mount removable media when inserted" etc. (Tried toggling it off and back on, no effect.) I've logged out and back in, even rebooted. /var/log/messages shows the devices are being recognized by udev:

Hi guys, I'm trying to use asterisk with my slackware 10.2 box. Kernel 2.6.13 from the testing... The udevd are not creating the /dev/zap devices. Someone already have success installing asterisk over slackware? Thanks in advance. Fernando Lujan

Hi, I have upgraded an Asterisk installation with a Xorcom BRI Astribank that was working under Ubuntu 8.04 to Ubuntu 9.10 and the device is no longer initialized. When I reload the udev rules, I see that the rules seems to be correctly loaded: udevd[452]: reading '/etc/udev/rules.d/40-xpp.rules' as rules file However, these rules do not seem to be triggered: # udevadm trigger

2012/6/5 Kok, Auke-jan H <auke-jan.h.kok@intel.com> wrote on systemd-devel list: > It seems your system is taking well into 15+ seconds before btrfs is > actually *ready* on your system, which seems to be the main hiccup > (note, speculation here). I''ve personally become a bit displeased with > btrfs performance recently myself, so, I''m wondering if you should

https://bugzilla.redhat.com/show_bug.cgi?id=1165785 Since the --boot option is relatively new (added 2013-12), I suspect this will break older versions of systemd. However it should be fine for all currently supported versions of Fedora. Rich.

On 09/01/2017 02:41 PM, Kevin Stange wrote: > On 08/31/2017 07:50 AM, PJ Welsh wrote: >> A recently created and fully functional CentOS 7.3 VM fails to boot >> after applying CR updates: > <snip> >> Server OS is CentOS 7.3 using Xen (no CR updates): >> rpm -qa xen\* >> xen-hypervisor-4.6.3-15.el7.x86_64 >> xen-4.6.3-15.el7.x86_64 >>

I've seen this now a few times, but of course I didn't write them down, so I may have the wording a little off. The new kernel seems to contain something in udevd that is now generating a whole slew of unknown attribute(or something like that) errors during the boot, before the part where dmesg picks up. They don't seem to be causing any actual problems while the system is up and