September 2018 - openSUSE Support - openSUSE Mailing Lists

[opensuse-support] reboot and shutdown not completing

by mike

Hi, Running Tumbleweed...is this a known problem...unable to reboot or shut down with an nvme ssd?? Running with a Ryzen 2700 and Gigabyte 470 aorus ultra gaming motherboard...Thanks for any help... mike -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 years, 3 months

4
13
0 0

[opensuse-support] wifi and eth wicked same network should fallback - bond?

by Simon Becherer

Hi, i try the whole day to get a laptop tumbleweed kde, xwindows, wicked running with wifi and cable lan, static ipv4 only. network is 192.168.0.x cable: enp3s0 should be 192.168.0.23 wifi: wlp2s0 should be 192.168.0.43 (driver is iwlwifi) most of time this laptop is connected to the eth0 sometimes if it is not connected, it should use wifi to go into the same network (and to go only in this network). so i decided to configure both networks inside yast i get it running with cable, and i get it running with wifi, BUT if i activate both together inside yast, it will mess up. the reason seems to be the routing. if i do NOT assign enp3s0 or wlp2s0 "-" inside yast, ip ro will show no routing at all. if insert one of them, it will partly work as long as this connection is ok. i tried to add a second routing with: ip route delete default ip route add default via 192.168.0.99 metric 101 dev wlp2s0 ip route add default via 192.168.0.99 metric 102 dev enp3s0 but still the same problem. then i was thinking try to bond both networkadapters together: in yast i made a bond0 gave theme the address 192.168.0.23 and put both network adapters to the bond0 (removed the ip addresses and they jump to "activate by hotplugged" and made standartroute to bond0 as soon as i say ok in yast it takes some seconds to write the configuration, and after this (if before both adapters where visible inside the network) the wifi adapter will switched off, never seen by ip ro (and of course also not inside the net) i checked also: rfkill list (to make shure its not blocked) all are on "no" inside /etc/sysconfig/network/ifcfg-bon0 both slaves are inside, and the ifcfg-wlp2s0 file only differs from standalone to the bond version in BOOTPROTO and STARTMODE and as i have read inside internet, thats correct. could anybody help me to get it running like: fallback from one to the other network adapters, normally using enp3s0 if not present using wlp2s0 i do not take care how to get to this. i have had it running with opensuse 42.2? i think was before on that laptop. as i remember there it was networkmanager. but if i now switch inside yast to networkmanager, i have no possibility to change anything inside yast at enp3s0 or bond0 or wlp2s0 and network is not present at all. simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 years, 3 months

3
5
0 0

[opensuse-support] question about ldd

by mike

Hi, I'm still trying to figure out why I can't get fahclient to run, and I found out that ldd shows which libraries are needed by a program. Now I'm really no linux expert (or even close) so I'm trying things that I hope will not cause any system damage. This is the output of ldd FAHClient ./FAHClient: /usr/lib64/libssl.so.10: version `libssl.so.10' not found (required by ./FAHClient) ./FAHClient: /usr/lib64/libcrypto.so.10: version `OPENSSL_1.0.1_EC' not found (required by ./FAHClient) ./FAHClient: /usr/lib64/libcrypto.so.10: version `libcrypto.so.10' not found (required by ./FAHClient) linux-vdso.so.1 (0x00007ffcb07c6000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f2df40ab000) libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007f2df3e3c000) libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x00007f2df39d3000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f2df37cf000) librt.so.1 => /lib64/librt.so.1 (0x00007f2df35c7000) libbz2.so.1 => /usr/lib64/libbz2.so.1 (0x00007f2df44a4000) libz.so.1 => /lib64/libz.so.1 (0x00007f2df33b0000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f2df4316000) libm.so.6 => /lib64/libm.so.6 (0x00007f2df301d000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f2df42fc000) libc.so.6 => /lib64/libc.so.6 (0x00007f2df2c5d000) /lib64/ld-linux-x86-64.so.2 (0x00007f2df42ca000) So if I read this right, I have the necessary libs are installed, so why does it say that it can not find 3 of the libraries?? mike -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 years, 3 months

3
5
0 0

[opensuse-support] What to do when a bug isn't taken?

by Mischa Salle

Hi all, I filed bug https://bugzilla.suse.com/show_bug.cgi?id=1096328 about 3 1/2 month ago, and nothing has happened since, it's still in state New. Is there anything I could do to make this change? The issue certainly hasn't changed with any updates since then. Best wishes, Mischa Salle -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 years, 3 months

4
8
0 0

[opensuse-support] yesterday's update changed xterm font size

by Patrick Shanahan

did an update yesterday and rec'd new kernel, kernel-default-4.17.14-1.2.x86_64, and about 300 other packages. rebooted for new kernel and now opening xterm provides a large font (unwanted). <ctrl><rt-click> on <medium> provides original font. what changed that may have caused this? If needed I can provide a list of the updated packages. tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 years, 4 months

5
14
0 0

[opensuse-support] Folding@Home

by mike

Hi, OK I had this working on my old system and now all I get is-- /etc/init.d/FAHClient start FAILED when run as root...zypper installed the 3 fah packages and it refuses to start. using latest tumbleweed.....am I missing something?? mike -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 years, 4 months

4
11
0 0

[opensuse-support] configuration of ipv6 forwarding

by Adam Mizerski

Hi, I have the following situation: I have a VPS with openSUSE 15 Leap on it. It has a public IPv6 address and connectivity with outside world works correctly. I also have a whole /64 subnet to use (public address is not in this subnet). I want to configure WireGuard so that devices connected to it would have addresses from my subnet (for now set by hand, I'll play with autoconfiguration later) and connectivity to outside world. My VSP operator requires that all IPv6 traffic should come out of my public address. Here's what I've got: # ip -6 a [...] 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000 inet6 {PUBLIC_IP}/64 scope global valid_lft forever preferred_lft forever [...] 3: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 state UNKNOWN qlen 1000 inet6 {SUBNET}::1/64 scope global deprecated valid_lft forever preferred_lft 0sec # ip -6 r local ::1 dev lo proto kernel metric 256 pref medium {SUBNET}::/64 dev wg0 proto kernel metric 256 pref medium {PUBLIC_IP_SUBNET}::/64 dev eth0 proto kernel metric 256 pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium default via {GATEWAY} dev eth0 src {PUBLIC_IP} metric 1024 pref medium # sysctl -a | grep ipv6 | grep forwarding | grep -v mc_forwarding net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.default.forwarding = 1 net.ipv6.conf.eth0.forwarding = 1 net.ipv6.conf.lo.forwarding = 0 net.ipv6.conf.wg0.forwarding = 1 # ping6 -c1 sixxs.net -I eth0 PING sixxs.net(nlams01.paphosting.net (2a02:898:146::2)) from {PUBLIC_IP} eth0: 56 data bytes 64 bytes from nlams01.paphosting.net (2a02:898:146::2): icmp_seq=1 ttl=58 time=28.1 ms --- sixxs.net ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 28.109/28.109/28.109/0.000 ms # ping6 -c1 sixxs.net -I wg0 ping6: Warning: source address might be selected on device other than wg0. PING sixxs.net(nlams01.paphosting.net (2a02:898:146::2)) from {PUBLIC_IP} wg0: 56 data bytes From {PUBLIC_IP} icmp_seq=1 Destination unreachable: Address unreachable ping: sendmsg: Destination address required --- sixxs.net ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms # ping6 -c1 {PUBLIC_IP} -I wg0 ping6: Warning: source address might be selected on device other than wg0. PING {PUBLIC_IP}({PUBLIC_IP}) from {PUBLIC_IP} wg0: 56 data bytes From {PUBLIC_IP} icmp_seq=1 Destination unreachable: Address unreachable ping: sendmsg: Destination address required --- {PUBLIC_IP} ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms Address at wg0 has status "deprecated", because from what I've read, command # ip a change {SUBNET}::1 dev wg0 preferred_lft 0 should make connections not come out of this address. But it seems it's not working, because if I run ping6 without "-I" option, it works the same if I use "-I wg0". iptables is managed by firewalld and wg0 interface is in "trusted" zone. As I understand output of "ip6tables -L -nv" command, from this interface all traffic (including FORWARD) is allowed. Am I doing something wrong? Or is there something I'm not aware of? Because my understanding is that packets from wg0 interface should be forwarded to eth0 and from it further to the world. But that's not happening and I don't even know how to find out what's really going on. Any help is appreciated, no question is dumb, and don't assume anything to be obvious. -- Adam Mizerski

3 years, 4 months

2
13
0 0

[opensuse-support] 'shutdown -r now' fails at dracut debug shell

by Felix Miata

Happens at every attempt to 'shutdown -r now' from root login. 'shutdown -h now' succeeds. Fresh online upgrade from 42.2 on RAID1 to 15.0. Enabled optional repos: Trinity; Packman; Mozilla; MozillaLegacy; FileCommander; Rebuild of initrd did not help. /etc/fstab exclusive of noauto and commented lines: http://fm.no-ip.com/Tmp/SUSE/Leap/fstab-fi965-s150 /shutdown-log.txt: http://fm.no-ip.com/Tmp/SUSE/Leap/shutdown-log-fi965-s150.txt Full rdsosreport.txt: http://fm.no-ip.com/Tmp/SUSE/Leap/rdsosreport-fi965-s150.txt Grep of "ailed" lines from full rdsosreport: [ 0.107132] fi965 kernel: acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM [ 24.415225] fi965 avahi-daemon[948]: socket() failed: Address family not supported by protocol [ 24.415463] fi965 avahi-daemon[948]: Failed to create IPv6 socket, proceeding in IPv4 only mode [ 24.417157] fi965 avahi-daemon[948]: socket() failed: Address family not supported by protocol [ 29.490053] fi965 smbd[1336]: open_socket_in(): socket() call failed: Address family not supported by protocol [ 29.491883] fi965 smbd[1336]: open_socket_in(): socket() call failed: Address family not supported by protocol [ 117.547920] fi965 systemd[1]: proc-sys-fs-binfmt_misc.automount: Unit entered failed state. [ 117.604466] fi965 systemd[1]: Failed to create compat systemd cgroup /system.slice/dracut-shutdown.service/control: Read-only file system [ 117.604833] fi965 systemd[1]: Failed to attach 1431 to compat systemd cgroup /system.slice/dracut-shutdown.service/control: No such file or directory [ 117.609694] fi965 systemd[1]: Failed to create compat systemd cgroup /system.slice/alsa-restore.service/control: Read-only file system [ 117.610133] fi965 systemd[1]: Failed to attach 1432 to compat systemd cgroup /system.slice/alsa-restore.service/control: No such file or directory [ 117.637742] fi965 systemd[1353]: Failed to create compat systemd cgroup /user.slice/user-0.slice/user(a)0.service/systemd-exit.service: Read-only file system [ 117.638097] fi965 systemd[1353]: Failed to attach 1435 to compat systemd cgroup /user.slice/user-0.slice/user(a)0.service/systemd-exit.service: No such file or directory [ 117.638466] fi965 systemd[1]: Failed to create compat systemd cgroup /system.slice/var-run-user-0.mount: Read-only file system [ 117.638637] fi965 systemd[1]: Failed to create compat systemd cgroup /system.slice/run-user-0.mount: Read-only file system [ 117.834736] fi965 systemd[1]: Failed to create compat systemd cgroup /system.slice/systemd-user-sessions.service/control: Read-only file system [ 117.835130] fi965 systemd[1]: Failed to attach 1445 to compat systemd cgroup /system.slice/systemd-user-sessions.service/control: No such file or directory [ 118.437964] fi965 systemd[1]: Failed to create compat systemd cgroup /system.slice/wicked.service/control: Read-only file system [ 118.438867] fi965 systemd[1]: Failed to attach 1448 to compat systemd cgroup /system.slice/wicked.service/control: No such file or directory [ 118.439467] fi965 systemd[1]: Failed to create compat systemd cgroup /system.slice/nscd.service/control: Read-only file system [ 118.440020] fi965 systemd[1]: Failed to attach 1449 to compat systemd cgroup /system.slice/nscd.service/control: No such file or directory [ 119.044771] fi965 systemd[1]: Failed to trim compat systemd cgroup /user.slice: Read-only file system [ 119.052600] fi965 systemd[1]: Failed to create compat systemd cgroup /system.slice/systemd-random-seed.service/control: Read-only file system [ 119.053074] fi965 systemd[1]: Failed to attach 1573 to compat systemd cgroup /system.slice/systemd-random-seed.service/control: No such file or directory [ 119.053951] fi965 systemd[1]: Failed to attach 1574 to compat systemd cgroup /system.slice/dev-disk-by\x2dlabel-ss50c\x2dswap.swap: No such file or directory [ 119.054570] fi965 systemd[1]: Failed to attach 1575 to compat systemd cgroup /system.slice/dev-disk-by\x2dlabel-ss50b\x2dswap.swap: No such file or directory [ 119.055755] fi965 systemd[1]: Failed to create compat systemd cgroup /system.slice/systemd-update-utmp.service/control: Read-only file system [ 119.056350] fi965 systemd[1]: Failed to attach 1576 to compat systemd cgroup /system.slice/systemd-update-utmp.service/control: No such file or directory [ 119.679714] fi965 systemd[1]: Failed to attach 1581 to compat systemd cgroup /system.slice/run-user-0.mount: No such file or directory [ 119.681140] fi965 systemd[1]: Failed to attach 1582 to compat systemd cgroup /system.slice/var-run-user-0.mount: No such file or directory [ 119.688461] fi965 systemd[1]: var-run-user-0.mount: Unit entered failed state. [ 119.689048] fi965 systemd[1]: Failed to attach 1583 to compat systemd cgroup /system.slice/var-run.mount: No such file or directory [ 119.692058] fi965 systemd[1]: Failed unmounting Runtime Directory. [ 119.697739] fi965 systemd[1]: Failed to create compat systemd cgroup /system.slice/systemd-reboot.service: Read-only file system [ 119.698322] fi965 systemd[1]: Failed to attach 1584 to compat systemd cgroup /system.slice/systemd-reboot.service: No such file or directory [ 119.698706] fi965 systemd[1]: Failed to create compat systemd cgroup /system.slice/lvm2-monitor.service/control: Read-only file system [ 119.698986] fi965 systemd[1]: Failed to attach 1585 to compat systemd cgroup /system.slice/lvm2-monitor.service/control: No such file or directory Lines on screen at failure that don't make it into rdsosreport.txt: [OK] Stopped Load/Save Random Seed. [OK] Stopped Create Volatile Files and Directories. [OK] Stopped Restore /run/initramfs on shutdown. [OK] Stopped target Local File Systems. Unmounting /run/user/0... Unmounting /var/run/user/0... [OK] Unmounted /var/run/user/0. Unmounting Runtime Directory... [OK] Unmounted /run/user/0. [FAILED] Failed unmounting Runtime Directory. [OK] Reached target Unmount All Filesystems. [OK] Stopped target Local File Systems (Pre). Stopping Monitoring of LVM2 mirrors, snapshots, etc. using dmeventd or progress polling... [OK] Stopped Create Static Device Nodes in /dev. [OK] Stopped Remount Root and Kernel File Systems. [OK] Reached target Shutdown. mkdir: cannot create directory '/oldsys': Read-only file system mkdir: cannot create directory '/oldsys/sys': No such file or directory mount:/oldsys/sys: mount point does not exist. mkdir: cannot create directory '/oldsys/proc': No such file or directory mount:/oldsys/proc: mount point does not exist. mkdir: cannot create directory '/oldsys/run': No such file or directory mount:/oldsys/run: mount point does not exist. mkdir: cannot create directory '/oldsys/dev': No such file or directory mount:/oldsys/dev: mount point does not exist. dracut Warning: Killing all remaining processes mdadm: stopped /dev/md0 mdadm: stopped /dev/md7 mdadm: stopped /dev/md6 mdadm: stopped /dev/md5 mdadm: stopped /dev/md4 mdadm: stopped /dev/md3 mdadm: stopped /dev/md2 mdadm: Cannot get exclusive access to /dev/md1: Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot get exclusive access to /dev/md1: Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot get exclusive access to /dev/md1: Perhaps a running process, mounted filesystem or active volume group? rm: cannot remove '/lib/dracut/hooks/shutdown/30-md-shutdown.sh': Read-only file system Failed to unlink reboot parameter file: Read-only file system dracut Warning: reboot failed: dracut Warning: Generating "/run/initramfs/rdsosreport.txt" /sbin/rdsosreport: line 7: /run/initramfs/rdsosreport.txt": Read-only file system You might want to save "/run/initramfs/rdsosreport.txt: to a USB stick or /boot after mounting them and attach it to a bug report. To get more debug information in the report, reboot with "rd.debug" added to the kernel command line. Dropping to debug shell. /lib/dracut-lib.sh: line 1089: /.profile: Read-only file system shutdown:/# *************************************************************** On successful reboot, no such file /lib/dracut-lib.sh exists, and neither /.profile. Can someone suggest a cause or fix? Should I report a bug? About a dozen bugzilla.o.o searches turned up nothing. I've done several 42.2 to 15.0 upgrades before without any trouble at all, but none involving RAID; also 13.2, 13.1 and 42.1 directly to 15.0 sans trouble. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 years, 4 months

2
2
0 0

[opensuse-support] KDE Plasma on Wayland with openSUSE Tumbleweed

by H Zeng

Hello, I just upgraded my Tumbleweed to the lastest 0915 snapshot and tried the Plasma (wayland) but failed to enter the desktop. After select wayland session and input my password to login, the screen turns black (seems no backlight?) and the system does not repond to keystrokes. I have to press the power button to poweroff the system. I am using an (integrated ?) Intel GPU with Mesa driver. Does anyone know what's going on? I thought Wayland is stable for at least a try now, did it? Best regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 years, 4 months

2
3
0 0

[opensuse-support] Prevent system unresponsive state on huge memory consumption

by Mykola Krachkovsky

Hi, I've tried to compare two XML (each roughly 3MiB in size) using `xmldiff`. But this program have eaten whole RAM and swap and ended up in unresponsive system and then crashed almost everything — X session with all applications — so I've got just tty's. "Nice". Is there any way to prevent such behaviour in future? There is ulimit, but I don't want to limit all of my processes. Nice solution is (IMO) would be to allow every process to reach some limit after which application would be stopped (not killed), some notification sent (if possible) and user (me) could make some decision what to do with it — kill, allow once, add to white list. If program is white-listed allow it to do anything until ulimit/OOM-killer behaviour. Is there any way to do this? I'm not expecting absolutely ready solution, but at least some direction how I can achieve this. The only solution I'm aware of and could do — make some daemon that periodically checks process memory usage and sends SIGSTOP if some of them uses too much, but I'd prefer not use this approach — there is no perfect time period — high CPU usage vs too late to do anything. -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський

3 years, 4 months

2
3
0 0

2022

2021

2020

2019

2018

openSUSE Support September 2018