[opensuse-factory] New Tumbleweed snapshot 20190205 released!
Please note that this mail was generated by a script.
The described changes are computed based on the x86_64 DVD.
The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading:
https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&version=Tumbleweed&build=20190205
Please do not reply to this email to report issues, rather file a bug
on bugzilla.opensuse.org. For more information on filing bugs please
see https://en.opensuse.org/openSUSE:Submitting_bug_reports
Packages changed:
ImageMagick (7.0.8.21 -> 7.0.8.25)
Mesa (18.3.1 -> 18.3.2)
Mesa-drivers (18.3.1 -> 18.3.2)
apache2 (2.4.37 -> 2.4.38)
apparmor
apr (1.6.3 -> 1.6.5)
autofs (5.1.3 -> 5.1.5)
autoyast2 (4.0.70 -> 4.1.0)
bluez
ceph (14.0.1.1555+g42662f72f4 -> 14.0.1.3346+g0364ec8d2f)
djvulibre
dpdk (18.02.2_k4.20.6_1 -> 18.11_k4.20.6_1)
exo (0.12.3 -> 0.12.4)
ffmpeg-4
fontconfig (2.12.6 -> 2.13.1)
fonts-config (20181211 -> 20190119)
glusterfs (4.0.2 -> 5.3)
gnutls (3.6.4 -> 3.6.6)
groff (1.22.3 -> 1.22.4)
groff-full (1.22.3 -> 1.22.4)
guile
hugin
installation-images-Kubic (14.404 -> 14.408)
kernel-firmware (20181218 -> 20190118)
kimageformats
kmail-account-wizard
konsole
libappindicator
libblockdev (2.18 -> 2.20)
libcaca
libcdio-paranoia (10.2+0.93+1 -> 10.2+2.0.0)
libcontainers-common
libesmtp
libgxps (0.3.0 -> 0.3.1)
libinput (1.12.5 -> 1.12.6)
libjansson (2.11 -> 2.12)
libpng16
libseccomp
libstorage-ng (4.1.78 -> 4.1.84)
libvirt (4.10.0 -> 5.0.0)
libxml2 (2.9.8 -> 2.9.9)
llvm (7.0.0 -> 7.0.1)
llvm7 (7.0.0 -> 7.0.1)
man-pages-posix
mercurial (4.8.2 -> 4.9)
metis
mozilla-nss (3.40.1 -> 3.41.1)
nbd (3.17 -> 3.18)
nftables
open-iscsi
openconnect (7.08 -> 8.02)
openssh
perl-Inline (0.80 -> 0.81)
perl-JSON (4.00 -> 4.01)
pfstools
postfix
protobuf
python-libvirt-python (4.10.0 -> 5.0.0)
python-libxml2-python (2.9.8 -> 2.9.9)
python-setuptools (40.6.3 -> 40.7.2)
qemu
qemu-linux-user
rebootmgr (0.17 -> 0.18)
rubygem-rails-5.2
sysconfig (0.85.0 -> 0.84.3)
tigervnc
traceroute (2.0.21 -> 2.1.0)
udisks2 (2.7.8 -> 2.8.1)
valgrind
wget
xorg-x11-server
xrx
xterm (342 -> 343)
xtermset
yast2-apparmor (4.1.5 -> 4.1.7)
yast2-bootloader (4.1.13 -> 4.1.14)
yast2-control-center (4.1.4 -> 4.1.5)
yast2-firstboot (4.1.3 -> 4.1.4)
yast2-installation (4.1.34 -> 4.1.35)
yast2-network (4.1.34 -> 4.1.36)
yast2-packager (4.1.24 -> 4.1.25)
yast2-schema (4.1.1 -> 4.1.3)
yast2-services-manager (4.1.11 -> 4.1.12)
yast2-storage-ng (4.1.48 -> 4.1.50)
yast2-tftp-server (4.1.6 -> 4.1.7)
yast2-theme (4.1.8 -> 4.1.9)
yast2-trans (84.87.20190119.79f0258829 -> 84.87.20190201.2c07938cca)
zsh (5.6.2 -> 5.7.1)
=== Details ===
==== ImageMagick ====
Version update (7.0.8.21 -> 7.0.8.25)
Subpackages: ImageMagick-extra libMagick++-7_Q16HDRI4 libMagickCore-7_Q16HDRI6 libMagickWand-7_Q16HDRI6 perl-PerlMagick
- update to 7.0.8-25:
* Eliminate spurious font warning (#1458)
* Support HEIC EXIF & XMP profiles.
- changelog for 7.0.8-24:
* Support -clahe option real clip limit
* ShadeImage() kernels can return negative pixels, clamp to range (#1319)
* Annotate with negative offsets no longer renders slanted text
- clamp after edge [bsc#1106415]
+ ImageMagick-clamp-after-edge.patch
- update to 7.0.8-23:
* CacheInfo destructor must be aligned in DestroyPixelStream().
* Support negative rotations in a geometry (e.g. -10x-10+10+10).
* Return expected canvas offset after a crop with gravity.
==== Mesa ====
Version update (18.3.1 -> 18.3.2)
Subpackages: Mesa-dri-devel Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0 libgbm1
- Update to 18.3.2
* In this release candidate we have added more PCI IDs for AMD
Vega devices and a number of fixes for the RADV Vulkan drivers.
* On the Intel side we have a selection ranging from quad swizzles
support for ICL to compiler fixes.
* The nine state tracker has also seen some love as do the
Broadcom drivers.
* To top it all up, we have a healthy mount of build system fixes.
==== Mesa-drivers ====
Version update (18.3.1 -> 18.3.2)
Subpackages: Mesa-dri Mesa-dri-nouveau Mesa-gallium Mesa-libva libvdpau_nouveau libvdpau_r300 libvdpau_r600 libvdpau_radeonsi libvulkan_intel libvulkan_radeon libxatracker2
- Update to 18.3.2
* In this release candidate we have added more PCI IDs for AMD
Vega devices and a number of fixes for the RADV Vulkan drivers.
* On the Intel side we have a selection ranging from quad swizzles
support for ICL to compiler fixes.
* The nine state tracker has also seen some love as do the
Broadcom drivers.
* To top it all up, we have a healthy mount of build system fixes.
==== apache2 ====
Version update (2.4.37 -> 2.4.38)
Subpackages: apache2-devel apache2-doc apache2-example-pages apache2-prefork apache2-utils
- updated to 2.4.38
* mod_ssl: Clear retry flag before aborting client-initiated renegotiation.
PR 63052 [Joe Orton]
* mod_negotiation: Treat LanguagePriority as case-insensitive to match
AddLanguage behavior and HTTP specification. PR 39730 [Christophe Jaillet]
* mod_md: incorrect behaviour when synchronizing ongoing ACME challenges
have been fixed. [Michael Kaufmann, Stefan Eissing]
* mod_setenvif: We can have expressions that become true if a regex pattern
in the expression does NOT match. In this case val is NULL
and we should just set the value for the environment variable
like in the pattern case. [Ruediger Pluem]
* mod_session: Always decode session attributes early. [Hank Ibell]
* core: Incorrect values for environment variables are substituted when
multiple environment variables are specified in a directive. [Hank Ibell]
* mod_rewrite: Only create the global mutex used by "RewriteMap prg:" when
this type of map is present in the configuration. PR62311.
[Hank Ibell <hwibell gmail.com>]
* mod_dav: Fix invalid Location header when a resource is created by
passing an absolute URI on the request line [Jim Jagielski]
* mod_session_cookie: avoid duplicate Set-Cookie header in the response.
[Emmanuel Dreyfus
Am 06.02.19 um 16:00 schrieb Dominique Leuenberger:
sysconfig (0.85.0 -> 0.84.3)
Hi, Next to tons of upgrades, this also comes with the sysconfig reverted that broke resolv.conf for many. If you however already have 0.85 and migrated to a symlink yourself, I suggest to zypper al it and keep it. Otherwise you might end up with a forth and back between file and symlink. As far as we know, the bug is purely in the migration. But I wanted to have this reverted for people that skipped 0201 and 0202. Greetings, Stephan -- Lighten up, just enjoy life, smile more, laugh more, and don't get so worked up about things. Kenneth Branagh -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, since this Update I have some trouble, with at least all my Desktops. I've not find any message related this toppic here so I will ask if this is a special issue at my system or someone else know this problem? Setup: 1 Server as NFS (kernel) Server for /home 3 Desktops which mount /home remotly SW: All uses this Tumbleweed snapshot 20190205 and was afterwords rebootet All desktops used KDE Plasma 5 Behavior: At all desktops, the desktop will be frozen from time to time One or more CPUs ("Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz") are at 100% load. Mouse is still movable but nicer a klick on any button or menu takes an action nor a hotkey (like <alt>+F2) works. Only <strg>+<alt>+Fx or restart of the desktop or reboot hotkey works. In the loogs there are some messages, but I'm not sure that this are linking to the issue. Sometimes the load of the named (linked to yp-service?!) are very high: 2075 named 20 0 470072 145988 6048 S 12,50 0,903 1:42.80 named There are some messages like: Feb 09 16:23:44 yo org_kde_powerdevil[2337]: powerdevil: Suspend session triggered with QMap(("Explicit", QVariant(bool, true))("Type", QVariant(uint, 1))) Feb 09 16:20:38 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:38 yo org_kde_powerdevil[2337]: powerdevil: Added interrupt session Feb 09 16:20:38 yo org_kde_powerdevil[2337]: powerdevil: Enforcing inhibition from ":1.158" "/usr/bin/falkon" with cookie 34 and reason "WebRTC has active PeerConnections" Feb 09 16:20:34 yo org_kde_powerdevil[2337]: powerdevil: Scheduling inhibition from ":1.158" "/usr/bin/falkon" with cookie 34 and reason "WebRTC has active PeerConnections" Feb 09 16:20:32 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:32 yo org_kde_powerdevil[2337]: powerdevil: Releasing inhibition with cookie 17 Feb 09 16:20:04 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:04 yo org_kde_powerdevil[2337]: powerdevil: Restoring DPMS features after inhibition release Feb 09 16:20:04 yo org_kde_powerdevil[2337]: powerdevil: Releasing inhibition with cookie 33 Feb 09 16:20:04 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:04 yo org_kde_powerdevil[2337]: powerdevil: Releasing inhibition with cookie 32 Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Added interrupt session Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Added change screen settings Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Enforcing inhibition from ":1.14" "firefox" with cookie 33 and reason "video-playing" Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Disabling DPMS due to inhibition or Feb 09 15:24:06 yo plasmashell[2208]: plasma-pk-updates: Is net online: true Feb 09 15:24:06 yo plasmashell[2208]: plasma-pk-updates: Total number of updates: 0 Feb 09 15:24:06 yo plasmashell[2208]: plasma-pk-updates: Check updates transaction finished successfully Feb 09 15:24:06 yo plasmashell[2208]: plasma-pk-updates: Transaction "/2_bdadadee" finished with status "success" in 2 seconds Feb 09 15:24:06 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:04 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "refresh-cache" "(22%)" Feb 09 15:24:03 yo plasmashell[2208]: file:///home/yi/.local/share/plasma/plasmoids/org.kde.simpleMonitor/contents/ui/main.qml:114: Error: Cannot assign [undefined] to QStri> Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "query" "(0%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "query" "(0%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "query" "(0%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Updates changed, getting updates! Feb 09 15:24:01 yo plasmashell[2208]: plasma-pk-updates: Cache transaction finished successfully Feb 09 15:24:01 yo plasmashell[2208]: plasma-pk-updates: Transaction "/1_eedeadda" finished with status "success" in 3 seconds Feb 09 15:24:01 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "refresh-cache" "(22%)" Feb 09 15:24:01 yo plasmashell[2208]: org.kde.plasmaquick: Applet "Lautstärke" loaded after 52 msec Feb 09 15:24:01 yo plasmashell[2208]: org.kde.plasmaquick: Delayed preload of "Lautstärke" after 1.196 seconds Feb 09 15:24:01 yo plasmashell[2208]: org.kde.plasmaquick: Applet "Zwischenablage" loaded after 128 msec Feb 09 15:24:01 yo plasmashell[2208]: org.kde.plasmaquick: Delayed preload of "Zwischenablage" after 0 seconds Feb 09 15:24:00 yo plasmashell[2208]: Both point size and pixel size set. Using pixel size. Feb 09 15:24:00 yo dbus-daemon[2079]: [session uid=1004 pid=2079] Successfully activated service 'org.freedesktop.secrets' or Feb 09 15:23:52 yo plasmashell[2208]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:251: TypeError: Cannot read property > Feb 09 15:23:52 yo plasmashell[2208]: Model size of -2147483647 is less than 0 Feb 09 15:23:52 yo plasmashell[2208]: <Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "preferredWidth" Nicer a reboot nor others fix this issue. Still valid for all desktops during Wednesday after the update. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, no one the same Problem ??? I can't find the reason but my PCs are unusable since them (randomly between 1 and 10 minutes the system hangs and sometimes it will be operabel after 5 to 10 minutes - sometimes only a reset of the desktop via <strg>+<alt>+<back> key helps. No one of my family are able to work anymore especially in case of the fact that Editing of a file will sometimes broken! In hope that someone is able to support me to find the reason :-( Ulf
Gesendet: Samstag, 09. Februar 2019 um 17:57 Uhr Von: ub22@gmx.net An: "Mailing List openSUSE Factory"
Betreff: Aw: [opensuse-factory] New Tumbleweed snapshot 20190205 released! => unoperabel KDE Hi,
since this Update I have some trouble, with at least all my Desktops. I've not find any message related this toppic here so I will ask if this is a special issue at my system or someone else know this problem?
Setup: 1 Server as NFS (kernel) Server for /home 3 Desktops which mount /home remotly
SW: All uses this Tumbleweed snapshot 20190205 and was afterwords rebootet All desktops used KDE Plasma 5
Behavior: At all desktops, the desktop will be frozen from time to time One or more CPUs ("Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz") are at 100% load. Mouse is still movable but nicer a klick on any button or menu takes an action nor a hotkey (like <alt>+F2) works. Only <strg>+<alt>+Fx or restart of the desktop or reboot hotkey works.
In the loogs there are some messages, but I'm not sure that this are linking to the issue.
Sometimes the load of the named (linked to yp-service?!) are very high: 2075 named 20 0 470072 145988 6048 S 12,50 0,903 1:42.80 named
There are some messages like: Feb 09 16:23:44 yo org_kde_powerdevil[2337]: powerdevil: Suspend session triggered with QMap(("Explicit", QVariant(bool, true))("Type", QVariant(uint, 1))) Feb 09 16:20:38 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:38 yo org_kde_powerdevil[2337]: powerdevil: Added interrupt session Feb 09 16:20:38 yo org_kde_powerdevil[2337]: powerdevil: Enforcing inhibition from ":1.158" "/usr/bin/falkon" with cookie 34 and reason "WebRTC has active PeerConnections" Feb 09 16:20:34 yo org_kde_powerdevil[2337]: powerdevil: Scheduling inhibition from ":1.158" "/usr/bin/falkon" with cookie 34 and reason "WebRTC has active PeerConnections" Feb 09 16:20:32 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:32 yo org_kde_powerdevil[2337]: powerdevil: Releasing inhibition with cookie 17 Feb 09 16:20:04 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:04 yo org_kde_powerdevil[2337]: powerdevil: Restoring DPMS features after inhibition release Feb 09 16:20:04 yo org_kde_powerdevil[2337]: powerdevil: Releasing inhibition with cookie 33 Feb 09 16:20:04 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:04 yo org_kde_powerdevil[2337]: powerdevil: Releasing inhibition with cookie 32 Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Can't contact ck Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Added interrupt session Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Added change screen settings Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Enforcing inhibition from ":1.14" "firefox" with cookie 33 and reason "video-playing" Feb 09 16:20:02 yo org_kde_powerdevil[2337]: powerdevil: Disabling DPMS due to inhibition
or
Feb 09 15:24:06 yo plasmashell[2208]: plasma-pk-updates: Is net online: true Feb 09 15:24:06 yo plasmashell[2208]: plasma-pk-updates: Total number of updates: 0 Feb 09 15:24:06 yo plasmashell[2208]: plasma-pk-updates: Check updates transaction finished successfully Feb 09 15:24:06 yo plasmashell[2208]: plasma-pk-updates: Transaction "/2_bdadadee" finished with status "success" in 2 seconds Feb 09 15:24:06 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:04 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "refresh-cache" "(22%)" Feb 09 15:24:03 yo plasmashell[2208]: file:///home/yi/.local/share/plasma/plasmoids/org.kde.simpleMonitor/contents/ui/main.qml:114: Error: Cannot assign [undefined] to QStri> Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "query" "(0%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "query" "(0%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "query" "(0%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" Feb 09 15:24:03 yo plasmashell[2208]: plasma-pk-updates: Updates changed, getting updates! Feb 09 15:24:01 yo plasmashell[2208]: plasma-pk-updates: Cache transaction finished successfully Feb 09 15:24:01 yo plasmashell[2208]: plasma-pk-updates: Transaction "/1_eedeadda" finished with status "success" in 3 seconds Feb 09 15:24:01 yo plasmashell[2208]: plasma-pk-updates: Transaction status changed: "refresh-cache" "(22%)" Feb 09 15:24:01 yo plasmashell[2208]: org.kde.plasmaquick: Applet "Lautstärke" loaded after 52 msec Feb 09 15:24:01 yo plasmashell[2208]: org.kde.plasmaquick: Delayed preload of "Lautstärke" after 1.196 seconds Feb 09 15:24:01 yo plasmashell[2208]: org.kde.plasmaquick: Applet "Zwischenablage" loaded after 128 msec Feb 09 15:24:01 yo plasmashell[2208]: org.kde.plasmaquick: Delayed preload of "Zwischenablage" after 0 seconds Feb 09 15:24:00 yo plasmashell[2208]: Both point size and pixel size set. Using pixel size. Feb 09 15:24:00 yo dbus-daemon[2079]: [session uid=1004 pid=2079] Successfully activated service 'org.freedesktop.secrets'
or
Feb 09 15:23:52 yo plasmashell[2208]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:251: TypeError: Cannot read property > Feb 09 15:23:52 yo plasmashell[2208]: Model size of -2147483647 is less than 0 Feb 09 15:23:52 yo plasmashell[2208]: <Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "preferredWidth"
Nicer a reboot nor others fix this issue. Still valid for all desktops during Wednesday after the update.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Am Freitag, 15. Februar 2019, 00:04:10 CET schrieb ub22@gmx.net:
no one the same Problem ???
At least here it works well.....
I can't find the reason but my PCs are unusable since them (randomly between 1 and 10 minutes the system hangs and sometimes it will be operabel after 5 to 10 minutes - sometimes only a reset of the desktop via <strg>+<alt>+<back> key helps. No one of my family are able to work anymore especially in case of the fact that Editing of a file will sometimes broken!
Check your background jobs for heavy disk activities - or in your case, network activities (home was on a NFS share, right?). Baloo indexer might be a candidate, btrfs maintenance as well. I remember a KDE update some time ago that changed the structure of the database (if I'm not mistaken), that caused my destop to be unuseable as well for some time. After the dust has settled, all back to normal HTH Aaxel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi,
Gesendet: Freitag, 15. Februar 2019 um 10:33 Uhr; Von: "Axel Braun"
I can't find the reason but my PCs are unusable since them (randomly between 1 and 10 minutes the system hangs and sometimes it will be operabel after 5 to 10 minutes - sometimes only a reset of the desktop via <strg>+<alt>+<back> key helps. No one of my family are able to work anymore especially in case of the fact that Editing of a file will sometimes broken!
Check your background jobs for heavy disk activities - or in your case, network activities (home was on a NFS share, right?). Baloo indexer might be a candidate, btrfs maintenance as well.
Yes - /home was mounted on the Server xxx (192.168.111.1) Client: cat /etc/fstab 192.168.111.1:/home /home nfs4 defaults 0 0 [...] Server: cat /etc/fstab UUID=xyz /home ext4 defaults 0 0 /home /mnt/nfs4/home none bind 0 0 [...]
I remember a KDE update some time ago that changed the structure of the database (if I'm not mistaken), that caused my destop to be unuseable as well for some time. After the dust has settled, all back to normal
Now I checked the server with a second PC and during the time the test systems hang (mainly in KDE plasma - and now I can see on the CPU monitor, that at min. one CPU is running on 100% during the time the system hangs). At the second PC I can find in the log Feb 17 22:11:00 xxx kernel: nfs: server 192.168.111.1 not responding, still trying # zypper se Baloo [...] S | Name | Zusammenfassung | Typ --+--------------------------+-----------------------------------------------+------ | baloo5-devel | Development package for baloo5 | Paket i | baloo5-file | Filesearch components for Baloo Framework | Paket i | baloo5-file-lang | Translations for package baloo5 | Paket i | baloo5-imports | QML components for Baloo Framework | Paket i | baloo5-imports-lang | Translations for package baloo5 | Paket i | baloo5-kioslaves | KIO slave components for Baloo Framework | Paket i | baloo5-kioslaves-lang | Translations for package baloo5 | Paket i | baloo5-tools | Aditional components for Baloo Framework | Paket i | baloo5-tools-lang | Translations for package baloo5 | Paket i | baloo5-widgets | Framework for searching and managing metadata | Paket | baloo5-widgets-devel | Development package for baloo5-widgets | Paket i | baloo5-widgets-lang | Translations for package baloo5-widgets | Paket i | libKF5Baloo5 | Core library for Baloo Framework | Paket | libKF5Baloo5-32bit | Core library for Baloo Framework | Paket i | libKF5BalooEngine5 | Baloo Engine library | Paket | libKF5BalooEngine5-32bit | Baloo Engine library | Paket i | libKF5BalooEngine5-lang | Translations for package baloo5 | Paket # ps ax | grep -i baloo 28322 pts/6 S+ 0:00 grep --color=auto -i baloo But systemload seams to be normal during the hanging time (also no entry beside named during this time in the journalctl log): # head top-bn1_2019-02-17_* ==> top-bn1_2019-02-17_12:54:08.txt <== top - 12:54:08 up 11:22, 2 users, load average: 2.12, 5.34, 5.89 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 3.0 sy, 0.0 ni, 97.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1338.551 free, 1174.246 used, 13272.32+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14278.46+avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.12 systemd 2 root 20 0 0 0 0 S 0.000 0.000 0:00.05 kthreadd 3 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_gp ==> top-bn1_2019-02-17_12:55:22.txt <== top - 12:55:22 up 11:24, 2 users, load average: 4.19, 5.18, 5.78 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 2.9 sy, 1.5 ni, 48.5 id, 47.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1332.992 free, 1174.430 used, 13277.70+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14278.27+avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3525 root 39 19 670772 653112 5532 D 6.250 4.041 5:10.51 storeBackup 10961 root 20 0 8128 4124 3476 R 6.250 0.026 0:00.02 top 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.12 systemd ==> top-bn1_2019-02-17_12:56:43.txt <== top - 12:56:43 up 11:25, 2 users, load average: 3.11, 4.72, 5.58 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 4.4 sy, 0.0 ni, 76.5 id, 19.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1326.566 free, 1174.949 used, 13283.60+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14277.76+avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1932 root 20 0 0 0 0 S 6.250 0.000 0:06.02 nfsd 1933 root 20 0 0 0 0 S 6.250 0.000 0:08.92 nfsd 1934 root 20 0 0 0 0 D 6.250 0.000 0:12.13 nfsd ==> top-bn1_2019-02-17_13:04:32.txt <== top - 13:04:33 up 11:33, 2 users, load average: 4.25, 3.59, 4.60 Tasks: 199 total, 1 running, 198 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.5 us, 1.5 sy, 0.0 ni, 70.6 id, 25.0 wa, 0.0 hi, 1.5 si, 0.0 st MiB Mem : 15785.12+total, 1214.164 free, 1177.508 used, 13393.45+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14275.20+avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.13 systemd 2 root 20 0 0 0 0 S 0.000 0.000 0:00.05 kthreadd 3 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_gp Remark - during the 15 min. the test systems hangs - seems to be no special load or something others which pop's in my eyes. Thanks Ulf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El dom., 17 feb. 2019 a las 18:49,
Hi,
Gesendet: Freitag, 15. Februar 2019 um 10:33 Uhr; Von: "Axel Braun"
I can't find the reason but my PCs are unusable since them (randomly between 1 and 10 minutes the system hangs and sometimes it will be operabel after 5 to 10 minutes - sometimes only a reset of the desktop via <strg>+<alt>+<back> key helps. No one of my family are able to work anymore especially in case of the fact that Editing of a file will sometimes broken!
Check your background jobs for heavy disk activities - or in your case, network activities (home was on a NFS share, right?). Baloo indexer might be a candidate, btrfs maintenance as well.
Yes - /home was mounted on the Server xxx (192.168.111.1)
Client: cat /etc/fstab 192.168.111.1:/home /home nfs4 defaults 0 0 [...]
Server: cat /etc/fstab UUID=xyz /home ext4 defaults 0 0 /home /mnt/nfs4/home none bind 0 0 [...]
I remember a KDE update some time ago that changed the structure of the database (if I'm not mistaken), that caused my destop to be unuseable as well for some time. After the dust has settled, all back to normal
Now I checked the server with a second PC and during the time the test systems hang (mainly in KDE plasma - and now I can see on the CPU monitor, that at min. one CPU is running on 100% during the time the system hangs).
At the second PC I can find in the log Feb 17 22:11:00 xxx kernel: nfs: server 192.168.111.1 not responding, still trying
# zypper se Baloo [...] S | Name | Zusammenfassung | Typ --+--------------------------+-----------------------------------------------+------ | baloo5-devel | Development package for baloo5 | Paket i | baloo5-file | Filesearch components for Baloo Framework | Paket i | baloo5-file-lang | Translations for package baloo5 | Paket i | baloo5-imports | QML components for Baloo Framework | Paket i | baloo5-imports-lang | Translations for package baloo5 | Paket i | baloo5-kioslaves | KIO slave components for Baloo Framework | Paket i | baloo5-kioslaves-lang | Translations for package baloo5 | Paket i | baloo5-tools | Aditional components for Baloo Framework | Paket i | baloo5-tools-lang | Translations for package baloo5 | Paket i | baloo5-widgets | Framework for searching and managing metadata | Paket | baloo5-widgets-devel | Development package for baloo5-widgets | Paket i | baloo5-widgets-lang | Translations for package baloo5-widgets | Paket i | libKF5Baloo5 | Core library for Baloo Framework | Paket | libKF5Baloo5-32bit | Core library for Baloo Framework | Paket i | libKF5BalooEngine5 | Baloo Engine library | Paket | libKF5BalooEngine5-32bit | Baloo Engine library | Paket i | libKF5BalooEngine5-lang | Translations for package baloo5 | Paket
# ps ax | grep -i baloo 28322 pts/6 S+ 0:00 grep --color=auto -i baloo
But systemload seams to be normal during the hanging time (also no entry beside named during this time in the journalctl log):
# head top-bn1_2019-02-17_* ==> top-bn1_2019-02-17_12:54:08.txt <== top - 12:54:08 up 11:22, 2 users, load average: 2.12, 5.34, 5.89 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 3.0 sy, 0.0 ni, 97.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1338.551 free, 1174.246 used, 13272.32+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14278.46+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.12 systemd 2 root 20 0 0 0 0 S 0.000 0.000 0:00.05 kthreadd 3 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_gp
==> top-bn1_2019-02-17_12:55:22.txt <== top - 12:55:22 up 11:24, 2 users, load average: 4.19, 5.18, 5.78 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 2.9 sy, 1.5 ni, 48.5 id, 47.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1332.992 free, 1174.430 used, 13277.70+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14278.27+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3525 root 39 19 670772 653112 5532 D 6.250 4.041 5:10.51 storeBackup 10961 root 20 0 8128 4124 3476 R 6.250 0.026 0:00.02 top 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.12 systemd
==> top-bn1_2019-02-17_12:56:43.txt <== top - 12:56:43 up 11:25, 2 users, load average: 3.11, 4.72, 5.58 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 4.4 sy, 0.0 ni, 76.5 id, 19.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1326.566 free, 1174.949 used, 13283.60+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14277.76+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1932 root 20 0 0 0 0 S 6.250 0.000 0:06.02 nfsd 1933 root 20 0 0 0 0 S 6.250 0.000 0:08.92 nfsd 1934 root 20 0 0 0 0 D 6.250 0.000 0:12.13 nfsd
==> top-bn1_2019-02-17_13:04:32.txt <== top - 13:04:33 up 11:33, 2 users, load average: 4.25, 3.59, 4.60 Tasks: 199 total, 1 running, 198 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.5 us, 1.5 sy, 0.0 ni, 70.6 id, 25.0 wa, 0.0 hi, 1.5 si, 0.0 st MiB Mem : 15785.12+total, 1214.164 free, 1177.508 used, 13393.45+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14275.20+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.13 systemd 2 root 20 0 0 0 0 S 0.000 0.000 0:00.05 kthreadd 3 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_gp
Remark - during the 15 min. the test systems hangs - seems to be no special load or something others which pop's in my eyes.
Hi! You has verified the free disk space with command "df"? It looks like so: df S.ficheros bloques de 1K Usados Disponibles Uso% Montado en devtmpfs 8157692 0 8157692 0% /dev tmpfs 8202896 63092 8139804 1% /dev/shm tmpfs 8202896 9816 8193080 1% /run tmpfs 8202896 0 8202896 0% /sys/fs/cgroup /dev/sdb1 41945088 35785932 5268900 88% / /dev/sdb1 41945088 35785932 5268900 88% /boot/grub2/x86_64-efi /dev/sdb1 41945088 35785932 5268900 88% /tmp /dev/sdb1 41945088 35785932 5268900 88% /boot/grub2/i386-pc /dev/sdb1 41945088 35785932 5268900 88% /srv /dev/sdb1 41945088 35785932 5268900 88% /var /dev/sdb1 41945088 35785932 5268900 88% /usr/local /dev/sdb1 41945088 35785932 5268900 88% /opt /dev/sdb1 41945088 35785932 5268900 88% /root /dev/sdb2 1910635004 1284943776 625691228 68% /home tmpfs 1640576 8 1640568 1% /run/user/1000 A pair weeks ago I must to delette the older btrfs snapshots, because /dev/sdb1 was near the 100% Good luck! Juan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Juan Erbes
El dom., 17 feb. 2019 a las 18:49,
escribió: Hi,
Gesendet: Freitag, 15. Februar 2019 um 10:33 Uhr; Von: "Axel Braun"
I can't find the reason but my PCs are unusable since them (randomly between 1 and 10 minutes the system hangs and sometimes it will be operabel after 5 to 10 minutes - sometimes only a reset of the desktop via <strg>+<alt>+<back> key helps. No one of my family are able to work anymore especially in case of the fact that Editing of a file will sometimes broken!
Check your background jobs for heavy disk activities - or in your case, network activities (home was on a NFS share, right?). Baloo indexer might be a candidate, btrfs maintenance as well.
Yes - /home was mounted on the Server xxx (192.168.111.1)
Client: cat /etc/fstab 192.168.111.1:/home /home nfs4 defaults 0 0 [...]
Server: cat /etc/fstab UUID=xyz /home ext4 defaults 0 0 /home /mnt/nfs4/home none bind 0 0 [...]
I remember a KDE update some time ago that changed the structure of the database (if I'm not mistaken), that caused my destop to be unuseable as well for some time. After the dust has settled, all back to normal
Now I checked the server with a second PC and during the time the test systems hang (mainly in KDE plasma - and now I can see on the CPU monitor, that at min. one CPU is running on 100% during the time the system hangs).
At the second PC I can find in the log Feb 17 22:11:00 xxx kernel: nfs: server 192.168.111.1 not responding, still trying
# zypper se Baloo [...] S | Name | Zusammenfassung | Typ --+--------------------------+-----------------------------------------------+------ | baloo5-devel | Development package for baloo5 | Paket i | baloo5-file | Filesearch components for Baloo Framework | Paket i | baloo5-file-lang | Translations for package baloo5 | Paket i | baloo5-imports | QML components for Baloo Framework | Paket i | baloo5-imports-lang | Translations for package baloo5 | Paket i | baloo5-kioslaves | KIO slave components for Baloo Framework | Paket i | baloo5-kioslaves-lang | Translations for package baloo5 | Paket i | baloo5-tools | Aditional components for Baloo Framework | Paket i | baloo5-tools-lang | Translations for package baloo5 | Paket i | baloo5-widgets | Framework for searching and managing metadata | Paket | baloo5-widgets-devel | Development package for baloo5-widgets | Paket i | baloo5-widgets-lang | Translations for package baloo5-widgets | Paket i | libKF5Baloo5 | Core library for Baloo Framework | Paket | libKF5Baloo5-32bit | Core library for Baloo Framework | Paket i | libKF5BalooEngine5 | Baloo Engine library | Paket | libKF5BalooEngine5-32bit | Baloo Engine library | Paket i | libKF5BalooEngine5-lang | Translations for package baloo5 | Paket
# ps ax | grep -i baloo 28322 pts/6 S+ 0:00 grep --color=auto -i baloo
But systemload seams to be normal during the hanging time (also no entry beside named during this time in the journalctl log):
# head top-bn1_2019-02-17_* ==> top-bn1_2019-02-17_12:54:08.txt <== top - 12:54:08 up 11:22, 2 users, load average: 2.12, 5.34, 5.89 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 3.0 sy, 0.0 ni, 97.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1338.551 free, 1174.246 used, 13272.32+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14278.46+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.12 systemd 2 root 20 0 0 0 0 S 0.000 0.000 0:00.05 kthreadd 3 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_gp
==> top-bn1_2019-02-17_12:55:22.txt <== top - 12:55:22 up 11:24, 2 users, load average: 4.19, 5.18, 5.78 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 2.9 sy, 1.5 ni, 48.5 id, 47.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1332.992 free, 1174.430 used, 13277.70+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14278.27+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3525 root 39 19 670772 653112 5532 D 6.250 4.041 5:10.51 storeBackup 10961 root 20 0 8128 4124 3476 R 6.250 0.026 0:00.02 top 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.12 systemd
==> top-bn1_2019-02-17_12:56:43.txt <== top - 12:56:43 up 11:25, 2 users, load average: 3.11, 4.72, 5.58 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 4.4 sy, 0.0 ni, 76.5 id, 19.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1326.566 free, 1174.949 used, 13283.60+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14277.76+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1932 root 20 0 0 0 0 S 6.250 0.000 0:06.02 nfsd 1933 root 20 0 0 0 0 S 6.250 0.000 0:08.92 nfsd 1934 root 20 0 0 0 0 D 6.250 0.000 0:12.13 nfsd
==> top-bn1_2019-02-17_13:04:32.txt <== top - 13:04:33 up 11:33, 2 users, load average: 4.25, 3.59, 4.60 Tasks: 199 total, 1 running, 198 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.5 us, 1.5 sy, 0.0 ni, 70.6 id, 25.0 wa, 0.0 hi, 1.5 si, 0.0 st MiB Mem : 15785.12+total, 1214.164 free, 1177.508 used, 13393.45+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14275.20+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.13 systemd 2 root 20 0 0 0 0 S 0.000 0.000 0:00.05 kthreadd 3 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_gp
Remark - during the 15 min. the test systems hangs - seems to be no special load or something others which pop's in my eyes.
Hi!
You has verified the free disk space with command "df"? It looks like so: df
Not directly related, but: Please use `btrfs filesystem df` instead of df if you have a btrfs partition and want to measure free space. You'll get different results, which could matter if your filesystem is nearly full.
S.ficheros bloques de 1K Usados Disponibles Uso% Montado en devtmpfs 8157692 0 8157692 0% /dev tmpfs 8202896 63092 8139804 1% /dev/shm tmpfs 8202896 9816 8193080 1% /run tmpfs 8202896 0 8202896 0% /sys/fs/cgroup /dev/sdb1 41945088 35785932 5268900 88% / /dev/sdb1 41945088 35785932 5268900 88% /boot/grub2/x86_64-efi /dev/sdb1 41945088 35785932 5268900 88% /tmp /dev/sdb1 41945088 35785932 5268900 88% /boot/grub2/i386-pc /dev/sdb1 41945088 35785932 5268900 88% /srv /dev/sdb1 41945088 35785932 5268900 88% /var /dev/sdb1 41945088 35785932 5268900 88% /usr/local /dev/sdb1 41945088 35785932 5268900 88% /opt /dev/sdb1 41945088 35785932 5268900 88% /root /dev/sdb2 1910635004 1284943776 625691228 68% /home tmpfs 1640576 8 1640568 1% /run/user/1000
A pair weeks ago I must to delette the older btrfs snapshots, because /dev/sdb1 was near the 100%
Good luck! Juan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
--
Dan Čermák
At first Thanks Dan and Juan:-) It seems that I'm a step further. If I don't use Mozilla Firefox it seems that the system is still stable. So from my point of view it looks like an issue with Firefox file management (caches or configs) and an NFS mounted filesystem.
Gesendet: Montag, 18. Februar 2019 um 12:31 Uhr; Von: "Dan Čermák"
Juan Erbes
writes: El dom., 17 feb. 2019 a las 18:49,
escribió: You has verified the free disk space with command "df"? It looks like so: df
Not directly related, but:
Please use `btrfs filesystem df` instead of df if you have a btrfs partition and want to measure free space. You'll get different results, which could matter if your filesystem is nearly full.
Like you can see I never use btrfs again - so I had much trouble with full running file systems in the beginning of the stable system. It's not an only usage file system, you must monitor it continously :-(
A pair weeks ago I must to delette the older btrfs snapshots, because /dev/sdb1 was near the 100%
No, there is enough space on root and /home (not so much, but I will move some data to through data2 or delete them: /dev/md126 ext4 117G 14G 97G 13% / /dev/sde1 vfat 31M 0 31M 0% /boot/efi.sik /dev/sdd1 vfat 31M 0 31M 0% /boot/efi /dev/md125 ext4 902G 800G 56G 94% /home /dev/md1 ext4 2,7T 2,4T 324G 89% /mnt/data2 /dev/mapper/data1-common ext4 2,7T 2,4T 164G 94% /mnt/data1
Good luck! Thanks, I think I need them
Regards Ulf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi together, after a very long time of search I found the reason of the hanging of the NFS-Server and depends on this the NFS-Clients with mounted /home which are blocked several time for some minutes till hours. The reason was a hangig daemon which are included in the /etc/init.d/boot.local Script. After the update to systemd, the script was included in /usr/lib/systemd/system/rc-local.service Inside of the boot.local there are only one relevant line: test -x /usr/bin/aerod && ( /usr/bin/aerod -f -t &>> /var/log/aquero.log )& Which starts the lynix aerodamon which allows to monitor my FAN-Control. https://github.com/lynix/aerotools https://www.aquacomputer.de/steuerung.html Due to the fact that boot.local was not canceled before a reboot and Continuos hangs, I created an aerod.service in the /etc/systemd/system like described in some openSUSE forums: # cat /etc/systemd/system/aerod.service [Unit] Description=aerod Serice ConditionFileIsExecutable=/usr/bin/aerod After=basic.target [Service] Type=oneshot ExecStart=/usr/bin/aerod -f -t ExecStop=killall aerod TimeoutSec=0 #StandardOutput=/var/log/aquero.log StandardOutput=tty RemainAfterExit=yes [Install] WantedBy=multi-user.target # Now I saw some errors in the log some USB errors - which seams the reason. Excuse me but I didn't store the error messages and was out of the journalctl log :-( Regards Ulf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Axel Braun
-
Dan Čermák
-
Dominique Leuenberger
-
Juan Erbes
-
Stephan Kulow
-
ub22@gmx.net