On 05/02/2020 23.36, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-05-20 17:30]:
On 05/02/2020 23.17, Patrick Shanahan wrote:
* Carlos E. R. <> [02-05-20 16:36]:
On 05/02/2020 19.33, Patrick Shanahan wrote:
* Carlos E. R. <> [02-05-20 12:18]:
On 05/02/2020 16.44, Patrick Shanahan wrote:
...
Maybe portmap is not running.
there is no service named portmap
I don't know or remember the actual name of the service.
client: ~ # rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper
Then it is running.
server: ~ # rpcinfo -p 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 100024 1 udp 59771 status 100024 1 tcp 36477 status 100005 1 udp 38791 mountd 100005 1 tcp 55147 mountd 100005 2 udp 40803 mountd 100005 2 tcp 35003 mountd 100005 3 udp 35077 mountd 100005 3 tcp 35217 mountd
did you check apparmor, on both machines? aa-logprof.
yes, no listing for portmap or rpc* on either.
Not just that, but anything.
yes, for locate which should not be relevant.
Er... I don't remember this instant for sure, but I think you have to tell AA what to do on whatever (locate this time) to see if there are more issues left after it.
But I do have nfs mounts on both machines and exports from the server open on other machines.
~ # zypper se -sd portmap Loading repository data... Reading installed packages...
S | Name | Type | Version | Arch | Repository
--+---------+------------+------------+--------+------------------------
i | rpcbind | package | 1.2.5-3.2 | x86_64 | openSUSE-Tumbleweed OSS
v | rpcbind | package | 1.2.5-3.2 | i586 | openSUSE-Tumbleweed OSS
server: ~ # systemctl status rpcbind ● rpcbind.service - RPC Bind Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2020-02-04 09:56:01 EST; 1 day 7h ago
Ok.
TriggeredBy: ● rpcbind.socket Docs: man:rpcbind(8) Main PID: 1040 (rpcbind) Tasks: 1 (limit: 4915) Memory: 1.9M CGroup: /system.slice/rpcbind.service └─1040 /sbin/rpcbind -w -f
Feb 04 09:56:01 crash systemd[1]: Starting RPC Bind... Feb 04 09:56:01 crash systemd[1]: Started RPC Bind.
client: ~ # systemctl status rpcbind ● rpcbind.service - RPC Bind Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2020-02-04 17:30:00 EST; 23h ago
Ok
TriggeredBy: ● rpcbind.socket Docs: man:rpcbind(8) Main PID: 1031 (rpcbind) Tasks: 1 (limit: 4530) Memory: 1.0M CGroup: /system.slice/rpcbind.service └─1031 /sbin/rpcbind -w -f
Feb 04 17:29:58 crash2 systemd[1]: Starting RPC Bind... Feb 04 17:30:00 crash2 systemd[1]: Started RPC Bind.
And the firewall?
why would the firewall stop one nfs mount and pass another from the same server?
Because we are grasping at straws here? :-D IIRC, the portmapper job has to coordinate with the firewall to open the negotiated port.
But, I previously tested with both server and client firewalls off and still no mount on either subject client.
Ok... I'm out of ideas. Reboot? -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)