Re: Default DNS lookup command?
Perfect! Then I just need to add an alias to my profile and can use nslookup :-) On 21.10.23 17:58, David Wright wrote: On Sat 21 Oct 2023 at 17:35:21 (+0200), Reiner Buehl wrote: > is there a DNS lookup command that is installed by default on any > Debian Bullseye or Bookworm install? Something that doesn't require as > much dependencies as bind9-utils (which provides dig and nslookup) or > bind9-host? nslookup is in busybox. Type: $ busybox nslookup $ busybox nslookup debian.org Cheers, David.
Default DNS lookup command?
Hi all, is there a DNS lookup command that is installed by default on any Debian Bullseye or Bookworm install? Something that doesn't require as much dependencies as bind9-utils (which provides dig and nslookup) or bind9-host? Best regards, Reiner
lm_sensors coretemp-isa-0000 values below ambient temp
Hi, I am trying to setup lm_sensors for an older Zotac IONITX-U-E mainboard. The values I get from the w83667hg-isa-0a10 are all looking good and are in line with what I see in the BIOS. But the values I get from coretemp-isa- are way off. They are around +9/+10°C for both cores while the ambient temperature is already 24°C and the CPU temperature is reported with ~45°C in the bios and from the w83667hg. Is it possible that these are differences to the reported CPU temp? If so, is there a way to add CPU temp to it since both come from different sensors? Or is it more likely that there is a unknown offset that tneeds to be added? I tried adding an offset of 40° with compute temp2 @+40,@+40 but that also increases the critical temperature value from 100 to 140°C which I don't want. Setting the critical threshold with set temp2_crit 100 did not work. It still showed 140. Reiner
Re: ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
On 27.03.2022 18:12, Nicholas Geovanis wrote: On Sun, Mar 27, 2022, 7:31 AM Reiner Buehl wrote: Hi all! I am trying to build an amd64 Debian package from sources but the command dpkg-buildpackage -us -uc fails with a number of the following error messages: ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. Is it possible that you are already setting the LD_LIBRARY_PATH environment variable for your shell? And that its contents are pointing the loader at the wrong libraries? The environment has no LD_LIBRARY_PATH set (env | grep LD is empty). /etc/ld.so.conf and the files in /etc/ld.so.conf.d (i386-linux-gnu.conf, libc.conf, x86_64-linux-gnu.conf) are unmodified according to dpkg --verify libc-bin libc6:i386 libc6:amd64 Only other thing I can think of: Were there any newer header-file packages that needed to be installed along with? Again maybe finding an older include file ahead of the newer confused the loader at runtime. HTH. Do you know how to verify this?
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
Hi all! I am trying to build an amd64 Debian package from sources but the command dpkg-buildpackage -us -uc fails with a number of the following error messages: ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. I have installed (and re-installed) the devscripts, fakeroot and build-essential packages but still get the error. The system was crossgraded from i386 to amd64 and still runs a mix of i386 and amd64 but the build packages seem to be all amd64: bilbo:~# dpkg -l | grep fake ii fakeroot 1.23-1 amd64 tool for simulating superuser privileges ii libfakeroot:amd64 1.23-1 amd64 tool for simulating superuser privileges - shared libraries bilbo:~# dpkg -l | grep devscripts ii devscripts 2.19.5+deb10u1 amd64 scripts to make the life of a Debian Package maintainer easier bilbo:~# dpkg -l | grep build-essentila bilbo:~# dpkg -l | grep build-essential ii build-essential 12.6 amd64 Informational list of build-essential packages Is there anything else that I need to (manually) change? Reiner
Re: LVM activation on boot hangs after crossgrade
It seems that the command /sbin/lvm pvscan --cache --activate ay 9:0 from the Systemd unit lvm2-pvscan@9:0.service is hanging and blocks all subsequent lvm activities. Am Fr., 25. März 2022 um 20:40 Uhr schrieb Reiner Buehl < reiner.bu...@gmail.com>: > Hi all, > > I am crossgrading my Debian Buster system from i386 to amd64 following the > guide from the Debian Wiki (https://wiki.debian.org/CrossGrading). After > the apt full-upgrade I rebooted but now my LVM volumes are not activated > again. > The LVM event activation by systemd times out after 90s. I can boot the > system if I comment out the filesystem that is on LVM (I only have one vg > with one logical volume) but I would like to get that one back. > The system creates lock files P_global and V_vg_data in /var/lock/lvm > which prevent a manual activation. Tools like vgscan or vgdisplay hang > because they can't get the lock. > > What can I do to resolve this? > > Best regards, > Reiner >
LVM activation on boot hangs after crossgrade
Hi all, I am crossgrading my Debian Buster system from i386 to amd64 following the guide from the Debian Wiki (https://wiki.debian.org/CrossGrading). After the apt full-upgrade I rebooted but now my LVM volumes are not activated again. The LVM event activation by systemd times out after 90s. I can boot the system if I comment out the filesystem that is on LVM (I only have one vg with one logical volume) but I would like to get that one back. The system creates lock files P_global and V_vg_data in /var/lock/lvm which prevent a manual activation. Tools like vgscan or vgdisplay hang because they can't get the lock. What can I do to resolve this? Best regards, Reiner
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot
On 04.10.2021 03:41, Joe Pfeiffer wrote: That's not it then... googling "md127" I found a *bunch* of possible causes. I tried already updating the name attribute, setting the homehost to none and a few others. Unfortunately none helped.
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot
On 02.10.2021 01:32, Joe Pfeiffer wrote: Is it possible you need to update your init ramdisk? Maybe your changes to your mdadm.conf aren't being seen? I do run update-initramfs -u after each change. Shouldn't that be enough to to update the mdadm.conf in the init ramdisk?
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot
On 01.10.2021 16:11, Felix Miata wrote: Mine (old) is like so: # head -n3 /etc/mdadm.conf HOMEHOST DEVICE containers partitions ARRAY /dev/md0 metadata=1.0 name=msi85:0tmp UUID=... I tried changing the HOMEHOST from to but that did not help.
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot
On 01.10.2021 15:50, Linux-Fan wrote: I have observed this in the past, too and do not know how to "fix" it. Why is it necessary for the volume to appear under /dev/md3? Might it be possible to use its UUID instead, i.e. check the output of ls -l /dev/disk/by-uuid to find out if your md3/md127 can be accessed by an unique ID. You could then point the entries in /etc/fstab to the UUID rather than the "unstable" device name? It would be beneficial to have the /dev/md3 since I have a few regular expressions that look for only one digit numbers in md arrays but the main reason for me is that I do not trust the array if it randomly renames itself. Mounting via UUID would be possible but I am not sure that a few of the monitoring tools that I use like the UUID.
New mdadm RAID1 gets renamed from md3 to md127 after each reboot
I created a new mdadm RAID 1 as /dev/md3. But after each reboot, it gets activated as md127. How can I fix this - preferably without haveing to delete the whole array again... The array is defined like this in /etc/mdadm: ARRAY /dev/md3 metadata=1.2 level=raid1 num-devices=1 UUID=41e0a87f:22a2205f:0187c73d:d8ffefea (yes, it only has one disk at the moment, the other will be added once this issue is fixed :-) ) I also did run update-initramfs -u to ensure that this is updated there too. If I manually stop and re-assemble it, it shows as md3, but once I reboot, it shows up as md127 again. In the mdadm --detail --scan output, it shows up like this: ARRAY /dev/md/:3 metadata=1.2 name=:3 UUID=41e0a87f:22a2205f:0187c73d:d8ffefea How can I stop the renaming? Best regards, Reiner
Re: Memory allocation failed during fsck of large EXT4 filesystem
/ and /home are fine on the system. The data on the affected filesystem is a collection of data from different remote sites, so it could be restored but that would take a lot of time. That's why I would like to fix the filesystem so that I can then use more intelligent recovery methods that do not need to copy every file. Am Mo., 5. Juli 2021 um 23:21 Uhr schrieb Thomas D. Dean < tomd...@wavecable.com>: > On 7/5/21 1:54 PM, Michael Stone wrote: > > On Mon, Jul 05, 2021 at 12:53:39PM +0300, IL Ka wrote: > >> 7TB seems like too much for one partition imho. > >> Consider splitting it into the parts > > > > That's silly. It's 2021; 7TB isn't particularly large and there's no > > value in breaking things into multiple partitions for no reason. > > > > Maybe to have the ability to restore or reinstall the system without > bothering /home? > >
Re: Memory allocation failed during fsck of large EXT4 filesystem
It seems swap is not the solution: Even after adding a 50G swap file, I still get the same error message and the swap usage stats from collectd show that max swap usage was not more than just 2G. I will now try if the scratch_files stanza makes a difference. Am Mo., 5. Juli 2021 um 11:50 Uhr schrieb Thomas Schmitt : > Hi, > > Reiner Buehl wrote: > > Is there a quick way to enlarge the swap space > > According to old memories of mine you may create a large, non-sparse file > as you would do for a virtual disk. E.g. by mkfile (which seems not to be > in Debian) or qemu-img (from qemu-utils): > > qemu-img create "$swap_file_path" 8G > > Set ownership and access rights of "$swap_file_path" so that no > unprivileged users can spy. > > Then you tell the system to use it for swapping > > swapon "$swap_file_path" > > > > fsck.ext4 fails with the error message: > > Error storing directory block information (inode=366740508, block=0, > > num=406081): Memory allocation failed > > According to > > https://codesearch.debian.net/search?q=package%3Ae2fsprogs+Memory+allocation+failed > this message is emitted if error code EXT2_ET_NO_MEMORY was returned. > This error code indeed occurs if memory allocating system calls fail. > In these cases i would expect that more virtual memory could help. > > > > > But i see questionable occurences of EXT2_ET_NO_MEMORY which get triggered > by bad data. In these cases no extra memory can help: > > Halfways correct is its use to mark an insane request for a memory array > which would exceed the maximum number that can be stored in unsigned long > integer variables. > > There are possible misattributions of that error code if get_icount_el() > returns 0 to set_inode_count() for reasons of bad data. > > https://sources.debian.org/src/e2fsprogs/1.46.2-2/lib/ext2fs/icount.c/?hl=461#L461 > > https://sources.debian.org/src/e2fsprogs/1.46.2-2/lib/ext2fs/icount.c/?hl=388#L388 > (in line 496 the same return value leads to ENOENT.) > > In > > https://sources.debian.org/src/e2fsprogs/1.46.2-2/lib/ext2fs/hashmap.c/?hl=33#L33 > i see a potential memory fault by using the calloc(3) return without > checking it for NULL. (A caller of ext2fs_hashmap_create() would later > throw EXT2_ET_NO_MEMORY if the program did not crash yet.) > > Return value 0 from get_refcount_el() is converted to EXT2_ET_NO_MEMORY > in ea_refcount_increment(), although get_refcount_el() did not attempt to > allocate memory. > > It stays a riddle from where e2fsprogs links sparse_file_new(). I find it > only as Android C++ call. Whatever, if it fails then EXT2_ET_NO_MEMORY > can be returned by its caller io_manager_configure(), which seems not > restricted to Android. > > > Have a nice day :) > > Thomas > >
Memory allocation failed during fsck of large EXT4 filesystem
Hi all, I have a corrupt EXT4 filesystem where fsck.ext4 fails with the error message: Error storing directory block information (inode=366740508, block=0, num=406081): Memory allocation failed /dev/vg_data/lv_mpg: * FILE SYSTEM WAS MODIFIED * e2fsck: aborted /dev/vg_data/lv_mpg: * FILE SYSTEM WAS MODIFIED * The system has 4GB of memory and a 8GB swap partition. The filesystem has 7TB. Is there a quick way to enlarge the swap space to help fsck.ext4 to finish the repair? I do not have any unused partitions but have space for swap on other filesystems if that is possible.
Re: systemd nfs mount blocked until first entered
I think I found a solution! For whatever reason, my network interface enp5s11 was not in the "auto" line in /etc/network/interfaces. After adding it there and a reboot, the filesystem is mounted correct without any of the x-systemd mount options. Am Fr., 2. Juli 2021 um 19:30 Uhr schrieb Reiner Buehl < reiner.bu...@gmail.com>: > Hello, > > this is the full unit: > > # /etc/systemd/system/vdr.service > [Unit] > Description=Video Disk Recorder > > Wants=systemd-udev-settle.service > After=systemd-udev-settle.service > > [Service] > Type=notify > ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh "commands" > ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh "reccmds" > ExecStart=/usr/bin/vdr > Restart=on-failure > RestartPreventExitStatus=0 2 > > [Install] > WantedBy=multi-user.target > > # /etc/systemd/system/vdr.service.d/override.conf > [Unit] > After=remote-fs.target > Requires=remote-fs.target > > I only added the x-systemd options to /etc/fstab because the filesystems > where not mounted at boot time at all with the old fstab options that I > used before the upgrade to Debian (I did use yavdr before - a distro that > was based on a super old 12.x version of Ubuntu). There I just used > > 192.168.1.2:/video /video nfs > defaults,rsize=8192,wsize=8192,soft,nolock,noatime 0 0 > > If I try with this entry, the auto-generated video.mount unit fails as it > seems to be started too early: > > ● video.mount - /video >Loaded: loaded (/etc/fstab; generated) >Active: failed (Result: exit-code) since Fri 2021-07-02 19:26:02 CEST; > 2min 46s ago > Where: /video > What: 192.168.1.2:/video > Docs: man:fstab(5) >man:systemd-fstab-generator(8) > > Jul 02 19:26:02 vdr systemd[1]: Mounting /video... > Jul 02 19:26:02 vdr mount[403]: mount.nfs: Network is unreachable > Jul 02 19:26:02 vdr systemd[1]: video.mount: Mount process exited, > code=exited, status=32/n/a > Jul 02 19:26:02 vdr systemd[1]: video.mount: Failed with result > 'exit-code'. > Jul 02 19:26:02 vdr systemd[1]: Failed to mount /video. > > Best regards, > Reiner > > Am Fr., 2. Juli 2021 um 19:15 Uhr schrieb Reco : > >> Hi. >> >> On Fri, Jul 02, 2021 at 06:12:58PM +0200, Reiner Buehl wrote: >> > I have a directory that is mounted via NFS from a remote server. >> >> Actually, you have an autofs mountpoint, because you set >> x-systemd.automount option in fstab. >> Only if something starts using that mountpoint an NFS filesystem should >> be mounted there. >> >> In another words - you do not require your NFS filesystem to be mounted >> at boot time, and thus remote-fs.target does not include your NFS >> filesystem. >> >> >> > If I boot the vdr daemon fails during startup with the error message >> >> In other words, vdr fails to trigger automounting of the filesystem in >> question. As usual with journald, the actual reason of this is not >> present in this log. >> >> >> > The vdr.service has an override of >> > >> > [Unit] >> > After=remote-fs.target >> > Requires=remote-fs.target >> > >> > to ensure that the filesystem is mounted. >> >> These dependencies are useless for your service given the current state >> of your fstab. >> The reason being - "autofs" filesystems belong to local-fs.target, not >> remote-fs.target, and explicitly depending on local-fs.target is useless >> anyway (it's one of the default dependencies for the most units). >> What you probably need here is a dependency for a .mount unit >> corresponding to your NFS filesystem. >> >> >> > If I try to restart vdr.service, it fails again with the same error but >> if >> > I just cd to the directory and then try to restart it, it starts and >> works >> > fine. >> >> Can you show the result of "systemctl cat vdr" please? >> >> > What is systemd doing here that blocks the mount point for the vdr >> process? >> >> Many things are possible here. You have ProtectSystem=full set in unit, >> or you have PrivateMounts=true set in there. >> >> > Do I need different fstab options? >> >> It depends. x-systemd.automount is useful, because it does not require >> your NFS server to be present at boot time. >> I'll refrain from suggesting certain hacks for now, I'd like to see your >> unit in full first. >> >> Reco >> >>
Re: systemd nfs mount blocked until first entered
Hello, this is the full unit: # /etc/systemd/system/vdr.service [Unit] Description=Video Disk Recorder Wants=systemd-udev-settle.service After=systemd-udev-settle.service [Service] Type=notify ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh "commands" ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh "reccmds" ExecStart=/usr/bin/vdr Restart=on-failure RestartPreventExitStatus=0 2 [Install] WantedBy=multi-user.target # /etc/systemd/system/vdr.service.d/override.conf [Unit] After=remote-fs.target Requires=remote-fs.target I only added the x-systemd options to /etc/fstab because the filesystems where not mounted at boot time at all with the old fstab options that I used before the upgrade to Debian (I did use yavdr before - a distro that was based on a super old 12.x version of Ubuntu). There I just used 192.168.1.2:/video /video nfs defaults,rsize=8192,wsize=8192,soft,nolock,noatime 0 0 If I try with this entry, the auto-generated video.mount unit fails as it seems to be started too early: ● video.mount - /video Loaded: loaded (/etc/fstab; generated) Active: failed (Result: exit-code) since Fri 2021-07-02 19:26:02 CEST; 2min 46s ago Where: /video What: 192.168.1.2:/video Docs: man:fstab(5) man:systemd-fstab-generator(8) Jul 02 19:26:02 vdr systemd[1]: Mounting /video... Jul 02 19:26:02 vdr mount[403]: mount.nfs: Network is unreachable Jul 02 19:26:02 vdr systemd[1]: video.mount: Mount process exited, code=exited, status=32/n/a Jul 02 19:26:02 vdr systemd[1]: video.mount: Failed with result 'exit-code'. Jul 02 19:26:02 vdr systemd[1]: Failed to mount /video. Best regards, Reiner Am Fr., 2. Juli 2021 um 19:15 Uhr schrieb Reco : > Hi. > > On Fri, Jul 02, 2021 at 06:12:58PM +0200, Reiner Buehl wrote: > > I have a directory that is mounted via NFS from a remote server. > > Actually, you have an autofs mountpoint, because you set > x-systemd.automount option in fstab. > Only if something starts using that mountpoint an NFS filesystem should > be mounted there. > > In another words - you do not require your NFS filesystem to be mounted > at boot time, and thus remote-fs.target does not include your NFS > filesystem. > > > > If I boot the vdr daemon fails during startup with the error message > > In other words, vdr fails to trigger automounting of the filesystem in > question. As usual with journald, the actual reason of this is not > present in this log. > > > > The vdr.service has an override of > > > > [Unit] > > After=remote-fs.target > > Requires=remote-fs.target > > > > to ensure that the filesystem is mounted. > > These dependencies are useless for your service given the current state > of your fstab. > The reason being - "autofs" filesystems belong to local-fs.target, not > remote-fs.target, and explicitly depending on local-fs.target is useless > anyway (it's one of the default dependencies for the most units). > What you probably need here is a dependency for a .mount unit > corresponding to your NFS filesystem. > > > > If I try to restart vdr.service, it fails again with the same error but > if > > I just cd to the directory and then try to restart it, it starts and > works > > fine. > > Can you show the result of "systemctl cat vdr" please? > > > What is systemd doing here that blocks the mount point for the vdr > process? > > Many things are possible here. You have ProtectSystem=full set in unit, > or you have PrivateMounts=true set in there. > > > Do I need different fstab options? > > It depends. x-systemd.automount is useful, because it does not require > your NFS server to be present at boot time. > I'll refrain from suggesting certain hacks for now, I'd like to see your > unit in full first. > > Reco > >
systemd nfs mount blocked until first entered
Hi all, I have a directory that is mounted via NFS from a remote server. The mount is done via an /etc/fstab entry like this: 192.168.1.2:/video /video nfs defaults,x-systemd.automount,x-systemd.requires=network-online.target,x-systemd.device-timeout=10,rsize=8192,wsize=8192,soft,nolock,noatime 0 0 If I boot the vdr daemon fails during startup with the error message vdr.service - Video Disk Recorder Loaded: loaded (/etc/systemd/system/vdr.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/vdr.service.d └─override.conf Active: failed (Result: exit-code) since Thu 2021-07-01 23:27:25 CEST; 8h ago Process: 523 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh commands (code=exited, status=0/SUCCESS) Process: 533 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh reccmds (code=exited, status=0/SUCCESS) Process: 543 ExecStart=/usr/bin/vdr (code=exited, status=2) Main PID: 543 (code=exited, status=2) Jul 01 23:27:25 vdr systemd[1]: Starting Video Disk Recorder... Jul 01 23:27:25 vdr vdr[543]: [543] ERROR: can't access /video Jul 01 23:27:25 vdr vdr[543]: vdr: can't access video directory /video Jul 01 23:27:25 vdr systemd[1]: vdr.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Jul 01 23:27:25 vdr systemd[1]: vdr.service: Failed with result 'exit-code'. Jul 01 23:27:25 vdr systemd[1]: Failed to start Video Disk Recorder. The vdr.service has an override of [Unit] After=remote-fs.target Requires=remote-fs.target to ensure that the filesystem is mounted. If I try to restart vdr.service, it fails again with the same error but if I just cd to the directory and then try to restart it, it starts and works fine. What is systemd doing here that blocks the mount point for the vdr process? Do I need different fstab options? Best regards, Reiner
Re: Add /dev/disk/by-id path to mdadm error emails?
That seems perfect. Many thanks! Am Fr., 4. Juni 2021 um 15:10 Uhr schrieb Dan Ritter : > Reiner Buehl wrote: > > Hello all, > > > > I have setup mdadm to email me when disks in one of my RAID arrays fail. > > Unfortunately the email messages only contain the device as /dev/sdb1 > which > > does not give any hint which of the four identical disks in the array is > > the affected one. > > As /dev/sdb1 is only a symbolic link to a device in /dev/disk/by-id and > > that device contains the serial number of the disk, I was wondering if > > there is a way to add the /dev/disk/by-id information - or just a ls -l > > /dev/disk/by-id - to that email that would allow me to see which disk > > really is the failed one? > > > --prefer= > When mdadm needs to print the name for a device it > normally finds the name in /dev which refers to the device > and is shortest. When a path component is given with > --prefer mdadm will prefer a longer name if it contains > that component. For example --prefer=by-uuid will > prefer a name in a subdirectory of /dev called by-uuid. > This functionality is currently only provided by --detail > and --monitor. > > If you have a cron job to run mdadm -F, this can be added. If > you have a system service to run mdadm -F in daemon mode, that > can be edited to include --prefer=by-id > > -dsr- >
Add /dev/disk/by-id path to mdadm error emails?
Hello all, I have setup mdadm to email me when disks in one of my RAID arrays fail. Unfortunately the email messages only contain the device as /dev/sdb1 which does not give any hint which of the four identical disks in the array is the affected one. As /dev/sdb1 is only a symbolic link to a device in /dev/disk/by-id and that device contains the serial number of the disk, I was wondering if there is a way to add the /dev/disk/by-id information - or just a ls -l /dev/disk/by-id - to that email that would allow me to see which disk really is the failed one? Best regards, Reiner
Cacti logfile access error after upgrade Stretch -> Buster
Hi all, after upgrading from Debian Stretch (cacti 0.8.x) to Buster (cacti 1.2.x), I can't access the cacti web ui anymore. I only get a message "System log file is not available for writing, please enable write access Log: /usr/share/cacti/site/log/cacti.log" in the browser. Am I missing some upgrade steps here? Best regards, Reiner
Re: key "cdrom" not found in map source(s).
Here the complete grep cdrom /var/log/syslog: Jul 7 10:48:44 bilbo automount[31697]: key "cdrom" not found in map source(s). Jul 7 11:35:04 bilbo automount[31697]: key "cdrom" not found in map source(s). Jul 7 11:39:20 bilbo automount[31697]: key "cdrom" not found in map source(s). Jul 7 11:40:38 bilbo automount[31697]: key "cdrom" not found in map source(s). Jul 7 14:10:41 bilbo automount[31697]: key "cdrom" not found in map source(s). Jul 7 14:33:05 bilbo automount[31697]: key "cdrom" not found in map source(s). Jul 7 14:39:05 bilbo automount[31697]: key "cdrom" not found in map source(s). Jul 7 15:42:33 bilbo automount[31697]: key "cdrom" not found in map source(s). Jul 7 16:59:00 bilbo automount[31697]: key "cdrom" not found in map source(s). Jul 7 17:00:36 bilbo automount[31697]: key "cdrom" not found in map source(s). Jul 7 18:23:37 bilbo automount[31697]: key "cdrom" not found in map source(s). Best regards, Reiner Am Mo., 6. Juli 2020 um 08:05 Uhr schrieb Andrei POPESCU < andreimpope...@gmail.com>: > On Lu, 06 iul 20, 07:49:09, Reiner Buehl wrote: > > Hello, > > > > I keep getting messages from syslog "key "cdrom" not found in map > > source(s)." on the console of my Debian Stretch system but I don't even > > have a cd rom installed in this system. > > > > I already checked /etc/fstab, /etc/samba/smb.conf, /etc/autofs.conf and > all > > the /etc/auto.* files as this message normally points to wrong NFS or > other > > file system exports. I also checked the output of exportfs and did reboot > > many times but I can't get rid of these messages. > > > > Do you have any idea what else could cause them? > > Please post the entire log / dmesg entry (copy-paste). > > Kind regards, > Andrei > -- > http://wiki.debian.org/FAQsFromDebianUser >
key "cdrom" not found in map source(s).
Hello, I keep getting messages from syslog "key "cdrom" not found in map source(s)." on the console of my Debian Stretch system but I don't even have a cd rom installed in this system. I already checked /etc/fstab, /etc/samba/smb.conf, /etc/autofs.conf and all the /etc/auto.* files as this message normally points to wrong NFS or other file system exports. I also checked the output of exportfs and did reboot many times but I can't get rid of these messages. Do you have any idea what else could cause them? Best regards, Reiner
Re: Re: Select between 686-pae and amd64 kernel in Grub?
Many thanks, Floris! With your expression I now see the other options:
bilbo:~# awk -F"'" '/menuentry/ {print $2}' /boot/grub/grub.cfg
Debian GNU/Linux
Advanced options for Debian GNU/Linux
Debian GNU/Linux, with Linux 4.9.0-7-686-pae
Debian GNU/Linux, with Linux 4.9.0-7-686-pae (sysvinit)
Debian GNU/Linux, with Linux 4.9.0-7-686-pae (recovery mode)
Debian GNU/Linux, with Linux 4.9.0-7-amd64
Debian GNU/Linux, with Linux 4.9.0-7-amd64 (sysvinit)
Debian GNU/Linux, with Linux 4.9.0-7-amd64 (recovery mode)
Debian GNU/Linux, with Linux 4.9.0-6-686-pae
Debian GNU/Linux, with Linux 4.9.0-6-686-pae (sysvinit)
Debian GNU/Linux, with Linux 4.9.0-6-686-pae (recovery mode)
Debian GNU/Linux, with Linux 4.9.0-5-686-pae
Debian GNU/Linux, with Linux 4.9.0-5-686-pae (sysvinit)
Debian GNU/Linux, with Linux 4.9.0-5-686-pae (recovery mode)
Do you know if just specifying "Debian GNU/Linux, with Linux 4.9.0-7-amd64"
as option to grub-set-default is enough or do I need to somehow "navigate"
into the "Advanced options for Debian GNU/Linux" sub menu?
Best regards,
Reiner
Re: RAID1 with multiple partitions
On 10.12.2010 21:15, David Gaudine wrote: The system works, but I still have some questions about whether what I've already done is OK. 1) Is it OK to use 4 MD arrays like this, or should I use just one and LVM like the jerryweb link? I got a bit confused reading about LVM and I don't need anything fancy like being able to resize partitions. I personally prefer LVM as it gives me more flexibility, but if you do not need that, the setup you selected is fine. 2) I put the SWAP partition on RAID. The first guide doesn't use RAID for swap. The author emailed me his comments about the pros and cons, and I think I want it on RAID for peace of mind. It shouldn't really matter since I have much more RAM than I need. Is there any reason I might regret putting SWAP on RAID? cat /proc/mdstat reports the MD1 (the swap device) as auto-read-only. In Linux, all raid arrays stay in auto-read-only mode until they are access the first time after each reboot, so this seems to imply that your system has not yet initialized the swap. Did you add your swap to /etc/fstab and mark it as swap there? 3) The first guide doesn't use a separate boot partion, the second does. Comments? I've never used a separate boot partition. I think it used to be important on large disks, to keep the kernel in the first 1024 cylinders, but isn't important anymore. A separate boot partition still makes sense for example if you would like to use a root file system that is not directly supported by your boot manager. I am not sure if the 1024 cylinders border is still valid. Maybe somebody else can comment on this? 4) The first guide shows how to install Grub on both disks. After that's done once, do I have to do it again whenever there's a new kernel package? Or in any other situation that I have to watch out for? You only need to install grub on both disks once. After that, there is no need to repeat that again unless you upgrade grub itself. For the other two questions, I cannot say anything. Hope this helps. Regards, Reiner. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d029285.2090...@buehl.net
Cannot create raid5 with 4 disks corectly
Hi all, on my Debian Lenny system (with latest updates), I have the following problem: I would like to create another RAID5 array consisting of 4 2TB disks. When creating the array with /sbin/mdadm --create --verbose /dev/md5 --level=5 --raid-devices=4 /dev/sdm1 /dev/sdn1 /dev/sdo1 /dev/sdp1 the array is created but with one failed disk and a spare instead of 4 working disks: bilbo:~# mdadm --detail /dev/md5 /dev/md5: Version : 00.90 Creation Time : Sat Dec 4 12:55:01 2010 Raid Level : raid5 Array Size : 5860540416 (5589.05 GiB 6001.19 GB) Used Dev Size : 1953513472 (1863.02 GiB 2000.40 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 5 Persistence : Superblock is persistent Update Time : Sat Dec 4 12:55:01 2010 State : clean, degraded Active Devices : 3 Working Devices : 4 Failed Devices : 0 Spare Devices : 1 Layout : left-symmetric Chunk Size : 64K UUID : cd14d406:2f66f930:ac80d277:73fa76dc (local to host bilbo.lan.buehl.net) Events : 0.1 Number Major Minor RaidDevice State 0 8 1930 active sync /dev/sdm1 1 8 2091 active sync /dev/sdn1 2 8 2252 active sync /dev/sdo1 3 003 removed 4 8 241- spare /dev/sdp1 The funny thing is, that this is not related to one disk: If I change the order of the devices in the mdadm command line, another device gets marked as spare instead of /dev/sdp1. It is always the device that was specified last in the mdadm --create command line. dmesg shows no obvious errors and gives no hint, why one disk is not added and is treated as spare instead: [ 5634.208141] md: bindsdm1 [ 5634.216134] md: bindsdn1 [ 5634.224044] md: bindsdo1 [ 5634.231632] md: bindsdp1 [ 5634.273202] raid5: device sdo1 operational as raid disk 2 [ 5634.273210] raid5: device sdn1 operational as raid disk 1 [ 5634.273214] raid5: device sdm1 operational as raid disk 0 [ 5634.273470] raid5: allocated 4222kB for md5 [ 5634.273555] 2: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 [ 5634.273557] 1: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 [ 5634.273558] 0: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 [ 5634.273560] raid5: raid level 5 set md5 active with 3 out of 4 devices, algorithm 2 [ 5634.273562] RAID5 conf printout: [ 5634.273563] --- rd:4 wd:3 [ 5634.273564] disk 0, o:1, dev:sdm1 [ 5634.273566] disk 1, o:1, dev:sdn1 [ 5634.273567] disk 2, o:1, dev:sdo1 [ 5634.273588] md5: detected capacity change from 0 to 6001193385984 [ 5634.275048] md5: unknown partition table Any ideas how I can fix this? Regards, Reiner Buehl. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cfa3a84.2070...@buehl.net
Use RAID1 mirror as backup during dist-upgrade?
Hi all, I have a Debian Etch system that runs on a RAID 1 software raid system. now I would like to upgrade it to Lenny by splitting the mirror off and keep one mirror as a backup. Alternatively I could add a third disk as a second mirror and split off this one. If the upgrade works, I then add in the old disk again. If it fails I'd like to be able to rebuild the array using the OLD mirror that I kept. Does anybody have a more detailed description on how to do this? I know I can fail a drive with mdadm, but my understanding is that the data on this this drive can't then be used again after that. Is that correct or can the bad upgrade disk be failed and then the old disk un-failed? How would I tell the system which disk to use? What preparation steps are necessary other than making both/all mirrors bootable? Best regards, Reiner. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Kaputte Threads
Antworten. Denn laut Andreas setzt Outlook dann doch die Header. Das wundert mich zwar etwas, aber da ich es nicht überprüft habe, glaube ich das jetzt einfach mal. Ich denke ein Allen-Antworten müsste in Outlook richtik sein, da bei einem einfachen Antworten die Mail an den Orginal-Poster geht und nicht mehr an die Liste. Daher Reply-to-all und alles ausser der Liste aus dem AN: Feld löschen. Alternativ solltest Du Dir vielleicht mal Thunderbird ansehen. Immerhin wird dann das lesen der Liste auch für Dich angenehmer. Denn der kann auch nach Threads sortieren und Redner farbig markieren. Aber letztendlich ist das ja Leider können es sich viele nicht aussuchen, welchen Mailer sie verwenden... ich persönlich muss von der Firma aus Outlook/Exchange verwenden und rege mich täglich über die mutt-User hier auf, die meinen sie müssten den Outlook Benutzern irgendwelche nützlichen Tipps zur Mailer-Wahl im Message Header unterbringen! Gruß, Reiner. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Beobachten von log-Files
Hallo Ulrich, Nach dem starten funktionierte das ganze auch für ca. 1 Stunde. danach ist zwar noch der Prozess vorhanden root 3686 0.0 0.2 4200 1204 ?Ss 12:21 0:00 /bin/sh -c tail -f /var/log/mail/procmail.log | egrep 'Folder| Subject:|Match' /var/log/ma[...] Kann es sein, das genau nach einer Stunde das Logfile rotiert wurde? Das würde das verhalten zumindest erklären. Dein nach dem reboot gestarteter tail schaut dann nämlich weiterhin auf den selben Inode, der aber jetzt das file procmail.log.1 oder so repräsentiert und procmail schreibt munter in das neue log. Beim manuellen aufrufen des Kommandos gehst Du dann wieder auf den neuen Inode, daher kommen auch wieder Einträge an. Gruß, Reiner. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Benutzer darf nur su
Was Du haben möchtest geht mit einer restricted Shell. Schau mal in die bash man page und such nach restricted. bash -r sollte der Aufruf sein, wenn ich mich recht erinnere. Hätte man so wohl auch im Archiv dieser Liste gefunden... Gruß, Reiner. Hallo Leute, in welcher Datei kann ich einstellen was der Benutze auf Konsole ausführen darf? Ich habe eine Benutzer und möchte das dieser nur den su Befehl ausführen kann sonst aber keinen anderem nichtmal vi oder date. Wo kann man das konfigurieren habe da noch nicths zu gefunden. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl) -- .._/. Reiner Buehl_/ Hewlett-Packard GmbH _/_/_/_/ _/_/_/_/ Consulting Integration _/_/ _/_/ Mailstop ESD1_/_/ _/_/ Mail: [EMAIL PROTECTED] 71034 Boeblingen_/_/ _/_/_/_/ Phone: (+49) 7031 14-6701 Germany _/ Fax: (+49) 7031 14-4961 ._/.. Hewlett-Packard GmbH, Herrenberger Str. 140, D-71034 Böblingen, Germany http://www.hp.com/de Geschäftsführer: Jörg Menno Harms (Vorsitzender), Jürgen Banhardt, Wolfram Fischer, Rainer Kaczmarczyk, Bärbel Schmidt, Fritz Schuller, Regine Stachelhaus Vorsitzender des Aufsichtsrates: Heribert Schmitz Sitz der Gesellschaft: Böblingen, Amtsgericht Böblingen HRB 4081 . -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: SSH Passphrase geht nicht
Hallo Saskia, hast Du schon mal versucht, den Client-Schlüssel mit Putty auf dem Client zu erzeugen und in dann von dort ins authorized_keys file auf dem Server zu kopieren? So mache ich das immer und hatte damit noch nie Probleme. Gruß, Reiner. Hallo Leute, ich habe hier ja schon öfter mal was zu ssh gepostet. Mein jetziges Problem besteht darin das ich kein Client Schlüssel verwenden kann die eine Passphrase enthalten. Erstelle ich Schlüssel mit Passphrase bekomme ich in Putty immer die Antwort Server refused our key. Mache ich es ohne Passphrase funktioniert es. Ich wollte aber das der leint eine Passphrase eingeben muss. Aus diesem Grund beschreibe ich hier einmal kurz mein vorgehen vielleicht könnt Ihr mir ja sagenwas ich falsch mache. - Mein System Debian 3.1 Sarge - Kernel 2.6.8-2-686 - ssh -v ergibt OpenSSH 3.8.1p1 Debian-8.sarge.4 , OpenSSL 0.9.7e 25 Oct 2004 - SSH ist von einem stable Server - in der SSH Conf ist alles ist nichts veränder worden ausser das ich die Raute # vor AuthorizedKeysFile weg genommen habe - dann habe ich die Schlüssel für den Server mittels ssh-keygen -b 2048 -t rsa ohne Passphrase gebildelt. In der SSH Conf habe ich dann bei HostKey /etc/ssh/server angegeben (server heisst der private Key für den Server) - danach habe ich mittels ssh-keygen -b 2048 -t rsa die Client Schlüssel mit Passphrase erstellt. danach den Client public key mittel cp /etc/ssh/client.pub nach /home/client/.ssh/authorized_keys kopiert und die Rechte auf chmod 600 authorized_keys gesetzt. authorized_keys gehört dem Benutzer client und der Gruppe client (nur mal so als Info). - jetzt habe ich mir den privaten Schlüssel des client auf diskette gezogen und danach auf meine Windows Rechner gebracht. - Dann habe ich Puttygen geöffnet und über Conversion \ import key den private key eingelesen. Dabei habe ich die Passphrase des private Client Key eingeben weil danach gefragt wurde. Anschließend habe ich durch save private Key den Schlüssel gespeichert. Im Verzeicnis habe ich dann die Datei mir Endung .ppk. - Putty geöffnet Ip und Port angegeben und unter SSH \ Auth den Pfad zum Key angegebn - beim Login werde ich nach dem Benutzenamen gefragt. Diesen geben ich auch an und dann kommt Server refused our key und er schaltete auf normal Passwortabfrage um. Könnt ihr mir sagen was ich falsch gemacht bzw. vergessen habe? -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl) -- .._/. Reiner Buehl_/ Hewlett-Packard GmbH _/_/_/_/ _/_/_/_/ Consulting Integration _/_/ _/_/ Mailstop ESD1_/_/ _/_/ Mail: [EMAIL PROTECTED] 71034 Boeblingen_/_/ _/_/_/_/ Phone: (+49) 7031 14-6701 Germany _/ Fax: (+49) 7031 14-4961 ._/.. Hewlett-Packard GmbH, Herrenberger Str. 140, D-71034 Böblingen, Germany http://www.hp.com/de Geschäftsführer: Jörg Menno Harms (Vorsitzender), Jürgen Banhardt, Wolfram Fischer, Rainer Kaczmarczyk, Bärbel Schmidt, Fritz Schuller, Regine Stachelhaus Vorsitzender des Aufsichtsrates: Heribert Schmitz Sitz der Gesellschaft: Böblingen, Amtsgericht Böblingen HRB 4081 . -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: ntpd stirbt immer wenn Internetverbindung kurz weg ist
Dies tritt immer dann auf, wenn die Verbindung zum Internet kurz weg ist. Das ist ein bekanntes Problem des ntpd für das es meines Wissens nach (noch) keine Lösung gibt. Der ntpd macht, wenn das Interface kurz weg war keinen Reconnect mehr sondern hängt nur noch rum. Eine Möglichkeit dies zu umgehen hast Du, wenn Du den ntpd nicht auf dem Rechner laufen läßt, mit dem die Internet-Verbindung hergestellt wird. Das Problem tritt nämlich nicht auf, wenn der ntpd über einen Router geht. Wegen der Zeitdifferenz von einer Stunde würde ich auf eine Fehleinstellung bei der CMOS Uhr tippen. Ist die auf UTC und weiss das Linux auch? Normalerweise wird die mit hwclock ausgelesen und in die Systemzeit übertragen. Wenn dabei hwclock mit den falschen Parametern gestartet wird, kann es genau zu sowas kommen. Gruß, Reiner. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Keine Tastatur mehr nach update auf 2.6.11
Hallo, mit dem Sid 2.6.11 Kernel Paket funktioniert bei meinem Sarge System meine Tastatur nicht mehr! Am LILO-Prompt funktioniert die Tastatur noch, das System fährt normal hoch, akzeptiert dann aber am Login-Prompt keine Tastatur-Eingaben mehr. Einfügen von Text per Maus über gpm funktioniert, nur die PS/2-Tastatur wird nicht erkannt. Brauche ich für den Kernel spezielle Device Files? Login per ssh klappt auch und mit dem alten 2.4.27 klappt auch alles... Gruß, Reiner.
RE: Problem Debian Neuinstallation und DSL
Hallo, hast Du mal geschaut, was pppoe -I eth0 -A zurückliefert? Das sollte Dir die MAC Adresse und den Namen des Access Concentrators liefern. Schau auch mal, ob nicht vielleicht ein übereifriges Konfigurations- Script dem Netzwerk-Interface eine IP-Adresse verpasst hat oder versucht sich eine per DHCP zu besorgen. Das interface sollte im ifconfig output als UP angegeben sein, sonnst sollten aber vor dem start des pppoe keine IP einstellungen wie IP-Adresse, Netmask, o.ä. eingestellt sein. Gruß, Reiner. -Original Message- From: Andreas Hannemann [mailto:[EMAIL PROTECTED] Sent: Sunday, July 03, 2005 9:45 AM To: debian-user-german@lists.debian.org Subject: Re: Problem Debian Neuinstallation und DSL Am Sonntag, 3. Juli 2005 08:02 schrieb Andreas Hannemann: Am Sonntag, 3. Juli 2005 00:40 schrieb Walter Saner: Andreas Hannemann schrieb: habe mir nen Schlepptop zugelegt und war vorhin dabei Debian darauf zu installieren. Ich wollte allerdings eine Net-Installation über DSL machen. Hi,... Habe heute morgen nochmals eine Neuinstallation, diesmal mit einer aktuellen Netinst CD gemacht,... dort sucht der pppoeconf ebenfalls noch den Access Concentrator und findet nichts,(so wie ich gesehen habe, bekommt ein ein timeout zurück, das blinkte kurz auf)...immerhin wurde die Hardware erkannt.(RTL-8169) Kabel rausgerupft, in meinen Desktop gesteckt,. einmal pon dsl-provider getippt und schon war ich wieder online, woran kann das noch liegen? Bin mit meinem Latein am Ende,... Habe übrigens einen Wortmann terra aura 1710K AMD 3000+, ansonsten ein sehr geniales Gerät...leise, sehr großem Display... MfG Andreas -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.8.8/37 - Release Date: 01.07.2005
RE: [OT] Kernel ohne modul support
PS Die config des 2.4.30 mit Modul unterstützung habe ich übernommen nur eben dann die Unterstützung deaktiviert. Kann es sein, das dabei irgendwelche Treiber für Netzwerk-Protokolle nicht übernommen worden sind? Oder Firewall-Module, oder ... ich denke ohne nähere Angabe zu Deiner Kernel-Config wirds schwer da was zu sagen. Wie äussert sich den das funktionieren der Karten? Werden sie nur vom Kernel erkannt oder wird ihnen auch eine IP-Adresse zugewiesen? Was sagen den Programme wie ifconfig, iptables, route u.ä.? Gruß, Reiner.
