November 2022 - openSUSE Support - openSUSE Mailing Lists

changed ssh port for <user> not honored
by Patrick Shanahan 16 Nov '22

16 Nov '22

I have a converted to Tw laptop and have moved ssh to a high port which <root> honors but <user> does not, ie: ssh <user>@box1 ssh: connect to host box1 port 22: Connection refused as root: ssh <user>@box1 success I changed the firewall ports for ssh to the utilized high port I altered both ssh_config and sshd_config to designate the high port. restarted firewalld and sshd what have I missed? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

3 7

how did I screw up grub? and how do I fix it?
by David T-G 16 Nov '22

16 Nov '22

Hi, all -- I have a system with a 128G SSD /dev/sda that is my boot, swap, and data drive. It is sliced into partitions with a GPT layout and it has been working fabulously for over a year. My long-term plans are to add a 256G SSD, set up either the disk or the slices as [a] mirror[s], migrate from small to large, and then replace the small with another large that gets added to the mirror[s]. I've had /dev/sde in place for a while across a couple of reboots and have been waiting for the right time to copy the XFS content across. I also have a RAID-0 stripe of RAID-5 slices across 10T disks, and the other day I bought another to add to grow the slices. I shut down, installed it, and thought to myself it would be a great time to do the xfs dump->restore thing to get ready to swing. Should be simple, right? Somehow I have tanked grub2. If the box gets anywhere at all, it only gets as far as "GRUB2 loading" (or whatever it says; I can't access remotely when it's dead and so I can't mouse the message) and then hangs. Mostly it doesn't even get that far. I have unplugged everything except the RAID-5 big disks, even going so far as to rip out the new 256G, to no avail. I can boot into a Leap 15.2 rescue system on a thumb drive and even mount /dev/sda2 manually, but when I then try to reinstall grub2 it complains that it can't work on a GPT system. But it was working before! Exactly once I was able to use the boot menu in my BIOS to tell it to boot from SATA0 (aka /dev/sda), although it threw another error much further down the line and wanted a root password for a shell. I've never had a separate /boot or /efi partition and I've switched over to GPT long ago; this system was built with GPT tables. But it somehow used to boot ... How do I repair grub2 to get back to booting on sda first, just so that we can be back where we were and I can start adding the slices? I'll tackle migration from sda (raw) to sde (mirrors) once it's up and running again; for now I just want to get back to where I was. TIA & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

8 62

Re: whatsapp-purple does not work
by Axel Braun 13 Nov '22

13 Nov '22

I doubt that this is an official openSUSE package -> support@ is more appropriate for your question Aside of this, try to start it from command line and see the messages in the terminal Viele Grüße Axel -- Diese Nachricht wurde von meinem Android-Tablet mit K-9 Mail gesendet. Am 13. November 2022 12:51:43 GMT+00:00 schrieb Constant Brouerius van Nidek <cbroueriusvannidek(a)gmail.com>: >I just installed whatsapp-purple from plater on my system. > >It installed without an hitch but I do not seem to start the whatsapp. > >Need help to solve this problem. Chechek my install and got following info: > >whatsapp-purple-0.8.6-5.75.x86_64'. The highest available version is already installed

1 0

mdadm: Raid1 array constantly degrading.
by Mark Neugebauer 11 Nov '22

11 Nov '22

For several weeks my Raid1 array is constantly degrading on Tumbleweed. Running two HDDs, one of them is suddenly inactive. Re-adding is no problem. What I did so far: - Backup as usual an hoping that things change due to some kind of regression being sorted out via update. - Checking several logs with help of the forum. I could not find a single hint of what is going on - even with running "dd if=/dev/sdb of=/dev/null bs=4M" on both HDDs. - Changing SATA cables. Please find a more detailed description on what has been done via this link: https://forums.opensuse.org/showthread.php/577384-Raid1-array-constantly-de… Would highly appreciate any suggestions how to sort this out.

3 4

Could not prepare Boot variable: No medium found
by Felix Miata 10 Nov '22

10 Nov '22

I'm trying to make an upgraded NVME boot. Old was 120G. New is 500G. The ESP is giving me no apparent trouble, but booting from NVME normally from NVME instead of via rescue media is somehow being blocked by inability to create an EFI boot entry causing $SUBJECT message. # grep DISTR /etc/default/grub GRUB_DISTRIBUTOR="opensusetw" # ls -1 /sys/firmware/efi/efivars | wc -l 82 # parted /dev/nvme0n1 print | grep -Ei 'p01|p07' 1 1049kB 337MB 336MB fat32 PNY5 p01 EFI System (ESP) boot, esp 7 29.3GB 37.7GB 8389MB ext4 PNY5 p07 openSUSE Tumbleweed # grep -E '0 1|boot/' /etc/fstab LABEL=PNY5P01ESP /boot/efi vfat codepage=437 0 0 LABEL=pny5p07stw / ext4 noatime 0 1 # ls -gG /boot/efi/EFI/opensusetw/ -rwxr-xr-x 1 143360 Sep 19 18:55 grubx64.efi # ls -gG /sys/firmware/ drwxr-xr-x 6 0 Nov 7 23:14 acpi drwxr-xr-x 3 0 Nov 7 23:14 dmi drwxr-xr-x 7 0 Nov 7 23:14 efi drwxr-xr-x 27 0 Nov 8 03:27 memmap # mount | grep nvme0 /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) /dev/nvme0n1p7 on / type ext4 (rw,noatime) # ls -Gg /boot | grep '5.19' | grep -E 'vmlinuz|initrd' lrwxrwxrwx 1 24 Oct 9 23:10 initrd -> initrd-5.19.13-1-default -rw------- 1 14166604 Oct 9 23:10 initrd-5.19.13-1-default lrwxrwxrwx 1 25 Oct 9 23:10 vmlinuz -> vmlinuz-5.19.13-1-default lrwxrwxrwx 1 44 Oct 9 23:10 vmlinuz-5.19.13-1-default -> ../usr/lib/modules/5.19.13-1-default/vmlinuz # efibootmgr BootCurrent: 0007 Timeout: 1 seconds BootOrder: 0003,0004,0007 Boot0003* Hard Drive Boot0004* CD/DVD Drive Boot0007* UEFI: USB DISK 3.2 PMAP, Partition 2 # lsblk -f | grep nvme0 nvme0n1 ├─nvme0n1p1 vfat FAT32 PNY5P01ESP 4C58-8D7E 294.1M 8% /boot/efi ├─nvme0n1p7 ext4 1.0 pny5p07stw ae6c138b-f360-45e7-a43c-188fcd3b3f07 2.7G 60% / # blkid | grep nvme0 /dev/nvme0n1p1: LABEL_FATBOOT="PNY5P01ESP" LABEL="PNY5P01ESP" UUID="4C58-8D7E" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="PNY5 p01 EFI System (ESP)" PARTUUID="6369e907-1e83-4df5-8574-d6d1d34e9b7e" /dev/nvme0n1p7: LABEL="pny5p07stw" UUID="ae6c138b-f360-45e7-a43c-188fcd3b3f07" BLOCK_SIZE="2048" TYPE="ext4" PARTLABEL="PNY5 p07 openSUSE Tumbleweed" PARTUUID="6369ef77-a213-4df5-8bfd-cd881d32e345" # efibootmgr -c -L "opensusetw" -l '\EFI\opensusetw\grubx64.efi' # lower case EL, not one Could not prepare Boot variable: No medium found A web search found me zero hits for "Could not prepare Boot variable: No medium found" What medium is missing from where? What's necessary to fix this (make efibootmgr -c work)? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

4 14

Not in sudoers file after installing docker
by Maxwell Heeschen 05 Nov '22

05 Nov '22

Hey everyone, I got this message, "maxwell is not in the sudoers file. This incident has been reported to the administrator." while trying to run some sudo commands after recently following the instructions to install Docker here: https://en.opensuse.org/Docker I was following the Yast2 installation instructions until I got to the adding user to the docker group step. For some reason I thought I would continue the steps using the command line so I ran following commands which I got from the "history" command: 861 sudo usermod -G docker -a $USER 862 sudo systemctl restart docker 863 docker version 864 docker run --rm hello-world 865 echo $USER 866 man usermod 867 systemctl start docker -- 868 docker run --rm hello-world 869 sudo zypper dup 870 sudo shutdown -r now After those last two commands I was starting to get worried, but I can still login as root (su) and use Yast to do stuff. I figured it might be an issue with how I ran the usermod command, but I'm not sure. On the bright side Docker is installed now. Things I have tried: restart my computer use Yast to add my user account to the wheel group use Yast to remove myself from the wheel group use Yast to add myself to the user group restart after doing those group changes I am running Tumbleweed.

4 5