* Carlos E. R. <robin.listas@telefonica.net> [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:
I have two boxes where I merged the mentioned rpm{new,save} files and can no longer mount one of three nfs drives.
And two boxes where I did not merge the mentioned rpm{new,save} files and can mount all of the nfs drives.
It is not blind merging you need to do. You have to copy to your working config files the new features or changes in the rpmnew file, while keeping the old parts that you still need, and possibly make edit changes as appropriate.
yes, meld file.rpmnew file.rpm merged new, non-conflicting items
If what you get is an rpmsave the procedure is inverted: copy to the actual file, which is new, the old lines that you still need, possibly after checking in the man that they are still correct; if not, edit them.
My routine is:
zypper dup rpmconfigcheck
now for every resultingline:
cp /etc/actual_file /some_backup/etc/actual_file cp /etc/rpmsomething_file /some_backup/etc/rpmsomething_file meld /etc/actual_file /etc/rpmsomething_file rm /etc/rpmsomething_file
Most often the changes are cosmetic.
yes, but I still cannot one of the nfs drives on two boxes, but can on one box where the rpm files were merged/updated and can on one where I have not yet done the merge/update. Makes no sense.
~ # mount -vvv -t auto 192.168.1.10:/data /mnt/nfs/data mount.nfs: timeout set for Wed Feb 5 13:09:12 2020 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.10,clientaddr=192.168.1.8' mount.nfs: mount(2): Connection refused mount.nfs: trying text-based options 'addr=192.168.1.10' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.10,clientaddr=192.168.1.8' mount.nfs: mount(2): Connection refused mount.nfs: trying text-based options 'addr=192.168.1.10' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered
Maybe portmap is not running.
there is no service named portmap client: ~ # 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 40710 status 100024 1 tcp 49619 status 100005 1 udp 58700 mountd 100005 1 tcp 45657 mountd 100005 2 udp 44972 mountd 100005 2 tcp 54895 mountd 100005 3 udp 50609 mountd 100005 3 tcp 58619 mountd 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. 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 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 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. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org