Tumbleweed Webserver, nach update kein NFS mount aus fstab
- thorium666
- Erledigt
Hinweis: In dem Thema Tumbleweed Webserver, nach update kein NFS mount aus fstab gibt es 32 Antworten auf 4 Seiten. Der letzte Beitrag () befindet sich auf der letzten Seite.
-
-
NFS Server (Leap 42.1)
Codetoxic:/ # systemd-analyze blame |grep nfs 321ms var-lib-nfs-rpc_pipefs.mount 303ms proc-fs-nfsd.mount 34ms nfs-server.service 17ms nfs-mountd.service 5ms nfs-config.service 3ms nfs-idmapd.service 2ms nfsserver.service
NFS Client (TW)NFS Client (TW)
Codevega:/home/devil # systemctl status nfs-mountd.service ● nfs-mountd.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
NFS Server (Leap 42.1)
Codetoxic:/ # zypper se -si | grep nfs i | nfs-client | package | 1.3.0-14.1 | x86_64 | Main Update Repository i | nfs-kernel-server | package | 1.3.0-14.1 | x86_64 | Main Update Repository i | nfsidmap | package | 0.25-7.1 | x86_64 | Main Repository (OSS) i | yast2-nfs-client | package | 3.1.16-5.2 | noarch | Main Repository (OSS) i | yast2-nfs-common | package | 3.1.8-5.2 | noarch | Main Repository (OSS) i | yast2-nfs-server | package | 3.1.8-5.2 | noarch | Main Repository (OSS)
NFS Client (TW)Codevega:/home/devil # zypper se -si | grep nfs i | nfs-client | package | 1.3.3-5.1 | x86_64 | openSUSE-Tumbleweed-Oss i | nfsidmap | package | 0.26-1.3 | x86_64 | openSUSE-Tumbleweed-Oss i | yast2-nfs-client | package | 3.1.16-1.1 | noarch | openSUSE-Tumbleweed-Oss i | yast2-nfs-common | package | 3.1.8-1.4 | noarch | openSUSE-Tumbleweed-Oss
-
Schön das du filterst, das war nur nicht gefordert.
-
NFS Client:
Code
Alles anzeigen15.577s plymouth-quit-wait.service 15.257s wicked.service 4.813s clamd.service 3.236s systemd-udev-settle.service 1.037s mysql.service 381ms apparmor.service 252ms dev-sda3.device 202ms vboxadd.service 187ms apache2.service 180ms ModemManager.service 160ms postfix.service 109ms mediatomb.service 104ms systemd-journal-flush.service 73ms systemd-tmpfiles-clean.service 64ms freshclam.service 63ms cups.service 57ms systemd-udevd.service 44ms plymouth-quit.service 44ms polkit.service 40ms systemd-tmpfiles-setup-dev.service 38ms sshd.service 37ms rpcbind.service 37ms wickedd-dhcp6.service 36ms wickedd-dhcp4.service 34ms ntpd.service 32ms systemd-vconsole-setup.service 29ms avahi-daemon.service 27ms wickedd-auto4.service 26ms vboxadd-service.service 24ms plymouth-start.service 23ms boot-efi.mount 19ms systemd-udev-trigger.service 18ms systemd-journald.service 17ms user@1000.service 16ms lvm2-activation-early.service 15ms sys-kernel-debug.mount 15ms nscd.service 14ms plymouth-read-write.service 13ms dev-hugepages.mount 13ms kmod-static-nodes.service 13ms systemd-fsck-root.service 12ms systemd-udev-root-symlink.service 12ms apcupsd.service 11ms systemd-logind.service 10ms systemd-modules-load.service 9ms wickedd-nanny.service 9ms systemd-tmpfiles-setup.service 7ms systemd-remount-fs.service 7ms systemd-random-seed.service 6ms lvm2-activation.service 6ms dev-mqueue.mount 5ms wickedd.service 4ms systemd-sysctl.service 4ms systemd-update-utmp.service 4ms var-run.mount 4ms rc-local.service 3ms auditd.service 3ms systemd-update-utmp-runlevel.service 2ms dracut-shutdown.service 2ms systemd-user-sessions.service
NFS Server:
Code
Alles anzeigen5.439s wicked.service 3.025s stor_agent.service 1.273s lvm2-pvscan@259:3.service 1.264s lvm2-pvscan@8:32.service 515ms oscam.service 321ms var-lib-nfs-rpc_pipefs.mount 307ms var-lib-mailman.mount 306ms var-crash.mount 306ms usr-local.mount 303ms var-log.mount 303ms proc-fs-nfsd.mount 301ms var-lib-mariadb.mount 300ms var-lib-libvirt-images.mount 298ms tmp.mount 298ms srv.mount 297ms opt.mount 296ms boot-grub2-x86_64\x2defi.mount 296ms boot-grub2-i386\x2dpc.mount 290ms vboxdrv.service 287ms \x2esnapshots.mount 286ms var-tmp.mount 286ms var-spool.mount 285ms var-opt.mount 285ms var-lib-pgsql.mount 284ms var-lib-named.mount 284ms var-lib-mysql.mount 189ms vboxweb-service.service 178ms apparmor.service 141ms dev-md126p2.device 131ms dhcpd.service 110ms postfix.service 86ms apache2.service 73ms named.service 66ms plymouth-quit-wait.service 63ms media-lvm-mediadata.mount 53ms media-lvm-vmfs.mount 34ms nfs-server.service 33ms boot-efi.mount 28ms smb.service 26ms rpcbind.service 24ms plymouth-start.service 22ms ModemManager.service 22ms plymouth-quit.service 22ms nmb.service 17ms nfs-mountd.service 16ms systemd-udev-trigger.service 13ms ntpd.service 13ms rpc-statd.service 13ms sshd.service 12ms polkit.service 12ms wickedd-dhcp6.service 11ms wickedd-dhcp4.service 11ms plymouth-read-write.service 11ms systemd-tmpfiles-setup.service 10ms user@1001.service 10ms wickedd-auto4.service 10ms sys-kernel-debug.mount 9ms systemd-fsck@dev-disk-by\x2duuid-d67f885d\x2d150c\x2d4c6e\x2db357\x2d342a01533b06.service 8ms dev-mqueue.mount 8ms systemd-fsck@dev-array2-media.service 8ms systemd-journald.service 8ms dev-hugepages.mount 8ms ypbind.service 7ms wickedd.service 7ms systemd-readahead-replay.service 7ms avahi-daemon.service 7ms systemd-udev-root-symlink.service 7ms systemd-readahead-collect.service 6ms wpa_supplicant.service 6ms user@1000.service 5ms systemd-readahead-done.service 5ms systemd-user-sessions.service 5ms rpc-statd-notify.service 5ms nfs-config.service 5ms systemd-journal-flush.service 4ms kmod-static-nodes.service 4ms nscd.service 4ms wickedd-nanny.service 4ms systemd-vconsole-setup.service 4ms mdmon@md127.service 3ms systemd-backlight@backlight:acpi_video0.service 3ms apcupsd.service 3ms systemd-tmpfiles-clean.service 3ms nfs-idmapd.service 3ms systemd-update-utmp-runlevel.service 3ms systemd-remount-fs.service 3ms systemd-logind.service 3ms systemd-update-utmp.service 2ms nfsserver.service 2ms systemd-tmpfiles-setup-dev.service 2ms iscsi.service 2ms mdmonitor.service 2ms systemd-random-seed.service 2ms systemd-udevd.service 2ms systemd-modules-load.service 2ms systemd-sysctl.service 1ms auditd.service 1ms rc-local.service
-
-
Code
Alles anzeigenmulti-user.target @23.854s └─clamd.service @19.028s +4.825s └─freshclam.service @18.954s +61ms └─network.target @18.937s └─wicked.service @3.698s +15.238s └─wickedd-nanny.service @3.690s +7ms └─wickedd.service @3.681s +8ms └─wickedd-auto4.service @3.654s +25ms └─dbus.service @3.593s └─basic.target @3.590s └─sockets.target @3.589s └─cups.socket @3.589s └─sysinit.target @3.584s └─systemd-update-utmp.service @3.578s +5ms └─auditd.service @3.573s +3ms └─systemd-tmpfiles-setup.service @3.558s +9ms └─local-fs.target @3.541s └─boot-efi.mount @3.514s +26ms └─local-fs-pre.target @3.512s └─systemd-tmpfiles-setup-dev.service @210ms +15ms └─kmod-static-nodes.service @163ms +10ms └─systemd-journald.socket └─-.mount └─system.slice └─-.slice
Hi,
den Eindruck habe ich auch, ich habe auf meinem Laptop geschaut und da ist das gleiche Bild.
Nachtrag: Auf allen 3 TWs...Hier auch noch ein Leap (nicht der NFS server)
Code
Alles anzeigenmulti-user.target @16.535s └─cron.service @16.535s └─postfix.service @16.401s +133ms └─time-sync.target @16.400s └─ntpd.service @16.368s +31ms └─network.target @16.365s └─wicked.service @1.044s +15.320s └─wickedd-nanny.service @1.014s +16ms └─wickedd.service @985ms +25ms └─wickedd-auto4.service @939ms +42ms └─dbus.service @883ms └─basic.target @879ms └─timers.target @879ms └─systemd-tmpfiles-clean.timer @878ms └─sysinit.target @877ms └─apparmor.service @468ms +408ms └─systemd-tmpfiles-setup.service @440ms +27ms └─local-fs.target @423ms └─boot-efi.mount @412ms +10ms └─dev-disk-by\x2duuid-109A\x2dD42D.device @408ms
Der hat auch kein NFS in der chain (hat auch kein NFS in der fstab) jedoch:Codenfs-mountd.service - NFS Mount Daemon Loaded: loaded (/usr/lib/systemd/system/nfs-mountd.service; static) Active: inactive (dead)
Was bei den TWs ergibt: -
-
Hi,
das hat funktioniert, habe dadraufhin neugestartet und hatte wieder keine mappings.
Code
Alles anzeigensystemctl status nfs.service ● nfs.service - Alias for NFS client Loaded: loaded (/usr/lib/systemd/system/nfs.service; enabled; vendor preset: disabled) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: active (exited) since Mon 2016-03-21 19:10:10 CET; 1min 13s ago Process: 872 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 872 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 512) CGroup: /system.slice/nfs.service Mar 21 19:10:10 vega systemd[1]: Starting Alias for NFS client... Mar 21 19:10:10 vega systemd[1]: Started Alias for NFS client.
Dienst läuft, nützt aber nichts, es gibt keinerlei EInträge im Journal. Ich werde den Workarround wieder aktivieren.
-
Ich werde am Wochenende einmal mit NFS spielen, mal schauen.
-
Danke dir. NFS funktioniert je generell, irgend ein Deamon der das beim Boot startet ist scheinbar weggeupdated worden.