I have setup my server logging with graylog and now I see that my logs are being spamed by level: 3 errors like these:
systemd-udevd[1523120]: veth20996a5: Failed to get link config: No such device
I think vethxxxxxxx is an interface created by Docker, but I can't figure out what is causing these errors.
Any help to solve this and find reason for these errors would be really appreciated.
I am trying to set some universal names for the predictable names. I am doing this to be able to have the same interface names on all my machines.
Iam trying to follow "Example 2. /etc/systemd/network/10-dmz.link" from https://www.freedesktop.org/software/systemd/man/systemd.link.html
my files look as follows:
/etc/systemd/network/10-dmz.link
[Match]
MACAddress=80:ee:73:f1:01:43
[Link]
Name=dmz0
/etc/systemd/network/10-dmz.network
[Match]
Name=dmz0
[Network]
Address=192.168.25.2/24
After reboot I do not get an interface called dmz0. Systemd-networkd is enabled and setting a IP on another interface with a .network file works.
What am I missing?
thank you
I have a Ubuntu 8.04 LTS (server edition), and I need to write a udev rule for it to act upon plugging a USB thumb drive. However, I need a different action depending on the filesystem of the drive. I know I can use the ID_FS_TYPE environment variable to check for the filesystem on the drive.
Following instructions found here, I try a dummy udev rule as such :
KERNEL!="sd[a-z][0-9]", GOTO="my_udev_rule_end"
ACTION=="add", RUN+="/usr/bin/touch /tmp/test_udev_%E{ID_FS_TYPE}"
ACTION=="add", ENV{ID_FS_TYPE}=="vfat", RUN+="/usr/bin/touch /tmp/test_udev_it_works"
LABEL="my_udev_rule_end"
However, when I plug in a thumb drive with a vfat filesystem (which should trigger both rules), I end up with a file called /tmp/test_udev_vfat, meaning the first rule was triggered successfully, and that the ID_FS_TYPE environment variable is "vfat", but I don't have the other file, meaning that although I know the ID_FS_TYPE env variable is "vfat", I can't seem to check against it for a match.
I tried googling the thing, but pretty much every result seems to assume ENV{ID_FS_TYPE}=="vfat" works. I also tested the exact same udev rule on Ubuntu 10.04 LTS server, and I have the same result.
I'm probably missing something very simple, but I just don't get it. Does anyone see what is wrong with my udev rule that would prevent it from matching on ENV{ID_FS_TYPE}?
Thanks.
Currently my distribution of choice (ArchLinux) has an automounting script like this:
KERNEL!="sd[a-z][0-9]", GOTO="media_by_label_auto_mount_end"
But that will automount only partitions up to sdX9. I do have USB drives with 6 or more partitions (that is, starting from 5, up to 12, 13, 19).
All partitions have VFAT on them and have labels (the label is used for naming the mountpoint).
I have tried to modify it to:
KERNEL!="sd[a-z][0-9]+", GOTO="media_by_label_auto_mount_end"
but that doesn't work.
So how to make it work for sdb5, sdb42 or sdb31337 likewise?
Thanks.
Addendum
I've just tried the \d+? method, udevadm monitor says:
KERNEL[1295719513.473653] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb (block)
KERNEL[1295719513.473687] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb1 (block)
KERNEL[1295719513.473706] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb5 (block)
KERNEL[1295719513.473725] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb6 (block)
KERNEL[1295719513.473743] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb7 (block)
KERNEL[1295719513.473761] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb8 (block)
KERNEL[1295719513.473791] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb9 (block)
KERNEL[1295719513.473811] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb10 (block)
KERNEL[1295719513.473830] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb11 (block)
KERNEL[1295719513.473848] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb12 (block)
UDEV [1295719513.593213] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb (block)
UDEV [1295719514.959983] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb5 (block)
UDEV [1295719514.960053] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb1 (block)
UDEV [1295719514.961528] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb6 (block)
UDEV [1295719514.963793] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb9 (block)
UDEV [1295719514.964930] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb10 (block)
UDEV [1295719514.965794] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb12 (block)
UDEV [1295719514.967418] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb8 (block)
UDEV [1295719514.968466] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb7 (block)
UDEV [1295719514.973757] add /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host29/target29:0:0/29:0:0:0/block/sdb/sdb11 (block)
But it doesn't work either. If I leave the default rule, sdb5-9 are mounted properly.
I was upgrading my servers today and it all went fine except the last machine which has the following issues:
[Resolved using http://www.ndchost.com/wiki/server-administration/upgrade-ubuntu-pre-10.04#post-1004-upgradefinal-steps]
No login prompt on console
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
[ 0.545705] blkfront: xvda: barriers enabled
[ 0.546949] xvda: xvda1
[ 0.549961] blkfront: xvde: barriers enabled
[ 0.550619] xvde: xvde1 xvde2
Begin: Running /scripts/local-premount ...
Done.
[ 0.870385] kjournald starting. Commit interval 5 seconds
[ 0.870449] EXT3-fs: mounted filesystem with ordered data mode.
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
Also tried by pressing ENTER and CTRL+C many times, no use.
Resolved: [/tmp was mounted as noexec, changing that fix it]:
I get errors when i try to re-install udev in single user mode:
Unpacking replacement udev ...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Processing triggers for man-db ...
Setting up udev (151-12.1) ...
udev start/running, process 1003
Removing `local diversion of /sbin/udevadm to /sbin/udevadm.upgrade'
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.32-25-server
/usr/sbin/mkinitramfs: 329: /tmp/mkinitramfs_yuuTSc/scripts/local-premount/fixrtc: Permission denied
/usr/sbin/mkinitramfs: 329: /tmp/mkinitramfs_yuuTSc/scripts/local-premount/ntfs_3g: Permission denied
/usr/sbin/mkinitramfs: 329: /tmp/mkinitramfs_yuuTSc/scripts/local-premount/resume: Permission denied
/usr/sbin/mkinitramfs: 329: /tmp/mkinitramfs_yuuTSc/scripts/nfs-top/udev: Permission denied
/usr/sbin/mkinitramfs: 329: /tmp/mkinitramfs_yuuTSc/scripts/panic/console_setup: Permission denied
/usr/sbin/mkinitramfs: 329: /tmp/mkinitramfs_yuuTSc/scripts/init-top/all_generic_ide: Permission denied
/usr/sbin/mkinitramfs: 329: /tmp/mkinitramfs_yuuTSc/scripts/init-top/blacklist: Permission denied
/usr/sbin/mkinitramfs: 329: /tmp/mkinitramfs_yuuTSc/scripts/init-top/udev: Permission denied
/usr/sbin/mkinitramfs: 329: /tmp/mkinitramfs_yuuTSc/scripts/init-bottom/udev: Permission denied
/usr/sbin/mkinitramfs: 329: /tmp/mkinitramfs_yuuTSc/scripts/local-bottom/ntfs_3g: Permission denied