Erst einmal herzlichen Dank, dass ihr euch mit auf die Fehlersuche macht! Ich habe nach der Anregung, die Protokolle des shre Servers auszwerten auch noch ein paar andere Sachen probiert bis hin zu einer Aktualisierung mit pacaman -Suy. Hat leider alles nichts gebracht. Im folgenden etliche Protokollauszüge und Ergebnisse von Netzwerkscans:
Server-Protokoll über eine Anmeldung von einem Rechner (Desktop, Ubuntu 14.04), von dem das mounten klappt. Die Share steht anschließend auf dem Client zur Verfügung:
svc: 192.168.178.37, port=689: unknown version (4 for prog 100003, nfsd)
svc: 192.168.178.37, port=665: unknown version (4 for prog 100003, nfsd)
svc: 192.168.178.37, port=917: unknown version (4 for prog 100003, nfsd)
svc: 192.168.178.37, port=962: unknown version (4 for prog 100003, nfsd)
svc: 192.168.178.37, port=766: unknown version (4 for prog 100003, nfsd)
svc: 192.168.178.37, port=855: unknown version (4 for prog 100003, nfsd)
Server-Protokoll von dem Anmeldeversuch des Raspi, nichts wird gemountet:
svc: 192.168.178.21, port=887: unknown version (4 for prog 100003, nfsd)
svc: 192.168.178.21, port=765: unknown version (4 for prog 100003, nfsd)
svc: 192.168.178.21, port=681: unknown version (4 for prog 100003, nfsd)
svc: 192.168.178.21, port=55687: unknown version (-1225759528 for prog 100003, nfsd)
svc: 192.168.178.21, port=51278: unknown version (-1225759528 for prog 100003, nfsd)
Ergebnis eines Netzwerkscans mit dem Befehl:
nmap -A -T4 192.168.178.0/24
Dieser Raspi funktioniert als nfs-Client und ist korrekt mit den shares von 192.168.178.11 verbunden:
Nmap scan report for alarmpi (192.168.178.19)
Host is up (0.021s latency).
Not shown: 998 closed ports
PORT STATE SERVICE VERSION
22/tcp open ssh OpenSSH 6.7 (protocol 2.0)
|_ssh-hostkey: ERROR: Script execution failed (use -d to debug)
111/tcp open rpcbind 2-4 (RPC #100000)
| rpcinfo:
| program version port/proto service
| 100000 2,3,4 111/tcp rpcbind
| 100000 2,3,4 111/udp rpcbind
| 100021 1,3,4 32892/tcp nlockmgr
| 100021 1,3,4 34521/udp nlockmgr
| 100024 1 57313/udp status
|_ 100024 1 59592/tcp status
Dies ist der Raspi, der NICHT als nfs-Client mounten kann aber als nfs-Server funktioniert:
Nmap scan report for raspi2 (192.168.178.21)
Host is up (0.00055s latency).
Not shown: 997 closed ports
PORT STATE SERVICE VERSION
22/tcp open ssh OpenSSH 6.7 (protocol 2.0)
|_ssh-hostkey: ERROR: Script execution failed (use -d to debug)
111/tcp open rpcbind 2-4 (RPC #100000)
| rpcinfo:
| program version port/proto service
| 100000 2,3,4 111/tcp rpcbind
| 100000 2,3,4 111/udp rpcbind
| 100003 3,4 2049/tcp nfs
| 100003 3,4 2049/udp nfs
| 100005 1,2,3 20048/tcp mountd
| 100005 1,2,3 20048/udp mountd
| 100021 1,3,4 34834/tcp nlockmgr
| 100021 1,3,4 60398/udp nlockmgr
| 100024 1 50681/tcp status
| 100024 1 53178/udp status
| 100227 3 2049/tcp nfs_acl
|_ 100227 3 2049/udp nfs_acl
2049/tcp open nfs 3-4 (RPC #100003)
Dies ist die Ressource (NAS), die von .19 gemountet wird aber von .21 nicht:
Nmap scan report for MyBookLive (192.168.178.11)
Host is up (0.052s latency).
Not shown: 987 closed ports
PORT STATE SERVICE VERSION
21/tcp open ftp vsftpd 2.0.8 or later
22/tcp open ssh OpenSSH 5.1p1 Debian 5 (protocol 2.0)
| ssh-hostkey: 1024 b3:f5:93:40:09:2a:74:e0:3e:01:73:86:29:24:36:27 (DSA)
|_2048 93:62:c5:80:01:dc:48:0d:d5:99:03:20:91:1e:6c:3b (RSA)
80/tcp open http Apache httpd
| http-methods: Potentially risky methods: TRACE
|_See http://nmap.org/nsedoc/scripts/http-methods.html
|_http-title: Site doesn't have a title (text/html).
111/tcp open rpcbind 2 (RPC #100000)
| rpcinfo:
| program version port/proto service
| 100000 2 111/tcp rpcbind
| 100000 2 111/udp rpcbind
| 100003 2,3 2049/tcp nfs
| 100003 2,3 2049/udp nfs
| 100005 1,2,3 50604/tcp mountd
| 100005 1,2,3 53469/udp mountd
| 100021 1,3,4 36539/tcp nlockmgr
| 100021 1,3,4 55428/udp nlockmgr
| 100024 1 40174/tcp status
|_ 100024 1 41728/udp status
139/tcp open netbios-ssn Samba smbd 3.X (workgroup: WORKGROUP)
443/tcp open ssl/http Apache httpd
| http-methods: Potentially risky methods: TRACE
|_See http://nmap.org/nsedoc/scripts/http-methods.html
|_http-title: 404 Not Found
| ssl-cert: Subject: commonName=*.device133549.wd2go.com/organizationName=Western Digital/stateOrProvinceName=California/countryName=US
| Not valid before: 2012-02-24T07:34:19+00:00
|_Not valid after: 2022-02-24T07:34:19+00:00
|_ssl-date: 2015-02-25T08:17:03+00:00; -2s from local time.
445/tcp open netbios-ssn Samba smbd 3.X (workgroup: WORKGROUP)
548/tcp open afp Netatalk 2.2.3 (name: MyBookLive-; protocol 3.3)
| afp-serverinfo:
| | Server Flags: 0x8f7d
| | Super Client: Yes
| | UUIDs: Yes
| | UTF8 Server Name: Yes
| | Open Directory: Yes
| | Reconnect: No
| | Server Notifications: Yes
| | TCP/IP: Yes
| | Server Signature: Yes
| | ServerMessages: Yes
| | Password Saving Prohibited: Yes
| | Password Changing: No
| |_ Copy File: Yes
| Server Name: MyBookLive-
| Machine Type: Netatalk2.2.3
| AFP Versions: AFP2.2, AFPX03, AFP3.1, AFP3.2, AFP3.3
| UAMs: DHX2, Cleartxt Passwrd, No User Authent
| Server Signature: 544d3030393061396231613864350000
| Network Address 1: 192.168.178.11
|_ UTF8 Server Name: MyBookLive-
873/tcp open rsync (protocol version 30)
2049/tcp open nfs 2-3 (RPC #100003)
| rpcinfo:
| program version port/proto service
| 100000 2 111/tcp rpcbind
| 100000 2 111/udp rpcbind
| 100003 2,3 2049/tcp nfs
| 100003 2,3 2049/udp nfs
| 100005 1,2,3 50604/tcp mountd
| 100005 1,2,3 53469/udp mountd
| 100021 1,3,4 36539/tcp nlockmgr
| 100021 1,3,4 55428/udp nlockmgr
| 100024 1 40174/tcp status
|_ 100024 1 41728/udp status
3689/tcp open daap forked-daapd
9000/tcp open upnp TwonkyMedia UPnP (UPnP 1.0; pvConnect SDK 1.0; Twonky SDK 1.1)
49152/tcp open upnp Portable SDK for UPnP devices 1.6.6 (Linux 2.6.32.11-svn70860; UPnP 1.0)
Service Info: OSs: Linux, Unix; CPE: cpe:/o:linux:linux_kernel, cpe:/o:linux:linux_kernel:2, cpe:/o:linux:linux_kernel:2.6.32.11-svn70860
Host script results:
|_nbstat: NetBIOS name: MYBOOKLIVE, NetBIOS user: <unknown>, NetBIOS MAC: <unknown>
| smb-os-discovery:
| OS: Unix (Samba 3.6.5)
| Computer name: MyBookLive
| NetBIOS computer name:
| Domain name:
FQDN: MyBookLive
|_ System time: 2015-02-25T09:17:08+01:00
| smb-security-mode:
| Account that was used for smb scripts: guest
| User-level authentication
| SMB Security: Challenge/response passwords supported
|_ Message signing disabled (dangerous, but default)
|_smbv2-enabled: Server supports SMBv2 protocol
Alle Türen am NAS stehen weit offen und , wie bereits geschrieben, kann ich die Samba-Ressource von dem Raspi .21 aus einbinden.
Alles folgende ist von dem Client (.21), der nicht mounten will:
Ergebnis von systemctl status rpc-statd.service:
* rpc-statd.service - NFS status monitor for NFSv2/3 locking.
Loaded: loaded (/usr/lib/systemd/system/rpc-statd.service; static; vendor preset: disabled)
Active: active (running) since Wed 2015-02-25 09:08:37 UTC; 2min 11s ago
Process: 185 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=0/SUCCESS)
Main PID: 186 (rpc.statd)
CGroup: /system.slice/rpc-statd.service
`-186 /usr/sbin/rpc.statd --no-notify
Feb 25 09:08:36 alarmpi rpc.statd[186]: Version 1.3.2 starting
Feb 25 09:08:36 alarmpi rpc.statd[186]: Flags: TI-RPC
Feb 25 09:08:36 alarmpi rpc.statd[186]: Running as root. chown /var/lib/nfs to choose different user
Feb 25 09:08:37 alarmpi systemd[1]: Started NFS status monitor for NFSv2/3 locking..
Ergebnis von systemctl status rpcbind.service:
* rpcbind.service - RPC bind service
Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; indirect; vendor preset: disabled)
Active: active (running) since Wed 2015-02-25 09:07:27 UTC; 6min ago
Process: 173 ExecStart=/usr/bin/rpcbind -w ${RPCBIND_ARGS} (code=exited, status=0/SUCCESS)
Main PID: 174 (rpcbind)
CGroup: /system.slice/rpcbind.service
`-174 /usr/bin/rpcbind -w
Feb 25 09:07:27 alarmpi systemd[1]: Started RPC bind service.
Ergebns von systemctl rpcbind.target:
* rpcbind.target - RPC Port Mapper
Loaded: loaded (/usr/lib/systemd/system/rpcbind.target; static; vendor preset: disabled)
Active: active since Wed 2015-02-25 09:08:36 UTC; 6min ago
Docs: man:systemd.special(7)
Feb 25 09:08:36 alarmpi systemd[1]: Starting RPC Port Mapper.
Feb 25 09:08:36 alarmpi systemd[1]: Reached target RPC Port Mapper.
Ergebnis von systemctl status rpcbind.socket:
* rpcbind.socket - RPCbind Server Activation Socket
Loaded: loaded (/usr/lib/systemd/system/rpcbind.socket; enabled; vendor preset: disabled)
Active: active (running) since Wed 2015-02-25 09:01:48 UTC; 14min ago
Listen: /var/run/rpcbind.sock (Stream)
Feb 25 09:01:48 alarmpi systemd[1]: Starting RPCbind Server Activation Socket.
Feb 25 09:01:48 alarmpi systemd[1]: Listening on RPCbind Server Activation Socket.
Alle rpc* beinhaltenden Meldungen aus dem Journal seit dem letzen Bootvorgang. Vorher hatte ich noch ein pacman -Suy durchgeführt. Also aktueller geht's wirklich nicht:
Jan 01 00:00:07 alarmpi kernel: RPC: Registered named UNIX socket transport module.
Jan 01 00:00:07 alarmpi kernel: RPC: Registered udp transport module.
Jan 01 00:00:07 alarmpi kernel: RPC: Registered tcp transport module.
Jan 01 00:00:07 alarmpi kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 01 00:00:08 alarmpi systemd[1]: Mounting RPC Pipe File System...
Jan 01 00:00:08 alarmpi systemd[1]: Mounted RPC Pipe File System.
Feb 25 09:52:38 alarmpi systemd[1]: Starting RPCbind Server Activation Socket.
Feb 25 09:52:38 alarmpi systemd[1]: Listening on RPCbind Server Activation Socket.
Feb 25 09:52:38 alarmpi systemd[1]: Started Kernel Module supporting RPCSEC_GSS.
Feb 25 09:52:38 alarmpi systemd[1]: Started RPC security service for NFS client and server.
Feb 25 09:52:38 alarmpi systemd[1]: Started RPC security service for NFS server.
Feb 25 09:55:35 alarmpi systemd[1]: Starting RPC Port Mapper.
Feb 25 09:55:35 alarmpi systemd[1]: Reached target RPC Port Mapper.
Feb 25 09:55:35 alarmpi rpc.statd[184]: Version 1.3.2 starting
Feb 25 09:55:35 alarmpi rpc.statd[184]: Flags: TI-RPC
Feb 25 09:55:36 alarmpi systemd[1]: Starting RPC bind service...
Feb 25 09:55:36 alarmpi systemd[1]: Started RPC bind service.
Feb 25 09:55:36 alarmpi rpc.statd[184]: Running as root. chown /var/lib/nfs to choose different user
Alle nfs* beinhaltenden Meldungen seit dem letzen booten:
Jan 01 00:00:07 alarmpi kernel: TCP: Hash tables configured (established 4096 bind 4096)
Jan 01 00:00:07 alarmpi kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 01 00:00:07 alarmpi kernel: FS-Cache: Netfs 'nfs' registered for caching
Jan 01 00:00:07 alarmpi kernel: NFS: Registering the id_resolver key type
Jan 01 00:00:07 alarmpi kernel: nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Jan 01 00:00:08 alarmpi systemd[1]: Starting PNFS blkmaping enablement..
Jan 01 00:00:08 alarmpi systemd[1]: Reached target PNFS blkmaping enablement..
Jan 01 00:00:08 alarmpi systemd[1]: Mounting Configuration File System...
Jan 01 00:00:08 alarmpi systemd-modules-load[79]: Module 'nfs' is builtin
Jan 01 00:00:08 alarmpi systemd[1]: Starting pNFS block layout mapping daemon...
Jan 01 00:00:08 alarmpi systemd[1]: Mounted Configuration File System.
Jan 01 00:00:09 alarmpi systemd[1]: Started pNFS block layout mapping daemon.
Feb 25 09:52:38 alarmpi systemd[1]: Starting Preprocess NFS configuration...
Feb 25 09:52:38 alarmpi systemd[1]: Started Preprocess NFS configuration.
Feb 25 09:52:38 alarmpi systemd[1]: Started RPC security service for NFS client and server.
Feb 25 09:52:38 alarmpi systemd[1]: Started RPC security service for NFS server.
Feb 25 09:52:38 alarmpi kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 25 09:52:38 alarmpi systemd-networkd[149]: eth0 : link configured
Feb 25 09:52:39 alarmpi systemd[1]: Starting Notify NFS peers of a restart...
Feb 25 09:52:39 alarmpi systemd[1]: Started Notify NFS peers of a restart.
Feb 25 09:52:39 alarmpi systemd[1]: Starting NFS client services.
Feb 25 09:52:39 alarmpi systemd[1]: Reached target NFS client services.
Feb 25 09:52:40 alarmpi kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 25 09:52:40 alarmpi systemd-timesyncd[144]: Network configuration changed, trying to establish connection.
Feb 25 09:52:42 alarmpi systemd-timesyncd[144]: Network configuration changed, trying to establish connection.
Feb 25 09:55:35 alarmpi systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
Feb 25 09:55:36 alarmpi rpc.statd[184]: Running as root. chown /var/lib/nfs to choose different user
Feb 25 09:55:36 alarmpi systemd[1]: Started NFS status monitor for NFSv2/3 locking.
Und zum Schluss noch eine Ausgabe von
rpcinfo -p localhost
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100227 3 tcp 2049 nfs_acl
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100227 3 udp 2049 nfs_acl
100021 1 udp 60398 nlockmgr
100021 3 udp 60398 nlockmgr
100021 4 udp 60398 nlockmgr
100021 1 tcp 34834 nlockmgr
100021 3 tcp 34834 nlockmgr
100021 4 tcp 34834 nlockmgr
100024 1 udp 55839 status
100024 1 tcp 39392 status
bei inzwischen abgeschaltetem nfs-server. Vielleicht ist da ja eine Information zwischen, die weiter hilft..