seduction
 Language:
Welcome, Guest. Please login or register.
Did you miss your activation email?
2020/11/28, 17:35:38


Help

Author [EN] [PL] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: [solved] Problem (nfs ?) nach du heute Mittag  (Read 3550 times)

0 Members and 1 Guest are viewing this topic.

Offline jure

  • User
  • Posts: 536
[solved] Problem (nfs ?) nach du heute Mittag
« on: 2018/01/30, 16:35:30 »
Hallo zusammen,

ich habe ein Problem, dass ich leider nicht so einfach zu beschreiben weiß - sorry
ich versuche es mal ... wenn noch weitere/andere Infos gebraucht werden, bitte fragen !

also, nach einem du heute Mittag auf meinem PC bootet dieser mit einer Pause bei
"[OK] - Started Network Time Service"

mit der Meldung
Quote
[***] (1 of 2) a start job is running for pNFS block layout mapping daemon 1 min 30
[***] (2 of 2) a start job is running for NFS status monitor for NFSv2/3 locking 1min 30

nach 1min 30 erscheint der lightdm login und es dauert ca 45s bis der KDE Desktop erscheint - allerdings ohne Taskleiste. Die erscheint dann nach ein paar Minuten, ist aber erst nach weiteren Minuten  benutzbar. Das ist unabhängig vom Kernel, also mit 4.14xxx oder 4.15.0-towo.1.

"Irgendwas" ist mit NFS faul (?) - das per NFS eingebundene NAS ist somit nicht erreichbar ...
Das Netzwerk läuft (ich schreibe von diesem pc) - aber alles was NFS (im Hintergrund braucht) funzt nicht.

Quote
systemctl list-units | grep failed
● media-daten\x2dnas.mount                                                                  loaded failed failed    /media/daten-nas                                                                 
● nfs-blkmap.service                                                                        loaded failed failed    pNFS block layout mapping daemon                                                 
● rpc-statd.service                                                                         loaded failed failed    NFS status monitor for NFSv2/3 locking.                                         
● systemd-backlight@backlight:acpi_video0.service                                           loaded failed failed    Load/Save Screen Backlight Brightness

Quote
systemd-analyze critical-chain

graphical.target @1min 31.609s
└─multi-user.target @1min 31.609s
  └─minidlna.service @1min 31.293s +315ms
    └─remote-fs.target @1min 31.292s
      └─remote-fs-pre.target @1min 31.291s
        └─nfs-server.service @1min 31.267s +20ms
          └─network.target @1.028s
            └─networking.service @813ms +143ms
              └─resolvconf.service @803ms +5ms
                └─systemd-journald.socket @154ms
                  └─system.slice @154ms
                    └─-.slice @151ms

das müssten die Fehlermeldungen bei booten nach dem du sein
Code: [Select]
journalctl -p err --since=today | grep -i Failed
Jan 30 13:51:41 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 13:51:41 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 13:51:41 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 13:51:41 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 13:51:41 siductionbox blkmapd[343]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Jan 30 13:51:42 siductionbox systemd-backlight[748]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
Jan 30 13:51:42 siductionbox systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Jan 30 13:51:45 siductionbox ntpd[1816]: bind(21) AF_INET6 fe80::a60:6eff:fe73:6eea%2#123 flags 0x11 failed: Cannot assign requested address
Jan 30 13:51:47 siductionbox ntpd[1816]: bind(24) AF_INET6 fd00::a60:6eff:fe73:6eea#123 flags 0x11 failed: Cannot assign requested address
Jan 30 13:53:16 siductionbox systemd[1]: Failed to start pNFS block layout mapping daemon.
Jan 30 13:53:17 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 13:53:17 siductionbox nfsdcltrack[5149]: Failed to init database: -13
Jan 30 13:53:27 siductionbox sudo[5589]: pam_unix(sudo:auth): conversation failed
Jan 30 13:54:39 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 13:54:39 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 13:54:39 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 13:54:39 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 13:54:39 siductionbox blkmapd[338]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Jan 30 13:54:43 siductionbox ntpd[1088]: bind(21) AF_INET6 fe80::a60:6eff:fe73:6eea%2#123 flags 0x11 failed: Cannot assign requested address
Jan 30 13:54:44 siductionbox ntpd[1088]: bind(24) AF_INET6 fe80::a60:6eff:fe73:6eea%2#123 flags 0x11 failed: Cannot assign requested address
Jan 30 13:56:16 siductionbox systemd[1]: Failed to start pNFS block layout mapping daemon.
Jan 30 13:56:17 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 13:56:17 siductionbox nfsdcltrack[1447]: Failed to init database: -13


Code: [Select]
System:    Host: siductionbox Kernel: 4.15.0-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.10.5
           Distro: Debian GNU/Linux buster/sid
Machine:   Device: desktop Mobo: ASUSTeK model: P8Z77-M v: Rev 1.xx serial: N/A
           BIOS: American Megatrends v: 2203 date: 12/18/2015
CPU:       Quad core Intel Core i5-3570 (-MCP-) speed/max: 1604/3800 MHz
Graphics:  Card: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
           Display Server: x11 (X.Org 1.19.6 ) driver: intel Resolution: 1920x1200@59.95hz
           OpenGL: renderer: Mesa DRI Intel Ivybridge Desktop version: 4.2 Mesa 17.3.3
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives:    HDD Total Size: 256.1GB (50.9% used)
Info:      Processes: 239 Uptime: 10 min Memory: 1523.7/7671.1MB Client: Shell (bash) inxi: 2.3.56

« Last Edit: 2018/01/31, 14:23:33 by jure »
Gruss Juergen

Offline bluelupo

  • Global Moderator
  • User
  • *****
  • Posts: 2.066
    • BluelupoMe
Re: Problem (nfs ?) nach du heute Mittag
« Reply #1 on: 2018/01/30, 17:48:21 »
Hi jure,

was sagt den das Journal zu NFS bzw. welche Fehler sind beim letzten Bootvorgang aufgetreten.

Code: [Select]
# journalctl -u nfs-server.service
# journalctl -p err -b0
# systemctl status nfs*
# systemctl status systemd-timesyncd.service
« Last Edit: 2018/01/30, 18:02:33 by bluelupo »

Offline jure

  • User
  • Posts: 536
Re: Problem (nfs ?) nach du heute Mittag
« Reply #2 on: 2018/01/30, 18:19:50 »
Hi bluelupo

journalctl -u nfs-server.service
Quote

Jan 30 13:51:31 siductionbox systemd[1]: Stopping NFS server and services...
Jan 30 13:51:31 siductionbox systemd[1]: Stopped NFS server and services.
^[[0;1;39m-- Reboot --
Jan 30 13:53:17 siductionbox systemd[1]: Starting NFS server and services...
Jan 30 13:53:17 siductionbox systemd[1]: Started NFS server and services.
Jan 30 13:54:21 siductionbox systemd[1]: Stopping NFS server and services...
Jan 30 13:54:21 siductionbox systemd[1]: Stopped NFS server and services.
.....

journalctl -p err -b0 | cat
Quote
                                                                                                             
-- Logs begin at Wed 2014-12-31 09:40:16 CET, end at Tue 2018-01-30 18:11:46 CET. --                                                                                     
Jan 30 15:25:50 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)                                                     
Jan 30 15:25:50 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170831/psparse-550)                             
Jan 30 15:25:50 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)                                                     
Jan 30 15:25:50 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170831/psparse-550)                             
Jan 30 15:25:50 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)                                                     
Jan 30 15:25:50 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170831/psparse-550)                             
Jan 30 15:25:50 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)                                                                         
Jan 30 15:25:50 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170831/psparse-550)                                                 
Jan 30 15:25:50 siductionbox blkmapd[339]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory                                                                 
Jan 30 15:25:50 siductionbox systemd-udevd[345]: Specified user '<Juergen Rehnen' unknown
Jan 30 15:25:50 siductionbox kernel: kvm: disabled by bios
Jan 30 15:25:50 siductionbox systemd-udevd[345]: GOTO 'mm_zte_port_types_end' has no matching label in: '/etc/udev/rules.d/77-mm-zte-port-types.rules'
Jan 30 15:25:50 siductionbox systemd-udevd[345]: GOTO 'mm_zte_port_types_end' has no matching label in: '/etc/udev/rules.d/77-mm-zte-port-types.rules'
Jan 30 15:25:50 siductionbox systemd-udevd[345]: GOTO 'mm_zte_port_types_end' has no matching label in: '/etc/udev/rules.d/77-mm-zte-port-types.rules'
Jan 30 15:25:51 siductionbox systemd-backlight[560]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
Jan 30 15:25:51 siductionbox systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Jan 30 15:25:52 siductionbox ntpd[767]: error resolving pool 0.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Jan 30 15:25:53 siductionbox ntpd[767]: error resolving pool 1.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Jan 30 15:25:54 siductionbox ntpd[1085]: bind(21) AF_INET6 fe80::a60:6eff:fe73:6eea%2#123 flags 0x11 failed: Cannot assign requested address
Jan 30 15:25:54 siductionbox ntpd[1085]: unable to create socket on eth0 (5) for fe80::a60:6eff:fe73:6eea%2#123
Jan 30 15:25:56 siductionbox ntpd[1085]: bind(24) AF_INET6 fd00::a60:6eff:fe73:6eea#123 flags 0x11 failed: Cannot assign requested address
Jan 30 15:25:56 siductionbox ntpd[1085]: unable to create socket on eth0 (6) for fd00::a60:6eff:fe73:6eea#123
Jan 30 15:27:28 siductionbox blkmapd[339]: exit on signal(15)
Jan 30 15:27:28 siductionbox systemd[1]: Failed to start pNFS block layout mapping daemon.
Jan 30 15:27:29 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 15:27:29 siductionbox nfsdcltrack[1446]: Failed to init database: -13
Jan 30 15:27:36 siductionbox sudo[1877]: pam_unix(sudo:auth): conversation failed
Jan 30 15:27:36 siductionbox sudo[1877]: pam_unix(sudo:auth): auth could not identify password for [juergen]
Jan 30 15:27:36 siductionbox sudo[1877]:  juergen : command not allowed ; TTY=unknown ; PWD=/home/juergen ; USER=root ; COMMAND=/bin/ln -sf /var/run/xauth/* /root/.Xauthority
Jan 30 15:29:07 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 15:29:07 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 15:30:38 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 15:30:38 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 15:32:08 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 15:32:08 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 15:33:38 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 15:33:38 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 15:35:10 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 15:35:10 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 16:05:13 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 16:05:13 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 16:06:43 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 16:06:43 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 16:08:13 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 16:08:13 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 16:09:43 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 16:09:43 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 16:12:19 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 16:12:19 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 16:24:38 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 16:24:38 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 16:33:54 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 16:33:54 siductionbox nfsdcltrack[21892]: Failed to init database: -13
Jan 30 17:15:44 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 30 17:15:44 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 17:28:25 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Jan 30 17:28:25 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 17:28:25 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Jan 30 17:28:25 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 17:28:25 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Jan 30 17:28:25 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 17:28:25 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Jan 30 17:28:25 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 17:28:27 siductionbox ntpd[2770]: error resolving pool 0.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Jan 30 17:28:28 siductionbox ntpd[2770]: error resolving pool 1.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Jan 30 17:28:28 siductionbox ntpd[2916]: bind(21) AF_INET6 fe80::a60:6eff:fe73:6eea%2#123 flags 0x11 failed: Cannot assign requested address
Jan 30 17:28:28 siductionbox ntpd[2916]: unable to create socket on eth0 (5) for fe80::a60:6eff:fe73:6eea%2#123
Jan 30 17:28:29 siductionbox ntpd[2916]: bind(24) AF_INET6 fe80::a60:6eff:fe73:6eea%2#123 flags 0x11 failed: Cannot assign requested address
Jan 30 17:28:29 siductionbox ntpd[2916]: unable to create socket on eth0 (6) for fe80::a60:6eff:fe73:6eea%2#123
Jan 30 17:28:31 siductionbox ntpd[2916]: bind(24) AF_INET6 fd00::a60:6eff:fe73:6eea#123 flags 0x11 failed: Cannot assign requested address
Jan 30 17:28:31 siductionbox ntpd[2916]: unable to create socket on eth0 (7) for fd00::a60:6eff:fe73:6eea#123
Jan 30 18:01:22 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Jan 30 18:01:22 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 18:01:22 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Jan 30 18:01:22 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 18:01:22 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Jan 30 18:01:22 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 18:01:22 siductionbox kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Jan 30 18:01:22 siductionbox kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20170831/psparse-550)
Jan 30 18:01:24 siductionbox ntpd[8065]: error resolving pool 0.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Jan 30 18:01:25 siductionbox ntpd[8065]: error resolving pool 1.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Jan 30 18:01:26 siductionbox ntpd[8205]: bind(21) AF_INET6 fe80::a60:6eff:fe73:6eea%2#123 flags 0x11 failed: Cannot assign requested address
Jan 30 18:01:26 siductionbox ntpd[8205]: unable to create socket on eth0 (5) for fe80::a60:6eff:fe73:6eea%2#123
Jan 30 18:01:28 siductionbox ntpd[8205]: bind(24) AF_INET6 fd00::a60:6eff:fe73:6eea#123 flags 0x11 failed: Cannot assign requested address
Jan 30 18:01:28 siductionbox ntpd[8205]: unable to create socket on eth0 (6) for fd00::a60:6eff:fe73:6eea#123
Jan 30 18:03:30 siductionbox systemd[1]: Failed to mount /media/daten-nas.
Jan 30 18:03:30 siductionbox systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..

systemctl status nfs*
Quote
● nfs-client.target - NFS client services
   Loaded: loaded (/lib/systemd/system/nfs-client.target; enabled; vendor preset: enabled)
   Active: active since Tue 2018-01-30 15:25:51 CET; 2h 41min ago

Jan 30 15:25:51 siductionbox systemd[1]: Reached target NFS client services.

● nfs-idmapd.service - NFSv4 ID-name mapping service
   Loaded: loaded (/lib/systemd/system/nfs-idmapd.service; static; vendor preset: enabled)
   Active: active (running) since Tue 2018-01-30 16:32:24 CET; 1h 35min ago
  Process: 21493 ExecStart=/usr/sbin/rpc.idmapd $RPCIDMAPDARGS (code=exited, status=0/SUCCESS)
 Main PID: 21495 (rpc.idmapd)
   CGroup: /system.slice/nfs-idmapd.service
           └─21495 /usr/sbin/rpc.idmapd

Jan 30 16:32:24 siductionbox systemd[1]: Starting NFSv4 ID-name mapping service...
Jan 30 16:32:24 siductionbox systemd[1]: Started NFSv4 ID-name mapping service.

● nfs-mountd.service - NFS Mount Daemon
   Loaded: loaded (/lib/systemd/system/nfs-mountd.service; static; vendor preset: enabled)
   Active: active (running) since Tue 2018-01-30 16:32:58 CET; 1h 34min ago
  Process: 21662 ExecStart=/usr/sbin/rpc.mountd $RPCMOUNTDARGS (code=exited, status=0/SUCCESS)
 Main PID: 21663 (rpc.mountd)
   CGroup: /system.slice/nfs-mountd.service
           └─21663 /usr/sbin/rpc.mountd --manage-gids

Jan 30 16:32:58 siductionbox systemd[1]: Starting NFS Mount Daemon...
Jan 30 16:32:58 siductionbox rpc.mountd[21663]: ^[[0;1;39m^[[0;1;39mVersion 1.3.3 starting
Jan 30 16:32:58 siductionbox systemd[1]: Started NFS Mount Daemon.

● nfs-blkmap.service - pNFS block layout mapping daemon
   Loaded: loaded (/lib/systemd/system/nfs-blkmap.service; disabled; vendor preset: enabled)
   Active: failed (Result: timeout) since Tue 2018-01-30 15:27:28 CET; 2h 39min ago
  Process: 338 ExecStart=/usr/sbin/blkmapd $BLKMAPDARGS (code=exited, status=0/SUCCESS)

Jan 30 15:25:50 siductionbox blkmapd[339]: ^[[0;1;39mopen pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Jan 30 15:27:28 siductionbox systemd[1]: ^[[0;1;39m^[[0;1;39mnfs-blkmap.service: Start operation timed out. Terminating.
Jan 30 15:27:28 siductionbox blkmapd[339]: ^[[0;1;39mexit on signal(15)
Jan 30 15:27:28 siductionbox systemd[1]: ^[[0;1;39m^[[0;1;39mnfs-blkmap.service: Failed with result 'timeout'.
Jan 30 15:27:28 siductionbox systemd[1]: ^[[0;1;39mFailed to start pNFS block layout mapping daemon.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.


● nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
   Active: active (exited) since Tue 2018-01-30 16:33:54 CET; 1h 33min ago
  Process: 21488 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)
  Process: 21487 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS)
  Process: 21486 ExecStop=/usr/sbin/rpc.nfsd 0 (code=exited, status=0/SUCCESS)
  Process: 21891 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=0/SUCCESS)
  Process: 21890 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
 Main PID: 21891 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/nfs-server.service

Jan 30 16:33:54 siductionbox systemd[1]: Starting NFS server and services...
Jan 30 16:33:54 siductionbox systemd[1]: Started NFS server and services.


systemctl status systemd-timesyncd.service
Quote
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
Gruss Juergen

Offline bluelupo

  • Global Moderator
  • User
  • *****
  • Posts: 2.066
    • BluelupoMe
Re: Problem (nfs ?) nach du heute Mittag
« Reply #3 on: 2018/01/30, 18:32:01 »
Hi jure,

irgendetwas stimmt mit deinem Netzwerk nicht. Du hast mit NTP und NFS Probleme. Bist du sicher das dein Netzwerk richtig läuft?

Code: [Select]
Jan 30 15:27:28 siductionbox systemd[1]: Failed to start pNFS block layout mapping daemon.
....
Jan 30 15:25:52 siductionbox ntpd[767]: error resolving pool 0.debian.pool.ntp.org: Temporary failure in name resolution (-3)

Offline jure

  • User
  • Posts: 536
Re: Problem (nfs ?) nach du heute Mittag
« Reply #4 on: 2018/01/30, 19:12:00 »
das Netzwerk funzt grundsätzlich, ich bin auch mit dem pc online, email geht, kann das NAS pingen, aber NFS funktioniert wohl nicht. Die Ordner auf dem NAS werden nicht eingebunden (NFS).

Nach einem "systemctl start systemd-timesyncd.service" läuft der service auch nach einem Neustart

Ich hatte außer dem du heute Mittag NICHTS geändert, entfernt, hinzugefügt ... und vorher lief alles ohne Probleme.
Gruss Juergen


Offline jure

  • User
  • Posts: 536
Re: Problem (nfs ?) nach du heute Mittag
« Reply #6 on: 2018/01/30, 19:38:52 »
da war im du - siehe Anhang

wie schon geschrieben, bis zum du heute keine Probleme ....  :(
Gruss Juergen

Offline jure

  • User
  • Posts: 536
Re: Problem (nfs ?) nach du heute Mittag
« Reply #7 on: 2018/01/30, 20:29:35 »
das ist echt strange - nach ca 10min kommt die Taskleiste, nach ca 45min konnte ich auf die NFS mounts zugreifen.

mal das Ende von dmesg & ifconfig nach einem reboot
Quote
[    2.900128] r8169 0000:03:00.0: firmware: direct-loading firmware rtl_nic/rtl8168f-1.fw
[    2.999969] r8169 0000:03:00.0 eth0: link down
[    2.999970] r8169 0000:03:00.0 eth0: link down
[    3.000030] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    3.027830] VBoxNetFlt: Successfully started.
[    3.029492] VBoxNetAdp: Successfully started.
[    3.031368] VBoxPciLinuxInit
[    3.032589] vboxpci: IOMMU not found (not registered)
[    5.344907] r8169 0000:03:00.0 eth0: link up
[    5.344950] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    5.385431] NET: Registered protocol family 17
[   92.968426] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[   92.968580] NFSD: starting 90-second grace period (net f00000a9)

[  100.533364] FS-Cache: Loaded
[  100.544955] FS-Cache: Netfs 'nfs' registered for caching
[  100.561635] NFS: Registering the id_resolver key type
[  100.561645] Key type id_resolver registered
[  100.561646] Key type id_legacy registered
[  315.903236] nfsd: last server has exited, flushing export cache
[  371.204004] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[  371.204015] NFSD: starting 90-second grace period (net f00000a9)
[  649.619544] nfsd: last server has exited, flushing export cache

root@siductionbox:/home/juergen# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.25  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fd00::a60:6eff:fe73:6eea  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::a60:6eff:fe73:6eea  prefixlen 64  scopeid 0x20<link>
        ether 08:60:6e:73:6e:ea  txqueuelen 1000  (Ethernet)
        RX packets 15021  bytes 14521342 (13.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9398  bytes 1054057 (1.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Gruss Juergen

Offline orinoco

  • User
  • Posts: 175
Re: Problem (nfs ?) nach du heute Mittag
« Reply #8 on: 2018/01/30, 20:37:37 »
Hi,

hier hat jemand ein ähnliches Problem mit Lösung. Vielleicht hilft es dir.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850464

Offline jure

  • User
  • Posts: 536
Re: Problem (nfs ?) nach du heute Mittag
« Reply #9 on: 2018/01/30, 21:33:33 »
danke für deine Recherche - aber bei mir steht da schon
Quote
Could you please test editing nfs-blkmap.service on your system
> and replace:
> PIDFile=/var/run/blkmapd.pid
> with:
> PIDFile=/run/blkmapd.pid

systemctl status nfs* bringt am Anfang
Quote
● nfs-blkmap.service - pNFS block layout mapping daemon
   Loaded: loaded (/lib/systemd/system/nfs-blkmap.service; disabled; vendor preset: enabled)
   Active: failed (Result: timeout) since Tue 2018-01-30 21:20:43 CET; 3min 51s ago
  Process: 20193 ExecStart=/usr/sbin/blkmapd $BLKMAPDARGS (code=exited, status=0/SUCCESS)

Jan 30 21:19:13 siductionbox systemd[1]: Starting pNFS block layout mapping daemon...
Jan 30 21:19:13 siductionbox systemd[1]: nfs-blkmap.service: Permission denied while opening PID file or unsafe symlink chain: /run/blkmapd.pid
Jan 30 21:19:13 siductionbox blkmapd[20194]: ^[[0;1;39mopen pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Jan 30 21:20:43 siductionbox systemd[1]: ^[[0;1;39m^[[0;1;39mnfs-blkmap.service: Start operation timed out. Terminating.
Jan 30 21:20:43 siductionbox blkmapd[20194]: ^[[0;1;39mexit on signal(15)
Jan 30 21:20:43 siductionbox systemd[1]: ^[[0;1;39m^[[0;1;39mnfs-blkmap.service: Failed with result 'timeout'.
Jan 30 21:20:43 siductionbox systemd[1]: ^[[0;1;39mFailed to start pNFS block layout mapping daemon

und ein systemctl restart nfs-blkmap.service auf der einen Konsole ergibt auf einer 2ten Konsole bei journalctl -f
Quote
Jan 30 21:27:39 siductionbox systemd[1]: Starting pNFS block layout mapping daemon...
Jan 30 21:27:39 siductionbox systemd[1]: nfs-blkmap.service: Permission denied while opening PID file or unsafe symlink chain: /run/blkmapd.pid
Jan 30 21:27:39 siductionbox blkmapd[22301]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory

"/run/rpc_pipefs/nfs/blocklayout failed" das gibt es auch nicht
Quote
ls -l /run/rpc_pipefs/nfs/
insgesamt 0
dr-xr-xr-x 2 root root 0 Jan 30 20:12 clntc
dr-xr-xr-x 2 root root 0 Jan 30 20:12 clntd

 :-[ :-[ - sorry wenn ich hier soviel texte, aber ich weiß nicht, wie das Problem sonst rüber bringen kann, geschweige denn beheben ....
« Last Edit: 2018/01/30, 21:45:07 by jure »
Gruss Juergen

Offline bluelupo

  • Global Moderator
  • User
  • *****
  • Posts: 2.066
    • BluelupoMe
Re: Problem (nfs ?) nach du heute Mittag
« Reply #10 on: 2018/01/30, 22:35:33 »
Hi jure,

wenn dein Netzwerk läuft kann es nur noch an der neuen systemd-Version liegen der laut deinem Anhang ja upgedatet wurde. Ich würde als Workaround erstmal alle NFS-Service dekativieren, damit du wieder vernüftig arbeiten kannst  und danach einen Bugreport verfassen.

Offline jure

  • User
  • Posts: 536
Re: Problem (nfs ?) nach du heute Mittag
« Reply #11 on: 2018/01/30, 23:18:41 »
NFS-Service dekativieren ist nicht so einfach / praktikabel, weil x Teile des Systems (dolphin ...) dauernd nach den nicht eingebundenen NFS-mounts suchen und hängen.

Ich verstehe z.B. nicht das hier bei https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850464 scheinbar auf genau die obigen Fehlermeldungen
Quote
nfs-blkmap.service: PID file /var/run/blkmapd.pid not readable (yet?) after start: No such file or directory
(ob das wirklich mein Problem ist ??) Bezug genommen wird und mit einer neuen Version von nfs-utils am 25 Mar 2017 gefixt wurde, ich aber keine nfs-utils habe und es die auch nicht (mehr) gibt

Code: [Select]
apt policy nfs-utils
N: Paket nfs-utils kann nicht gefunden werden.

root@siductionbox:/home/juergen# dpkg -l nfs*
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
         Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name                             Version               Architektur           Beschreibung
+++-================================-=====================-=====================-======================================================================
un  nfs-client                       <keine>               <keine>               (keine Beschreibung vorhanden)
ii  nfs-common                       1:1.3.4-2.1+b1        amd64                 NFS support files common to client and server
ii  nfs-kernel-server                1:1.3.4-2.1+b1        amd64                 support for NFS kernel server
un  nfs-server                       <keine>               <keine>               (keine Beschreibung vorhanden)
ii  nfs4-acl-tools                   0.3.3-3               amd64                 Commandline and GUI ACL utilities for the NFSv4 client
Gruss Juergen

Offline Geier0815

  • User
  • Posts: 496
Re: Problem (nfs ?) nach du heute Mittag
« Reply #12 on: 2018/01/31, 08:51:38 »
Du arbeitest mit automount oder machst Du mit fstab-Einträgen? Dein Rechner ist ein reiner nfs-client oder hast Du auch selber Freigaben per nfs laufen?

Deaktiviere als erstes mal deine "automatischen" nfs-mounts (egal ob automount oder fstab) und versuche dann, nach einem Neustart, die nfs-Freigaben per Konsole einzubinden. Keine schwindeligen Optionen, sondern so straight wie möglich. Nur damit wir sehen können ob es ein grundsätzliches Problem ist oder "nur" an deiner Konfiguration liegt.
Wenn Du selber keine Freigaben zur Verfügung stellst, deaktiviere auch den nfs-kernel-server-Dienst.
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

Offline jure

  • User
  • Posts: 536
Re: Problem (nfs ?) nach du heute Mittag
« Reply #13 on: 2018/01/31, 11:22:12 »
Danke für eure Hilfe !

Quote
Du arbeitest mit automount oder machst Du mit fstab-Einträgen? Dein Rechner ist ein reiner nfs-client oder hast Du auch selber Freigaben per nfs laufen?

die besagten Ordner auf dem NAS sind/waren über die fstab auf dem pc gemountet
Code: [Select]
192.168.2.60:/volume1/daten  /media/daten-nas   nfs  users,noauto,nofail,noatime,intr,soft,timeo=14,x-systemd.automount,x-systemd.device-timeout=10 0  0  automount habe ich nicht explizit eingerichtet ?

Die nfs mounts sollen möglichst nicht das NAS die ganze Zeit "wach halten" wenn nicht auf die eingebundenen Verzeichnisse auf dem pc zugegriffen wird - wenn sie wissen was ich meine ;-)

nfs-kernel-server ist nicht wichtig und erst mal deinstalliert.

Die NAS mounts in der fstab habe ich alle deaktiviert (#) und der pc startet und läuft wieder normal.
Per "mount -t nfs 192.168.2.60:/volume1/daten /media/daten-nas" kann ich Ordner vom NAS manuell auf dem pc einbinden/mounten. Der Zugriff darauf ist problemlos (zur Zeit ;-))

Bleibt die Frage was wurde denn über das du gestern geändert, das diese Auswirkungen hat.
Gruss Juergen

Offline jure

  • User
  • Posts: 536
Re: Problem (nfs ?) nach du heute Mittag
« Reply #14 on: 2018/01/31, 14:22:59 »
ich habe die Einträge in der fstab bzgl der NAS mounts geändert  (mit den Optionen werde ich noch ein wenig testen auto/noauto , timeout=xx ...)
Code: [Select]
192.168.2.60:/volume1/daten   /media/daten-nas    nfs4    auto,x-systemd.automount,x-systemd.device-timeout=5,defaults  0 0
und auf dem NAS NFSv4 Unterstützung aktiviert. Damit startet der ps wieder gewohnt zügig (zur Zeit ;-)) und die Taskleiste ist sofort vorhanden und benutzbar.
Irgendwas beim du gestern hatte also Einfluss auf NFS genommen ... denn ich hatte da seit geraumer Zeit nix geändert, weder am pc noch auf dem NAS.

systemclt status:
Code: [Select]
● siductionbox
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Wed 2018-01-31 14:08:15 CET; 8min ago

systemctl status nfs*
Code: [Select]
● nfs-client.target - NFS client services
   Loaded: loaded (/lib/systemd/system/nfs-client.target; enabled; vendor preset: enabled)
   Active: active since Wed 2018-01-31 14:08:15 CET; 9min ago

Jan 31 14:08:15 siductionbox systemd[1]: Reached target NFS client services.


Danke für eure Unterstützung
Gruss Juergen