prompt stringlengths 1 63.6k | completion stringlengths 1 53.1k |
|---|---|
Hi, all in order to use secureboot with the liquorix kernel I made a self-signed certificate, today I made a new one and after a reboot when I type the command: Code: Select allmokutil --sb-state it returns This system doesn't support Secure Boot but it does. Afterwards when I enable or disable secureboot in bios the kernel with/without signature still goes through Any idea how to fix that? | I'm no expert on Secure Boot but I believe the kernel must be signed. Liquorix kernel is not signed. Code: Select allosslsigncode extract-signature -in /boot/vmlinuz-6.7.12-1-liquorix-amd64 -out kernel.sig PE file does not have any signature: /boot/vmlinuz-6.7.12-1-liquorix-amd64 Failed |
I've been running my own certificate authority on my home network for well over ten years now, and it's been working fine. Now it's time to make a new once, since the old one expires soon. So I created one, just as before, using "openssl ca". Had a little trouble with changing requirements (my old openssl.cnf still mentioned Netscape!), but at last I finished it and used it to create a server certificate. After a lot of fiddling and reading instructions, my iPad works with it, my iPhone works with it, Firefox on Linux likes it, and it even works on Windows. The only boxes that don't like it are my three Debian boxes (one testing, two stable). Aptitude and "apt-get update" fail on reading my local repository (containing stuff I've written): its server is running Apache2, using the new CA and server certificate. When I run apt-get update, for example, I get Err:1 https://www.mydomain.net/Debian local InRelease Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. [IP: 192.168.x.x 443] I've tried lots of suggestions that I've seen on the net. I have the CA certificate in /usr/share/ca-certificates, I've run "dpkg-reconfigure ca-certificates", I've run "update-ca-certificates" (with and without "--fresh"), but nothing seems to help. Suggestions appreciated. | rjmx wrote: 2024-05-07 22:29 How do I mark this topic as solved? (Sorry, I don't do this very often). You can mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message (after other tags, if any). It is also an opportunity to the make the subject more understandable to other forum users and readers, if necessary; i.e. : [Solved] apt don't recognise the CA certificate of my local https repository Happy Debian ! EDIT Wed May 15 19:46:58 CEST 2024: discussion marked as solved. |
Dear all, As of late, I experience the following issues with regard to my following Samba setup: I am running a Debian 12 Bookworm instance on my desktop in conjunction with a Debian 11 Bullseye instance on my server. Both boxes are up-to-date regarding maintenance updates. When mounting my Samba share on my desktop via Nautilus --> Other locations --> Connect to server --> "smb://server/share", I can perform the following file operations without difficulties within Nautlius: 1. copying files from a desktop folder to the Samba share 2. copying files from the Samba share to a desktop folder 3. copying files within the Samba share However, problems emerge when instead mounting the Samba share via /etc/fstab: //server/share /home/user/share cifs credentials=/home/user/.cifs-credentials,uid=1000,gid=100 0 1 Suddenly, copying files within the Samba share (see #3 above) stalls at the beginning of the first file: Though created, no content is being copied. Nautilus indicates that open and active operations exist. When performing the same operation on the command line, the cp command is terminated with the error message "Killed". In such a situation, /proc/fs/cifs/open_files on the desktop exhibits according entries. The desktop shut down procedure would run into a timeout. To prevent this from happening, the Samba share has first to be unmounted via: umount --force --lazy /home/user/share Most interestingly, file operations from or to local folders remain possible (see #1 and #2 above). I am a bit puzzled about the sudden emergence of this error on an otherwise stable configuration: My samba configuration has not changed for *ages*. My overall server configuration has not been touched for at least a month. The only reason I can think of are the above maintenance updates executed on a regular basis on both the desktop and the server (and that I might not have paid enough attention to lately). And I am a bit puzzled about the next steps that I could take to tackle this issue. Has anybody experienced the same or similar issues lately? Or could somebody at least point me into the right direction for solving this issue? I will gladly share more information but am a bit clueless about where to start. Thanks in advance! | Hello, Take a look at this discussion: [Solved] Help investigating/reporting possible kernel bug with SMB Hope this helps. Let me know. |
Hello, I try to use dm-verity to check my rootfs but always get the following error: device-mapper: table: 253:0: verity: Data device lookup failed (-ENXIO) I recompile the kernel with the configuration attached I booted from a live Linux, run the command veritysetup format /dev/sda2 /dev/sda3 Then modify the grub.cfg to add the md-mod.create to the kernel parameter with the value given by the previous command as following dm-mod.create="verity,,,ro,0 131072 verity 1 /dev/sda2 /dev/sda3 4096 4096 16384 1 sha256 hash salt 0 " Did I miss a step or a config somewhere? Best regards Alexandre | Hello, afr wrote: 2024-05-07 01:49 Then modify the grub.cfg to add the md-mod.create to the kernel parameter with the value given by the previous command as following dm-mod.create="verity,,,ro,0 131072 verity 1 /dev/sda2 /dev/sda3 4096 4096 16384 1 sha256 hash salt 0 " I'm not an expert of dm-verify, but the parameter for dm-verity kernel module the grub.cfg (sent as attachment) looks like are different from the ones quotes in the post above: Code: Select all[..] menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-682a05ae-5b0a-42a7-b998-b0674a3fd8b6' { load_video [..] echo 'Loading Linux 6.1.85 ...' linux /boot/vmlinuz-6.1.85 ro dm-mod.create=\"verity,,,ro,0 156250112 verity 1 8:2 8:3 4096 4096 19531264 1 sha256 d667cd79057ae7b67846bac7a69dd2a8248b780f66d7ee0b9aa5610789ce2b55 21b6353c4cbff01b734604e559cb1d62246445e3097e08387a5656769932d9e9 0 \" root=/dev/dm-0 quiet ### linux /boot/vmlinuz-6.1.85 root=UUID=682a05ae-5b0a-42a7-b998-b0674a3fd8b6 ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-6.1.85 } Hope it helps. |
For a couple of days, DNS resolving does not work anymore (but ping does). I tried several DNS servers, all with the same problem. In addition, I noticed that probably my CMOS battery died (at least there is a preboot message "time of day not set" and the date / time is not saved between system boots). When I manually set the correct date / time as a workaround, DNS resolving works again. I would like to understand how DNS resolving and system date / time are connected and why DNS resolving does not work when the date / time are incorrect. | The short answer is that DNS Security Extensions require a valid client timestamp. This article is a little old but explains things fairly well - https://arstechnica.com/information-tec ... ate-chaos/ Hope this helps clear things up - |
I've got a slew of old machines with Gforce 6xx cards in them and I attempt to install the older legacy driver, but lots of messages similar to the following: Code: Select allden:~$ Z apt-get install nvidia-alternative Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: nvidia-alternative : PreDepends: nvidia-legacy-check (>= 396) but it is not going to be installed Depends: glx-alternative-nvidia (>= 1.2) but it is not installable E: Unable to correct problems, you have held broken packages. den:~$ This is in old-stable and I don't want to update those machines. Thoughts? I then attempted to install the vendor supplied drivers directly from nvidia but Debian isn't very friendly toward that packaging channel. Seems it wants me to not only install all the kernel source for "exactly my kernel version", but also to build the kernel so that the version.h file exists. Not interested in jumping thru those hoops. | Of course this would all be irrelevant if there was a way to do monitor calibration with the nouveau driver...none exists, that I'm aware of. |
I have installed a few days ago Debian 12 (Bookworm) in a dualboot setup together with Windows 10. However, i have an (inconsistent, usually presents when I use the OS for more than 5/10 minutes) issue: when I shutdown my pc (a Lenovo ThinkBook 15 ACL) I get greeted with the log displayed at the startup (the one with all the starting services etc.) and another line at the end, saying "The system will shutdown now!" (or reboot, depends on what I chose), and a blinking cursor, that does not allow me however to input any keys. The system at that point is pretty much useless, and the only option for me is to force shutdown with the power button. Is there a way to restore full functionality of the shutdown and reboot? | Hello, Your computer looks like quite new. You may try installing a newer kernel from Debian Backports. Hope this helps. -- [1] https://backports.debian.org/ |
I have been trying to move the Skype for Linux key to the /usr/share/keyrings directory to address the deprecated apt-key situation. I have followed various guides from the net, principally https://www.linuxuprising.com/2021/01/a ... o-add.html and https://unix.stackexchange.com/question ... sted-gpg-k I thought that I had got it done properly, but when I did an apt update at the end, I got the following warnings... All packages are up to date. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.skype.com/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1F3045A5DF7587C3 W: Failed to fetch https://repo.skype.com/deb/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1F3045A5DF7587C3 W: Some index files failed to download. They have been ignored, or old ones used instead. Now I do not know how to proceed to get the Skype key and to ensure that it is placed in the correct (new) keyring, instead of the deprecated apt-key list. I am running Debian 12 Bookworm with Cinnamon desktop. Please can someone assist me to get this key and get it properly installed so that I can use Skype again? Tom. | @DocTomJP edit your first post to add prefix [Solved] |
Hello, I recently wanted to configure a wifi network on my laptop, and I tried to find network manager / the GUI that usually lets me do this. I can't find it anywhere. and the little icon that was in the system tray of the bottom desktop panel has disappeared. There is nothing relevant under the network section of settings. Package manager shows that 'network-manager' package is installed. I reinstalled it but it didn't change anything. I tried doing 'sudo service network-manager start' and 'sudo service network-manager restart' but it gives this error: Failed to restart network-manager.service: Unit network-manager.service not found. what should I do? | Hi, You don't say what desktop you use but I guess you refer to the nm-applet. To restart networking: Code: Select alluser@debian:~$ su - Password: root@debian:~# systemctl restart networking Maybe you can restore it simply by typing nm-applet in the terminal and add it to start-up applications? Code: Select all$ apt search nm-applet Sorting... Done Full Text Search... Done nm-tray/stable 0.4.3-2+b1 amd64 Simple Network Manager frontend written in Qt nm-tray-l10n/stable 0.4.3-2 all Language package for nm-tray |
Hi, i installed the Debian Bullseye and downloaded the os. On the setup, i only picked the "standard system utilies" choise. Now, i don't have window manager and desktop environment. There is only terminal. I must be connect the internet with my wireless network card. I tried theese: 1) First i learned the wifi card name. Code: Select alliwconfig My wifi card name is wlp7s0 2) Then i wanted the scan network. Code: Select alliw wlp7s0 scan Error: command failed: Network is down (-100) 3) I entered this command for upped the wifi card: Code: Select allip link set wlp7s0 up Error: RTNETLINK answers: Operation not possible due to RF-kill 4) Finally i entered this command, because i wanted unblock the card: Code: Select allrfkill unblock all But this command is not founded. I don't have an ethernet. How can i solved this problem? | You need to run rfkill with root privileges or sudo. |
hi all, I upgraded my laptop from Debian 10 to Debian 11. I have not troubles, but I can not turn off the system properly. I start shutdown from Debian 11 GUI, system shutdown starts, but it stucks so I have to force computer shutdown pressing power button. What can you suggest me to solve the issue? Thanks for your help | Hello, You can try to investigate following advices in https://wiki.debian.org/systemd#systemd ... r_shutdown . What is your init system ? |
Hi all, I have a remote headless linux machine, nobody can use a keyboard to change during system boot kernel. I need to change headless linux machine kernel used to boot Debian 11. cat /etc/os-release Code: Select allPRETTY_NAME="Debian GNU/Linux bullseye/sid" NAME="Debian GNU/Linux" ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" In this remote Linux PC there are these kernels installed: dpkg --list | grep linux-image Code: Select allii linux-image-4.19.0-9-amd64 4.19.118-2+deb10u1 amd64 Linux 4.19 for 64-bit PCs (signed) ii linux-image-5.10.0-3-amd64 5.10.13-1 amd64 Linux 5.10 for 64-bit PCs (signed) ii linux-image-5.10.0-8-amd64 5.10.46-5 amd64 Linux 5.10 for 64-bit PCs (signed) ii linux-image-5.14.0-2-amd64 5.14.9-2 amd64 Linux 5.14 for 64-bit PCs (signed) ii linux-image-amd64 5.10.13-1 amd64 Linux for 64-bit PCs (meta-package) In this moment system is running uname -r Code: Select all5.14.0-2-amd64 In my case I need to set that remote PC starts using "linux-image-5.10.0-3-amd64". I noted that inside the system there is etc/default/grub file. Code: Select all# If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" After that I noted file /boot/grub/grub.cfg. Here I copied a part of this long file. In this piece of code there are different settings about Grub menu. Code: Select allmenuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-87f34e93-5364-4558-b677-6c9d9605b020' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 87f34e93-5364-4558-b677-6c9d9605b020 else search --no-floppy --fs-uuid --set=root 87f34e93-5364-4558-b677-6c9d9605b020 fi echo 'Loading Linux 5.14.0-2-amd64 ...' linux /boot/vmlinuz-5.14.0-2-amd64 root=UUID=87f34e93-5364-4558-b677-6c9d9605b020 ro net.ifnames=0 biosdevname=0 quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-5.14.0-2-amd64 } submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-87f34e93-5364-4558-b677-6c9d9605b020' { menuentry 'Debian GNU/Linux, with Linux 5.14.0-2-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.14.0-2-amd64-advanced-87f34e93-5364-4558-b677-6c9d9605b020' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 87f34e93-5364-4558-b677-6c9d9605b020 else search --no-floppy --fs-uuid --set=root 87f34e93-5364-4558-b677-6c9d9605b020 fi echo 'Loading Linux 5.14.0-2-amd64 ...' linux /boot/vmlinuz-5.14.0-2-amd64 root=UUID=87f34e93-5364-4558-b677-6c9d9605b020 ro net.ifnames=0 biosdevname=0 quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-5.14.0-2-amd64 } menuentry 'Debian GNU/Linux, with Linux 5.14.0-2-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.14.0-2-amd64-recovery-87f34e93-5364-4558-b677-6c9d9605b020' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 87f34e93-5364-4558-b677-6c9d9605b020 else search --no-floppy --fs-uuid --set=root 87f34e93-5364-4558-b677-6c9d9605b020 fi echo 'Loading Linux 5.14.0-2-amd64 ...' linux /boot/vmlinuz-5.14.0-2-amd64 root=UUID=87f34e93-5364-4558-b677-6c9d9605b020 ro single net.ifnames=0 biosdevname=0 echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-5.14.0-2-amd64 } menuentry 'Debian GNU/Linux, with Linux 5.10.0-8-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-8-amd64-advanced-87f34e93-5364-4558-b677-6c9d9605b020' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 87f34e93-5364-4558-b677-6c9d9605b020 else search --no-floppy --fs-uuid --set=root 87f34e93-5364-4558-b677-6c9d9605b020 fi echo 'Loading Linux 5.14.0-2-amd64 ...' linux /boot/vmlinuz-5.14.0-2-amd64 root=UUID=87f34e93-5364-4558-b677-6c9d9605b020 ro single net.ifnames=0 biosdevname=0 echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-5.14.0-2-amd64 } menuentry 'Debian GNU/Linux, with Linux 5.10.0-8-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-8-amd64-advanced-87f34e93-5364-4558-b677-6c9d9605b020' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 87f34e93-5364-4558-b677-6c9d9605b020 else search --no-floppy --fs-uuid --set=root 87f34e93-5364-4558-b677-6c9d9605b020 fi echo 'Loading Linux 5.10.0-8-amd64 ...' linux /boot/vmlinuz-5.10.0-8-amd64 root=UUID=87f34e93-5364-4558-b677-6c9d9605b020 ro net.ifnames=0 biosdevname=0 quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-5.10.0-8-amd64 } menuentry 'Debian GNU/Linux, with Linux 5.10.0-8-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-8-amd64-recovery-87f34e93-5364-4558-b677-6c9d9605b020' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 87f34e93-5364-4558-b677-6c9d9605b020 else search --no-floppy --fs-uuid --set=root 87f34e93-5364-4558-b677-6c9d9605b020 fi echo 'Loading Linux 5.10.0-8-amd64 ...' linux /boot/vmlinuz-5.10.0-8-amd64 root=UUID=87f34e93-5364-4558-b677-6c9d9605b020 ro single net.ifnames=0 biosdevname=0 echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-5.10.0-8-amd64 } menuentry 'Debian GNU/Linux, with Linux 5.10.0-3-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-3-amd64-advanced-87f34e93-5364-4558-b677-6c9d9605b020' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 87f34e93-5364-4558-b677-6c9d9605b020 else search --no-floppy --fs-uuid --set=root 87f34e93-5364-4558-b677-6c9d9605b020 fi echo 'Loading Linux 5.10.0-3-amd64 ...' linux /boot/vmlinuz-5.10.0-3-amd64 root=UUID=87f34e93-5364-4558-b677-6c9d9605b020 ro net.ifnames=0 biosdevname=0 quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-5.10.0-3-amd64 } menuentry 'Debian GNU/Linux, with Linux 5.10.0-3-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-3-amd64-recovery-87f34e93-5364-4558-b677-6c9d9605b020' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 87f34e93-5364-4558-b677-6c9d9605b020 else search --no-floppy --fs-uuid --set=root 87f34e93-5364-4558-b677-6c9d9605b020 fi echo 'Loading Linux 5.10.0-3-amd64 ...' linux /boot/vmlinuz-5.10.0-3-amd64 root=UUID=87f34e93-5364-4558-b677-6c9d9605b020 ro single net.ifnames=0 biosdevname=0 echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-5.10.0-3-amd64 } menuentry 'Debian GNU/Linux, with Linux 4.19.0-9-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-9-amd64-advanced-87f34e93-5364-4558-b677-6c9d9605b020' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 87f34e93-5364-4558-b677-6c9d9605b020 else search --no-floppy --fs-uuid --set=root 87f34e93-5364-4558-b677-6c9d9605b020 fi echo 'Loading Linux 4.19.0-9-amd64 ...' linux /boot/vmlinuz-4.19.0-9-amd64 root=UUID=87f34e93-5364-4558-b677-6c9d9605b020 ro net.ifnames=0 biosdevname=0 quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-4.19.0-9-amd64 } menuentry 'Debian GNU/Linux, with Linux 4.19.0-9-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-9-amd64-recovery-87f34e93-5364-4558-b677-6c9d9605b020' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 87f34e93-5364-4558-b677-6c9d9605b020 else search --no-floppy --fs-uuid --set=root 87f34e93-5364-4558-b677-6c9d9605b020 fi echo 'Loading Linux 4.19.0-9-amd64 ...' linux /boot/vmlinuz-4.19.0-9-amd64 root=UUID=87f34e93-5364-4558-b677-6c9d9605b020 ro single net.ifnames=0 biosdevname=0 echo 'Loading initial ramdisk ...' How can I do? How can I set to boot Debian 11 using "linux-image-5.10.0-3-amd64" kernel? Thanks so much for your help! Best regards | I have to ask why you would want to install 5.10.0-3 when 5.10.0-8 is basically the same kernel with security patches applied? |
Hello, I am using Jessie, and was just updating some software. I guess I have learned my lesson now, and that is, just don't blindly update software unless you know what it is =( I restarted my system, and get the "oh no, something is terribly wrong" message. I can only login to recovery mode, as root. If I try to run startx, it also fails. After some log digging, I think it has to do with my video card. When I try to update my driver, the system seems to hang on the "nvidia-installer-cleanup" forever. Now, after a couple of restarts, the problem has not resolved itself. I get the message that I need to run "dpkg --configure -a" to fix it (to complete the above application, but regardless of options, the system just hangs). Granted, I have only waited about an hour -- should I wait longer? Can anyone give me any other pointers, or ideas? It shouldn't be that complicated, should it? I already started migrating my data, and planning to just re-install unless I can get a helpful tip, in the right direction. Thanks! | That package says in the description that it prevents driver upgrades. So maybe you updated the drive from a third party source and had this package installed? Maybe try remove it |
We have a high (>20%) packet loss and latency (>10ms) between VMs (debian 10 and 11) running on the same KVM hypervisor host (debian 11) on a bridge that connects only virtual interfaces with no physical interface involved. The packet loss takes only place on the red connectivity. All other links that involve physical interfaces are not affected. The physical interfaces A and B are attached to the bgp-VM via passthru. Interface C is a bridge (br0) and attached to a physical interface. Interface "D" is only virtual (virbr1) with no physical interfaces attached. bgp1.png (22.17 KiB) Viewed 3765 times https://github.com/appliedprivacy/techn ... s/issues/1 The packet drops start to occur at around 20k packets per second. We are looking for suggestions on how to further analyze this issue to find the root cause. thanks! | we got the packet drops down to an neglectable level by using multi-queue virtio-net on the bgp-VM and VM interfaces pointing to the bridge (at the price of significant CPU load). Code: Select all<driver name='vhost' queues='8'/> |
I have downloaded the universal Linux driver from the HP support page. Installed the driver and I have added the printer via the CUPS web interface. When I try to print something, nothing is printed. The same goes for test page. With the CUPS web interface I can see that jobs are accepted but filter is failing. I have never have problems with this driver under Debian 10, but now with Debian 11 there is a problem. I don't know how to solve this problem. | Cups errors are logged by Systemd now, I believe. This should give you cups messages since last boot. Try printing and see if there are any messages. You might need to enable cups error logging, or change the level of logging. Code: Select all# journalctl -b -u cups |
Dear all, I bought a new Linux laptop with Nvidia RTX 3060 and Ryzen 7 5800H (bought at Tuxedo). Because TuxedoOS contains a bug and because I am a fan of Debian, I decided to do a fresh install of Debian bookworm (hence Testing and Linux kernel 5.14) with GNOME to use the recent Nvidia driver 470.82 which should work with the RTX 3060 and Wayland (according to some reports). After installation, it seems that the nouveau in bookworm does not run well (movies did not went smooth), as expected with the relatively new Nvidia hardware. So I followed the instructions on Debian wiki exactly. During the reboot, Grub appeared as usual and then the laptop went to the regular scrolling text lines. But somewhere during that process, 1, 2 or 3 lines after "[OK] started GNOME Display Manager", the laptop hangs for a while (for about 5 seconds), then the screen went suddenly black with a blinking cursor. Login screen did not appear. Simply pressing the on-button shortly the laptop went to the complete shut-down. Is it something with Wayland, despite the statements that Nvidia driver 470 should work with Wayland? I don´t know. In any case, TuxedoOS 20.04 LTS based on Budgie on the laptop works well with Nivida driver. I don´t think TuxedoOS comes with Wayland. But how can solve the issue of the freeze during boot? | Boot into recovery mode from Grub then use Code: Select all# journalctl -b -1 to see what the final messages before the black screen were. |
Hello everyone! We have diskless AMD stations that use iPXE to boot LTSP-generated images. They work alright with Debian 11 image, but identically set up Debian 10 image doesn't - Xorg fails to start properly. And we need to use Debian 10 for some testing. The APU on the computers is AMD Ryzen 3 4300GE. It seems like the amdgpu driver isn't loading for some reason. I followed the wiki guide and installed the packages firmware-amd-graphics libgl1-mesa-dri libglx-mesa0 mesa-vulkan-drivers xserver-xorg-video-all and recreated the image (obviously). Please see the attached archive, it contains logs/commands output for the same machine when booted from Debian 11 (good) and when booted from Debian 10 (bad). Notice I removed the time brackets [..........] from Xorg logs, so you can diff them easily. And notice how /dev/dri is missing in Debian 10, indicating that the DRM didn't load for some reason. Please let me know if you need more information/logs. Any help is greatly appreciated! | I'm not looking at your logs, dmesg is where kernel initialization is and it is not there. It may be the KMS driver in older kernel does not support your AMD card. Unfortunately your lspci is useless, there is no PCI-ID in it. You should use 'lspci -knn' to see it. Once you have the PCI-ID you can check if your kernel supports it at cateee.net - the kernel driver database. The other possible cause for missing /dev/dri is required firmware is not available at the time when kernel driver loads. It is also in dmesg then, with 'error -2' - which means not found. This may help to get the idea of kernel issues. My hints for kernel builders. |
My data disk, dev/sdb1, is not automatically mounted in Debian Bullseye. Can I fix this by adding a line to fstab? | Disks are not guaranteed to have the same /dev/sdX name with every boot, better to go with UUID or partition LABEL. Follow Hetzer's suggestion regarding creating a mount point owned by your user. Then in fstab (assuming the UUID in your above post is the actual one): Code: Select allUUID=66b4ff4f-4c11-4d4f-9fe1-57b6bd96b5ca /mnt/data ext4 auto,user,rw,noatime 0 0 "noatime" reduces unnecessary writes, "nofail" is only really needed for external and network disks. |
Hello everyone. I've recently installed Debian 12 on my laptop and have generally been really happy with it, but for some reason whenever I am in public and I need to connect to the Internet, the login screen (if the owner of the network wants you to agree to certain terms and conditions and such) just never shows up. In other distributions that I have used, which use newer versions of GNOME, a separate login window appears, but I don't see anything of the sort now. I've tried doing in through Firefox and even tried installing the newer official Mozilla repository version, but no "log into network" button appears either. Is there a dependency or something of the sort that I'm missing? | Hello, I would suggest reading the following Debian wiki page: https://wiki.debian.org/CaptivePortal Hope this helps. Please let me know. |
After a lot of trial and error I think I found how to enable and configure Samba. Still, my Windows 11 pc will not connect to the share? Installed Samba on my Debian pc. I created a folder /mnt/Muziek and made it r/w. I opened and edited the smb.conf file by adding the following to the end of the file: path = /mnt/Muziek browseable = yes writable = yes read only = no guest ok = yes I did not change anything else. Saved the file and restarted Samba. I can not connect to the share? I issued the command smbclient -L localhost -N to find if I am in the correct WORKGROUP and the answer I get is SMB1 disabled --no workgroup available? Can somebody tell me where I go wrong? | Hello @audiolover, Did you fix it following the advice of user RedGreen925 ? |
This was a minimal installation, no initial desktop environment, I built it up to the Qtile window manager. Everythign was going great into I decided I needed a wifi selector widget. When I installed Connman the wifi died and I haven’t been able to restore it. The first thing I tried to do to restore connectivity was purge connman. I found this: viewtopic.php?t=157975&sid=3e89a0d19cd4 ... 104f65#top stating that references to wlp2s0 should have been commented out as it caused a conflict with both Connman and NetworkManager. But I suspect this was too little, too late. I've been down this road before on the same system when I installed NetworkManager. My solution then was to reinstall. I would prefer to not do that again. My /etc/network/interfaces: Code: Select all# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface #allow-hotplug wlp2s0 #iface wlp2s0 inet dhcp # wpa-ssid ViRuS # wpa-psk <password> When I run ip link show: Code: Select all1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp0s31f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether c8:f7:50:37:c3:6c brd ff:ff:ff:ff:ff:ff 3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether d8:f2:ca:c0:d8:34 brd ff:ff:ff:ff:ff:ff 4: zt2lrsatmv: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2800 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 46:a1:cb:4b:47:31 brd ff:ff:ff:ff:ff:ff 5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:00:24:b1 brd ff:ff:ff:ff:ff:ff If Up was unresponsive. Running list-units | grep ifup: Code: Select all ifupdown-pre.service loaded active exited Helper to synchronize boot up for ifupdown My /etc/resolve.conf (10.20.30.3 is my Pi Hole): Code: Select alldomain palazzomilazzo search palazzomilazzo nameserver 10.20.30.3 /etc/network/interfaces.d is empty ifconfig binary seems to be missing | Hello. I suggest you edit your message and hide the wifi password. After all, you don't want bad people (hackers) breaking into your network. Or do you want to? |
My nvme storage, formatted NTFS, is sometimes not mounted because it is "not clean". A restart solves the problem so it does not happen all the time. Can I force it to be mounted, even if it is not clean? Maybe by adding something in fstab where it is mounted? | Is it happening after booting Windows? Maybe you need to disable Windows Fast Startup. |
Recently upgraded to Bookworm (running headless), and all seemed fine. Yesterday I ran speedtest-cli, and the download results are 30Mbps (other devices report 300Mbps). When I run Iperf3, all looks fine at 940Mbps. I reinstalled speedtest-cli after remove/purge, but its result is the same. So I am puzzled. Is there an alternate test for internet download that can clear this up. I'm a bit of a noobie so please be easy on me. Thanks for your help! | Hello, devNull wrote: 2024-02-08 16:36 Recently upgraded to Bookworm (running headless), and all seemed fine. Yesterday I ran speedtest-cli, and the download results are 30Mbps (other devices report 300Mbps). You need to use the same benchmark and the same connection type (wired or wireless) on all devices to compare the results. devNull wrote: 2024-02-08 16:36 When I run Iperf3, all looks fine at 940Mbps. As reported before, you need to use the same benchmark to compare results. devNull wrote: 2024-02-08 16:36 So I am puzzled. Is there an alternate test for internet download that can clear this up. I would suggest to focus on the type of measurement you want to achieve. Are you interested in the download speed of your internet service provider or something else ? |
I am using Debian 12 and I am trying to open port 7890. I added the rules to iptables using the following command. Code: Select all$ sudo iptables -A INPUT -p tcp --dport 7890 -j ACCEPT $ sudo iptables-save # Generated by iptables-save v1.8.9 (nf_tables) on Tue Jul 23 18:15:42 2024 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -p tcp -m tcp --dport 7890 -j ACCEPT COMMIT # Completed on Tue Jul 23 18:15:42 2024 The rules are shown when iptables is listed. Code: Select all$ sudo iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp -- anywhere anywhere tcp dpt:7890 Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination However, when I check the status of port 7890, it is show as closed. Code: Select all$ nmap localhost -p 7890 Starting Nmap 7.93 ( https://nmap.org ) at 2024-07-23 18:16 UTC Nmap scan report for localhost (127.0.0.1) Host is up (0.000096s latency). Other addresses for localhost (not scanned): ::1 PORT STATE SERVICE 7890/tcp closed unknown Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds What am I doing wrong? | Is there a service listening on port 7890 running? |
I want to mount the maps of my nas without sudo asking for a password but it does not work. Here is my sudoers file: Code: Select all GNU nano 5.4 /etc/sudoers.tmp # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" # Host alias specification # User alias specification # Cmnd alias specification (added by peer) Cmnd_Alias FOTOOS = /bin/mount -t nfs 192.168.178.5\:/volume1/fotoos, /bin/umount 192.168.178.5\:/volume1/fotoos Cmnd_Alias DATA = /bin/mount -t nfs 192.168.178.5\:/volume1/data, /bin/umount 192.168.178.5\:/volume1/data # User privilege specification (second line added by peer) root ALL=(ALL:ALL) ALL peer ALL=(ALL) NOPASSWD: FOTOOS, DATA # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL # See sudoers(5) for more information on "@include" directives: @includedir /etc/sudoers.d I added two Cmnd_Aliasses and one user privilege. In the Aliasses I used the full path of the commands and I used an escape key for the special character ':'. When I save the file visudo does not complain. I looked at several howto's but I cannot see what I am doing wrong. Can somebody help me? edit: I moved the user privilege line to the bottom of the file: no change Then I changed the line to Code: Select allpeer ALL=(ALL) NOPASSWD: ALL This works but I this is not what I want | Code: Select allpeer ALL=(ALL:ALL) NOPASSWD: ALL Is not necessarily use visudo but 1st and 2nd fields must be separate by TAB. Peter. |
I just installed a new debian 11 from netinstall. But actually I want to use testing env (I thought I download netinstall testing version, but it turns out I am wrong). Now the source.list in /etc/apt folder is as below. My question - how can I switch to use testing version? I heard that it's not good to mix up normal e.g. debian 11 with testing or unstable version. So I am wondering what is a good way to switch to use testing version. The reason I want to switch to testing is because this is just my desktop env. So I am not worried about bug, but have more concern about software version. And in the past I always use testing version, but mix up stable with testing version (by changing the key word from e.g. bullseye to testing). Thanks Code: Select alldeb http://deb.debian.org/debian/ bullseye main non-free contrib deb-src http://deb.debian.org/debian/ bullseye main non-free contrib deb http://security.debian.org/debian-security bullseye-security main contrib non-free deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free | Bloom wrote: 2021-09-04 09:28You could use something like Siduction, which has a delay before Sid packages are added.siduction uses the default Debian unstable repos, no delay. |
I have been testing (read playing) Debian 11 Bullseye on an old MacBook so I may be a little ahead of myself here. The truth is I am a hack and have no real computer skills. Anyway I installed Bullseye netinst (minimum CD) and built the system up from there. All went well just the packages that I want and nothing else and the MacBook runs great. The goal is a lean system that runs relatively well on a low resource system that still looks and feels modern. I tried several approaches running different combs of DMs, WMs, DEs etc. After adding an SSD from an old Lenovo and adding a 4Gib RAM stick I had around I got it running pretty nice even with a heavy DE Cinnamon which I really like. EXCEPT - no sound - it runs with Code: Select allAudio: Device-1: NVIDIA MCP89 High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.10.0-5-amd64 entire system info below I pretty much tried everything I could find searcing the Internet. Debian does have a WiKi regarding installing up to Buster on a 13" MacBook 7,1 but the driver does not apply to Bullseye although is supported in 5.10 kernel which I don't understand. Anyway the sound supposedly works OOB. Anyway I have ripped everything out that I installed trying to fix the sound to include the NVIDIA driver that I found, alsamixer, alsamixergui PulseAudio and pavucontrol. I am thinking of a fresh install in case I jacked something up along the way but obviously would rather fix it. I could go with Buster but the version of Cinnamon is too old (version 3) and lacks the configure-ability of the version provide with Bullseye (version 4). Any help would be much appreciated. Code: Select allsparky@MacBook:~$ inxi -F System: Host: MacBook Kernel: 5.10.0-5-amd64 x86_64 bits: 64 Desktop: Cinnamon 4.8.6 Distro: Debian GNU/Linux bullseye/sid Machine: Type: Laptop System: Apple product: MacBook7,1 v: 1.0 serial: <superuser required> Mobo: Apple model: Mac-F22C89C8 serial: <superuser required> UEFI: Apple v: MB71.88Z.0039.B0E.1111071359 date: 11/07/11 Battery: ID-1: BAT0 charge: 54.9 Wh condition: 57.0/62.9 Wh (91%) CPU: Info: Dual Core model: Intel Core2 Duo P8600 bits: 64 type: MCP L2 cache: 3 MiB Speed: 796 MHz min/max: 798/2394 MHz Core speeds (MHz): 1: 796 2: 796 Graphics: Device-1: NVIDIA MCP89 [GeForce 320M] driver: nouveau v: kernel Device-2: Apple Built-in iSight type: USB driver: uvcvideo Display: x11 server: X.org 1.20.10 driver: loaded: modesetting unloaded: fbdev,vesa resolution: <missing: xdpyinfo> OpenGL: renderer: NVAF v: 3.3 Mesa 20.3.4 Audio: Device-1: NVIDIA MCP89 High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.10.0-5-amd64 Network: Device-1: NVIDIA MCP89 Ethernet driver: forcedeth IF: enp0s9 state: down mac: 70:cd:60:86:00:ba Device-2: Broadcom BCM43224 802.11a/b/g/n driver: bcma-pci-bridge IF-ID-1: wlp1s0b1 state: up mac: e4:ce:8f:74:76:82 Bluetooth: Device-1: Apple Bluetooth Host Controller type: USB driver: N/A Drives: Local Storage: total: 171.41 GiB used: 9.24 GiB (5.4%) ID-1: /dev/sda vendor: Intel model: SSDSC2BW180A3H size: 167.68 GiB ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer Glide size: 3.73 GiB Partition: ID-1: / size: 162.62 GiB used: 7.42 GiB (4.6%) fs: ext4 dev: /dev/sda2 ID-2: /boot/efi size: 511 MiB used: 13 MiB (2.6%) fs: vfat dev: /dev/sda1 Swap: ID-1: swap-1 type: partition size: 976 MiB used: 0 KiB (0.0%) dev: /dev/sda3 Sensors: Missing: Required tool sensors not installed. Check --recommends Info: Processes: 139 Uptime: 3h 10m Memory: 4.57 GiB used: 1.07 GiB (23.4%) Shell: Bash inxi: 3.3.01 | Does Code: Select all$ aplay /dev/urandom -f dat -D plughw:0,0 produce any sound? Should send random noise to card 0 device 0 ie the analogue output. Be prepared if it does work. The sound card has an issue switching to digital after a reboot on the MacBook? Is this relevant? https://wiki.debian.org/InstallingDebia ... idia_MCP89 |
I am using debian 10 with gnome. I would like to try alsa intead, if possible. | Pulseaudio is married to Gnome, but I use an XFCE desktop and there I could use only ALSA and that suits me fine. |
After a recent update a couple of days ago, my PC goes straight from the motherboard logo to the GRUB command line. I was able to boot into Debian by typing "exit". Yesterday I ran "update-grub" in Debian and this morning typing "exit" causes the system to stay on a black screen. I was able to boot into Debian by loading the kernel and running initrd from the GRUB command line. I just ran "update-grub2" to see if that made a difference but now I daren't reboot my system without posting the problem here. | I haven't experienced anything like this, but if I did, I might follow this advice: https://unix.stackexchange.com/question ... 852#330852 Which is based on this advice: https://www.linux.com/training-tutorial ... b-2-linux/ |
Hello everyone. I've asked about this on reddit and the KDE forums but I'm still stuck. I have a Samsung RF510 laptop with an NVIDIA card (I'm writing from a different place so I can't put the particular details now). Up until the upgrade everything was working fine but now suspension (or hibernation) doesn't work, the screen goes black as if trying to shut down but the fans and everything seems to be working. The main problem is the computer becomes irresponsive and there's no way of waking it up and I have to end up pressing the switch button until it shuts down. Do you have any idea why this could be happening or do you know any fix for this? I've been thinking about the drivers of the graphic card but I don't really know. If you need more information about my system or my issue, tell me and I'll try to find it. Thanks. --- October 9 2021 I managed to make my system suspension work again by following a bug report: First modify your /etc/default/grub so it looks like the following (sudo nano /etc/default/grub): Code: Select all[...] GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="no_console_suspend nouveau.debug=warn init_on_alloc=0" [...] The last line is the important one (and the one you'll have to add or modify) and the previous three lines should already look the same. After that update your grub with: Code: Select allsudo update-grub2 | rghedin wrote: 2021-10-05 17:51 I'm having the same issue, but with an integrated GPU (Intel HD 2000). OP seems to have an issue with Nvidia and you with Intel GPU. Not the same so start a new thread for your issue. How can I export a journalctl --boot=-1 output to file? Code: Select alljournalctl -b -1 > filename "filename" can be any name. It may help to filter priority to only show warnings or errors with the -p option. I usually use -p3 or -p4 see Code: Select allman journalctl |
I am using Debian 10.11 and I want to install the new Debian stable. So I downloaded the Live ISO image for Debian 11.1 and boot from it. I tried suspend to RAM with Live image but it is not working, the monitor goes off but the power is on. After that everything is blocked. I have to do hardware reset. I have GForce 210 graphic card and I think that the driver for the card is the problem. I had the same problem with Debian 10, but I found that the firmware for the graphic card was missing. After installing it everything was OK. This time I downloaded the non-free version of Debian and I was thinking that everything will work, but that is not the case. What can I do to diagnose the problem and solve it? | Hello, See https://bugs.debian.org/cgi-bin/bugrepo ... =989705#30 |
I am pretty sure I have covered all the bases but can't seem to get my wi-fi up and running in Bullseye although it ran with no issues in Buster. Code: Select allSystem: Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Cinnamon 4.8.6 Distro: Debian GNU/Linux 11 (bullseye) Network: Device-1: Ralink RT5390 Wireless 802.11n 1T/1R PCIe driver: rt2800pci v: 2.3.0 port: e000 bus ID: 06:00.0 IF: wlp6s0 state: down mac: <filter> Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: d000 bus ID: 07:00.0 IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 1. My sources.list are all contrib nonfree 2. I did successfully install the realtec driver for RTL8111/8168/8411 PCI Express Gigabit Ethernet 3. just to make sure I reinstalled initramfs-tools ( firmware for Realtek Ethernet, wifi and Bluetooth adapters supported by various drivers) 4. did sudo apt install -y firmware-realtek Code: Select allmajpooper@1150z:~$ sudo apt install -y firmware-realtek Reading package lists... Done Building dependency tree... Done Reading state information... Done firmware-realtek is already the newest version (20210315-3). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I do get this output for dmesg which I don't understand what rt2860.bin is Code: Select allmajpooper@1150z:~$ sudo dmesg [ 5.834720] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin' [ 5.834743] rt2800pci 0000:06:00.0: firmware: failed to load rt2860.bin (-2) [ 5.834746] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 5.834748] rt2800pci 0000:06:00.0: Direct firmware load for rt2860.bin failed with error -2 [ 5.835246] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin' [ 5.835258] rt2800pci 0000:06:00.0: firmware: failed to load rt2860.bin (-2) [ 5.835260] rt2800pci 0000:06:00.0: Direct firmware load for rt2860.bin failed with error -2 [ 5.848532] audit: type=1400 audit(1634409334.017:21): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=843 comm="cups-browsed" capability=23 capname="sys_nice" [ 8.054195] usb 2-2: 3:1: cannot get freq at ep 0x84 [ 8.126242] usb 2-2: 3:1: cannot get freq at ep 0x84 [ 8.605094] r8169 0000:07:00.0 enp7s0: Link is Up - 1Gbps/Full - flow control rx/tx [ 8.605114] IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready [ 13.604812] sdg: sdg1 [ 13.639465] sd 7:0:0:0: [sdg] Attached SCSI disk [ 13.639728] ses 7:0:0:1: Attached Enclosure device [ 38.889856] FAT-fs (sdh1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 38.900484] FAT-fs (sdj1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 38.949495] EXT4-fs (sdi1): mounted filesystem with ordered data mode. Opts: (null) [ 38.988525] EXT4-fs (sdk1): mounted filesystem with ordered data mode. Opts: (null) [ 39.007603] EXT4-fs (sdk2): mounted filesystem with ordered data mode. Opts: (null) [ 64.966445] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin' [ 64.966482] rt2800pci 0000:06:00.0: firmware: failed to load rt2860.bin (-2) [ 64.966490] rt2800pci 0000:06:00.0: Direct firmware load for rt2860.bin failed with error -2 | rt2860.bin is in firmware-misc-nonfree. Have you got it? https://packages.debian.org/buster/firm ... sc-nonfree |
I know there is a guide in this forum, I have seen it in the past but I can't find it, please give me the link if you have it | Hello, Diesel330 wrote: 2024-07-26 11:22 Thanks guys for suggesting gufw, the other day someone suggested it to me in an other forum and I'm using it since then. Very simple GUI and very informative Please, mark the discussion as solved adding the tag "[Solved]" at the beginning of the subject of the first post. Thanks. |
Lately, my laptop regularly crashes whenever I have ~10 tabs open in my browser or if I have 2-3 apps that do heavy lifting. This rarely happened before (like once every two months?) but now occurs 2-3x a day. I have made two different adjustments to my laptop recently and can't determine which to revert and what it would look like if they were the culprit: I tackled a few lynis suggestions to harden my laptop a bit more (installed the following packages: evtest libpam-pwquality libpam-tmpdir needrestart ufw). There's an attached screenshot below of the suggestions that I followed. I installed antivirus protection (installed the following packages: clamav clamav-daemon) I think that the antivirus might be the culprit because it takes up a sizeable amount of memory, and I've noticed that when an app crashes, clamd appears to disappear from the list of processes. Also, I read that the antivirus often leads to memory issues generally. I reduced memory usage for clamav by setting ConcurrentDatabaseReload false in /etc/clamav/clam.conf as well but it's still crashing With that said, attached is an example of the system resources before/after of launching an app that crashes the system, and my (un)educated guess is that the CPU straining is what is leading to the crashes. Questions Can someone explain whether memory or CPU is liable to be the culprit? From there, I can try to reverse engineer the changes I've made to revert the laptop to it's prior state. If it is a memory issue, do I need clamAV or an antivirus in 2024? | Both CPU and RAM appear to be in short supply. I'd suggest reverting your changes one at a time until the issue resolves. Nobody can tell you if you need AV, but if you share files with Windows users it might be worth exploring. Hope this helps - |
For some reason, I cannot access some websites anymore on my work laptop, since booting up this morning. I can ping google.com or debian.net, but cannot ping duckduckgo.com or slack.com. My machine is up to date on Debian 12.6, and everything was working fine yesterday... (?!) How can I troubleshoot this ? | You could reboot your modem/router too, might be an ISP thing. What do these commands return? Code: Select all$ host duckduckgo.com $ host slack.com For me they return... Code: Select all$ host duckduckgo.com duckduckgo.com has address 52.142.124.215 duckduckgo.com mail is handled by 0 duckduckgo-com.mail.protection.outlook.com. $ host slack.com slack.com has address 18.169.61.189 slack.com has address 18.134.215.41 slack.com has address 18.168.172.238 slack.com has address 18.169.120.191 slack.com mail is handled by 1 aspmx.l.google.com. slack.com mail is handled by 10 aspmx2.googlemail.com. slack.com mail is handled by 10 aspmx3.googlemail.com. slack.com mail is handled by 5 alt1.aspmx.l.google.com. slack.com mail is handled by 5 alt2.aspmx.l.google.com. |
In the Debian Wiki Page regarding Blocking loading of Linux Kernel Modules it is mentioned that This procedure does not prevent another process from requesting a module addition during boot or runtime. Is it possible to prevent Modules from being loaded into the kernel at run time? If yes how? And in the steps it is given as 1) Create a Conf file in /etc/modprobe.d 2) Run the command depmod -ae' as root 3) Recreate your initrd with 'update-initramfs -u' Are Steps 2 and 3 required? Will simply creating the conf file and then rebooting the system not work? | DebianFox wrote: 2024-08-10 05:04Is there any alternative to lsmod that can be used to determine which modules have been loaded by the Kernel? lsmod gets information from procfs, i.e one can get much the same with: Code: Select allcat /proc/modules Similarly, modinfo gets most of its information from /sys/module/[name]/ |
Hi i'm running debian 12 on an i3 and an i5 and planning to use both for virtualization with qemu/kvm and bridged networking. On the i5 (tethys) all is fine i used the following config in the /etc/network/interface: Code: Select allazazel@tethys:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback auto enp2s0 iface enp2s0 inet manual auto br0 iface br0 inet static address 192.168.1.25 netmask 255.255.255.0 gateway 192.168.1.1 bridge_ports enp2s0 dns-nameservers 8.8.8.8 the output of ip addr show follow azazel@tethys:~$ ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000 link/ether 40:61:86:7b:2a:49 brd ff:ff:ff:ff:ff:ff 3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether a2:bb:44:15:e0:1b brd ff:ff:ff:ff:ff:ff inet 192.168.1.25/24 brd 192.168.1.255 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::a0bb:44ff:fe15:e01b/64 scope link valid_lft forever preferred_lft forever 4: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UNKNOWN group default qlen 1000 link/ether fe:90:06:09:32:49 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc90:6ff:fe09:3249/64 scope link valid_lft forever preferred_lft forever 6: tap1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UNKNOWN group default qlen 1000 link/ether fe:e8:b9:fe:ae:b8 brd ff:ff:ff:ff:ff:ff inet6 fe80::fce8:b9ff:fefe:aeb8/64 scope link valid_lft forever preferred_lft forever azazel@tethys:~$ sudo ifconfig -a [sudo] password di azazel: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.25 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::a0bb:44ff:fe15:e01b prefixlen 64 scopeid 0x20<link> ether a2:bb:44:15:e0:1b txqueuelen 1000 (Ethernet) RX packets 1089880 bytes 1052012702 (1003.2 MiB) RX errors 0 dropped 438 overruns 0 frame 0 TX packets 737030 bytes 50497945 (48.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 40:61:86:7b:2a:49 txqueuelen 1000 (Ethernet) RX packets 1100106 bytes 1068932549 (1019.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 752367 bytes 52003350 (49.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 34 bytes 3841 (3.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 34 bytes 3841 (3.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::fc90:6ff:fe09:3249 prefixlen 64 scopeid 0x20<link> ether fe:90:06:09:32:49 txqueuelen 1000 (Ethernet) RX packets 12473 bytes 1097505 (1.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 20786 bytes 1917975 (1.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tap1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::fce8:b9ff:fefe:aeb8 prefixlen 64 scopeid 0x20<link> ether fe:e8:b9:fe:ae:b8 txqueuelen 1000 (Ethernet) RX packets 2862 bytes 407768 (398.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 16558 bytes 1535643 (1.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 note that the 2 tap are created by bridge helper for two specific vm launched from command line with a custom qemu-system-ppc for running IBM AIX 4.3/5.1. th config is working perfectly and the VM are accessible throught al my LAN I transferred the same config on the i3 (cecilie) changing the ip and the interfaces obviously according to the ones specific to the new machine and nothing is working. Assigning a simple static ip to the machine work fine, producing the following output Code: Select allazazel@cecilie:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet static address 192.168.1.219 netmask 255.255.255.0 gateway 192.168.1.1 dns-nameservers 8.8.8.8 azazel@cecilie:~$ ifconfig -a -bash: ifconfig: comando non trovato azazel@cecilie:~$ sudo ifconfig -a [sudo] password di azazel: eno1: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500 inet 192.168.1.141 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::7627:eaff:fef3:4a1c prefixlen 64 scopeid 0x20<link> ether 74:27:ea:f3:4a:1c txqueuelen 1000 (Ethernet) RX packets 358 bytes 109760 (107.1 KiB) RX errors 0 dropped 13347 overruns 0 frame 0 TX packets 262 bytes 39149 (38.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xf7c00000-f7c20000 enp0s25: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500 inet 192.168.1.219 netmask 255.255.255.0 broadcast 192.168.1.255 ether 74:27:ea:f3:4a:1c txqueuelen 1000 (Ethernet) device interrupt 20 memory 0xf7c00000-f7c20000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 28 bytes 3398 (3.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 28 bytes 3398 (3.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 azazel@cecilie:~$ ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: eno1: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 74:27:ea:f3:4a:1c brd ff:ff:ff:ff:ff:ff altname enp0s25 inet 192.168.1.219/24 brd 192.168.1.255 scope global enp0s25 valid_lft forever preferred_lft forever inet 192.168.1.141/24 brd 192.168.1.255 scope global secondary eno1 valid_lft forever preferred_lft forever inet6 fe80::7627:eaff:fef3:4a1c/64 scope link valid_lft forever preferred_lft forever azazel@cecilie:~$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=115 time=12.6 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=115 time=12.9 ms ^C --- 8.8.8.8 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 12.596/12.747/12.899/0.151 ms azazel@cecilie:~$ s you can see eno1 is present, wich is assigned a different ip, maybe with dhcp than the one i assigned to enp0s25, as you can see from ip addr output enp0s25 is the altname for eno1. I reconfigure for bridge in a similar way wich i did for tethys and after systemctl restart networking, noting was working, the situation is as follows and network is unreachable: Code: Select allzazel@cecilie:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual auto br0 iface br0 inet static address 192.168.1.219 netmask 255.255.255.0 gateway 192.168.1.1 bridge_ports enp0s25 dns-nameservers 8.8.8.8 azazel@cecilie:~$ ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: eno1: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 74:27:ea:f3:4a:1c brd ff:ff:ff:ff:ff:ff altname enp0s25 inet6 fe80::7627:eaff:fef3:4a1c/64 scope link valid_lft forever preferred_lft forever 3: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether da:c1:e3:21:4f:09 brd ff:ff:ff:ff:ff:ff inet 192.168.1.219/24 brd 192.168.1.255 scope global br0 valid_lft forever preferred_lft forever azazel@cecilie:~$ sudo ifconfig -a br0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.1.219 netmask 255.255.255.0 broadcast 192.168.1.255 ether da:c1:e3:21:4f:09 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500 inet6 fe80::7627:eaff:fef3:4a1c prefixlen 64 scopeid 0x20<link> ether 74:27:ea:f3:4a:1c txqueuelen 1000 (Ethernet) RX packets 789 bytes 152317 (148.7 KiB) RX errors 0 dropped 30063 overruns 0 frame 0 TX packets 447 bytes 71061 (69.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xf7c00000-f7c20000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 237 bytes 40443 (39.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 237 bytes 40443 (39.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 azazel@cecilie:~$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. From 192.168.1.219 icmp_seq=1 Destination Host Unreachable From 192.168.1.219 icmp_seq=2 Destination Host Unreachable From 192.168.1.219 icmp_seq=3 Destination Host Unreachable From 192.168.1.219 icmp_seq=4 Destination Host Unreachable ^C --- 8.8.8.8 ping statistics --- 5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4042ms pipe 4 on a reboot the situation is similar, with nothing working Code: Select allazel@cecilie:~$ ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 74:27:ea:f3:4a:1c brd ff:ff:ff:ff:ff:ff altname enp0s25 inet 192.168.1.141/24 brd 192.168.1.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::7627:eaff:fef3:4a1c/64 scope link valid_lft forever preferred_lft forever 3: br0: <BROADCAST,MULTICAST,DYNAMIC> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether da:c1:e3:21:4f:09 brd ff:ff:ff:ff:ff:ff azazel@cecilie:~$ sudo ifconfog -a [sudo] password di azazel: sudo: ifconfog: comando non trovato azazel@cecilie:~$ sudo ifconfig -a br0: flags=-28670<BROADCAST,MULTICAST,DYNAMIC> mtu 1500 ether da:c1:e3:21:4f:09 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.141 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::7627:eaff:fef3:4a1c prefixlen 64 scopeid 0x20<link> ether 74:27:ea:f3:4a:1c txqueuelen 1000 (Ethernet) RX packets 225 bytes 94650 (92.4 KiB) RX errors 0 dropped 4095 overruns 0 frame 0 TX packets 184 bytes 32218 (31.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xf7c00000-f7c20000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 35 bytes 4012 (3.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35 bytes 4012 (3.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 will be grateful for any help or suggestion | azazel71 wrote: 2024-08-07 09:08 [..] config on the i3 (cecilie) [..] after systemctl restart networking, noting was working, the situation is as follows and network is unreachable: Code: Select allzazel@cecilie:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual auto br0 iface br0 inet static address 192.168.1.219 netmask 255.255.255.0 gateway 192.168.1.1 bridge_ports enp0s25 dns-nameservers 8.8.8.8 azazel@cecilie:~$ ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: eno1: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 74:27:ea:f3:4a:1c brd ff:ff:ff:ff:ff:ff altname enp0s25 inet6 fe80::7627:eaff:fef3:4a1c/64 scope link valid_lft forever preferred_lft forever 3: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether da:c1:e3:21:4f:09 brd ff:ff:ff:ff:ff:ff inet 192.168.1.219/24 brd 192.168.1.255 scope global br0 valid_lft forever preferred_lft forever azazel@cecilie:~$ sudo ifconfig -a br0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.1.219 netmask 255.255.255.0 broadcast 192.168.1.255 ether da:c1:e3:21:4f:09 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500 inet6 fe80::7627:eaff:fef3:4a1c prefixlen 64 scopeid 0x20<link> ether 74:27:ea:f3:4a:1c txqueuelen 1000 (Ethernet) RX packets 789 bytes 152317 (148.7 KiB) RX errors 0 dropped 30063 overruns 0 frame 0 TX packets 447 bytes 71061 (69.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xf7c00000-f7c20000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 237 bytes 40443 (39.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 237 bytes 40443 (39.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 azazel@cecilie:~$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. From 192.168.1.219 icmp_seq=1 Destination Host Unreachable From 192.168.1.219 icmp_seq=2 Destination Host Unreachable From 192.168.1.219 icmp_seq=3 Destination Host Unreachable From 192.168.1.219 icmp_seq=4 Destination Host Unreachable ^C --- 8.8.8.8 ping statistics --- 5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4042ms pipe 4 will be grateful for any help or suggestion If I understand correctly, the enp0s25 interface is not manually assigned an IP address for the server named cecile: Code: Select allzazel@cecilie:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual auto br0 iface br0 inet static address 192.168.1.219 netmask 255.255.255.0 gateway 192.168.1.1 bridge_ports enp0s25 dns-nameservers 8.8.8.8 As you can see the enp0s25 network interface is configured with a static IP address, but no IP address is specified: Code: Select allauto enp0s25 iface enp0s25 inet manual Hope this helps. |
I have a Debian 11, with nginx 1.18 and vsftp 3.0.3, using cloduflare... I can't understand why, but Google Search Console forcefully indexes the FTP pages... so I find in search console both www.mysite.my/index.html and ftp.mysite.my/index.html... any suggestions as to why this happens? Previously I used a debian server with lighttpd and this didn't happen. Thanks | Hello, I'm not an expert on the subject, but you can probably search for the robots.txt file [1] and its configuration to prevent crawlers like Google from indexing your ftp address. -- [1] https://developers.google.com/search/docs/crawling-indexing/robots/intro |
I recently installed debian 12. Networks shows "no available connections" and network manager shows I have an ethernet connection. I don't. Wifi only. I have this installed on 2 different laptops with the same results. How do I fix this. Thanks Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-22-amd64 (64-bit) Graphics Platform: Wayland Processors: 2 × Intel® Celeron® N4020 CPU @ 1.10GHz Memory: 3.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 600 Manufacturer: Google Product Name: Bobba System Version: rev5 | Please use code tags for terminal text and logs etc. Show us: Code: Select all$ cat /etc/NetworkManager/NetworkManager.conf |
Unable to hide grub boot logs with GRUB_CMDLINE_LINUX_DEFAULT=quiet https://i.imgur.com/EorYc5d.gif | "splash" option should hide the boot messages - https://easylinuxtipsproject.blogspot.c ... s.html#ID4 Run update-grub after you change it. |
Hi, I need to adjust brightness and sound from my USB keyboard that is missing those Fn keys.. so I would need something like this..: Ctrl+ LeftCursor (xdoot script Plama Shortcut)--> Maps: Fn+8 (brigntness Up keys on laptop keyboard) Ctrl+ RightCursor (xdoot script Plama Shortcut)--> Maps: Fn+7 (brigntness Down keys on laptop keyboard) Ctrl+ UpCursor (xdoot script Plama Shortcut)--> Maps: Fn+6 (Volume Up keys on laptop keyboard) Ctrl+ UpCursor (xdoot script Plama Shortcut)--> Maps: Fn+5 (Volume Down keys on laptop keyboard) xdotool <<Laptop Keyboard>> key <<ctrl+q>> I think to have readen somewhere xdotool cant use Fn buttons.. anyway.. is there an easy way to achieve this ..It doesnt seem easy task Thanks | ok, for Plasma, this will make it. https://martinovic.blog/post/kdeconnect_commands/ Volume Up: qdbus org.kde.kglobalaccel /component/kmix invokeShortcut "increase_volume" Volume Down: qdbus org.kde.kglobalaccel /component/kmix invokeShortcut "decrease_volume" Volume Mute: qdbus org.kde.kglobalaccel /component/kmix invokeShortcut "mute" Brightness Up: qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement/Actions/BrightnessControl org.kde.Solid.PowerManagement.Actions.BrightnessControl.setBrightness $(expr $(qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement/Actions/BrightnessControl org.kde.Solid.PowerManagement.Actions.BrightnessControl.brightness) + 20) Brightness Down: qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement/Actions/BrightnessControl org.kde.Solid.PowerManagement.Actions.BrightnessControl.setBrightness $(expr $(qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement/Actions/BrightnessControl org.kde.Solid.PowerManagement.Actions.BrightnessControl.brightness) - 20) Thanks. |
Hi, I'd like to install Windows in my system,but Ive found out I need a GPT table partition.. I didnt see there were any conversion in linux btrfs data between between a MSDOS and a GPT table partition.., I meant..when I do a copy/paste partition (gparted) , a btrfs send/receive, or a fsarchive restore, didnt see any kind of data conversion,... I also saw if i used sfdisk to backup/restore partition after changing Table partition type, data partition were backl available and recognozible under a different table partition type.. Am I missing something? , can you provide me some help cos I dont see where is the data conversion type among table partitions | bester69 wrote: 2021-08-31 18:18 I didnt see there were any conversion in linux btrfs data between between a MSDOS and a GPT table partition Btrfs is a filesystem. Partition table is beyond the scope of the filesystem. You can convert a partition table in-place with gdisk. You may also need to reinstall GRUB depending on how it was installed. Bloom wrote: 2021-09-01 18:45 GPT is required for UEFI and for every hard disk > 2 TB. Wrong and wrong. UEFI boot supports both DOS and GPT partition schemes. DOS partition scheme is limited to 2^32 sectors, i.e. 16 TiB with 4096-byte sectors (4Kn Advanced Format). Also, a partition table is not required at all when the drive is used entirely e.g. as a single filesystem, swap area, RAID array member, LVM physical volume or encrypted volume. All that being said, GPT is much better than DOS (partition UUID and labels, no need for extended partition, backup partition table). Bloom wrote: 2021-09-02 05:27 Changing the table type deletes everything on the hard disk. Wrong. There are several ways to change the partition table type without deleting anything. |
The most recent Debian 10.10 update has killed Virtualbox kernel modules working/signed, using MOK keys. I guess its due to fixes outlined here: GRUB2 UEFI SecureBoot vulnerabilities - 2021 https://www.debian.org/security/2021-GR ... ecureBoot/ I have been able to sign the vbox modules, after each kernel update since installation (Debian 10.5). I use the keys originally generated at: /root/MOK.priv /root/MOK.der After a kernel upgrade, the following one-liner would fix vbox modules, no problem: (Updating to latest kernel) Code: Select allcd /usr/lib/modules/4.19.0-17-amd64/misc/ && /usr/lib/linux-kbuild-4.19/scripts/sign-file sha256 /root/MOK.priv /root/MOK.der vboxnetadp.ko && /usr/lib/linux-kbuild-4.19/scripts/sign-file sha256 /root/MOK.priv /root/MOK.der vboxnetflt.ko && /usr/lib/linux-kbuild-4.19/scripts/sign-file sha256 /root/MOK.priv /root/MOK.der vboxdrv.ko Then Reboot. But since the Debian 10.10 update, after re-signing modules and rebooting, I now get the following error dialog popup when attempting to launch a Virtualbox VM: VirtualBox - Error in suplibOsInit Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing '/sbin/vboxconfig' as root. If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information. where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. I also tried Qemu/KVM using libvirt and virt-manager, after converting VM's to .qcow2 format, but had way too many issues to even boot the VMs. I have some Windows VMs that I need to use, and they used to work great in Virtualbox, so would like to get them working again if possible. What is preventing vbox modules now working with secure boot? Any ideas, approaches, to help resolve? | The main suspect is the shim update introduced in point release 10.10. Maybe this is the same bug as #990311. |
I have 2 PCs that are pretty much identical. Both systems had the NFS server service running perfectly and were using Debian 10 up until a few weeks ago when I upgraded them to Debian 11. Ever since the upgrade, PC 'A' fails to start the NFS server service. I made sure the nfs-kernel-server service was enabled: Code: Select allsudo systemctl enable nfs-kernel-server Synchronizing state of nfs-kernel-server.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable nfs-kernel-server and started the service: Code: Select allsudo systemctl start nfs-kernel-server After that, the NFS server is up and running.........until the next reboot. My secondary Debian 11 system does not exhibit this behaviour. The NFS server on it survives reboots perfectly so whatever is wrong, I don't think it's any sort of Debian 11 bug. Disclaimer: Been using Debian for a couple of years now but I'm by no means an expert or advanced user so please forgive me if this is an easy fix. | https://wiki.debian.org/systemd/Services and from the link above: Code: Select all[Service] Type=simple [Restart=always # <== this ExecStart=/usr/local/bin/myservice |
Folks: Been trying to navigate through the many wikis that would give the exact instructions on how to get wifi working in fresh Bookworm install on my '20 Gazelle 15 laptop . . . a lot of data about "what is wifi?". . . from back in the day??? hard to find the "get it done" pages . . . . I'm using MATE as the DE and I have NetworkManager because ethernet is now working . . . "enable networking" and Notifications is checked and "ethernet1" is showing, but the unit is a couple of feet from the router and nothing is showing up as "available" in Debian. I have Pop!_OS 21.04 and Gecko rolling Plasma installed and wifi works out of the box. I "added" my wifi network SSID and password manually and nuttin' . . . . I looked through the PCI options and my card doesn't seem to be listed with the driver that I would need to add for it??? Code: Select alllspci -nn | grep Network 00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH CNVi WiFi [8086:06f0] | Your wifi chip is supported in kernel 5.7 and up. It will need firmware-iwlwifi from non-free repo. The problem is I cant find your product id in sids 5.10 kernel. |
Hello, I'm currently executing Code: Select allip l add veth type dummy ip l dev veth address d4:d4:d4:d4:d4:d4 every time I start the machine. How can I configure Debian in a way that this dummy network device with fixed mac address is persisted between reboots? I wanted to avoid to "pollute" my crontab, but I did not find out what is _the_ way one should do it. The syntax of /etc/network/interfaces is a bit obscure to me, and I did not manage to add the device there (where IMHO it makes the most sense). | Hello, franke wrote: 2024-10-05 04:42 Hello, I'm currently executing Code: Select allip l add veth type dummy ip l dev veth address d4:d4:d4:d4:d4:d4 every time I start the machine. How can I configure Debian in a way that this dummy network device with fixed mac address is persisted between reboots? [..] Can you please give some context about the overall configuration using this dummy interface ? |
Hello everyone, I'm using vsFTPd and lovin it. the defaults are /etc/init.d/vsftpd (init script) and then /etc/vsftpd.conf (config file) The execution is by systemctl : sudo systemctl start vsftpd the system startup : sudo systemctl enable vsftpd What would be the proper way of initializing a second instance of vsFTPd ?? Second instance is needed because of different settings of FTP Server, different ftp_root etc. Of course will have different port_listen. Please for comments and suggestions how we can have a second instance of vsFTPd. Thank you. | Hello, I think this is what you want. No need for a second instance but an alias interface (virtual IP). Without *inetd, see /usr/share/doc/vsftpd/examples/PER_IP_CONFIG/README I don't know if it works with virtual IPs, let us know if you get a chance to test. [...] to enable tcp_wrappers integration, you need this in your vsftpd.conf: tcp_wrappers=YES And you'll need a tcp_wrappers config file. An example one is supplied in this directory: hosts.allow. It lives at /etc/hosts.allow. Let's have a look at the example: vsftpd: 192.168.1.3: setenv VSFTPD_LOAD_CONF /etc/vsftpd_tcp_wrap.conf vsftpd: 192.168.1.4: DENY The first line: If a client connects from 192.168.1.3, then vsftpd will apply the vsftpd config file /etc/vsftpd_tcp_wrap.conf to the session! These settings are applied ON TOP of the default vsftpd.conf. This is obviously very powerful. You might use this to apply different access restrictions for some IPs (e.g. the ability to upload). Or you could give certain classes of IPs the ability to skip connection limits (max_clients=0). Or you could increase / decrease the bandwidth limiter for certain classes of IPs. You get the point :-) The second line: Denies the ability of 192.168.1.4 to connect. Very useful to take care of troublemakers. And now you don't need xinetd to do it - hurrah. With *inetd, see /usr/share/doc/vsftpd/examples/VIRTUAL_HOSTS/README This example shows how you might set up virtual hosts. Virtual hosting is where different clients access your machine on different IP addresses (virtual IPs) and get redirected to different ftp sites. [...] Step 1) Set up a virtual IP address. [...] Step 2) Create a user / location for the new virtual site. [...] Step 3) Modify the existing site to respond to the primary IP. Edit /etc/xinetd.d/vsftpd, and add the config line: bind = 192.168.1.2 Step 4) Create the new site, responding on the virtual IP. cp /etc/xinetd.d/vsftpd /etc/xinetd.d/vsftpd2 Edit vsftpd2, and change - The bind line to refer to the IP address 192.168.1.10 - Add the line server_args = /etc/vsftpd_site2.conf This launches this FTP site with a different vsftpd configuration file. cp /etc/vsftpd.conf /etc/vsftpd_site2.conf Add two lines: ftp_username=ftp_site2 ftpd_banner=This is the alternative FTP site. Step 5) Restart xinetd and test! [...] Please let us know if this is what you are looking for. |
Up-to-date Debian 12 x64. Here is my /etc/default/mdadm: Code: Select allAUTOCHECK=true AUTOSCAN=true START_DAEMON=true DAEMON_OPTIONS="--syslog --test --pid-file /root/z_mdadm.pid" VERBOSE=true I've run dpkg-reconfigure mdadm a couple of times, but the DAEMON_OPTIONS does not work. The file "/root/z_mdadm.pid: does not exist at all. MDADM does not send an e-mail at the startup either. The options written by me does not present in the process list either. Code: Select all# ps aux | grep mdadm root 425 0.0 0.0 3580 1796 ? Ss 10:26 0:00 /sbin/mdadm --monitor --scan | Hello, Is the initramfs updated ? |
Hi, I have a Debian 12 server connected to my router via LAN. After booting, I can ping external IPv6 addresses, a few minutes later I cannot. It turns out that my server "receives" a second IPv6 address, which is not known and therefore not routed by my router. Unfortunately, my server uses this second address to send packets, which means there is no return path from the internet, and thus all external connections fail. Incoming connections and outgoing LAN connection do work. If I manually delete the unwanted address, everything works as it should - until it comes back after 2-3 minutes! I have checked syslog, but there is nothing regarding this. The server seems to create the second address all by itself, using the prefix my router gave it. Code: Select allPrefix: 2001:a61:50bb:8800::/56 working IP: 2001:a61:50bb:880[b]1[/b]:xxxx:xxxx:xxxx:xxxx/64 second IP: 2001:a61:50bb:880[b]2[/b]:xxxx:xxxx:xxxx:xxxx/64 The interface is configured in /etc/network/interfaces as follows: Code: Select allauto eno1 iface eno1 inet6 manual Being desperate, I have also tried dhcp, which my router does not provide on ipv6, and static, both to no avail. I did not really expect this to help anyway ... Has anyone seen this behavior and knows how to solve it? | Responding to my own post: this was actually a router issue, my server config and Debian are not at fault. My router has separate home and guest networks, and for some reason, it advertises the guest network to my server, which is in the home network, resulting in a route with an unreachable gateway. Three day's time gone up in smoke, duh! Once I had found the packet that should not even exist, I blocked the guest network on my server using ip6tables, and everything works as expected now. I also informed the manufacturer of the router of this issue. |
Problem: For some drive(s) the system sometimes does not create the appropriate wwn-0x... links. Here, in case of a HP S700 SSD, It sometimes only creates the ata-... links. This causes timeouts in the boot process when the system looks for the drives which were announced to it using the wwn-... link instead of ata-... or just sdX. (When the boot process continues after that timeout, ZFS on linux itself recognizes the ZFS filesystems itself automagically, so bad data in fstab or whatever usually does not matter that much) Questions: Often in documents/instructions it is recommended to use the WWN identification method, as it is most convenient and safe, because every device's WWN is written on it. But now I feel no longer sure about this. 1. Am I doing something grossly wrong which made the wwn-... identification links not appear? 2. Or, is this normal behaviour which makes more prudent to use the ata-... link instead of the wwn-...? | Hello, Meow wrote: 2024-10-30 09:03 Often in documents/instructions it is recommended to use the WWN identification method, as it is most convenient and safe, because every device's WWN is written on it. But now I feel no longer sure about this. Can you please provide a reference to an example of these documents/instructions? |
Please edit your post to use code tags for command output. The NIC does not send DHCP requests but there are multiple software components that do. You have mentioned ifupdown, NetworkManager and systemd-networkd. Choose one that you like and don't configure all of them at the same time. | @Best_Threads |
Never found out what the issue was but I reached back in Timeshift to the /etc/network/interfaces folder and replaced the current folder with a copy from a few weeks before the issue started and as a result the WOL is working properly now. So thanks to all those that provided input, I appreciate your help. Sardog Starting Point: I have two 64 bit systems on my home network that had Debian 11 loaded. I successfully configured both to WOL from a full shutdown by sending the proper magic packets using apps from any of my other home devices (laptops, tablets, phones). This was the way things worked for a very long time; wake-on-lan to start the computers when ever I needed them, and letting CRON shut them down at the end of the day. First Change: In order to update a piece of insignificant software to the latest version if was recommended that I dist-upgrade linux to Debian 12 so I upgraded one of the Debian 11 systems to Debian 12 to make sure everything worked before updating the other. After updating the first machine I discovered that this machine no longer reacted to WOL commands. Checking the configuration of the Network interface I found that the -g option had been reverted to the -d option on the card. Also it appeared that a few other network settings had been changed. I had already noticed and made some adjustments to the systems when the interface renaming occurred some time before so I can't believe that is the issue. I have made changes that seem to get the card to show WOL enabled after a reboot but it still won't react to WOL commands after shutdown. So that is my first issue. Next Change: On the second machine I chose to NOT update to Debian 12 and everything was fine until a few days ago when the system did a normal update where it updated the kernel among other things on its own, as I had set it to do. Following this update I found that the second system was also now affected by the refuse to react to WOL commands. Again I checked the configuration of the network card and found the WOL again turned off and no way to get the machine to accept WOL commands after shutdown. So my question is what changed that has disabled my ability to use WOL on these machines - NO nothing has changed in my BIOS settings and they are still set to WOL but something has changed with Debian that has disabled the WOL from a full shutdown condition. It is probably something basic that I missed in my searches online but maybe someone out there ran into similar problems and has a fix for me. Thanks Sardog | Hello, Sardog wrote: 2024-10-19 18:10 [..] Checking the configuration of the Network interface I found that the -g option had been reverted to the -d option on the card. What is the network card and the kernel module for the two computers ? You can use the following command (the inxi program must be installed): Code: Select allinxi -Faz How do you configure the activation if of the wake-on lan in the network configuration ? |
I was just browsing the web at the time. I thought the internet had gone down but eventually realised it was the ethernet connection. It's not a hardware issue as this is a dual boot system and ethernet works fine in Windows. I am not sure what info woulf be useful to this post. It will be a little tricky adding much as obviously the machine (desktop PC) has no internet connection and I am typing this from my laptop. | Happened to me this morning. I just rebooted the router and it was back. |
Because I've had it happen on two machines. The first one I noticed was originally installed a Neptune OS https://distrowatch.com/?newsid=11892 install from Summer 2023 that I upgraded to Debian testing/trixie & removed the Neptune packages & repos at some point. I'm not concerned about that one, more fool me for installing some Debian-based variant that apparently has abominations like grub-customizer installed on it. Derivative distros are just asking for trouble, especially upgrading. But the second installation is a pretty bog-standard Debian stable installation, albeit originally installed a longish time ago. cat /var/log/installer/lsb-release DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="8 (jessie) - installer build 20150422+deb8u1" X_INSTALLATION_MEDIUM=cdrom Old, but it is a trusty install, updated to current stable (bookworm) over the years, & I'm sure I have customized its grub plenty of times by editing /etc/default/grub. (I even have a bash alias to edit that file with vim since it is something I do often enough.) This time I went to edit the file and it was missing! Grub was working well enough, it keeps booting the luks-encrypted system and updating the kernels. And the install never had the grub-customizer package installed on it. The OS seems to have a fairly normal assortment of grub packages installed: dpkg -l | grep grub ii grub-common 2.06-13+deb12u1 amd64 GRand Unified Bootloader (common files) ii grub-efi 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (dummy package) ii grub-efi-amd64 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version) ii grub-efi-amd64-bin 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 modules) ii grub-efi-amd64-signed 1+2.06+13+deb12u1 amd64 GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian) ii grub2-common 2.06-13+deb12u1 amd64 GRand Unified Bootloader (common files for version 2) ii grub2-splashimages 1.0.1+nmu2 all a collection of great GRUB2 splashimages That is the same assortment that is on my local Debian stable server that does have /etc/default/grub intact. I copied the /etc/default/grub over from my server and executed "update-grub" and the operating system is now using the new file, I was able to enable & disable os-prober by editing the copied /etc/default/grub. Warning: os-prober will be executed to detect other bootable partitions. Warning: os-prober will not be executed to detect other bootable partitions. Has anyone seen this weirdness before? | Please use code tags for terminal text and commands etc. No I have never lost /etc/default/grub |
Hi all, is there a way to disable 'grub-install' during 'apt upgrade' ? If I rename it, during the upgrade what apt does ? | Please post more context. Why would you wish to do that? I run a few different distros in multiboot and found some would rewrite GRUB with new kernel upgrades. The solution was to remove the package grub-efi-amd64 from those distros. It's fairly trivial to boot the distro you wish to control GRUB if it has been overwritten and just grub-install to return it. |
I would like to replace my existing ISC-DHCP HA installation with a KEA HA solution, as the ISC-DHCP server has reached the end of its support life. The kea-dhcp4-server works perfectly . But I cannot get the high availability with the mode “hot-standby” and the variant “memfile” to work. I probably have an understanding problem in the configuration of kea-ctrl-agent.conf . Unfortunately, I have not found a solution for similar errors (which I have searched for on the Internet). I have already set the debug level to maximum, but unfortunately this does not give me a clear error message. Perhaps I also lack a certain basic knowledge. I would be very happy to receive support with the error diagnosis or suggestions for improved diagnosis . Please do not be confused by the names used, they are both x64 installations. Here is my installation base and the configuration files and log files: Code: Select all -the software version of both servers is identical Server 1 root@debian1:~# uname -a Linux debian1 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux ip a 2: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether bc:24:11:06:e3:ca brd ff:ff:ff:ff:ff:ff altname enp0s18 inet 192.168.1.220/24 brd 192.168.1.255 scope global ens18 valid_lft forever preferred_lft forever Server 2 root@debian2:~# uname -a Linux debian2 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux root@debian2:~# ip a 2: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether bc:24:11:d7:15:b3 brd ff:ff:ff:ff:ff:ff altname enp0s18 inet 192.168.1.221/24 brd 192.168.1.255 scope global ens18 valid_lft forever preferred_lft forever root@debian1:~# dpkg -l| grep kea ii kea-common 2.2.0-6 amd64 Common libraries for the Kea DHCP server ii kea-ctrl-agent 2.2.0-6 amd64 REST API service for Kea DHCP server ii kea-dhcp4-server 2.2.0-6 amd64 IPv4 DHCP server ii python3-kea-connector 2.2.0-6 all Python3 management connector for Kea DHCP server root@debian1:~# apt policy kea-ctrl-agent kea-ctrl-agent: Installiert: 2.2.0-6 Installationskandidat: 2.2.0-6 Versionstabelle: *** 2.2.0-6 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 100 /var/lib/dpkg/status Result of the recommended test Code: Select allroot@debian1:~# curl -X POST -H "Content-Type: application/json" -d '{ "command": "config-get", "service": [ "dhcp4" ] }' http://192.168.1.221:8000/ [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] root@debian2:~# curl -X POST -H "Content-Type: application/json" -d '{ "command": "config-get", "service": [ "dhcp4" ] }' http://192.168.1.220:8000/ [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Code: Select all Server1 kea-ctrl-agent.conf "Control-agent": { "http-host": "192.168.1.220", "http-port": 8000, "control-sockets": { "dhcp4": { "socket-type": "unix", "socket-name": "/run/kea/kea4-ctrl-socket" }, // "dhcp6": { // "socket-type": "unix", // "socket-name": "/run/kea/kea6-ctrl-socket" //}, "d2": { "socket-type": "unix", "socket-name": "/run/kea/kea-ddns-ctrl-socket" } }, "hooks-libraries": [ ], "loggers": [ { // This specifies the logging for Control Agent daemon. "name": "kea-ctrl-agent", "output_options": [ { "output": "stderr", "pattern": "%-5p %m " } ], "severity": "DEBUG", // If DEBUG level is specified, this value is used. 0 is least verbose, // 99 is most verbose. "debuglevel": 99 } ] } } Code: Select allServer2 kea-ctrl-agent.conf { // This is a basic configuration for the Kea Control Agent. // RESTful interface to be available at http://127.0.0.1:8000/ "Control-agent": { "http-host": "192.168.1.221", "http-port": 8000, "control-sockets": { "dhcp4": { "socket-type": "unix", "socket-name": "/run/kea/kea4-ctrl-socket" }, // "dhcp6": { // "socket-type": "unix", // "socket-name": "/run/kea/kea6-ctrl-socket" //}, "d2": { "socket-type": "unix", "socket-name": "/run/kea/kea-ddns-ctrl-socket" } }, "hooks-libraries": [ ], "loggers": [ { // This specifies the logging for Control Agent daemon. "name": "kea-ctrl-agent", "output_options": [ { "output": "stderr", "pattern": "%-5p %m " } ], "severity": "DEBUG", // If DEBUG level is specified, this value is used. 0 is least verbose, // 99 is most verbose. "debuglevel": 99 } ] } } Code: Select allroot@debian1:~# netstat -plan | grep 8000 tcp 0 0 192.168.1.220:8000 0.0.0.0:* LISTEN 441/kea-ctrl-agent tcp 0 0 192.168.1.220:8000 192.168.1.221:60032 VERBUNDEN 441/kea-ctrl-agent tcp 0 0 192.168.1.220:55212 192.168.1.221:8000 VERBUNDEN 445/kea-dhcp4 root@debian2:~# netstat -plan | grep 8000 tcp 0 0 192.168.1.221:8000 0.0.0.0:* LISTEN 427/kea-ctrl-agent tcp 0 0 192.168.1.221:8000 192.168.1.220:55212 VERBUNDEN 427/kea-ctrl-agent tcp 0 0 192.168.1.221:60032 192.168.1.220:8000 VERBUNDEN 432/kea-dhcp4 Code: Select allroot@debian1:~# journalctl -b|grep kea Dez 10 10:34:37 debian1 systemd[1]: Started kea-ctrl-agent.service - Kea Control Agent. Dez 10 10:34:37 debian1 systemd[1]: Starting kea-dhcp4-server.service - Kea IPv4 DHCP daemon... Dez 10 10:34:37 debian1 systemd[1]: Started kea-dhcp4-server.service - Kea IPv4 DHCP daemon. Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: 2024-12-10 10:34:37.841 INFO [kea-ctrl-agent.dctl/441.139963289622400] DCTL_STARTING Control-agent starting, pid: 441, version: 2.2.0 (stable) Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG DCTL_CONFIG_START parsing new configuration: { "control-sockets": { "d2": { "socket-name": "/run/kea/kea-ddns-ctrl-socket", "socket-type": "unix" }, "dhcp4": { "socket-name": "/run/kea/kea4-ctrl-socket", "socket-type": "unix" } }, "hooks-libraries": [ ], "http-host": "192.168.1.220", "http-port": 8000, "loggers": [ { "debuglevel": 99, "name": "kea-ctrl-agent", "output_options": [ { "output": "stderr", "pattern": "%-5p %m " } ], "severity": "DEBUG" } ] } Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: INFO CTRL_AGENT_HTTP_SERVICE_STARTED HTTP service bound to address 192.168.1.220:8000 Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: INFO DCTL_CONFIG_COMPLETE server has completed configuration: listening on 192.168.1.220, port 8000, control sockets: d2 dhcp4, 0 lib(s): Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG DCTL_RUN_PROCESS Control-agent starting application event loop Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: INFO CTRL_AGENT_STARTED Kea Control Agent version 2.2.0 started Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG COMMAND_REGISTERED Command list-commands registered Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG COMMAND_REGISTERED Command build-report registered Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG COMMAND_REGISTERED Command config-get registered Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG COMMAND_REGISTERED Command config-reload registered Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG COMMAND_REGISTERED Command config-set registered Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG COMMAND_REGISTERED Command config-test registered Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG COMMAND_REGISTERED Command config-write registered Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG COMMAND_REGISTERED Command shutdown registered Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG COMMAND_REGISTERED Command status-get registered Dez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG COMMAND_REGISTERED Command version-get registered Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.866 INFO [kea-dhcp4.dhcp4/445.139974734107136] DHCP4_STARTING Kea DHCPv4 server version 2.2.0 (stable) starting Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.869 INFO [kea-dhcp4.hosts/445.139974734107136] HOSTS_BACKENDS_REGISTERED the following host backend types are available: mysql postgresql Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.870 INFO [kea-dhcp4.dhcpsrv/445.139974734107136] DHCPSRV_CFGMGR_ADD_IFACE listening on interface ens18 Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.870 INFO [kea-dhcp4.dhcpsrv/445.139974734107136] DHCPSRV_CFGMGR_SOCKET_TYPE_DEFAULT "dhcp-socket-type" not specified , using default socket type raw Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.872 INFO [kea-dhcp4.hooks/445.139974734107136] HOOKS_LIBRARY_CLOSED hooks library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_lease_cmds.so successfully closed Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.874 INFO [kea-dhcp4.hooks/445.139974734107136] HOOKS_LIBRARY_CLOSED hooks library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_ha.so successfully closed Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.875 INFO [kea-dhcp4.dhcpsrv/445.139974734107136] DHCPSRV_CFGMGR_NEW_SUBNET4 a new subnet has been added to configuration: 192.168.1.0/24 with params: t1=21600, t2=43200, valid-lifetime=86400 Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.876 INFO [kea-dhcp4.lease-cmds-hooks/445.139974734107136] LEASE_CMDS_INIT_OK loading Lease Commands hooks library successful Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.876 INFO [kea-dhcp4.hooks/445.139974734107136] HOOKS_LIBRARY_LOADED hooks library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_lease_cmds.so successfully loaded Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.876 INFO [kea-dhcp4.ha-hooks/445.139974734107136] HA_CONFIGURATION_SUCCESSFUL HA hook library has been successfully configured Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.877 INFO [kea-dhcp4.ha-hooks/445.139974734107136] HA_INIT_OK loading High Availability hooks library successful Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.877 INFO [kea-dhcp4.hooks/445.139974734107136] HOOKS_LIBRARY_LOADED hooks library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_ha.so successfully loaded Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.877 INFO [kea-dhcp4.dhcp4/445.139974734107136] DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: added IPv4 subnets: 1; DDNS: disabled Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.877 INFO [kea-dhcp4.dhcpsrv/445.139974734107136] DHCPSRV_MEMFILE_DB opening memory file lease database: name=/var/lib/kea/kea-leases4.csv persist=true type=memfile universe=4 Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.877 INFO [kea-dhcp4.dhcpsrv/445.139974734107136] DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file /var/lib/kea/kea-leases4.csv Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.878 INFO [kea-dhcp4.dhcpsrv/445.139974734107136] DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to 3600 sec Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.897 INFO [kea-dhcp4.ha-hooks/445.139974734107136] HA_LOCAL_DHCP_DISABLE local DHCP service is disabled while the server1_raspi4b is in the WAITING state Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.897 INFO [kea-dhcp4.ha-hooks/445.139974734107136] HA_SERVICE_STARTED started high availability service in hot-standby mode as primary server Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.897 WARN [kea-dhcp4.dhcp4/445.139974734107136] DHCP4_MULTI_THREADING_INFO enabled: no, number of threads: 0, queue size: 0 Dez 10 10:34:37 debian1 kea-dhcp4[445]: 2024-12-10 10:34:37.897 INFO [kea-dhcp4.dhcp4/445.139974734107136] DHCP4_STARTED Kea DHCPv4 server version 2.2.0 started Dez 10 10:34:48 debian1 kea-dhcp4[445]: 2024-12-10 10:34:48.923 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_HEARTBEAT_FAILED heartbeat to server2_odroid (http://192.168.1.221:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:34:48 debian1 kea-dhcp4[445]: 2024-12-10 10:34:48.923 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_COMMUNICATION_INTERRUPTED communication with server2_odroid is interrupted Dez 10 10:34:48 debian1 kea-dhcp4[445]: 2024-12-10 10:34:48.923 INFO [kea-dhcp4.ha-hooks/445.139974734107136] HA_STATE_TRANSITION server transitions from WAITING to PARTNER-DOWN state, partner state is UNDEFINED Dez 10 10:34:48 debian1 kea-dhcp4[445]: 2024-12-10 10:34:48.923 INFO [kea-dhcp4.ha-hooks/445.139974734107136] HA_LEASE_UPDATES_DISABLED lease updates will not be sent to the partner while in PARTNER-DOWN state Dez 10 10:34:48 debian1 kea-dhcp4[445]: 2024-12-10 10:34:48.923 INFO [kea-dhcp4.ha-hooks/445.139974734107136] HA_LOCAL_DHCP_ENABLE local DHCP service is enabled while the server1_raspi4b is in the PARTNER-DOWN state Dez 10 10:34:49 debian1 kea-ctrl-agent[441]: DEBUG HTTP_REQUEST_RECEIVE_START start receiving request from 192.168.1.221 with timeout 10 Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.221 Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.221 Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.221: Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: POST / HTTP/1.1 Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: Host: 192.168.1.220 Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: Content-Length: 53 Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.221 Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.221 Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.221: Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: HTTP/1.1 200 OK Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: Content-Length: 140 Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: Date: Tue, 10 Dec 2024 09:34:50 GMT Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Dez 10 10:34:58 debian1 kea-dhcp4[445]: 2024-12-10 10:34:58.938 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_HEARTBEAT_FAILED heartbeat to server2_odroid (http://192.168.1.221:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:34:58 debian1 kea-dhcp4[445]: 2024-12-10 10:34:58.938 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_COMMUNICATION_INTERRUPTED communication with server2_odroid is interrupted Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.221 Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.221 Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.221: Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: POST / HTTP/1.1 Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: Host: 192.168.1.220 Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: Content-Length: 53 Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.221 Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.221 Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.221: Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: HTTP/1.1 200 OK Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: Content-Length: 140 Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: Date: Tue, 10 Dec 2024 09:35:00 GMT Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: Dez 10 10:35:00 debian1 kea-ctrl-agent[441]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Dez 10 10:35:09 debian1 kea-dhcp4[445]: 2024-12-10 10:35:09.273 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_HEARTBEAT_FAILED heartbeat to server2_odroid (http://192.168.1.221:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:35:09 debian1 kea-dhcp4[445]: 2024-12-10 10:35:09.273 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_COMMUNICATION_INTERRUPTED communication with server2_odroid is interrupted Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.221 Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.221 Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.221: Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: POST / HTTP/1.1 Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: Host: 192.168.1.220 Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: Content-Length: 53 Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.221 Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.221 Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.221: Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: HTTP/1.1 200 OK Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: Content-Length: 140 Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: Date: Tue, 10 Dec 2024 09:35:12 GMT Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: Dez 10 10:35:12 debian1 kea-ctrl-agent[441]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Dez 10 10:35:19 debian1 kea-dhcp4[445]: 2024-12-10 10:35:19.288 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_HEARTBEAT_FAILED heartbeat to server2_odroid (http://192.168.1.221:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:35:19 debian1 kea-dhcp4[445]: 2024-12-10 10:35:19.288 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_COMMUNICATION_INTERRUPTED communication with server2_odroid is interrupted Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.221 Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.221 Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.221: Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: POST / HTTP/1.1 Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: Host: 192.168.1.220 Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: Content-Length: 53 Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.221 Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.221 Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.221: Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: HTTP/1.1 200 OK Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: Content-Length: 140 Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: Date: Tue, 10 Dec 2024 09:35:22 GMT Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: Dez 10 10:35:22 debian1 kea-ctrl-agent[441]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Dez 10 10:35:29 debian1 kea-dhcp4[445]: 2024-12-10 10:35:29.302 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_HEARTBEAT_FAILED heartbeat to server2_odroid (http://192.168.1.221:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:35:29 debian1 kea-dhcp4[445]: 2024-12-10 10:35:29.302 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_COMMUNICATION_INTERRUPTED communication with server2_odroid is interrupted Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.221 Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.221 Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.221: Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: POST / HTTP/1.1 Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: Host: 192.168.1.220 Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: Content-Length: 53 Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.221 Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.221 Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.221: Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: HTTP/1.1 200 OK Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: Content-Length: 140 Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: Date: Tue, 10 Dec 2024 09:35:32 GMT Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: Dez 10 10:35:32 debian1 kea-ctrl-agent[441]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Dez 10 10:35:39 debian1 kea-dhcp4[445]: 2024-12-10 10:35:39.318 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_HEARTBEAT_FAILED heartbeat to server2_odroid (http://192.168.1.221:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:35:39 debian1 kea-dhcp4[445]: 2024-12-10 10:35:39.318 WARN [kea-dhcp4.ha-hooks/445.139974734107136] HA_COMMUNICATION_INTERRUPTED communication with server2_odroid is interrupted Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.221 Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.221 Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.221: Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: POST / HTTP/1.1 Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: Host: 192.168.1.220 Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: Content-Length: 53 Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.221 Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.221 Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.221: Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: HTTP/1.1 200 OK Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: Content-Length: 140 Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: Content-Type: application/json Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: Date: Tue, 10 Dec 2024 09:35:42 GMT Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: Dez 10 10:35:42 debian1 kea-ctrl-agent[441]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] ... Code: Select allroot@debian2:~# journalctl -b|grep kea Dez 10 10:34:40 debian2 systemd[1]: Started kea-ctrl-agent.service - Kea Control Agent. Dez 10 10:34:40 debian2 systemd[1]: Starting kea-dhcp4-server.service - Kea IPv4 DHCP daemon... Dez 10 10:34:40 debian2 systemd[1]: Started kea-dhcp4-server.service - Kea IPv4 DHCP daemon. Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: 2024-12-10 10:34:40.795 INFO [kea-ctrl-agent.dctl/427.140025023485824] DCTL_STARTING Control-agent starting, pid: 427, version: 2.2.0 (stable) Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG DCTL_CONFIG_START parsing new configuration: { "control-sockets": { "d2": { "socket-name": "/run/kea/kea-ddns-ctrl-socket", "socket-type": "unix" }, "dhcp4": { "socket-name": "/run/kea/kea4-ctrl-socket", "socket-type": "unix" } }, "hooks-libraries": [ ], "http-host": "192.168.1.221", "http-port": 8000, "loggers": [ { "debuglevel": 99, "name": "kea-ctrl-agent", "output_options": [ { "output": "stderr", "pattern": "%-5p %m " } ], "severity": "DEBUG" } ] } Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: INFO CTRL_AGENT_HTTP_SERVICE_STARTED HTTP service bound to address 192.168.1.221:8000 Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: INFO DCTL_CONFIG_COMPLETE server has completed configuration: listening on 192.168.1.221, port 8000, control sockets: d2 dhcp4, 0 lib(s): Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG DCTL_RUN_PROCESS Control-agent starting application event loop Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: INFO CTRL_AGENT_STARTED Kea Control Agent version 2.2.0 started Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG COMMAND_REGISTERED Command list-commands registered Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG COMMAND_REGISTERED Command build-report registered Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG COMMAND_REGISTERED Command config-get registered Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG COMMAND_REGISTERED Command config-reload registered Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG COMMAND_REGISTERED Command config-set registered Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG COMMAND_REGISTERED Command config-test registered Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG COMMAND_REGISTERED Command config-write registered Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG COMMAND_REGISTERED Command shutdown registered Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG COMMAND_REGISTERED Command status-get registered Dez 10 10:34:40 debian2 kea-ctrl-agent[427]: DEBUG COMMAND_REGISTERED Command version-get registered Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.817 INFO [kea-dhcp4.dhcp4/432.140326744490496] DHCP4_STARTING Kea DHCPv4 server version 2.2.0 (stable) starting Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.820 INFO [kea-dhcp4.hosts/432.140326744490496] HOSTS_BACKENDS_REGISTERED the following host backend types are available: mysql postgresql Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.821 INFO [kea-dhcp4.dhcpsrv/432.140326744490496] DHCPSRV_CFGMGR_ADD_IFACE listening on interface ens18 Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.821 INFO [kea-dhcp4.dhcpsrv/432.140326744490496] DHCPSRV_CFGMGR_SOCKET_TYPE_DEFAULT "dhcp-socket-type" not specified , using default socket type raw Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.822 INFO [kea-dhcp4.hooks/432.140326744490496] HOOKS_LIBRARY_CLOSED hooks library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_lease_cmds.so successfully closed Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.825 INFO [kea-dhcp4.hooks/432.140326744490496] HOOKS_LIBRARY_CLOSED hooks library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_ha.so successfully closed Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.825 INFO [kea-dhcp4.dhcpsrv/432.140326744490496] DHCPSRV_CFGMGR_NEW_SUBNET4 a new subnet has been added to configuration: 192.168.1.0/24 with params: t1=21600, t2=43200, valid-lifetime=86400 Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.827 INFO [kea-dhcp4.lease-cmds-hooks/432.140326744490496] LEASE_CMDS_INIT_OK loading Lease Commands hooks library successful Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.827 INFO [kea-dhcp4.hooks/432.140326744490496] HOOKS_LIBRARY_LOADED hooks library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_lease_cmds.so successfully loaded Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.828 INFO [kea-dhcp4.ha-hooks/432.140326744490496] HA_CONFIGURATION_SUCCESSFUL HA hook library has been successfully configured Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.828 INFO [kea-dhcp4.ha-hooks/432.140326744490496] HA_INIT_OK loading High Availability hooks library successful Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.828 INFO [kea-dhcp4.hooks/432.140326744490496] HOOKS_LIBRARY_LOADED hooks library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_ha.so successfully loaded Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.828 INFO [kea-dhcp4.dhcp4/432.140326744490496] DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: added IPv4 subnets: 1; DDNS: disabled Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.828 INFO [kea-dhcp4.dhcpsrv/432.140326744490496] DHCPSRV_MEMFILE_DB opening memory file lease database: name=/var/lib/kea/kea-leases4.csv persist=true type=memfile universe=4 Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.829 INFO [kea-dhcp4.dhcpsrv/432.140326744490496] DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file /var/lib/kea/kea-leases4.csv Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.829 INFO [kea-dhcp4.dhcpsrv/432.140326744490496] DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to 3600 sec Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.853 INFO [kea-dhcp4.ha-hooks/432.140326744490496] HA_LOCAL_DHCP_DISABLE local DHCP service is disabled while the server2_odroid is in the WAITING state Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.853 INFO [kea-dhcp4.ha-hooks/432.140326744490496] HA_SERVICE_STARTED started high availability service in hot-standby mode as standby server Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.853 WARN [kea-dhcp4.dhcp4/432.140326744490496] DHCP4_MULTI_THREADING_INFO enabled: no, number of threads: 0, queue size: 0 Dez 10 10:34:40 debian2 kea-dhcp4[432]: 2024-12-10 10:34:40.854 INFO [kea-dhcp4.dhcp4/432.140326744490496] DHCP4_STARTED Kea DHCPv4 server version 2.2.0 started Dez 10 10:34:48 debian2 kea-ctrl-agent[427]: DEBUG HTTP_REQUEST_RECEIVE_START start receiving request from 192.168.1.220 with timeout 10 Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.220 Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.220 Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.220: Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: POST / HTTP/1.1 Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: Host: 192.168.1.221 Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: Content-Length: 53 Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.220 Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.220 Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.220: Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: HTTP/1.1 200 OK Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: Content-Length: 140 Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: Date: Tue, 10 Dec 2024 09:34:49 GMT Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: Dez 10 10:34:49 debian2 kea-ctrl-agent[427]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Dez 10 10:34:51 debian2 kea-dhcp4[432]: 2024-12-10 10:34:51.879 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_HEARTBEAT_FAILED heartbeat to server1_raspi4b (http://192.168.1.220:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:34:51 debian2 kea-dhcp4[432]: 2024-12-10 10:34:51.880 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_COMMUNICATION_INTERRUPTED communication with server1_raspi4b is interrupted Dez 10 10:34:51 debian2 kea-dhcp4[432]: 2024-12-10 10:34:51.880 INFO [kea-dhcp4.ha-hooks/432.140326744490496] HA_STATE_TRANSITION server transitions from WAITING to PARTNER-DOWN state, partner state is UNDEFINED Dez 10 10:34:51 debian2 kea-dhcp4[432]: 2024-12-10 10:34:51.880 INFO [kea-dhcp4.ha-hooks/432.140326744490496] HA_LEASE_UPDATES_DISABLED lease updates will not be sent to the partner while in PARTNER-DOWN state Dez 10 10:34:51 debian2 kea-dhcp4[432]: 2024-12-10 10:34:51.880 INFO [kea-dhcp4.ha-hooks/432.140326744490496] HA_LOCAL_DHCP_ENABLE local DHCP service is enabled while the server2_odroid is in the PARTNER-DOWN state Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.220 Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.220 Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.220: Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: POST / HTTP/1.1 Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: Host: 192.168.1.221 Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: Content-Length: 53 Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.220 Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.220 Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.220: Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: HTTP/1.1 200 OK Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: Content-Length: 140 Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: Date: Tue, 10 Dec 2024 09:34:59 GMT Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: Dez 10 10:34:59 debian2 kea-ctrl-agent[427]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Dez 10 10:35:01 debian2 kea-dhcp4[432]: 2024-12-10 10:35:01.895 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_HEARTBEAT_FAILED heartbeat to server1_raspi4b (http://192.168.1.220:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:35:01 debian2 kea-dhcp4[432]: 2024-12-10 10:35:01.895 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_COMMUNICATION_INTERRUPTED communication with server1_raspi4b is interrupted Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.220 Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.220 Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.220: Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: POST / HTTP/1.1 Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: Host: 192.168.1.221 Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: Content-Length: 53 Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.220 Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.220 Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.220: Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: HTTP/1.1 200 OK Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: Content-Length: 140 Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: Date: Tue, 10 Dec 2024 09:35:08 GMT Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: Dez 10 10:35:08 debian2 kea-ctrl-agent[427]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Dez 10 10:35:11 debian2 kea-dhcp4[432]: 2024-12-10 10:35:11.911 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_HEARTBEAT_FAILED heartbeat to server1_raspi4b (http://192.168.1.220:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:35:11 debian2 kea-dhcp4[432]: 2024-12-10 10:35:11.911 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_COMMUNICATION_INTERRUPTED communication with server1_raspi4b is interrupted Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.220 Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.220 Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.220: Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: POST / HTTP/1.1 Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: Host: 192.168.1.221 Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: Content-Length: 53 Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.220 Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.220 Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.220: Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: HTTP/1.1 200 OK Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: Content-Length: 140 Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: Date: Tue, 10 Dec 2024 09:35:19 GMT Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: Dez 10 10:35:19 debian2 kea-ctrl-agent[427]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Dez 10 10:35:21 debian2 kea-dhcp4[432]: 2024-12-10 10:35:21.969 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_HEARTBEAT_FAILED heartbeat to server1_raspi4b (http://192.168.1.220:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:35:21 debian2 kea-dhcp4[432]: 2024-12-10 10:35:21.969 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_COMMUNICATION_INTERRUPTED communication with server1_raspi4b is interrupted Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.220 Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.220 Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.220: Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: POST / HTTP/1.1 Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: Host: 192.168.1.221 Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: Content-Length: 53 Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.220 Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.220 Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.220: Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: HTTP/1.1 200 OK Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: Content-Length: 140 Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: Date: Tue, 10 Dec 2024 09:35:29 GMT Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: Dez 10 10:35:29 debian2 kea-ctrl-agent[427]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Dez 10 10:35:32 debian2 kea-dhcp4[432]: 2024-12-10 10:35:32.000 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_HEARTBEAT_FAILED heartbeat to server1_raspi4b (http://192.168.1.220:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:35:32 debian2 kea-dhcp4[432]: 2024-12-10 10:35:32.000 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_COMMUNICATION_INTERRUPTED communication with server1_raspi4b is interrupted Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: DEBUG HTTP_DATA_RECEIVED received 145 bytes from 192.168.1.220 Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from 192.168.1.220 Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: DEBUG HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from 192.168.1.220: Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: POST / HTTP/1.1 Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: Host: 192.168.1.221 Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: Content-Length: 53 Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: { "command": "ha-heartbeat", "service": [ "dhcp4" ] } Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: INFO COMMAND_RECEIVED Received command 'ha-heartbeat' Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: INFO CTRL_AGENT_COMMAND_RECEIVED command ha-heartbeat received from remote address 192.168.1.220 Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command ha-heartbeat to service dhcp4 Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: DEBUG CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command ha-heartbeat: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND sending HTTP response HTTP/1.1 200 OK to 192.168.1.220 Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: DEBUG HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to 192.168.1.220: Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: HTTP/1.1 200 OK Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: Content-Length: 140 Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: Content-Type: application/json Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: Date: Tue, 10 Dec 2024 09:35:39 GMT Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: Dez 10 10:35:39 debian2 kea-ctrl-agent[427]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] Dez 10 10:35:42 debian2 kea-dhcp4[432]: 2024-12-10 10:35:42.021 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_HEARTBEAT_FAILED heartbeat to server1_raspi4b (http://192.168.1.220:8000/) failed: unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline, error code 1 Dez 10 10:35:42 debian2 kea-dhcp4[432]: 2024-12-10 10:35:42.021 WARN [kea-dhcp4.ha-hooks/432.140326744490496] HA_COMMUNICATION_INTERRUPTED communication with server1_raspi4b is interrupted ... Here is the configuration of the kea-dhcp4.conf of both servers kea-dhcp4.conf Server1 kea-dhcp4.conf Server2 Code: Select allroot@debian1:~# /etc/init.d/kea-dhcp4-server status ● kea-dhcp4-server.service - Kea IPv4 DHCP daemon Loaded: loaded (/etc/systemd/system/kea-dhcp4-server.service; enabled; preset: enabled) Active: active (running) since Tue 2024-12-10 10:34:37 CET; 56min ago Docs: man:kea-dhcp4(8) Process: 442 ExecStartPre=/bin/mkdir -p /var/run/kea (code=exited, status=0/SUCCESS) Main PID: 445 (kea-dhcp4) Tasks: 5 (limit: 2297) Memory: 15.3M CPU: 359ms CGroup: /system.slice/kea-dhcp4-server.service └─445 /usr/sbin/kea-dhcp4 -c /etc/kea/kea-dhcp4.conf root@debian2:~# /etc/init.d/kea-dhcp4-server status ● kea-dhcp4-server.service - Kea IPv4 DHCP daemon Loaded: loaded (/etc/systemd/system/kea-dhcp4-server.service; enabled; preset: enabled) Active: active (running) since Tue 2024-12-10 10:34:40 CET; 57min ago Docs: man:kea-dhcp4(8) Process: 428 ExecStartPre=/bin/mkdir -p /var/run/kea (code=exited, status=0/SUCCESS) Main PID: 432 (kea-dhcp4) Tasks: 5 (limit: 1097) Memory: 15.6M CPU: 357ms CGroup: /system.slice/kea-dhcp4-server.service └─432 /usr/sbin/kea-dhcp4 -c /etc/kea/kea-dhcp4.conf | Hello, According to this error message: Code: Select allDez 10 10:34:37 debian1 kea-ctrl-agent[441]: DEBUG DCTL_CONFIG_START parsing new configuration: { "control-sockets": { "d2": { "socket-name": "/run/kea/kea-ddns-ctrl-socket", "socket-type": "unix" }, "dhcp4": { "socket-name": "/run/kea/kea4-ctrl-socket", "socket-type": "unix" } }, "hooks-libraries": [ ], "http-host": "192.168.1.220", "http-port": 8000, "loggers": [ { "debuglevel": 99, "name": "kea-ctrl-agent", "output_options": [ { "output": "stderr", "pattern": "%-5p %m " } ], "severity": "DEBUG" } ] } [..] Dez 10 10:34:50 debian1 kea-ctrl-agent[441]: [ { "result": 1, "text": "unable to forward command to the dhcp4 service: No such file or directory. The server is likely to be offline" } ] it seems that the kea-ctrl-agent cannot communicate with the kea server using a unix socket [1] (i.e. /run/kea/kea4-ctrl-socket). This unix socket (filename) is not found by the kea-ctrl-agent, so the error message "No such file or directory". I'm not an kea expert, but the configuration for this socket seems to be missing in the server configurations you sent. (see [2]): [..] The management API allows the issuing of specific management commands, such as statistics retrieval, reconfiguration, or shutdown. For more details, see Management API. Currently, the only supported communication channel type is the UNIX stream socket. By default there are no sockets open; to instruct Kea to open a socket, the following entry in the configuration file can be used: Code: Select all"Dhcp4": { "control-socket": { "socket-type": "unix", "socket-name": "/path/to/the/unix/socket" }, "subnet4": [ ... ], ... } [..] Hope this helps. Please let me know. [1] https://sources.debian.org/src/isc-kea/2.4.1-3/src/bin/agent/ca_command_mgr.cc/?hl=246#L227 [2] Kea Administrator Reference Manual - 8.9 Management API for the DHCPv4 Server |
Hi Eveyone, I was hoping someone could point me in the correct direction to get my Intel® 82852/82855 Graphics Controller working under Debain 10 I have output on both the VGA and the DVI but the VGA is a clone of the DVI output and I want to have a extented Desktop on the VGA screen (this is so I can load another program onto that screen) This would be the format I need Main Screen on DVI port Seconday screen on VGA port I hope someone can help as I can not even get Windows 7 Drivers for this card anymore (and before you all say change the card This is built into the PC and I have 20 of them) | Does searching for that model of GPU here on the forums bring up nothing? |
Hi!I have Debian Bullseye 64 bit installed on my machine.I also use openSUSE and have my machine dual boot both Linux distros. I wanted to create a bootable USB disk for both distros by burning both Debian and openSUSE iso files on the same USB flash disk.I have created 2 BTRFS partitions on the USB,one to hold the Debian bootable ISO and the other to hold the openSUSE bootable iso. Unfortunately,when I use the Disk Image Writer tool in Debian,it states it will erase the entire USB but I want to burn the Debian ISO only on one partition and then burn the openSUSE ISO on the second partition so that if any of my linux distros fail,I can boot either distro from the same USB. Kindly advise if what I am requesting is even feasible and the tool to achieve both distros ISO writing on the same USB. Thanks. | Have you tried Ventoy? https://www.linux.org/threads/usb-linux ... toy.29944/ |
Hello, I am relatively new to Debian (I've been using it for about 2 years) but I am an experienced IT professional and I am having a really tough time replacing my WiFi link for a cable connection. I cannot get an IP using DHCP ("No DHCPOFFERS received") nor can I ping the router assigning an static IP to my interface ("Destination Host Unreachable"). I have all the required firmware installed and the networking itself is working fine, as I can get an IP and access the Internet from other computers here. I thought my motherboard could be damaged and I replaced it today by another one, but the result was the same. I also tried a Debian Live USB stick, to check if the problem was in my Debian setup, but the result was the same. Can anyone provide any pointers? I'm really out of ideas now. Thanks, M. | A good idea is to try another distro's Live USB, such as MX's or Mint's, just to see if they can get it to work. It never hurts to tell us as much as you can about the troublesome hardware, too. One good way is to install inxi and tell us the results of "inxi -Nxxz" |
Just installed Bullseye on a Lenovo IdeaPad 100. when I reboot it hangs to a blank screen. I have to poweroff - then power it back on. I have set the BIOS to Legacy boot mode not UEFI. Tried a few other tings I have found - editing GRUB etc. - no joy. Any ideas | https://www.reddit.com/r/linux/comments ... eapad_100/ https://everythingisamiracleblog.wordpr ... 00s-11iby/ |
Hi!I have Debian 11 Bullseye 64 bit installed on my machine.I initially installed my Debian without creating subvolumes during installation and now I have tried creating subvolumes and managed to successfully create the @home subvolume.However creating the @ subvolume for root has been a problem I think I finally managed to succesfully create it by copying contents of the root partition from / to @ subvolume folder i have also modified the etc/fstab for root as below Code: Select allUUID=45ce1280-0ffa-40e6-9774-3c9cfaa19ba8 / btrfs defaults,subvol=@ 0 0 The @home subvolume is being successfully mounted at boot with fstab entry below so I assume the line above should work for root Code: Select allUUID=e1a0bb7c-f2db-4d71-b4ae-ca50dd3c5a10 /home btrfs defaults,subvol=@home 0 0 However when I boot my Debian I am getting the BusyBox initramfs prompt as per screenshot attached below How can I resolve this and boot my Debian?Thanks | that boot look like a mess.. i dont know what is going on there..seem its not finding things the grub must be pointing to subvolume paths in fstab so you need to chroot subvolume @ and do : 0- install grub of that subvolume: chroot + grub-install /dev/sda 1- update grup of that subvolume chroot + update-grub then you reboot and things should go well if you copied files well and you're using rights paths.. you must use default subvolume as reference to use subvolume paths in fstab.. i meant, the subvolume paths you must using withing fstab must be matchable when you mount subvolid=0.: sudo mount -t btrfs -o subvolid=0 (default subvolume) /dev/sda1 /mnt All paths subvolume there, must be matchable with fstab paths To copy system files within subvolumes and prevent extended permissions issues or things like that.. I would better create a subvolume snapshot and delete all resting folders/file for example, in order to move root installation within @ folder I would do as followed.: cd / sudo btrfs subvolume snapshot . @ sudo mkdir DELETE sudo mv /bin /sys /etc /usr ..... /DELETE && sudo rm -rf /DELETE cos thought Im sure you can use rsync, im no sure how to do it.. I think rsync -aAXv would do it.. but not sure, so better use the method I indicated you above whole process and deployment installation is very easy once you understand how to work with subvolumes...easy peace |
I have just upgraded my system (debian buster kde) to bullseye. Everything seems to be ok but: the icons in gtk applications are not visible. (virt-manager, libreoffice, gnome-disk-utility) When I select the Adwaita-dark theme in Settings -> Application-Style -> Gnome/GTK-Application-Style the icons are visible but in the other themes: Adwaita; Breeze; Default; Emacs; HighContrast the icons are not visible. In Libreoffice I can make the icons visible by selecting 'Breeze' in the Tools -> Options -> General -> View -> Icon Style How can I solve this?? | I removed the map ~/.config/gtk3 Then I went back to the settings and reselected my preferred settings: Global Theme: Breeze Plasma Style: Breeze Dark Gnome/GTK Application Style: Default Now it is working again. I think something went wrong during the upgrade |
I have Debian 10 with open media vault installed. I can't to work out how to make Ethernet interface working with systemd. every boot i got this message in dmesg [ 29.242627] RTL8211DN Gigabit Ethernet r8169-400:00: Master/Slave resolution failed also wifi doesn't work without running wpa_supplicant and dhclient Code: Select allwpa_supplicant -B -i wlp3s0 -c /etc/wpa_supplicant/wpa_suppplicant.conf -D wext Code: Select allip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 30:85:a9:40:6a:09 brd ff:ff:ff:ff:ff:ff 3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 94:db:c9:b4:f7:f9 brd ff:ff:ff:ff:ff:ff inet 192.168.88.28/24 brd 192.168.88.255 scope global dynamic wlp3s0 valid_lft 582sec preferred_lft 582sec inet6 fe80::96db:c9ff:feb4:f7f9/64 scope link valid_lft forever preferred_lft forever Code: Select allcat /etc/network/interfaces # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. # interfaces(5) file used by ifup(8) and ifdown(8) # Better use netplan.io or systemd-networkd to configure additional interface stanzas. # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d Code: Select allcat /etc/systemd/network/lan0.network [Match] Name=enp4s0 [Network] DHCP=yes [DHCP] RouteMetric=10 Code: Select allcat /etc/systemd/network/wlan.network [Match] Name=wlp3s0 [Network] DHCP=yes [DHCP] RouteMetric=20 Code: Select allcat /etc/wpa_supplicant/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant update_config=1 network={ ssid="[i]<SSID>[/i]" #psk="[i]<PASSWORD>[/i]" psk=[i]<somethingInHex>[/i] } dmesg https://pastebin.com/snpjnndw | # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d Use this , not /etc/systemd/network/lan0.network in that rule directory the filenames should include the order prefix, ie 10-lan0 and not '.network' but .link create /etc/network/interfaces.d/lan0.conf Code: Select allallow-hotplug enp4s0 iface enp4s0 inet dhcp /etc/network/interfaces.d/wlan.conf Code: Select allallow-hotplug wlp3s0 iface wlp3s0 inet dhcp wpa-ssid 'ESSID' wpa-psk 'qwerty' ...something like that...delete the file you've made, there bogus |
Dear All, I made a fresh installation of Debian bullseye with LXDE as desktop on my box (a workstation with a wired internet connection). Everything works fine, but I noticed the absence of any network manager icon. So...what network manager is lxde using and how can I get something like a network manager gui? I found only some very seasoned discussion https://ubuntuforums.org/showthread.php ... ost7210414 I found something about nm-tray https://github.com/palinek/nm-tray but I wonder if I need to install something like that or not. Any suggestions? | I have debian 10 Xfce Have you installed: xfce4-goodies And i also have: network-manager-gnome Description: network-manager-gnome NetworkManager is a system network service that manages your network devices and connections, attempting to keep active network connectivity when available. It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE devices, and provides VPN integration with a variety of different VPN services. This package contains a systray applet for GNOME's notification area but it also works for other desktop environments which provide a systray like KDE or Xfce. It displays the available networks and allows users to easily switch between them. For encrypted networks it will prompt the user for the key/passphrase and it can optionally store them in the gnome-keyring. Is this what you might looking for? |
I have been working using Debian the last few weeks and I am satisfied so far. However, when I today went to restoring the local web server/development from BSD, I noticed that it seems very different, the httpd.conf broken up and cluttered over a multitude of files. Is it still somehow possible to somehow just use the (almost) unmodified httpd.conf from BSD? Edit: The reason is to have just one httpd.conf which with minimal modifications runs on practically all systems. Not elegant, but matches my need better. | Well I found out that it works just fine with a single file if one - renames /etc/apache2/apache2.conf to something else - copies the standard httpd.conf to a copy, for example httpd.conf.debian - changes the LoadModules' paths to Debian paths (eg. /usr/lib/apache2/modules/...) - defines an ServerRoot directory, create it and place the mime.types file there - creates a DefaultRuntime entry pointing to this same directory - change User and Group from www to www-data - creates a symlink from /etc/apache2/apache2.conf to the new apache config file just created on the disk pool that contains the web stuff - deletes the contents of /etc/apache2/mods-enabled and then restarts apache. Then the other Debian-specific configuration stuff seems to be ignored. Thus, my question is solved. |
Hi community, I have 3 drives on my system - one for debian (EXT4), one for windows (NTFS) and another for shared data storage (NTFS). I want to mount the data drive while using debian. The first way I did it was using the default settings, Code: Select allUUID=ALPHANUMERICVAL /media/myusername/Data ntfs-3g defaults 0 0 This resulted in all the files in the data drive owned by root and having rwx permissions for all users (777). This to me looks like a huge security risk (Pardon me if my understanding is flawed). So I decided to use the following method, Code: Select allUUID=ALPHANUMERICVAL /media/myusername/Data ntfs-3g defaults,dmask=022,fmask=133,uid=1000,gid=1000,permissions,windows_names 0 0 This changed the ownership to the user and reset the permissions to 755 for directories and 644 for files in the data drive. However, if I were to add executable permission to a particular file using chmod, It wouldn't work. The permission still remain 644. In essence, I'd like to use the the NTFS drive just like a normal linux partition (ie. capable of managing file permissions - I thought the permissions option in the fstab did that). So how can I change my mount options in fstab to achieve this? Is that even possible? | No, NTFS does not support Linux permissions. Better options are to use a DE's integrated solution, or systemd-mount into user space. A fully configured Xfce desktop for example will simply put a device icon on the desktop for a user to click on and use normally. We can configure a user with permission to use systemd-mount. This is independent of the DE, and can be done on a command line, or triggered by ~/.profile at logon. Don't over think it. NTFS does not need special consideration. In either method above there is no mention of NTFS, no use of fstab, and no need for root or jacking permissions. The NTFS partition will be mounted per user. |
Hello, I'm facing weird problem on debian 12.5 and this seems to started recently only, every time I do "apt update" or install any pacakges apt not able to resolve any repository hosts, though my Internet is working fine with all actions like, wget, curl, ping, etc. Seems like issue starts right after Joining AD with SSSD, Before joining AD apt update was working fine, to re-produce the issue, I've destroyed VM and provisioned again and validated apt update was working fine up until joining AD with SSSD. Things which I've already tried: Set resolve.conf to 8.8.8.8 or 1.1.1.1 Disable other repos other than debian Validated ip tables Validated Routing Validated file permissions No issue with Debian 12.1 VM in same Enviroment which are AD joined Output of: Code: Select allLANG="C" apt -o "Debug::Acquire::https=1" -o "Debug::Acquire::http=1" -o "Debug::Acquire::ftp=1" update Code: Select allIgn:1 http://packages.cloud.google.com/apt cloud-sdk-bookworm InRelease Ign:2 http://packages.cloud.google.com/apt google-compute-engine-bookworm-stable InRelease Ign:4 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-bookworm-stable InRelease Ign:5 http://deb.debian.org/debian bookworm InRelease Ign:6 http://deb.debian.org/debian-security bookworm-security InRelease Ign:7 http://deb.debian.org/debian bookworm-updates InRelease Ign:1 http://packages.cloud.google.com/apt cloud-sdk-bookworm InRelease Ign:2 http://packages.cloud.google.com/apt google-compute-engine-bookworm-stable InRelease Ign:4 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-bookworm-stable InRelease Ign:5 http://deb.debian.org/debian bookworm InRelease Ign:6 http://deb.debian.org/debian-security bookworm-security InRelease Ign:7 http://deb.debian.org/debian bookworm-updates InRelease Ign:1 http://packages.cloud.google.com/apt cloud-sdk-bookworm InRelease Ign:2 http://packages.cloud.google.com/apt google-compute-engine-bookworm-stable InRelease Ign:4 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-bookworm-stable InRelease Ign:5 http://deb.debian.org/debian bookworm InRelease Ign:6 http://deb.debian.org/debian-security bookworm-security InRelease Ign:7 http://deb.debian.org/debian bookworm-updates InRelease Err:1 http://packages.cloud.google.com/apt cloud-sdk-bookworm InRelease Temporary failure resolving 'packages.cloud.google.com' Err:2 http://packages.cloud.google.com/apt google-compute-engine-bookworm-stable InRelease Temporary failure resolving 'packages.cloud.google.com' Err:5 http://deb.debian.org/debian bookworm InRelease Temporary failure resolving 'deb.debian.org' Err:4 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-bookworm-stable InRelease Temporary failure resolving 'packages.cloud.google.com' Err:6 http://deb.debian.org/debian-security bookworm-security InRelease Temporary failure resolving 'deb.debian.org' Err:7 http://deb.debian.org/debian bookworm-updates InRelease Temporary failure resolving 'deb.debian.org' Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease Temporary failure resolving 'deb.debian.org' W: Failed to fetch http://deb.debian.org/debian-security/dists/bookworm-security/InRelease Temporary failure resolving 'deb.debian.org' W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease Temporary failure resolving 'deb.debian.org' W: Failed to fetch http://packages.cloud.google.com/apt/dists/cloud-sdk-bookworm/InRelease Temporary failure resolving 'packages.cloud.google.com' W: Failed to fetch http://packages.cloud.google.com/apt/dists/google-compute-engine-bookworm-stable/InRelease Temporary failure resolving 'packages.cloud.google.com' W: Failed to fetch http://packages.cloud.google.com/apt/dists/google-cloud-packages-archive-keyring-bookworm-stable/InRelease Temporary failure resolving 'packages.cloud.google.com' W: Some index files failed to download. They have been ignored, or old ones used instead. | Hello, What is the output of the following commands before and after the issue appears ? Code: Select allscript log.txt sudo apt install bind9-dnsutils ping -c 3 deb.debian.org dig deb.debian.org getent ahosts deb.debian.org exit The log of previous command will be stored in the file named "log.txt" after each run. If you wish, you can report logs in one of the following ways: paste them into the Debian Pastezone service (https://paste.debian.net) and report the URL/link of the paste in a follow-up message attach the logs to a follow-up forum message as a compressed zip or gz file paste the logs into the body of a follow-up message between code tags (if they fit the size of a forum message) What is the DNS configuration supplied by sssd for the AD ? Hope this helps. -- note: please edit the subject of the first post to add the "after Joining AD with SSSD" string; i.e.: apt problem with dns resolution after joining active directory with sssd |
How can I set nic to not respond to ping? I went to ShieldsUp and only had one port "0" that responded and did so with "closed" which I am assuming is the response to my guess is the ping. | Noidly1 wrote: 2024-10-10 02:32 How can I set nic to not respond to ping? By configuring your firewall of choice to drop ICMP echo requests. Noidly1 wrote: 2024-10-10 02:32 I went to ShieldsUp and only had one port "0" that responded and did so with "closed" which I am assuming is the response to my guess is the ping. Port 0 has nothing to do with ping. Port 0 is reserved, should never see any traffic at all, and is almost always blocked at your ISP. If it's not, you can use a firewall rule to drop that traffic as well. Aside, the "stealth" test on GRC is pure paranoia. A closed port will not accept any connections and presents no security risk. |
I've been trying to enable the zram writeback feature. I'm using it on Debian 12 Stable without any other swap device activated; no partition and no swap file, just zram. How do I activate this zram feature with the system configured this way? | @lazulistar Help me understand the use case you're trying to solve? We can run both zram and disk based swap and I did for awhile but found no advantage. |
Hello, Setting up a WiFi AP using NetworkManager on Debian 11. I am beginning with NetworkManager as I want to get rid off a complex system just for setting the network on Linux machines. Here the code I used to create the AP Code: Select allsudo nmcli c add type wifi ifname wlan0 mode ap con-name test-ap-1 ssid stnc-ap autoconnect false sudo nmcli c modify test-ap-1 802-11-wireless.band bg sudo nmcli c modify test-ap-1 ipv4.method shared ipv4.address 172.16.1.1/24 sudo nmcli c modify test-ap-1 wifi-sec.key-mgmt wpa-psk sudo nmcli c modify test-ap-1 wifi-sec.psk "testKEYS" sudo nmcli c up test-ap-1 After that the connection appears OK and the SSID is correctly broacasted but when I try to connect it fails. Trying from an Android phone and from another Linux machine. Here the logs I have from the connecting Linux machine => looks that no IP address is returned (DHCP server not reacting or no DHCP server at all) Code: Select allanv. 02 18:22:35 Arz NetworkManager[27905]: <info> [1735838555.2207] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating janv. 02 18:22:35 Arz NetworkManager[27905]: <info> [1735838555.2399] device (wlp0s20f3): supplicant interface state: associating -> 4way_handshake janv. 02 18:22:35 Arz NetworkManager[27905]: <info> [1735838555.2399] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> 4way_handshake janv. 02 18:22:35 Arz NetworkManager[27905]: <info> [1735838555.2558] device (wlp0s20f3): supplicant interface state: 4way_handshake -> group_handshake janv. 02 18:22:35 Arz NetworkManager[27905]: <info> [1735838555.2558] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> group_handshake janv. 02 18:22:35 Arz NetworkManager[27905]: <info> [1735838555.2717] device (wlp0s20f3): supplicant interface state: group_handshake -> completed janv. 02 18:22:35 Arz NetworkManager[27905]: <info> [1735838555.2717] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "stnc-ap" janv. 02 18:22:35 Arz NetworkManager[27905]: <info> [1735838555.2718] device (p2p-dev-wlp0s20f3): supplicant management interface state: group_handshake -> completed janv. 02 18:22:35 Arz NetworkManager[27905]: <info> [1735838555.2719] device (wlp0s20f3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') janv. 02 18:22:35 Arz NetworkManager[27905]: <info> [1735838555.2725] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) janv. 02 18:23:20 Arz NetworkManager[27905]: <info> [1735838600.2217] device (wlp0s20f3): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed') janv. 02 18:23:20 Arz NetworkManager[27905]: <warn> [1735838600.2238] device (wlp0s20f3): Activation: failed for connection 'stnc-ap' janv. 02 18:23:20 Arz NetworkManager[27905]: <info> [1735838600.2245] device (wlp0s20f3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') janv. 02 18:23:20 Arz NetworkManager[27905]: <info> [1735838600.2327] dhcp4 (wlp0s20f3): canceled DHCP transaction janv. 02 18:23:20 Arz NetworkManager[27905]: <info> [1735838600.2328] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) janv. 02 18:23:20 Arz NetworkManager[27905]: <info> [1735838600.2329] dhcp4 (wlp0s20f3): state changed no lease janv. 02 18:23:20 Arz NetworkManager[27905]: <info> [1735838600.3008] device (wlp0s20f3): supplicant interface state: completed -> disconnected janv. 02 18:23:20 Arz NetworkManager[27905]: <info> [1735838600.3008] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> disconnected On the AP machine nothing meaningful appears in the logs even with the DEBUG level. Tried dhcpdump, but it is not yet installed. I have looked any article explaining the use of DHCP server (dhcpd) with NetworkManager without anything useful found. | Hello, If I understand correctly the question, you have configured your Debian 11 WiFi adapter to work in "AP" (Access Point) mode: you have used the Network Manager from the command line to configure the Debian "access point". Then you tried to connect a second (Debian?) computer to the Debian 11 "access point", but the first one does not get a DHCP lease from the Debian 11 "access point" . Am I right? sterwen wrote: 2025-01-02 17:42 Setting up a WiFi AP using NetworkManager on Debian 11. I am beginning with NetworkManager as I want to get rid off a complex system just for setting the network on Linux machines. Here the code I used to create the AP Code: Select allsudo nmcli c add type wifi ifname wlan0 mode ap con-name test-ap-1 ssid stnc-ap autoconnect false sudo nmcli c modify test-ap-1 802-11-wireless.band bg sudo nmcli c modify test-ap-1 ipv4.method shared ipv4.address 172.16.1.1/24 sudo nmcli c modify test-ap-1 wifi-sec.key-mgmt wpa-psk sudo nmcli c modify test-ap-1 wifi-sec.psk "testKEYS" sudo nmcli c up test-ap-1 What is the source of the commands quoted above ? Below [1] is an alternate source (or is it the same ?). Is a DHCP server installed in the Debian 11 "access point" (e.g. dnsmasq) ? If yes, is it running ? You can verify it running the following commands in the Debian 11 "access point": Code: Select allps ax | grep dhcp apt list dnsmasq* sudo systemctl status dnsmasq Hope this helps. -- [1] Configuring RHEL as a WPA2 or WPA3 Personal access point |
I am running Buster amd64 with XFCE desktop. I know that I can change the DNS server by editing connections in the network icon. What I am wanting to know is this; can I get the system to use the new DNS server settings without having to reboot the computer? I tried to do it by issuing Code: Select all /etc/init.d/networking restart but that didn't seem to apply the new DNS server address. UPDATE: Well, I did what I maybe should have done in the first place; research. From what I can find, I would need to do Code: Select allifdown eth0 ifup eth0 to get the changes to take effect without rebooting. Of course one needs to use the correct interface for their system. In my case, instead of eth0 I would use enp2s0. I would welcome comments, especially if my research was flawed. | Assuming that your "editing connections in the network icons" ends up modifying /etc/resolv.conf, then the effect should be immediate, so there's no need to disconnect-reconnect, reboot, or anything. Most programs use the standard glibc resolver, so the effect is immediate. Maybe Chrome, Firefox, etc. might try to be too "smart" and require restarting (the program, not the computer). |
I've successfully got an old Samsung ML-1610 printer working with Debian. However, I don't know how to access printer specific options - such as clean print head and toner saving mode. Any GUI option? Or maybe something with lp switch -o option, -o option= ? Thanks in advance. | Often this is down to pressing printer buttons rather than using commands on the computer. I would check out the printer manual first e.g. https://www.manualsdir.com/manuals/1407 ... ml?page=62 "Clean printer head" is often applied to inkjets and not lasers. |
I recently did a fresh install of Bullseye on a SSD. Everything works fine. However, I noticed that the fsck message /dev/sdb1: clean #files/#blocks is a really large font, like maybe twice the size of my other three Debian installations.I upgraded two drives from Buster and have one drive still running Buster. The affected drive is booting in the legacy mode as are the Buster drive and the HDD that I upgraded to Bullseye. I have modified the GRUB_GFXMODE and while that makes the GRUB menu to have a nice size it has no effect on anything during boot. I really didn't think it would help but did it anyway. Interestingly, if I remove the quiet mode from GRUB then all the boot messages are a smaller, and acceptable, font size. So why would the freshly installed Bullseye be different? And more importantly is there a way to change the font size of that fsck message? It's really not that big a deal but it just bugs me. Additional info: The console-setup is the same on all Debian installs. Code: Select all# CONFIGURATION FILE FOR SETUPCON # Consult the console-setup(5) manual page. ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="Lat15" FONTFACE="Fixed" FONTSIZE="8x16" VIDEOMODE= # The following is an example how to use a braille font # FONT='lat9w-08.psf.gz brl-8x8.psf' | If you are using console-setup, then also use GRUB_TERMINAL=console and GRUB_GFXMODE comment out. Peter. |
Hi all, I have a Debian10 Linux Machine. It is physical machine. I need to install Kernel Linux Headers for Linux Kernel 5.8.0-1-amd64, unfortunatelly it seems to be not available kernel headers for Linux Kernel 5.8.0-1-amd64. I noted that in this machine is installed "linux-image-4.19.0-16-amd64". Is it possibile change kernel used to boot the system?? I am working remotelly on this machine so I can not select any GRUB Option using Monitor and Keyboard. I tryed to follow this guide but it did not work for me: https://meetrix.io/blog/aws/changing-de ... ernel.html (I know it is for Ubuntu and not Debian but I tryed...) In this moment the OS starts always using "linux-image-5.8.0-1-amd64" and I would use "linux-image-4.19.0-16-amd64" so I can install Kernel Headers (They exists for Linux Kernel linux-image-4.19.0-16-amd64) In this moment I have the following kernels: Code: Select allroot@XXXXXXXX~# dpkg -l | grep linux-image | awk '{print$2}' linux-image-4.19.0-16-amd64 linux-image-4.19.0-9-amd64 linux-image-4.9.0-11-amd64 linux-image-4.9.0-12-amd64 linux-image-5.8.0-1-amd64 linux-image-amd64 My source list APT repo are Code: Select allcat /etc/apt/sources.list # deb cdrom:[Debian GNU/Linux 9.11.0 _Stretch_ - Official amd64 NETINST 20190908-18:12]/ stretch main #deb cdrom:[Debian GNU/Linux 9.11.0 _Stretch_ - Official amd64 NETINST 20190908-18:12]/ stretch main deb http://ftp.it.debian.org/debian/ buster main deb-src http://ftp.it.debian.org/debian/ buster main deb http://security.debian.org/debian-security buster/updates main deb-src http://security.debian.org/debian-security buster/updates main # stretch-updates, previously known as 'volatile' deb http://ftp.it.debian.org/debian/ buster-updates main deb-src http://ftp.it.debian.org/debian/ buster-updates main #SNMP-MIBS #deb http://ftp.it.debian.org/debian sid main non-free #RANCID EXPECT #deb http://ftp.de.debian.org/debian sid main deb http://ftp.debian.org/debian stretch-backports main Have you got any suggestions? Do you suggest me some Kernel 5.8 with Headers? Thanks | Boot the 4.19 kernel and remove the 5.8 one. Then install headers as above although they may be installed already. Why do you have stretch-backports in your sources? Not compatible with Buster which I assume you have updated to and stretch backports should have been removed before updating. The sid sources are also incompatible but at least are commented out; hope you didn't install anything from there. |
Hi all, I would upgrade Debian 9 to Debian 10. Distro upgrade failed because I get this error: Code: Select all/var/caches/apt/archives/bsdextrautils_2.36.1-7_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) How can I solve it? Thanks so much! | That bsdextrautils looks to be from Sid (Unstable). It is not in either Sable or Testing. So, why do you have it? Do you have a mixed system? If this is a one off try removing it. Otherwise do a fresh install. |
Hello, I am using buster with KDE and I seem to be having some wifi issues. Internet connection seems stable to me, but looking in journal I keep getting these messages Code: Select allNetworkManager[974]: <warn> [1603235136.9130] sup-iface[0x563fe53c78b0,wlo1]: connection disconnected (reason -4) wpa_supplicant[972]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/1 NetworkManager[974]: <warn> [1603282864.9538] sup-iface[0x563fe53c78b0,wlo1]: connection disconnected (reason -3) NetworkManager[974]: <warn> [1603282872.4462] sup-iface[0x563fe53c7a10,wlo1]: connection disconnected (reason -4) wpa_supplicant[972]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Those messages would appear sometimes randomly, but would always appear whenever I would put laptop in standby mode, or when it would go to sleep. Looking in Code: Select allsystemctl cat wpa_supplicant I get Code: Select all[Unit] Description=WPA supplicant Before=network.target After=dbus.service Wants=network.target [Service] Type=dbus BusName=fi.w1.wpa_supplicant1 ExecStart=/sbin/wpa_supplicant -u -s -O /run/wpa_supplicant [Install] WantedBy=multi-user.target Alias=dbus-fi.w1.wpa_supplicant1.service As time would pass, I would get up to Interfaces/80 at times. All my networks are managed by network manager and I only use wifi, looking in /etc/network/interfaces shows Code: Select all# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). #source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback #auto eno1 #iface eno1 inet dhcp I haven't noticed any real issues with my internet connection, it only gets really slow from time to time, but I can't be sure it is because of my device. Now for what network device I use Code: Select allsudo lshw -class network *-network description: Wireless interface product: QCA9565 / AR9565 Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@0000:07:00.0 logical name: wlo1 version: 01 serial: a4:db:30:2b:14:5d width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless configuration: broadcast=yes driver=ath9k driverversion=4.19.0-12-amd64 firmware=N/A ip=192.168.1.105 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:c3500000-c357ffff memory:c3580000-c358ffff I had to install firmware-atheros as it was complaining about missing firmware. I have working connection just am slightly annoyed by those messages, and it worries it that could be causing me to lose performance. Running on Code: Select allLinux HP2000 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1 (2020-10-18) x86_64 GNU/Linux Thanks for help. | These are warnings, not errors, which are basically just informational. If your networking is working properly just ignore them. To make journalctl actually useful, use priority filter to only show errors: Code: Select alljournalctl -b -p3 |
For a new installation of Debian I install printing. My printer is HP_LaserJet_Pro_M428f_M429f_8264A8, which supports wireless connection. It is not connected by USB I install cups and hplip. I visit the CUPS interface at localhost:631 and find that CUPS detected my printer automatically. Queue Name Description Make and Model HP_LaserJet_Pro_M428f_M429f_8264A8 HP_LaserJet_Pro_M428f_M429f_8264A8 HP LaserJet Pro M428f-M429f, driverless, cups-filters.128.17 I modify the printer to make it shared and default, although its state ends up being not shared: HP_LaserJet_Pro_M428f_M429f_8264A8 (Idle, Accepting Jobs, Not Shared, Server Default) The problem seems that my system cannot see the printer via network: Code: Select all$ lpq lpq: lp: unknown printer This didn't help: Code: Select all$ sudo lpc restart all HP_LaserJet_Pro_M428f_M429f_8264A8: cannot open lock file HP_LaserJet_Pro_M428f_M429f_8264A8: daemon started There is a cups-dbus-notifier-lockfile in /var/spool/cups/tmp | Your printer supports driverless printing. That would be the way to go. Starting with Debian 11 (bullseye) the printing system is geared up to auto-setup both network and USB local print queues with cups-browsed. These are permanent queues and the auto-setup procedure is intended to sidestep a manual setup in order to make a printer immediately available when it is connected to the network or to USB. The outcome is almost always a happy one for most users. https://wiki.debian.org/CUPSDriverlessPrinting However, it is as well to be aware that drivers and PPDs are deprecated in CUPS and eventually they will not be catered for as they are now. https://wiki.debian.org/SystemPrinting |
Code: Select allroot@hostibu:/etc/apt/sources.list.d# cat /etc/resolv.conf cat: /etc/resolv.conf: No such file or directory root@hostibu:/etc/apt/sources.list.d# cat /etc/nsswitch.conf # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: files systemd group: files systemd shadow: files systemd gshadow: files systemd hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc: db files netgroup: nis root@hostibu:/etc/apt/sources.list.d# cat /etc/resolv.conf cat: /etc/resolv.conf: No such file or directory root@hostibu:/etc/apt/sources.list.d# ping debian.net ping: debian.net: Temporary failure in name resolution Server is far away from me. I am connecting to it via internet but i cant ping to websites from console | Hello, SalihBerat wrote: 2025-01-08 13:05 fix is editing /etc/resolv.conf then texting nameserver 1.1.1.1 I'm glad you got sorted. Please mark the discussion as "Solved" manually adding the tag "[Solved]" at the beginning of the subject of the first post; i.e.: [Networking] [Solved] Temporary failure in name resolution -- note: discussion moved to "System and Networking Configuration" sub-forum EDIT Sun Jan 12 08:59:02 CET 2025: added [Solved] tag. |
I'm running Synology NAS and I'm successfully mounting NFS volumes using Debian 12.4 i386 on other 32bit PCs. Using the same method using Debain 12.8, when I try to mount a volume, I get "mount.nfs: access denied by server while mounting 192.168.0.12:volume1/nas" 1. sudo mkdir -p /nas 2. sudo mount -t nfs 192.168.0.12:volume1/nas /nas I did not change any NFS settings on Synology. Was there some change in version 12.8? Super happy with Debian on my old PCs so hoping to get the latest version installed. Thank you. | The host machine is denying access. I'd be checking /etc/exports on the host machine to ensure the Debian machine's IP address has permission to mount the share. Hope this helps - |
For a new installation of Debian, I installed exiim4, fetchmail and mutt as well. I cannot receive mail because exim locks me out. Here are some lines from the exim log file: Code: Select all2024-12-30 00:21:07 Start queue run: pid=1114523 2024-12-30 00:21:07 1tRTX6-004EuV-0e Message is frozen ... 2024-12-30 00:21:07 1tS8DD-004fwO-28 <= <> R=1tRc6v-004dlL-2p U=Debian-exim P=local S=2247 2024-12-30 00:21:07 1tS8DD-004fwO-28 == /var/mail/haines <haines@iskra.histomat.net> R=userforward T=address_file defer (13): Permission denied: creating lock file hitching post /var/mail/haines.lock.iskra.histomat.net.67722dc3.001101ab (euid=1000 egid=1000) 2024-12-30 00:21:07 1tRbx2-004dkT-1g == /var/mail/haines <haines@localhost> R=userforward T=address_file defer (13): Permission denied: creating lock file hitching post /var/mail/haines.lock.iskra.histomat.net.67722dc3.001101af (euid=1000 egid=1000) 2024-12-30 00:21:07 1tRXHo-004FRR-2n Message is frozen Nothing seems wrong with my /var/mail/haines file: Code: Select all $ ls -la /var/mail total 12440 drwxrwsr-x 2 root mail 4096 Dec 29 16:08 . drwxr-xr-x 12 root root 4096 Dec 17 10:39 .. -rw-rw---- 1 haines mail 6362255 Dec 29 15:56 haines Where does exim put its lock fille? What does "hithing post" refer to? Can exum_lock command be sued to remove a lock? Does the S and R in the message number refer to send and receive? | Hello, Did you mean "exim" instead of "emacs" in the topic? |
Running debian 12 stable with everything updated, except the kernel. It's a dell inspiron 3501 Code: Select all$ sudo apt install linux-image-6.1.0-23-amd64 Lendo listas de pacotes... Pronto Construindo árvore de dependências... Pronto Lendo informação de estado... Pronto linux-image-6.1.0-23-amd64 is already the newest version (6.1.99-1). linux-image-6.1.0-23-amd64 configurado para instalar manualmente. 0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados. $ sudo apt install linux-image-6.1.0-25-amd64 Lendo listas de pacotes... Pronto Construindo árvore de dependências... Pronto Lendo informação de estado... Pronto E: Impossível encontrar o pacote linux-image-6.1.0-25-amd64 E: Couldn't find any package by glob 'linux-image-6.1.0-25-amd64' One of my pc's has this strange thing, I can't upgrade to latest kernel 6.1.0-25, running 6.1.0-23 now. On other machines the upgrade to 25 came as normal as always. What could it be? | Pinning, or a hold on linux-image-amd64 is nonsensical being a meta package. If linux-image-amd64 is not installed then the existing kernel is essentially on hold, and if you want to stay on a kernel that's how to do it. You can install or remove linux-image-amd64 as often as you want to suite. Installed, it will install the latest candidate without removing the last. apt-mark showhold will not reveal a package held by synaptic. If we're not doing this the easy way with syanptic, then the easiest check is with apt policy linux-image-amd64. That will show the installed and the candidate. If the candidate does not show the current repo choice, then the package database is out of date and needs an apt update. Rarely does the incremental kernel updates contain a critical ingredient relevant to every user. |
I got OpenVPN working quite smoothly following this debian wiki. I did all the steps, from the raw testing connection, the static key, and finally the certificates option with which I'm quite happy. My server and clients are linux machines, all using Debian 12 - bookworm. Following the above mentioned wiki link I created certificates and configuration files for both server and clients. It works pretty well every time I execute an openvpn instance from command line, like this: Code: Select allsudo openvpn --config /etc/openvpn/server.conf --verb 6 I can access remotely the server from the clients, and then I can shh from either server or client. But I cannot make it start as a service. So when I reboot my server I have to run openvpn manually from the command line. If I try to restart the openvpn service the tunnel doesn't come up. I'm trying to collect all information possible to find out why. I have read many related topics and guides, but still no luck. I've been a linux users for some years but I'm quite new to openvpn. I hope someone here could point at where I could start looking for logs to find the cause of the problem. This is the server configuration file, located at /etc/openvpn/server.conf: Code: Select allport 1194 proto udp dev tun ca /etc/openvpn/easy-rsa/pki/ca.crt cert /etc/openvpn/easy-rsa/pki/issued/server.crt key /etc/openvpn/easy-rsa/pki/private/server.key dh /etc/openvpn/easy-rsa/pki/dh.pem topology subnet server 10.*.*.0 255.255.255.0 ifconfig-pool-persist ipp.txt #push "route 192.168.0.0 255.255.255.0" # [1] #push "redirect-gateway def1 bypass-dhcp" # [1] keepalive 10 120 tls-auth /etc/openvpn/server/ta.key 0 auth-nocache cipher AES-256-CBC data-ciphers AES-256-CBC persist-key persist-tun status /var/log/openvpn/openvpn-status.log verb 3 client-to-client explicit-exit-notify 1 [1] Note: I intentionally commented those two lines because I was having some errors regarding them, and anyway I was not interested in forwarding client traffic through the server (and I'm not sure if 192.168.0.0 is a valid general address or I should use my real gateway instead, which by the way it is not 192.168.0.1 or ...1.1.) . The /var/log/openvpn/openvpn-status.log is quite 'empty': Code: Select allOpenVPN CLIENT LIST Updated,2025-02-08 11:58:59 Common Name,Real Address,Bytes Received,Bytes Sent,Connected Since ROUTING TABLE Virtual Address,Common Name,Real Address,Last Ref GLOBAL STATS Max bcast/mcast queue length,0 END Here is the output when I run openVPN from the command line with --verbose 6. I don't see any error. sudo openvpn --config /etc/openvpn/server.conf --verb 6 Code: Select all2025-02-08 13:34:13 us=523668 Note: cipher 'AES-256-CBC' in --data-ciphers is not supported by ovpn-dco, disabling data channel offload. 2025-02-08 13:34:13 us=523851 Current Parameter Settings: 2025-02-08 13:34:13 us=523880 config = '/etc/openvpn/server.conf' 2025-02-08 13:34:13 us=523904 mode = 1 2025-02-08 13:34:13 us=523928 persist_config = DISABLED 2025-02-08 13:34:13 us=523950 persist_mode = 1 2025-02-08 13:34:13 us=523973 show_ciphers = DISABLED 2025-02-08 13:34:13 us=523995 show_digests = DISABLED 2025-02-08 13:34:13 us=524017 show_engines = DISABLED 2025-02-08 13:34:13 us=524039 genkey = DISABLED 2025-02-08 13:34:13 us=524062 genkey_filename = '[UNDEF]' 2025-02-08 13:34:13 us=524084 key_pass_file = '[UNDEF]' 2025-02-08 13:34:13 us=524106 show_tls_ciphers = DISABLED 2025-02-08 13:34:13 us=524128 connect_retry_max = 0 2025-02-08 13:34:13 us=524151 Connection profiles [0]: 2025-02-08 13:34:13 us=524173 proto = udp 2025-02-08 13:34:13 us=524196 local = '[UNDEF]' 2025-02-08 13:34:13 us=524218 local_port = '1194' 2025-02-08 13:34:13 us=524240 remote = '[UNDEF]' 2025-02-08 13:34:13 us=524263 remote_port = '1194' 2025-02-08 13:34:13 us=524285 remote_float = DISABLED 2025-02-08 13:34:13 us=524307 bind_defined = DISABLED 2025-02-08 13:34:13 us=524329 bind_local = ENABLED 2025-02-08 13:34:13 us=524351 bind_ipv6_only = DISABLED 2025-02-08 13:34:13 us=524373 connect_retry_seconds = 1 2025-02-08 13:34:13 us=524395 connect_timeout = 120 2025-02-08 13:34:13 us=524418 socks_proxy_server = '[UNDEF]' 2025-02-08 13:34:13 us=524440 socks_proxy_port = '[UNDEF]' 2025-02-08 13:34:13 us=524462 tun_mtu = 1500 2025-02-08 13:34:13 us=524484 tun_mtu_defined = ENABLED 2025-02-08 13:34:13 us=524506 link_mtu = 1500 2025-02-08 13:34:13 us=524528 link_mtu_defined = DISABLED 2025-02-08 13:34:13 us=524550 tun_mtu_extra = 0 2025-02-08 13:34:13 us=524572 tun_mtu_extra_defined = DISABLED 2025-02-08 13:34:13 us=524594 tls_mtu = 1250 2025-02-08 13:34:13 us=524616 mtu_discover_type = -1 2025-02-08 13:34:13 us=524638 fragment = 0 2025-02-08 13:34:13 us=524660 mssfix = 1492 2025-02-08 13:34:13 us=524683 mssfix_encap = ENABLED 2025-02-08 13:34:13 us=524705 mssfix_fixed = DISABLED 2025-02-08 13:34:13 us=524727 explicit_exit_notification = 1 2025-02-08 13:34:13 us=524749 tls_auth_file = '[INLINE]' 2025-02-08 13:34:13 us=524771 key_direction = 0 2025-02-08 13:34:13 us=524793 tls_crypt_file = '[UNDEF]' 2025-02-08 13:34:13 us=524815 tls_crypt_v2_file = '[UNDEF]' 2025-02-08 13:34:13 us=524837 Connection profiles END 2025-02-08 13:34:13 us=524859 remote_random = DISABLED 2025-02-08 13:34:13 us=524881 ipchange = '[UNDEF]' 2025-02-08 13:34:13 us=524903 dev = 'tun' 2025-02-08 13:34:13 us=524925 dev_type = '[UNDEF]' 2025-02-08 13:34:13 us=524947 dev_node = '[UNDEF]' 2025-02-08 13:34:13 us=524969 tuntap_options.disable_dco = ENABLED 2025-02-08 13:34:13 us=524992 lladdr = '[UNDEF]' 2025-02-08 13:34:13 us=525014 topology = 3 2025-02-08 13:34:13 us=525036 ifconfig_local = '10.*.*.1' 2025-02-08 13:34:13 us=525058 ifconfig_remote_netmask = '255.255.255.0' 2025-02-08 13:34:13 us=525080 ifconfig_noexec = DISABLED 2025-02-08 13:34:13 us=525102 ifconfig_nowarn = DISABLED 2025-02-08 13:34:13 us=525124 ifconfig_ipv6_local = '[UNDEF]' 2025-02-08 13:34:13 us=525146 ifconfig_ipv6_netbits = 0 2025-02-08 13:34:13 us=525168 ifconfig_ipv6_remote = '[UNDEF]' 2025-02-08 13:34:13 us=525190 shaper = 0 2025-02-08 13:34:13 us=525212 mtu_test = 0 2025-02-08 13:34:13 us=525234 mlock = DISABLED 2025-02-08 13:34:13 us=525256 keepalive_ping = 10 2025-02-08 13:34:13 us=525278 keepalive_timeout = 120 2025-02-08 13:34:13 us=525300 inactivity_timeout = 0 2025-02-08 13:34:13 us=525322 session_timeout = 0 2025-02-08 13:34:13 us=525344 inactivity_minimum_bytes = 0 2025-02-08 13:34:13 us=525366 ping_send_timeout = 10 2025-02-08 13:34:13 us=525389 ping_rec_timeout = 240 2025-02-08 13:34:13 us=525411 ping_rec_timeout_action = 2 2025-02-08 13:34:13 us=525433 ping_timer_remote = DISABLED 2025-02-08 13:34:13 us=525475 remap_sigusr1 = 0 2025-02-08 13:34:13 us=525498 persist_tun = ENABLED 2025-02-08 13:34:13 us=525521 persist_local_ip = DISABLED 2025-02-08 13:34:13 us=525543 persist_remote_ip = DISABLED 2025-02-08 13:34:13 us=525565 persist_key = ENABLED 2025-02-08 13:34:13 us=525587 passtos = DISABLED 2025-02-08 13:34:13 us=525610 resolve_retry_seconds = 1000000000 2025-02-08 13:34:13 us=525632 resolve_in_advance = DISABLED 2025-02-08 13:34:13 us=525654 username = '[UNDEF]' 2025-02-08 13:34:13 us=525676 groupname = '[UNDEF]' 2025-02-08 13:34:13 us=525698 chroot_dir = '[UNDEF]' 2025-02-08 13:34:13 us=525720 cd_dir = '[UNDEF]' 2025-02-08 13:34:13 us=525742 writepid = '[UNDEF]' 2025-02-08 13:34:13 us=525764 up_script = '[UNDEF]' 2025-02-08 13:34:13 us=525786 down_script = '[UNDEF]' 2025-02-08 13:34:13 us=525808 down_pre = DISABLED 2025-02-08 13:34:13 us=525830 up_restart = DISABLED 2025-02-08 13:34:13 us=525852 up_delay = DISABLED 2025-02-08 13:34:13 us=525874 daemon = DISABLED 2025-02-08 13:34:13 us=525897 log = DISABLED 2025-02-08 13:34:13 us=525919 suppress_timestamps = DISABLED 2025-02-08 13:34:13 us=525942 machine_readable_output = DISABLED 2025-02-08 13:34:13 us=525964 nice = 0 2025-02-08 13:34:13 us=525986 verbosity = 6 2025-02-08 13:34:13 us=526009 mute = 0 2025-02-08 13:34:13 us=526031 gremlin = 0 2025-02-08 13:34:13 us=526053 status_file = '/var/log/openvpn/openvpn-status.log' 2025-02-08 13:34:13 us=526076 status_file_version = 1 2025-02-08 13:34:13 us=526098 status_file_update_freq = 60 2025-02-08 13:34:13 us=526120 occ = ENABLED 2025-02-08 13:34:13 us=526142 rcvbuf = 0 2025-02-08 13:34:13 us=526164 sndbuf = 0 2025-02-08 13:34:13 us=526186 mark = 0 2025-02-08 13:34:13 us=526208 sockflags = 0 2025-02-08 13:34:13 us=526230 fast_io = DISABLED 2025-02-08 13:34:13 us=526253 comp.alg = 0 2025-02-08 13:34:13 us=526275 comp.flags = 24 2025-02-08 13:34:13 us=526297 route_script = '[UNDEF]' 2025-02-08 13:34:13 us=526320 route_default_gateway = '10.*.*.2' 2025-02-08 13:34:13 us=526342 route_default_metric = 0 2025-02-08 13:34:13 us=526364 route_noexec = DISABLED 2025-02-08 13:34:13 us=526386 route_delay = 0 2025-02-08 13:34:13 us=526409 route_delay_window = 30 2025-02-08 13:34:13 us=526431 route_delay_defined = DISABLED 2025-02-08 13:34:13 us=526454 route_nopull = DISABLED 2025-02-08 13:34:13 us=526476 route_gateway_via_dhcp = DISABLED 2025-02-08 13:34:13 us=526498 allow_pull_fqdn = DISABLED 2025-02-08 13:34:13 us=526526 management_addr = '[UNDEF]' 2025-02-08 13:34:13 us=526549 management_port = '[UNDEF]' 2025-02-08 13:34:13 us=526571 management_user_pass = '[UNDEF]' 2025-02-08 13:34:13 us=526594 management_log_history_cache = 250 2025-02-08 13:34:13 us=526616 management_echo_buffer_size = 100 2025-02-08 13:34:13 us=526639 management_client_user = '[UNDEF]' 2025-02-08 13:34:13 us=526661 management_client_group = '[UNDEF]' 2025-02-08 13:34:13 us=526683 management_flags = 0 2025-02-08 13:34:13 us=526706 shared_secret_file = '[UNDEF]' 2025-02-08 13:34:13 us=526728 key_direction = 0 2025-02-08 13:34:13 us=526751 ciphername = 'AES-256-CBC' 2025-02-08 13:34:13 us=526773 ncp_ciphers = 'AES-256-CBC' 2025-02-08 13:34:13 us=526796 authname = 'SHA1' 2025-02-08 13:34:13 us=526818 engine = DISABLED 2025-02-08 13:34:13 us=526840 replay = ENABLED 2025-02-08 13:34:13 us=526863 mute_replay_warnings = DISABLED 2025-02-08 13:34:13 us=526885 replay_window = 64 2025-02-08 13:34:13 us=526908 replay_time = 15 2025-02-08 13:34:13 us=526930 packet_id_file = '[UNDEF]' 2025-02-08 13:34:13 us=526952 test_crypto = DISABLED 2025-02-08 13:34:13 us=526974 tls_server = ENABLED 2025-02-08 13:34:13 us=526997 tls_client = DISABLED 2025-02-08 13:34:13 us=527019 ca_file = '/etc/openvpn/easy-rsa/pki/ca.crt' 2025-02-08 13:34:13 us=527041 ca_path = '[UNDEF]' 2025-02-08 13:34:13 us=527064 dh_file = '/etc/openvpn/easy-rsa/pki/dh.pem' 2025-02-08 13:34:13 us=527086 cert_file = '/etc/openvpn/easy-rsa/pki/issued/server.crt' 2025-02-08 13:34:13 us=527121 extra_certs_file = '[UNDEF]' 2025-02-08 13:34:13 us=527144 priv_key_file = '/etc/openvpn/easy-rsa/pki/private/server.key' 2025-02-08 13:34:13 us=527167 pkcs12_file = '[UNDEF]' 2025-02-08 13:34:13 us=527189 cipher_list = '[UNDEF]' 2025-02-08 13:34:13 us=527211 cipher_list_tls13 = '[UNDEF]' 2025-02-08 13:34:13 us=527233 tls_cert_profile = '[UNDEF]' 2025-02-08 13:34:13 us=527256 tls_verify = '[UNDEF]' 2025-02-08 13:34:13 us=527278 tls_export_cert = '[UNDEF]' 2025-02-08 13:34:13 us=527300 verify_x509_type = 0 2025-02-08 13:34:13 us=527324 verify_x509_name = '[UNDEF]' 2025-02-08 13:34:13 us=527347 crl_file = '[UNDEF]' 2025-02-08 13:34:13 us=527370 ns_cert_type = 0 2025-02-08 13:34:13 us=527393 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527416 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527439 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527461 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527484 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527507 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527530 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527553 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527576 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527598 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527621 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527664 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527687 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527710 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527732 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527755 remote_cert_ku[i] = 0 2025-02-08 13:34:13 us=527778 remote_cert_eku = '[UNDEF]' 2025-02-08 13:34:13 us=527801 ssl_flags = 192 2025-02-08 13:34:13 us=527824 tls_timeout = 2 2025-02-08 13:34:13 us=527847 renegotiate_bytes = -1 2025-02-08 13:34:13 us=527870 renegotiate_packets = 0 2025-02-08 13:34:13 us=527893 renegotiate_seconds = 3600 2025-02-08 13:34:13 us=527916 handshake_window = 60 2025-02-08 13:34:13 us=527939 transition_window = 3600 2025-02-08 13:34:13 us=527962 single_session = DISABLED 2025-02-08 13:34:13 us=527984 push_peer_info = DISABLED 2025-02-08 13:34:13 us=528007 tls_exit = DISABLED 2025-02-08 13:34:13 us=528030 tls_crypt_v2_metadata = '[UNDEF]' 2025-02-08 13:34:13 us=528053 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528075 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528099 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528121 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528144 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528167 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528190 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528213 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528236 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528259 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528281 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528304 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528327 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528350 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528372 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528395 pkcs11_protected_authentication = DISABLED 2025-02-08 13:34:13 us=528419 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528442 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528465 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528488 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528511 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528534 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528557 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528580 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528603 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528625 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528660 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528683 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528705 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528728 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528750 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528772 pkcs11_private_mode = 00000000 2025-02-08 13:34:13 us=528794 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=528817 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=528839 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=528861 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=528883 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=528906 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=528928 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=528950 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=528972 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=528995 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=529017 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=529039 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=529061 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=529083 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=529106 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=529128 pkcs11_cert_private = DISABLED 2025-02-08 13:34:13 us=529151 pkcs11_pin_cache_period = -1 2025-02-08 13:34:13 us=529173 pkcs11_id = '[UNDEF]' 2025-02-08 13:34:13 us=529196 pkcs11_id_management = DISABLED 2025-02-08 13:34:13 us=529220 server_network = 10.*.*.0 2025-02-08 13:34:13 us=529244 server_netmask = 255.255.255.0 2025-02-08 13:34:13 us=529268 server_network_ipv6 = :: 2025-02-08 13:34:13 us=529291 server_netbits_ipv6 = 0 2025-02-08 13:34:13 us=529314 server_bridge_ip = 0.0.0.0 2025-02-08 13:34:13 us=529338 server_bridge_netmask = 0.0.0.0 2025-02-08 13:34:13 us=529361 server_bridge_pool_start = 0.0.0.0 2025-02-08 13:34:13 us=529384 server_bridge_pool_end = 0.0.0.0 2025-02-08 13:34:13 us=529407 push_entry = 'route-gateway 10.*.*.1' 2025-02-08 13:34:13 us=529429 push_entry = 'topology subnet' 2025-02-08 13:34:13 us=529452 push_entry = 'ping 10' 2025-02-08 13:34:13 us=529474 push_entry = 'ping-restart 120' 2025-02-08 13:34:13 us=529496 ifconfig_pool_defined = ENABLED 2025-02-08 13:34:13 us=529520 ifconfig_pool_start = 10.*.*.2 2025-02-08 13:34:13 us=529543 ifconfig_pool_end = 10.*.*.254 2025-02-08 13:34:13 us=529566 ifconfig_pool_netmask = 255.255.255.0 2025-02-08 13:34:13 us=529589 ifconfig_pool_persist_filename = 'ipp.txt' 2025-02-08 13:34:13 us=529611 ifconfig_pool_persist_refresh_freq = 600 2025-02-08 13:34:13 us=529633 ifconfig_ipv6_pool_defined = DISABLED 2025-02-08 13:34:13 us=529656 ifconfig_ipv6_pool_base = :: 2025-02-08 13:34:13 us=529679 ifconfig_ipv6_pool_netbits = 0 2025-02-08 13:34:13 us=529701 n_bcast_buf = 256 2025-02-08 13:34:13 us=529724 tcp_queue_limit = 64 2025-02-08 13:34:13 us=529746 real_hash_size = 256 2025-02-08 13:34:13 us=529769 virtual_hash_size = 256 2025-02-08 13:34:13 us=529791 client_connect_script = '[UNDEF]' 2025-02-08 13:34:13 us=529813 learn_address_script = '[UNDEF]' 2025-02-08 13:34:13 us=529846 client_disconnect_script = '[UNDEF]' 2025-02-08 13:34:13 us=529869 client_crresponse_script = '[UNDEF]' 2025-02-08 13:34:13 us=529891 client_config_dir = '[UNDEF]' 2025-02-08 13:34:13 us=529913 ccd_exclusive = DISABLED 2025-02-08 13:34:13 us=529936 tmp_dir = '/tmp' 2025-02-08 13:34:13 us=529958 push_ifconfig_defined = DISABLED 2025-02-08 13:34:13 us=529981 push_ifconfig_local = 0.0.0.0 2025-02-08 13:34:13 us=530004 push_ifconfig_remote_netmask = 0.0.0.0 2025-02-08 13:34:13 us=530027 push_ifconfig_ipv6_defined = DISABLED 2025-02-08 13:34:13 us=530050 push_ifconfig_ipv6_local = ::/0 2025-02-08 13:34:13 us=530073 push_ifconfig_ipv6_remote = :: 2025-02-08 13:34:13 us=530095 enable_c2c = ENABLED 2025-02-08 13:34:13 us=530118 duplicate_cn = DISABLED 2025-02-08 13:34:13 us=530141 cf_max = 0 2025-02-08 13:34:13 us=530174 cf_per = 0 2025-02-08 13:34:13 us=530197 cf_initial_max = 100 2025-02-08 13:34:13 us=530220 cf_initial_per = 10 2025-02-08 13:34:13 us=530242 max_clients = 1024 2025-02-08 13:34:13 us=530265 max_routes_per_client = 256 2025-02-08 13:34:13 us=530287 auth_user_pass_verify_script = '[UNDEF]' 2025-02-08 13:34:13 us=530310 auth_user_pass_verify_script_via_file = DISABLED 2025-02-08 13:34:13 us=530332 auth_token_generate = DISABLED 2025-02-08 13:34:13 us=530354 auth_token_lifetime = 0 2025-02-08 13:34:13 us=530377 auth_token_secret_file = '[UNDEF]' 2025-02-08 13:34:13 us=530399 port_share_host = '[UNDEF]' 2025-02-08 13:34:13 us=530421 port_share_port = '[UNDEF]' 2025-02-08 13:34:13 us=530444 vlan_tagging = DISABLED 2025-02-08 13:34:13 us=530466 vlan_accept = all 2025-02-08 13:34:13 us=530488 vlan_pvid = 1 2025-02-08 13:34:13 us=530511 client = DISABLED 2025-02-08 13:34:13 us=530533 pull = DISABLED 2025-02-08 13:34:13 us=530556 auth_user_pass_file = '[UNDEF]' 2025-02-08 13:34:13 us=530580 OpenVPN 2.6.3 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] 2025-02-08 13:34:13 us=530617 library versions: OpenSSL 3.0.15 3 Sep 2024, LZO 2.10 2025-02-08 13:34:13 us=530659 DCO version: N/A 2025-02-08 13:34:13 us=530848 net_route_v4_best_gw query: dst 0.0.0.0 2025-02-08 13:34:13 us=530952 sitnl_send: checking for received messages 2025-02-08 13:34:13 us=530991 sitnl_send: rtnl: received 496 bytes 2025-02-08 13:34:13 us=531053 net_route_v4_best_gw result: via 192.168.*.1 dev enp4s0 2025-02-08 13:34:13 us=533785 Diffie-Hellman initialized with 2048 bit key Enter Private Key Password: *********** 2025-02-08 13:34:17 us=761878 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication 2025-02-08 13:34:17 us=762008 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication 2025-02-08 13:34:17 us=762129 TLS-Auth MTU parms [ mss_fix:0 max_frag:0 tun_mtu:1250 tun_max_mtu:0 headroom:126 payload:1600 tailroom:126 ET:0 ] 2025-02-08 13:34:17 us=762987 TUN/TAP device tun0 opened 2025-02-08 13:34:17 us=763045 do_ifconfig, ipv4=1, ipv6=0 2025-02-08 13:34:17 us=763101 net_iface_mtu_set: mtu 1500 for tun0 2025-02-08 13:34:17 us=763173 sitnl_send: checking for received messages 2025-02-08 13:34:17 us=763204 sitnl_send: rtnl: received 36 bytes 2025-02-08 13:34:17 us=763254 net_iface_up: set tun0 up 2025-02-08 13:34:17 us=763595 sitnl_send: checking for received messages 2025-02-08 13:34:17 us=763663 sitnl_send: rtnl: received 36 bytes 2025-02-08 13:34:17 us=763715 net_addr_v4_add: 10.*.*.1/24 dev tun0 2025-02-08 13:34:17 us=763960 sitnl_send: checking for received messages 2025-02-08 13:34:17 us=764011 sitnl_send: rtnl: received 36 bytes 2025-02-08 13:34:17 us=764081 Data Channel MTU parms [ mss_fix:0 max_frag:0 tun_mtu:1500 tun_max_mtu:1600 headroom:136 payload:1768 tailroom:562 ET:0 ] 2025-02-08 13:34:17 us=764117 Could not determine IPv4/IPv6 protocol. Using AF_INET 2025-02-08 13:34:17 us=764177 Socket Buffers: R=[212992->212992] S=[212992->212992] 2025-02-08 13:34:17 us=764227 UDPv4 link local (bound): [AF_INET][undef]:1194 2025-02-08 13:34:17 us=764263 UDPv4 link remote: [AF_UNSPEC] 2025-02-08 13:34:17 us=764350 MULTI: multi_init called, r=256 v=256 2025-02-08 13:34:17 us=764459 IFCONFIG POOL IPv4: base=10.*.*.2 size=253 2025-02-08 13:34:17 us=764539 ifconfig_pool_read(), in='client_andalus,10.*.*.2,' 2025-02-08 13:34:17 us=764584 succeeded -> ifconfig_pool_set(hand=0) 2025-02-08 13:34:17 us=764618 ifconfig_pool_read(), in='clientname,10.*.*.3,' 2025-02-08 13:34:17 us=764654 succeeded -> ifconfig_pool_set(hand=1) 2025-02-08 13:34:17 us=764691 IFCONFIG POOL LIST 2025-02-08 13:34:17 us=764726 client_1,10.*.*.1, 2025-02-08 13:34:17 us=764760 client_2,10.*.*.1, 2025-02-08 13:34:17 us=764848 Initialization Sequence Completed What I don't undestand is why the openvpn service doesn't load when running systemctl restart or at the boot and it doesn't yield any error outputs. Please, where could I start looking for issues? | Hello, anndreih wrote: 2025-02-10 03:50 I focused on the passphrase messages and found some posts talking about parsing the passphrase. Some of them (eg. here) suggested to add the argument "askpass <file>" to the config file of the server. One hast to put the passphrase in a text file, protect it with "chmod 400 <file>" and add "askpass file.txt" to the server configuration file. It worked for me. The service now loads correctly, the openvpn tunnel appears (when check with "ip a") and if I restart the pc it automatically loads well. I checked that I can connect from the client. I'm glad you sorted it out. Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message. Thanks. Happy Debian ! |
Good day all the good people! I'll bypass all the opposite characters and go strict to the point. Having ProtonVPN service in Russia. That gives a bit of headache as if I broke down the law which I'm not even by distorted Russian judicial system. Pre-paid VPN services do connect and serve for both Android mobile and Android TV behind my router. Debian and AsusWRT-Merlin router both are completely stuck in the initial phase of connection using OVPN and WG. I did try to establish VPN tunnel for Debian using OpenVPN-client for TCP and UDP protocols - has failed. Then I've initiated WireGuard-client for Debian. Failure. Same connection status for the same clients on router. What irritates me most is that above mentioned Androids are connecting within the same WiFi ethernet without any delay. VPN config files for OpenVPN and WireGuard connections are set for different tunnels and for various platforms. Connection mode is described here: https://protonvpn.com/support/wireguard-linux and here: https://protonvpn.com/support/linux-openvpn . Upon setting either of two I could get 'ping', 'traceroute', 'dig' and 'nslookup' in the shell act absolutely normal. No internet browsing or any IM are operational though. Due to the nature of the connected services and Android clients behind router being successfully connected to VPN services I suggest I'm doing something wrong and need to correct my Debian configuration only. How to use OpenVPN or WireGuard in my Bullseye or router if nothing except 'ping', 'traceroute' and 'nslookup' shell commands seems to be passing through? WireGuard shell output given below. Code: Select all# Be advised that for privacy reasons I've replaced Endpoint Address and Port with other value from the same config for PC. # desktopuser@mydesktop:~$ sudo wg-quick up US21-TOR [sudo] password for desktopuser: [#] ip link add US21-TOR type wireguard [#] wg setconf US21-TOR /dev/fd/63 [#] ip -4 address add 10.2.0.2/32 dev US21-TOR [#] ip link set mtu 1420 up dev US21-TOR [#] resolvconf -a tun.US21-TOR -m 0 -x [#] wg set US21-TOR fwmark 51820 [#] ip -4 route add 0.0.0.0/0 dev US21-TOR table 51820 [#] ip -4 rule add not fwmark 51820 table 51820 [#] ip -4 rule add table main suppress_prefixlength 0 [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 [#] nft -f /dev/fd/63 desktopuser@mydesktop:~$ sudo wg interface: US21-TOR public key: KEYVALUE private key: (hidden) listening port: 34289 fwmark: 0xca6c peer: PEER/KEYVALUE endpoint: 84.17.63.17:51820 allowed ips: 0.0.0.0/0 transfer: 0 B received, 888 B sent desktopuser@mydesktop:~$ dig ip.me ; <<>> DiG 9.16.50-Debian <<>> ip.me ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44722 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;ip.me. IN A ;; ANSWER SECTION: ip.me. 10720 IN A 212.102.35.236 ;; Query time: 0 msec ;; SERVER: 192.168.249.1#53(192.168.249.1) ;; WHEN: Sat Sep 14 15:47:32 MSK 2024 ;; MSG SIZE rcvd: 50 desktopuser@mydesktop:~$ nslookup google.com Server: 192.168.249.1 Address: 192.168.249.1#53 Non-authoritative answer: Name: google.com Address: 142.251.1.139 Name: google.com Address: 142.251.1.113 Name: google.com Address: 142.251.1.101 Name: google.com Address: 142.251.1.100 Name: google.com Address: 142.251.1.102 Name: google.com Address: 142.251.1.138 Name: google.com Address: 2a00:1450:4010:c1e::8b Name: google.com Address: 2a00:1450:4010:c1e::64 Name: google.com Address: 2a00:1450:4010:c1e::65 Name: google.com Address: 2a00:1450:4010:c1e::8a | Since ping works, maybe an mtu problem? Try increasing the packet size and see when it breaks. Here for reference: Code: Select all$> ping -c 2 -M do -s 1452 debian.net PING debian.net(mirror-csail.debian.org (2603:400a:ffff:bb8::801f:3e)) 1452 data bytes 1460 bytes from mirror-csail.debian.org (2603:400a:ffff:bb8::801f:3e): icmp_seq=1 ttl=51 time=113 ms 1460 bytes from mirror-csail.debian.org (2603:400a:ffff:bb8::801f:3e): icmp_seq=2 ttl=51 time=109 ms --- debian.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 109.076/110.923/112.770/1.847 ms $> ping -c 2 -M do -s 1453 debian.net PING debian.net(mirror-csail.debian.org (2603:400a:ffff:bb8::801f:3e)) 1453 data bytes ping: local error: message too long, mtu: 1500 ping: local error: message too long, mtu: 1500 --- debian.net ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1004ms $> ip addr | grep "mtu" 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 |
Hi all, I installed Debian 12 a couple months ago on my Lenovo laptop with an Intel Core i5-7200U. I haven't done much other than some web browsing and GUI customization (no terminal), but I encounter this kernel error now when booting up. Code: Select allLoading Linux 6.1.0-31-amd64 Loading initial ramdisk error: out of memory Which then takes me to this screen where all I can do is manually power off my laptop. (btw this picture shows kernel 6.1.0-30, I get the same error for kernel 6.1.0-31) Screenshot from 2025-02-13 11-01-04_prnit.png (340.37 KiB) Viewed 5658 times I am able to boot when I select kernel 6.1.0-27 but would like to be up to date. When I do these commands, I am told that I'm already up to date. Code: Select allsudo apt update sudo apt upgrade I would prefer to avoid a fresh install of Debian since I've already done some customizing and want to learn how to fix this through commands or other methods instead. | Hello, If I read this correctly, the error occurs because the kernel cannot mount the root filesystem when booting Debian with kernel version 6.1.0-30. Is there free space on the root filesystem? Were the initramfs for recent kernels corrupted during installation? Can you boot with the working kernel and report the output of the following commands? Code: Select allscript log.txt lsblk -all -fs sudo update-initramfs -u -k all exit The log file will be named log.txt If you wish, you can report logs in one of the following ways: paste them into the Debian Pastezone service (https://paste.debian.net) and report the URL/link of the paste in a follow-up message attach the logs to a follow-up forum message as a compressed zip or gz file paste the logs into the body of a follow-up message between code tags (if they fit the size of a forum message) |
I have found the advanced install feature, that allows me to configure the network in "/etc/network/interfaces" but once I reboot, it is still doing DHCP config, and I can't find NetworkManager to disable it. I did one install with the network cable disconnected, and was able to have the proper configuration in "/etc/network/interfaces" Thank you for your time, | Hello, arussell wrote: 2025-02-17 05:16 I have found the advanced install feature, that allows me to configure the network in "/etc/network/interfaces" but once I reboot, it is still doing DHCP config, and I can't find NetworkManager to disable it. I did one install with the network cable disconnected, and was able to have the proper configuration in "/etc/network/interfaces" Thank you for your time, You can manually edit the /etc/network/interfaces using the "root" account. What are the content of /etc/network/interfaces ? |
I have two drives, a SSD and an HDD, installed in my desktop. Both drives have Debian Buster installed in the legacy mode. The fstab of the SSD has it mounting as /dev/sda1 and fstab of the HDD mounts as /dev/sdb1. GRUB is currently installed on the SSD. What I would like to do, if possible, is to have GRUB installed to the MBR of both drives so that if the SSD fails I can simply select the HDD in the BIOS boot order and then boot from that drive. As it stands, if I try to boot directly to the HDD I get a GRUB_calloc error. Maybe I am misunderstanding the problem but I am assuming that error is because GRUB is not installed to the MBR of the HDD. So, is it possible to have both drives bootable by selecting the appropriate boot order in the BIOS? What I have tried is to install grub on the HDD and while that makes that drive boot when selected in BIOS, then the SSD is no longer bootable when selected in the BIOS. | ticojohn wrote:if I try to boot directly to the HDD I get a GRUB_calloc error. Maybe I am misunderstanding the problem but I am assuming that error is because GRUB is not installed to the MBR of the HDD. No, GRUB is installed in the MBR of the HDD but you get this error because there is a version mismatch between the part installed in the MBR and the part installed in the /boot/grub location it points to (which may be on either disk). This can happen when one part is updated and not the other. There are two ways of installing GRUB on both drives : a) Install GRUB in the MBR on both drives from the same Debian instance. Both MBRs point to the same /boot/grub location of that instance. This means that the disk of the other Debian instance will not boot properly if the other disk is missing or failed. b) Install GRUB in the MBR of each drive from the Debian instance installed on that drive. Each MBR points to the /boot/grub location on its own disk and does not depend on the other disk. How you boot a Debian instance from GRUB installed by the other Debian instance is a separate issue. |
hi Ive this two audio cards and Im using pavucontrol to turn on/off between both of them, how can I do this with a command line??, thanks a lot | See pactl(1) & https://unix.stackexchange.com/question ... from-shell |
Hello, Today I tried to update my system (buster) and noticed some new zfs packages which I installed with apt-get dist-upgrade. The upgrade ended with an error message: Code: Select alldepmod... DKMS: install completed. Setting up libuutil3linux (2.0.2-1~bpo10+1) ... Setting up libzfs4linux (2.0.2-1~bpo10+1) ... Setting up libzpool4linux (2.0.2-1~bpo10+1) ... Setting up zfsutils-linux (2.0.2-1~bpo10+1) ... Installing new version of config file /etc/default/zfs ... Installing new version of config file /etc/zfs/zfs-functions ... zfs-import-scan.service is a disabled or a static unit not running, not starting it. Processing triggers for initramfs-tools (0.133+deb10u1) ... update-initramfs: Generating /boot/initrd.img-4.19.0-14-amd64 Processing triggers for libc-bin (2.28-10) ... Processing triggers for systemd (241-7~deb10u6) ... Processing triggers for man-db (2.8.5-2) ... Setting up zfs-zed (2.0.2-1~bpo10+1) ... Installing new version of config file /etc/init.d/zfs-zed ... Installing new version of config file /etc/zfs/zed.d/zed-functions.sh ... Installing new version of config file /etc/zfs/zed.d/zed.rc ... ln: failed to create symbolic link '/etc/zfs/zed.d/history_event-zfs-list-cacher.sh': File exists dpkg: error processing package zfs-zed (--configure): installed zfs-zed package post-installation script subprocess returned error exit status 1 Processing triggers for systemd (241-7~deb10u6) ... Errors were encountered while processing: zfs-zed E: Sub-process /usr/bin/dpkg returned an error code (1) The link /etc/zfs/zed.d/history_event-zfs-list-cacher.sh exists and points to a file that does not exist: Code: Select allroot@TRILLIAN:~# ls -l /etc/zfs/zed.d/history_event-zfs-list-cacher.sh lrwxrwxrwx 1 root root 51 Nov 11 14:34 /etc/zfs/zed.d/history_event-zfs-list-cacher.sh -> /usr/lib/zfs/zed.d/history_event-zfs-list-cacher.sh root@TRILLIAN:~# ls -l /usr/lib/zfs/zed.d/history_event-zfs-list-cacher.sh ls: cannot access '/usr/lib/zfs/zed.d/history_event-zfs-list-cacher.sh': No such file or directory How can I fix this? Is it safe to reboot the system in its current state? Thanks a lot for any advice. Toquinho PS: Code: Select allroot@TRILLIAN:~# uname -a Linux TRILLIAN 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux | toquinho wrote:How can I fix this? Delete the dangling symlink and try to upgrade the package again. This may be worth a bug report. toquinho wrote:Is it safe to reboot the system in its current state? I would think so, the upgrade didn't go through. But I don't use zfs so I might be wrong. |
I use Debian 10 on a desktop PC with ethernet connection. This morning, my house has been connected to the fibre instead of ADSL. Since, Debian connects to the ethernet network (1000MGB/s max), but I can't reach internet. I tried with Windows 10 (Dual boot), it works. I tried to connect the ethernet cable on my laptop with debian 10, it works... So the problem is on my Debian PC, but I don't know where to check ! Can someone help me ? | Code: Select alldefault via 192.168.1.254 Code: Select allnameserver 192.168.1.1 Usually, the internet box acts as default router and DNS server, so both settings are the same address. Maybe either setting has been fixed in the network configuration (resolvconf, NetworkManager, /etc/network/interfaces, /etc/dhcp/dhclient.conf...). |
I recently upgraded one of my installations to Bullseye (amd64). I noticed that and linux image (4.19) is still installed, although the associated header appears to not be installed. Code: Select all# dpkg --list | egrep -i --color 'linux-image|linux-headers' ii linux-headers-5.10.0-3-amd64 5.10.13-1 amd64 Header files for Linux 5.10.0-3-amd64 ii linux-headers-5.10.0-3-common 5.10.13-1 all Common header files for Linux 5.10.0-3 ii linux-headers-5.10.0-4-amd64 5.10.19-1 amd64 Header files for Linux 5.10.0-4-amd64 ii linux-headers-5.10.0-4-common 5.10.19-1 all Common header files for Linux 5.10.0-4 ii linux-headers-amd64 5.10.19-1 amd64 Header files for Linux amd64 configuration (meta-package) ii linux-image-4.19.0-13-amd64 4.19.160-2 amd64 Linux 4.19 for 64-bit PCs (signed) ii linux-image-5.10.0-3-amd64 5.10.13-1 amd64 Linux 5.10 for 64-bit PCs (signed) ii linux-image-5.10.0-4-amd64 5.10.19-1 amd64 Linux 5.10 for 64-bit PCs (signed) ii linux-image-amd64 5.10.19-1 amd64 Linux for 64-bit PCs (meta-package) Just wondering if this is normal and if not should I do anything? Perhaps the system defaults to retaining a certain number of old images. Enlightenment would be appreciated. Thanks. | ticojohn wrote:p.H wrote:ticojohn wrote:It was definitely NOT manually installed. Packages can be marked as manually installed for several reasons including if they are dependencies of other manually installed packages. Run this to check which packages are marked as manual: Code: Select allapt-mark showmanual But that's probably not your case as Head_on_a_Stick explained. apt will keep one previous kernel by default if you run Code: Select allapt full-upgradebut it won't remove any packages if you just Code: Select allapt upgrade In Testing and Unstable you should generally do Code: Select allapt full-upgrade or your system will become clogged with unneeded packages. Like old kernels. |
As the title says, I am having problems with SCT on a newly built system. With my old system, SCT works just fine, but with this new system, SCT (and also REDSHIFT) do not work at all. Issuing a "sct 2700" (or any other temperature) from the terminal does nothing, no errors reported. Tried "redshift -O 2700" also does not work... but does return the following: Gamma ramp size too small: 0 Failed to start adjustment method randr. Trying next method... Using method `vidmode'. ... and then returns to the terminal prompt. System Information: CPU: AMD Ryzen 5 3400G Monitor: Viewsonic XG2705-2K OS: Debian 10 (Buster), Kernel 4.19.0-14, Mate 1.20.4 Any help or suggestions would be much appreciated. | What is your graphics hardware and driver? Have you installed any non-free firmware that is required? |
Hi folks, I saw in the past a lot of routers/modems which are able to transform an "USB" printer into a "Network printer". USB Print Server devices are also available from various manufacturer. Fortunately, those devices don't need the driver of the printer : driver is installed on the client side. By doing so, client computer is able to access Ink levels and various things provided by the driver, so that the USB Print Server doesn't put any limitation by trying to drive the printer by itself. I'm pretty sure that it's possible to do it from Debian, after all. But everything I found is using CUPS, making it listen on every interface, installing the correct driver/PPD into CUPS, and then, connecting existing Windows computers to it thanks to the cups link (http://ip-address:631/printers/PrinterName) but it's not using an IP adress, it's using CUPS address, and cups drivers as an intermediate layer. I'm in front of an "8 cartdrige" printer and Windows computer cannot access the ink levels by this method. Before buying a physical USB Print Server, is it possible to configure some Debian service for making the printer available trough IP address, without using CUPS and his drivers ? Thank you in advance ! | jrobin28260 wrote:I saw in the past a lot of routers/modems which are able to transform an "USB" printer into a "Network printer". USB Print Server devices are also available from various manufacturer. Fortunately, those devices don't need the driver of the printer : driver is installed on the client side. By doing so, client computer is able to access Ink levels and various things provided by the driver, so that the USB Print Server doesn't put any limitation by trying to drive the printer by itself. I'm pretty sure that it's possible to do it from Debian, after all. I think what you're looking for is USB-over-IP, i.e. where a USB-connected device physically connected to a server is seen by a client as if it were physically connected to it. For that, you need the usbip package (# apt install usbip). You can then read: http://usbip.sourceforge.net/ https://www.howtoforge.com/how-to-modif ... -ip-server http://www.linux-magazine.com/Issues/20 ... ial-USB-IP I haven't tried this myself (and currently have no need for this), but hopefully it will work as you expect. Would appreciate feedback if it worked (and if it didn't). |
Hey everyone, I've installed Buster on a machine I put together at the weekend after my main box's SSD was killed by hot weather. Virtualisation is enabled in BIOS (CPU supports VT-x, VT-d & EPT) and installed qemu-kvm, libvirt-daemon, libvirt-clients and virt-manager, but when I try and create a new VM in virt-manger I get a message saying: Code: Select allWarning: KVM is not available. This may mean the KVM package is not installed, or the KVM kernel modules are not loaded. Your virtual machines may perform poorly. If I run lsmod | grep kvm I get: kvm_intel 245760 0 kvm 724992 1 kvm_intel irqbypass 16384 1 kvm so it looks like the modules are loaded ok. After I create a VM, the Hypervisor shown in the VM's config as QEMU TCG instead of KVM. If I run kvm from a terminal window it fires up and attempts to PXE boot. I created a live CD of Ubuntu 19, installed everything and it worked straight away. Does anyone have kvm and virt-manager working correctly under Buster? Thanks, bored | https://wiki.debian.org/KVM |
Hello, I want to use a laptop with a wireless and a wired network interface to set up a separate subnet that only the laptop can see. The interfaces are enp4s0 and wlp2s0: Code: Select allroot@FENCHURCH:~# netstat -i Tabela de Interfaces do Kernel Iface MTU RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg enp4s0 1500 0 0 0 0 0 0 0 0 BMU lo 65536 0 0 0 0 0 0 0 0 LRU wlp2s0 1500 3377 0 0 0 1598 0 0 0 BMRU I want wlp2s0 to connect to my normal LAN, and the laptop is supposed to act as a DHCP server for the devices attached to enp4s0. So I installed isc-dhcp-server and removed dnsmasq-base, which was installed on the laptop. I edited /etc/default/isc-dhcp-server and /etc/dhcp/dhcpd.conf: Code: Select allroot@FENCHURCH:~# more /etc/default/isc-dhcp-server INTERFACESv4="enp4s0" INTERFACESv6="" Code: Select alloption domain-name "mysubnetwork.org"; option domain-name-servers 8.8.8.8; default-lease-time 600; max-lease-time 7200; ddns-update-style none; subnet 10.254.239.0 netmask 255.255.255.0 { interface enp4s0; range 10.254.239.15 10.254.239.50; option subnet-mask 255.255.255.0; option routers 10.254.239.10; } host fenchurch { hardware ethernet 54:42:49:fb:dc:c3; fixed-address 10.254.239.10; } When starting the DHCP server, I get the following error: Code: Select allabr 05 00:19:27 FENCHURCH isc-dhcp-server[1420]: Launching IPv4 server only. abr 05 00:19:27 FENCHURCH dhcpd[1432]: Wrote 0 deleted host decls to leases file. abr 05 00:19:27 FENCHURCH dhcpd[1432]: Wrote 0 new dynamic host decls to leases file. abr 05 00:19:27 FENCHURCH dhcpd[1432]: Wrote 0 leases to leases file. abr 05 00:19:27 FENCHURCH dhcpd[1432]: abr 05 00:19:27 FENCHURCH dhcpd[1432]: No subnet declaration for enp4s0 (no IPv4 addresses). abr 05 00:19:27 FENCHURCH dhcpd[1432]: ** Ignoring requests on enp4s0. If this is not what abr 05 00:19:27 FENCHURCH dhcpd[1432]: you want, please write a subnet declaration abr 05 00:19:27 FENCHURCH dhcpd[1432]: in your dhcpd.conf file for the network segment abr 05 00:19:27 FENCHURCH dhcpd[1432]: to which interface enp4s0 is attached. ** abr 05 00:19:27 FENCHURCH dhcpd[1432]: abr 05 00:19:27 FENCHURCH dhcpd[1432]: abr 05 00:19:27 FENCHURCH dhcpd[1432]: Not configured to listen on any interfaces! abr 05 00:19:27 FENCHURCH dhcpd[1432]: abr 05 00:19:27 FENCHURCH dhcpd[1432]: If you think you have received this message due to a bug rather abr 05 00:19:27 FENCHURCH dhcpd[1432]: than a configuration issue please read the section on submitting abr 05 00:19:27 FENCHURCH dhcpd[1432]: bugs on either our web page at www.isc.org or in the README file abr 05 00:19:27 FENCHURCH dhcpd[1432]: before submitting a bug. These pages explain the proper abr 05 00:19:27 FENCHURCH dhcpd[1432]: process and the information we find helpful for debugging. abr 05 00:19:27 FENCHURCH dhcpd[1432]: abr 05 00:19:27 FENCHURCH dhcpd[1432]: exiting. abr 05 00:19:29 FENCHURCH isc-dhcp-server[1420]: Starting ISC DHCPv4 server: dhcpdcheck syslog for diagnostics. ... abr 05 00:19:29 FENCHURCH isc-dhcp-server[1434]: failed! abr 05 00:19:29 FENCHURCH isc-dhcp-server[1435]: failed! abr 05 00:19:29 FENCHURCH systemd[1]: isc-dhcp-server.service: Control process exited, code=exited, status=1/FAILURE I am not sure if the host section in dhcpd.conf is required, but it does not make any difference. I am making these edits in a remote terminal from another computer in my LAN. The laptop is connected to the LAN via wlp2s0 and gets its IP from a DHCP server. Currently, nothing is connected to enp4s0 of the laptop. Any help is of course greatly appreciated. Thanks, Toquinho | Did you assign an IP address in the 10.254.239.0/24 subnet to enp4s0 ? What does "ip addr" show ? |
Hi there, I'm running Debian on OpenMediaVault and I've encountered an error with Samba. I can copy a file to my NAS but it fails halfwaythrough with a network error and I get a "Panic or Segfault in Samba" error from the NAS. I am not a Linux expert - so please do let me know what is needed to diagnose - but I think I've managed to access the SAMBA logs and they look like this: Code: Select all[2025/02/17 13:38:03.576961, 0] ../../source3/smbd/fd_handle.c:39(fd_handle_destructor) PANIC: assert failed at ../../source3/smbd/fd_handle.c(39): (fh->fd == -1) || (fh->fd == AT_FDCWD) [2025/02/17 13:38:03.577101, 0] ../../lib/util/fault.c:173(smb_panic_log) =============================================================== [2025/02/17 13:38:03.577165, 0] ../../lib/util/fault.c:174(smb_panic_log) INTERNAL ERROR: assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in pid 2794 (4.17.12-Debian) [2025/02/17 13:38:03.577217, 0] ../../lib/util/fault.c:178(smb_panic_log) If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting [2025/02/17 13:38:03.577272, 0] ../../lib/util/fault.c:183(smb_panic_log) =============================================================== [2025/02/17 13:38:03.577321, 0] ../../lib/util/fault.c:184(smb_panic_log) PANIC (pid 2794): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.17.12-Debian [2025/02/17 13:38:03.615907, 0] ../../lib/util/fault.c:292(log_stack_trace) BACKTRACE: 27 stack frames: #0 /usr/lib/x86_64-linux-gnu/samba/libgenrand-samba4.so.0(log_stack_trace+0x2e) [0x7fddc6acc55e] #1 /usr/lib/x86_64-linux-gnu/samba/libgenrand-samba4.so.0(smb_panic+0x9) [0x7fddc6acc7b9] #2 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(+0x4f23b) [0x7fddc6eaa23b] #3 /lib/x86_64-linux-gnu/libtalloc.so.2(+0x47af) [0x7fddc6a857af] #4 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(file_free+0xd6) [0x7fddc6eaff36] #5 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(+0xbd031) [0x7fddc6f18031] #6 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(smbd_smb2_request_process_close+0x211) [0x7fddc6f187b1] #7 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(smbd_smb2_request_dispatch+0x1b02) [0x7fddc6f0bfb2] #8 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(+0xb2111) [0x7fddc6f0d111] #9 /lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x7fddc6a728c1] #10 /lib/x86_64-linux-gnu/libtevent.so.0(+0xee07) [0x7fddc6a78e07] #11 /lib/x86_64-linux-gnu/libtevent.so.0(+0xcef7) [0x7fddc6a76ef7] #12 /lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x91) [0x7fddc6a71ba1] #13 /lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7fddc6a71e7b] #14 /lib/x86_64-linux-gnu/libtevent.so.0(+0xce97) [0x7fddc6a76e97] #15 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(smbd_process+0x82f) [0x7fddc6efa21f] #16 /usr/sbin/smbd(+0x9e00) [0x55c975a64e00] #17 /lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x7fddc6a728c1] #18 /lib/x86_64-linux-gnu/libtevent.so.0(+0xee07) [0x7fddc6a78e07] #19 /lib/x86_64-linux-gnu/libtevent.so.0(+0xcef7) [0x7fddc6a76ef7] #20 /lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x91) [0x7fddc6a71ba1] #21 /lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7fddc6a71e7b] #22 /lib/x86_64-linux-gnu/libtevent.so.0(+0xce97) [0x7fddc6a76e97] #23 /usr/sbin/smbd(main+0x1489) [0x55c975a62269] #24 /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x7fddc68b024a] #25 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7fddc68b0305] #26 /usr/sbin/smbd(_start+0x21) [0x55c975a62b41] [2025/02/17 13:38:03.616416, 0] ../../source3/lib/util.c:702(smb_panic_s3) smb_panic(): calling panic action [/usr/share/samba/panic-action 2794] [2025/02/17 13:38:04.121642, 0] ../../source3/lib/util.c:709(smb_panic_s3) smb_panic(): action returned status 0 [2025/02/17 13:38:04.121884, 0] ../../source3/lib/dumpcore.c:315(dump_core) dumping core in /var/log/samba/cores/smbd The OMV team said they cannot help as this is a Samba issue within Debian. Any suggestions please? I think I'm running Samba smbd version 4.17.12-Debian and Linux 6.1.0-31-amd64 Thanks a lot! | Hello, Tony359 wrote: 2025-02-17 13:51 I'm running Debian on OpenMediaVault and I've encountered an error with Samba. [..] I can copy a file to my NAS but it fails halfwaythrough with a network error and I get a "Panic or Segfault in Samba" error from the NAS. I'm no expert on OMV, but it is described on its home page as a "network attached storage (NAS) solution based on Debian Linux" [1]. According to the log in the previous message, this could be it: Bug 15527 - fd_handle_destructor() panics within an smbd_smb2_close() if vfs_stat_fsp() fails in fd_close() It has been fixed in samba (2:4.19.6+dfsg-1) : Code: Select allsamba (2:4.19.6+dfsg-1) unstable; urgency=medium * new upstream stable/bugfix release: - https://bugzilla.samba.org/show_bug.cgi?id=15527 fd_handle_destructor() panics within an smbd_smb2_close() if vfs_stat_fsp() fails in fd_close() - https://bugzilla.samba.org/show_bug.cgi?id=15580 Packet marshalling push support missing for CTDB_CONTROL_TCP_CLIENT_DISCONNECTED and CTDB_CONTROL_TCP_CLIENT_PASSED - https://bugzilla.samba.org/show_bug.cgi?id=15588 samba-gpupdate: Correctly implement site support - https://bugzilla.samba.org/show_bug.cgi?id=15599 libgpo: Segfault in python bindings * revert d/rules: remove Debian/Ubuntu "branding" -- Michael Tokarev <mjt@tls.msk.ru> Mon, 08 Apr 2024 11:18:38 +0300 This should be the patch: patch for v418,v419,v420: Code: Select allrom a000ce99064c0c757c9ea66df516c9f98afaa01f Mon Sep 17 00:00:00 2001 From: Ralph Boehme <slow@samba.org> Date: Mon, 5 Feb 2024 15:03:48 +0100 Subject: [PATCH 1/2] smbd: simplify handling of failing fstat() after unlinking file close_remove_share_mode() already called vfs_stat_fsp(), so we can skip the fstat() triggered in fd_close() by fsp->fsp_flags.fstat_before_close being true. This avoids getting an EACCESS error when doing an fstat() on the removed file which seems to happen with some FUSE filesystems. BUG: https://bugzilla.samba.org/show_bug.cgi?id=15527 Signed-off-by: Ralph Boehme <slow@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org> (cherry picked from commit 6e6324cff29089a636823786183222a73fe7cb28) --- source3/smbd/close.c | 1 + source3/smbd/open.c | 15 +-------------- 2 files changed, 2 insertions(+), 14 deletions(-) diff --git a/source3/smbd/close.c b/source3/smbd/close.c index b42f4d2db71..04e39774950 100644 --- a/source3/smbd/close.c +++ b/source3/smbd/close.c @@ -603,6 +603,7 @@ static NTSTATUS close_remove_share_mode(files_struct *fsp, */ fsp->fsp_flags.delete_on_close = false; + fsp->fsp_flags.fstat_before_close = false; lck_state.reset_delete_on_close = true; done: diff --git a/source3/smbd/open.c b/source3/smbd/open.c index 3e7a8f45ebd..0862c956c45 100644 --- a/source3/smbd/open.c +++ b/source3/smbd/open.c @@ -952,20 +952,7 @@ NTSTATUS fd_close(files_struct *fsp) if (fsp->fsp_flags.fstat_before_close) { status = vfs_stat_fsp(fsp); if (!NT_STATUS_IS_OK(status)) { - /* - * If this is a stream and delete-on-close was set, the - * backing object (an xattr from streams_xattr) might - * already be deleted so fstat() fails with - * NT_STATUS_NOT_FOUND. So if fsp refers to a stream we - * ignore the error and only bail for normal files where - * an fstat() should still work. NB. We cannot use - * fsp_is_alternate_stream(fsp) for this as the base_fsp - * has already been closed at this point and so the value - * fsp_is_alternate_stream() checks for is already NULL. - */ - if (fsp->fsp_name->stream_name == NULL) { - return status; - } + return status; } } -- 2.35.3 From 73e08c4fde883014e8a9396c4f8c31600b162316 Mon Sep 17 00:00:00 2001 From: Noel Power <noel.power@suse.com> Date: Tue, 20 Feb 2024 09:26:29 +0000 Subject: [PATCH 2/2] s3/smbd: If we fail to close file_handle ensure we should reset the fd if fsp_flags.fstat_before_close == true then close_file_smb will call vfs_stat which can fail. If it does fail then the fd associated with the file handle will still be set (and we will hit an assert is the file handle destructor) when calling file_free. We need to set fd to -1 to avoid that. To achieve that we capture and return the vfs_stat_fsp failure status while still processing the rest of the fd_close logic. [2024/02/20 09:23:48.454671, 0, pid=9744] ../../source3/smbd/smb2_close.c:226(smbd_smb2_close) smbd_smb2_close: close_file[]: NT_STATUS_ACCESS_DENIED [2024/02/20 09:23:48.454757, 0, pid=9744] ../../source3/smbd/fd_handle.c:40(fd_handle_destructor) PANIC: assert failed at ../../source3/smbd/fd_handle.c(40): (fh->fd == -1) || (fh->fd == AT_FDCWD) [2024/02/20 09:23:48.454781, 0, pid=9744] ../../lib/util/fault.c:178(smb_panic_log) =============================================================== [2024/02/20 09:23:48.454804, 0, pid=9744] ../../lib/util/fault.c:185(smb_panic_log) INTERNAL ERROR: assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in smbd (smbd[192.168.10) (client [192.168.100.15]) pid 9744 (4.21.0pre1-DEVELOPERBUILD) [2024/02/20 09:23:48.454844, 0, pid=9744] ../../lib/util/fault.c:190(smb_panic_log) If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting [2024/02/20 09:23:48.454869, 0, pid=9744] ../../lib/util/fault.c:191(smb_panic_log) BUG: https://bugzilla.samba.org/show_bug.cgi?id=15527 Signed-off-by: Noel Power <noel.power@suse.com> Reviewed-by: Jeremy Allison <jra@samba.org> Autobuild-User(master): Noel Power <npower@samba.org> Autobuild-Date(master): Wed Mar 13 10:34:45 UTC 2024 on atb-devel-224 (cherry picked from commit 6ee3f809a54d7b833ff798e68a93ada00a215d4d) --- source3/smbd/open.c | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/source3/smbd/open.c b/source3/smbd/open.c index 0862c956c45..e5309a7be98 100644 --- a/source3/smbd/open.c +++ b/source3/smbd/open.c @@ -942,7 +942,7 @@ NTSTATUS fd_openat(const struct files_struct *dirfsp, NTSTATUS fd_close(files_struct *fsp) { - NTSTATUS status; + NTSTATUS stat_status = NT_STATUS_OK; int ret; if (fsp == fsp->conn->cwd_fsp) { @@ -950,10 +950,12 @@ NTSTATUS fd_close(files_struct *fsp) } if (fsp->fsp_flags.fstat_before_close) { - status = vfs_stat_fsp(fsp); - if (!NT_STATUS_IS_OK(status)) { - return status; - } + /* + * capture status, if failure + * continue close processing + * and return status + */ + stat_status = vfs_stat_fsp(fsp); } if (fsp->dptr) { @@ -975,7 +977,7 @@ NTSTATUS fd_close(files_struct *fsp) if (ret == -1) { return map_nt_error_from_unix(errno); } - return NT_STATUS_OK; + return stat_status; } /**************************************************************************** -- 2.35.3 You can try to install the samba package from the Debian backports repositories which contains the patch: Package: samba (2:4.21.3+dfsg-6~bpo12+1) Hope this helps. -- note: please, update the subject of the first post to "Samba: PANIC: assert failed at ../../source3/smbd/fd_handle.c(40): (fh->fd == -1) || (fh->fd == AT_FDCWD)" to make it more informative to forum readers. -- [1] network attached storage (NAS) solution based on Debian Linux [2] _PUBLIC_ void smb_panic_log(const char *why) [3] static int fd_handle_destructor(struct fd_handle *fh) |
I have installed Debian 10 MATE and the package-update-indicator, which I have also added to startup programs in System > Preferences > Personal > Startup Applications. I have available updates but the indicator program is not notifying me of the updates. Do I need to install any other programs for this to work? Thanks. | Rick B. wrote:To: stevepusser, One can add any desktop they want to a Debian or Ubuntu based distro, including MX Linux. So saying there is NO MX Linux MATE is incorrect. WTF are you talking about? You can install anything you want on any Linux. What Steve is saying is that the only official releases are Xfce or Fluxbox (with Xfce). Just because you can install it doesn't make it an official release. Steve is an MX developer by the way. |
I downloaded Bullseye Alpha3 iso (ran checksum aok) and tried to install into KVM/QEMU using virt-manager (choosing OS type as Debian testing) but it fails with Code: Select allSelect and install software installation step failed An installation step failed. You can try to run the failing item again from the menu, or skip it and choose something else. The failing step is: Select and install software I've written the same iso to a USB and have installed on same metal unit with a new additional drive without issue. How can I check what the KVM/QEMU issue is? | k829king wrote:How can I check what the KVM/QEMU issue is? Switch to TTY4 to see the actual error messages. Is the VM connected to the internet? |
Good day, I am a debian bullseye/sid 64 bit user.When I ran the command apt update && apt upgrade today to update my packages i got error messages below Code: Select all#apt update && apt upgrade You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libdw1:i386 : Depends: libelf1:i386 (= 0.182+20210203-1.1) but 0.182+20210203-1 is installed libelf1 : Breaks: libelf1:i386 (!= 0.182+20210203-1.1) but 0.182+20210203-1 is installed libelf1:i386 : Breaks: libelf1 (!= 0.182+20210203-1) but 0.182+20210203-1.1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). When I ran the apt --fix-broken install I got messages below Code: Select all#apt --fix-broken install Unpacking libelf1:i386 (0.182+20210203-1.1) over (0.182+20210203-1) ... dpkg: error processing archive /var/cache/apt/archives/libelf1_0.182+20210203-1.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/locale/en@boldquot/LC_MESSAGES/elfutils.mo', which is different from other instances of package libelf1:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libelf1_0.182+20210203-1.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) When I researched on this I stumbled onto the debian bugs webpage https://bugs.debian.org/cgi-bin/bugrepo ... bug=981835 but solutions provided dont work for me. Kindly assist. | I saw a report from a sid user on another forum that moving the file suggested in the bug report worked for them. You run bullseye/sid so you know there sometimes are version conflicts and/or breakages. Try full-upgrade again in a day or a week. |
debian buster, kde When my pc tries to connect to my router it takes a long time. Then I get an error message "No secrets were provided" and the connection is deactivated. After that the pc tries to reconnect and then it succeeds. output of lspci:Code: Select all02:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01) output of: lspci -vv -s 02:00.0 Code: Select all02:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01) Subsystem: Qualcomm Atheros AR93xx Wireless Network Adapter Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at f7d00000 (64-bit, non-prefetchable) [size=128K] Expansion ROM at f7d20000 [disabled] [size=64K] Capabilities: <access denied> Kernel driver in use: ath9k Kernel modules: ath9k This happens on the 5ghz band. It was a long time not possible to connect on 5Ghz. The SSID was not visible. Now I noticed that the band is visible again( probably a driver update: ath9k). What causes the error: "No secrets were provided"and how can I fix this?? | It seems to be an issue with the way whatever manages the network and whatever stores your password are configured meaning that whatever manages your network can't obtain the required password. To fix it I would investigate network manager and KDE wallet- if indeed that is how you manage the network and store passwords. I like search results that contain the words "fixed" or "solved", like these: https://superuser.com/questions/1463425 ... n-kde-neon https://bbs.archlinux.org/viewtopic.php?id=198606 Bear in mind that the advice might not be applicable to your set up or configuration, so if you try anything, make sure you remember what you have done so you can reverse it if it doesn't help or makes things worse. I would try investigating the network manager password setting in KDE wallet as described in the first link first. I'm not a KDE user, so maybe somebody who is can give you more specific advice. |
Wish everyone had a very nice and blessed Christmas despite anything else! I did a research online and here Debian forum and found nothing related to this issue I ran into. I'm still a noob but been using Buster every once in a while for a good while and, after reading some articles about xfs vs. ext4 file systems advantages and disadvantages, decided to give the latter a try for my /home partition, the only xfs file system in my DT Debian, all others being ext4. I only read very good recommendations to use fstransform to do this job, so I installed it on a Ventoy Live USB MX-Linux with persistence and run it from there following the instructions by Tim Schürmann. /home is on sda6 in my Debian system, so I entered: Code: Select all# fstransform /dev/sda6 ext4 It was done in less than two hours, with no error messages at all. I also checked its log files searching for key words like error or fail (using cat | grep), just in case. But nothing was found. So far so good! Then I rebooted into my Buster, expecting the usual start up. But guess what, I got: Timed out waiting for the device /dev/disk/by-uuid/...47649 Dependency failed for /home Dependency failed for Local File Systems ... You are in emergency mode... ... Give root password for maintenance Code: Select alljournalctl -xb | grep error gives kernel EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro Code: Select alljournalctl -xb | grep fail gives several error lines related to home.mount dependency for /home failures, including "failed with exit code 99" Code: Select allmount -a mount: /home: can't find UUID=...47649 cat /etc/fstab shows (only relevant lines) # / was on /dev/sda5 during installation UUID=...8b53d / ext4 errrors=remount-ro 0 1 # /home was on /dev/sda6 during installation UUID=...47649 /home xfs defaults 0 0 Afterwards using vi /etc/fstab I replaced xfs by ext4 but to no avail... Btw sda6 is in a logical partition. I did a Code: Select all# blkid | grep sda6 and the output was /dev/sda6: UUID=...31a1c), so it is different from what it is in /etc/fstab above. I run Code: Select all# ls -l /dev/disk/by-uuid | grep sda6 and confirmed it was the same UUID I went ahead and edited the fstab file using vi and replaced the UUID number. I also run Code: Select alllsblk -f | grep sda6 sda6 8:6 0 119.2G 0 part and it shows no MOUNTPOINT. And sda6 is not listed in df -h output Although I think this fstransform issue is a minor hiccup, at this point I'm not sure what the next steps are: 1. Can I now safely run systemctl reboot and no harm will be caused to the Buster system? 2. Should I first run mount /dev/sda6 /home instead? 3. What about UUID=...8b53d / ext4 errrors=remount-ro 0 1 for /dev/sda5 during installation?... Is it anything I should pay attention to? Any heads up deeply appreciated. Thanks a lot! | Correcting the UUID for /home in /etc/fstab should be enough. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.