Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: Problems with nfs server after upgrade to Leap 15.0

  1. #1
    Join Date
    Apr 2011
    Location
    Stockholm
    Posts
    81

    Default Problems with nfs server after upgrade to Leap 15.0

    Hi,

    Leap 42.3 used to run my nfs server without problem but ever since the upgrade this is broken. After boot I get this:

    Code:
    sudo systemctl status nfsserver
    ● nfsserver.service - Alias for NFS server
       Loaded: loaded (/usr/lib/systemd/system/nfsserver.service; enabled; vendor preset: disabled)
       Active: active (exited) since Tue 2019-08-06 18:29:46 CEST; 22h ago
     Main PID: 1023 (code=exited, status=0/SUCCESS)
        Tasks: 0 (limit: 4915)
       CGroup: /system.slice/nfsserver.service
    
    Aug 06 18:29:45 k2003734 systemd[1]: Starting Alias for NFS server...
    Aug 06 18:29:46 k2003734 systemd[1]: Started Alias for NFS server.
    gostal@k2003734:~> showmount -e
    Export list for k2003734.win.foi.se:
    and restarting it makes no difference. However, if I do first:
    Code:
    sudo systemctl enable nfsserver
    then I get:
    Code:
    ● nfsserver.service - Alias for NFS server
       Loaded: loaded (/usr/lib/systemd/system/nfsserver.service; enabled; vendor preset: disabled)
       Active: active (exited) since Wed 2019-08-07 16:43:57 CEST; 10min ago
      Process: 23444 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
     Main PID: 23444 (code=exited, status=0/SUCCESS)
        Tasks: 0 (limit: 4915)
       CGroup: /system.slice/nfsserver.service
    
    Aug 07 16:43:57 k2003734.win.foi.se systemd[1]: Starting Alias for NFS server...
    Aug 07 16:43:57 k2003734.win.foi.se systemd[1]: Started Alias for NFS server.
    gostal@k2003734:~> showmount -e
    Export list for k2003734.win.foi.se:
    /usr/local   ki003685.win.foi.se
    /disk2       ki003685.win.foi.se
    /opt         ki003685.win.foi.se
    /home/gostal ki003685.win.foi.se
    so now my shares are exported. There are other symptoms: using the nfs-server module in yast the firewall part says:
    Code:
    Some firewalld services are not available: 
    - nfs-kernel-server (Not available.)
    So I fire up the yast firewall module which then says:
    Code:
    Current status: stopped
    although Start During System Boot is marked.
    Starting the firewall makes no change to the nfs-server module which still complains that nfs-kernel-server is not available. The package is installed, however,
    Code:
    sudo zypper se -i nfs-kernel-server
    [sudo] password for gostal: 
    Loading repository data...
    Warning: Repository 'update-nonoss' appears to be outdated. Consider using a different mirror or server.
    Reading installed packages...
    
    S | Name              | Summary                           | Type   
    --+-------------------+-----------------------------------+--------
    i | nfs-kernel-server | Support Utilities for Kernel nfsd | package
    What is missing in all this? Please help!

    There is a Tumbleweed thread with like symptoms but unfortunately not concluded.

    Cheers,
    gostal

  2. #2
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,514

    Question Re: Problems with nfs server after upgrade to Leap 15.0

    @gostal:

    Is the systemd “nfs-server.service” enabled?
    • The systemd “nfsserver.service” is an alias for the “nfs-server.service” …

    The status of the “nfs-server.service” should be like this:
    Code:
     # systemctl status nfs-server.service nfsserver.service
    ● nfs-server.service - NFS server and services
       Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled)
      Drop-In: /usr/lib/systemd/system/nfs-server.service.d
               └─nfsserver.conf, options.conf
            /run/systemd/generator/nfs-server.service.d
               └─order-with-mounts.conf
       Active: active (exited) since Wed 2019-08-07 09:16:10 CEST; 9h ago
      Process: 2300 ExecStart=/usr/sbin/rpc.nfsd $NFSD_OPTIONS (code=exited, status=0/SUCCESS)
      Process: 2250 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
     Main PID: 2300 (code=exited, status=0/SUCCESS)
        Tasks: 0 (limit: 4915)
       CGroup: /system.slice/nfs-server.service
    
    Aug 07 09:16:10 xxx systemd[1]: Starting NFS server and services...
    Aug 07 09:16:10 xxx systemd[1]: Started NFS server and services.
     #
    Is the systemd “firewalld.service” enabled?

    The status should be as follows:
    Code:
     # systemctl status firewalld.service
    ● firewalld.service - firewalld - dynamic firewall daemon
       Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled)
       Active: active (running) since Wed 2019-08-07 09:15:58 CEST; 9h ago
         Docs: man:firewalld(1)
     Main PID: 1083 (firewalld)
        Tasks: 2 (limit: 4915)
       CGroup: /system.slice/firewalld.service
               └─1083 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork --nopid
    
    Aug 07 09:15:57 xxx systemd[1]: Starting firewalld - dynamic firewall daemon...
    Aug 07 09:15:58 xxx systemd[1]: Started firewalld - dynamic firewall daemon.
     #
    The following Firewall daemon packages should be installed:
    • firewalld, firewalld-lang, python3-firewall, yast2-firewall, firewall-config, firewall-macros.

    The previous SuSE Firewall package should have been removed: SuSEfirewall2.

  3. #3
    Join Date
    Apr 2011
    Location
    Stockholm
    Posts
    81

    Default Re: Problems with nfs server after upgrade to Leap 15.0

    Quote Originally Posted by dcurtisfra View Post
    @gostal:

    Is the systemd “nfs-server.service” enabled?
    Is the systemd “firewalld.service” enabled?

    The following Firewall daemon packages should be installed:
    • firewalld, firewalld-lang, python3-firewall, yast2-firewall, firewall-config, firewall-macros.

    The previous SuSE Firewall package should have been removed: SuSEfirewall2.
    @dcurtisfra: Thanks for responding!

    Packages: firewall-config was not installed. SuSEfirewall2 was still installed. Fixed those.

    Rebooted

    No, nfs-server.service is not enabled. I get this:
    Code:
    systemctl status nfs-server
    ● nfs-server.service - NFS server and services
       Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; disabled; vendor preset: disabled)
      Drop-In: /usr/lib/systemd/system/nfs-server.service.d
               └─nfsserver.conf, options.conf
       Active: active (exited) since Thu 2019-08-08 11:07:51 CEST; 6min ago
     Main PID: 1284 (code=exited, status=0/SUCCESS)
        Tasks: 0 (limit: 4915)
       CGroup: /system.slice/nfs-server.service
    
    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    Yes, firewalld is enabled:
    Code:
    systemctl status firewalld
    ● firewalld.service - firewalld - dynamic firewall daemon
       Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled)
       Active: active (running) since Thu 2019-08-08 11:07:51 CEST; 6min ago
         Docs: man:firewalld(1)
     Main PID: 972 (firewalld)
        Tasks: 2 (limit: 4915)
       CGroup: /system.slice/firewalld.service
               └─972 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork --nopid
    
    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    Still the yast2-nfs-server module says that nfs-kernel-server is not available.

    I then enabled nfs-server:
    Code:
    sudo systemctl enable nfs-server
    [sudo] password for gostal: 
    Created symlink /etc/systemd/system/multi-user.target.wants/nfs-server.service → /usr/lib/systemd/system/nfs-server.service.
    Perhaps now it will start enabled. Update after next reboot.

    Cheers,
    gostal

  4. #4
    Join Date
    Apr 2011
    Location
    Stockholm
    Posts
    81

    Default Re: Problems with nfs server after upgrade to Leap 15.0

    Yes, now nfs-server is enabled after boot but still my exports do not show until after restart of nfs-server:
    Code:
    systemctl status nfs-server
    ● nfs-server.service - NFS server and services
       Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled)
      Drop-In: /usr/lib/systemd/system/nfs-server.service.d
               └─nfsserver.conf, options.conf
       Active: active (exited) since Thu 2019-08-08 11:39:02 CEST; 2min 41s ago
     Main PID: 1339 (code=exited, status=0/SUCCESS)
        Tasks: 0 (limit: 4915)
       CGroup: /system.slice/nfs-server.service
    
    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    gostal@k2003734:~> showmount -e
    Export list for k2003734.win.foi.se:
    gostal@k2003734:~> sudo systemctl restart nfs-server
    [sudo] password for gostal: 
    gostal@k2003734:~> showmount -e
    Export list for k2003734.win.foi.se:
    /usr/local   ki003685.win.foi.se
    /disk2       ki003685.win.foi.se
    /opt         ki003685.win.foi.se
    /home/gostal ki003685.win.foi.se
    And still:

    - nfs-kernel-server (Not available.)

    from yast2-nfs-server module.

    Cheers,
    gostal

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,267
    Blog Entries
    1

    Default Re: Problems with nfs server after upgrade to Leap 15.0

    Quote Originally Posted by gostal View Post
    Yes, now nfs-server is enabled after boot but still my exports do not show until after restart of nfs-server:
    I'm speculating that this might happen if the network is not active when nfs-server is started perhaps? Which network management framework are you using (NetworkManager or wicked)?
    openSUSE Leap 15.0; KDE Plasma 5

  6. #6
    Join Date
    Apr 2011
    Location
    Stockholm
    Posts
    81

    Default Re: Problems with nfs server after upgrade to Leap 15.0

    Quote Originally Posted by deano_ferrari View Post
    I'm speculating that this might happen if the network is not active when nfs-server is started perhaps? Which network management framework are you using (NetworkManager or wicked)?
    Judging from systemctl status output NetworkManager is used:
    Code:
    ~> systemctl status wickedd
    ● wickedd.service - wicked network management service daemon
       Loaded: loaded (/usr/lib/systemd/system/wickedd.service; indirect; vendor preset: disabled)
       Active: inactive (dead)
    ~> systemctl status NetworkManager
    ● NetworkManager.service - Network Manager
       Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
      Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
               └─NetworkManager-ovs.conf
       Active: active (running) since Thu 2019-08-08 11:39:02 CEST; 4h 31min ago
         Docs: man:NetworkManager(8)
     Main PID: 1252 (NetworkManager)
        Tasks: 4 (limit: 4915)
       CGroup: /system.slice/NetworkManager.service
               ├─1252 /usr/sbin/NetworkManager --no-daemon
               └─1890 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-eth0.pid ->
    
    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    What file is determining the order in which services are loaded?

    /gostal

  7. #7
    Join Date
    Apr 2011
    Location
    Stockholm
    Posts
    81

    Default Re: Problems with nfs server after upgrade to Leap 15.0

    Yes, nfs-server starting before network is up seems to be the problem. Running now systemctl status with sudo shows the journal and the PID. Although the main PID of NetworkManager is 1177 the PID of dhcp-client is 1819 which is larger than the PID of nfs-server which is 1251. Also the time stamps of the journal entries are later for NetworkManager than for nfs-server:

    Code:
    sudo systemctl status nfs-server
    ● nfs-server.service - NFS server and services
       Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled)
      Drop-In: /usr/lib/systemd/system/nfs-server.service.d
               └─nfsserver.conf, options.conf
       Active: active (exited) since Thu 2019-08-08 16:37:01 CEST; 8min ago
     Main PID: 1251 (code=exited, status=0/SUCCESS)
        Tasks: 0 (limit: 4915)
       CGroup: /system.slice/nfs-server.service
    
    Aug 08 16:37:01 k2003734 systemd[1]: Starting NFS server and services...
    Aug 08 16:37:01 k2003734 exportfs[1245]: exportfs: Failed to resolve ki003685
    Aug 08 16:37:01 k2003734 exportfs[1245]: exportfs: Failed to resolve ki003685
    Aug 08 16:37:01 k2003734 exportfs[1245]: exportfs: Failed to resolve ki003685
    Aug 08 16:37:01 k2003734 exportfs[1245]: exportfs: Failed to resolve ki003685
    Aug 08 16:37:01 k2003734 exportfs[1245]: exportfs: Failed to resolve ki003685
    Aug 08 16:37:01 k2003734 exportfs[1245]: exportfs: Failed to resolve ki003685
    Aug 08 16:37:01 k2003734 exportfs[1245]: exportfs: Failed to resolve ki003685
    Aug 08 16:37:01 k2003734 systemd[1]: Started NFS server and services.
    ~> sudo systemctl status NetworkManager
    ● NetworkManager.service - Network Manager
       Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
      Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
               └─NetworkManager-ovs.conf
       Active: active (running) since Thu 2019-08-08 16:37:01 CEST; 18min ago
         Docs: man:NetworkManager(8)
     Main PID: 1177 (NetworkManager)
        Tasks: 4 (limit: 4915)
       CGroup: /system.slice/NetworkManager.service
               ├─1177 /usr/sbin/NetworkManager --no-daemon
               └─1819 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-eth0.pid -lf /var/lib/NetworkManager/dhclient-f11eadde-66ce-3934-bfd4-359f9e24a217-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0
    
    Aug 08 16:37:06 k2003734 NetworkManager[1177]: <info>  [1565275026.7457] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
    Aug 08 16:37:06 k2003734 NetworkManager[1177]: <info>  [1565275026.7462] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
    Aug 08 16:37:06 k2003734 NetworkManager[1177]: <info>  [1565275026.7464] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
    Aug 08 16:37:06 k2003734 NetworkManager[1177]: <info>  [1565275026.7465] manager: NetworkManager state is now CONNECTED_LOCAL
    Aug 08 16:37:06 k2003734 NetworkManager[1177]: <info>  [1565275026.7548] manager: NetworkManager state is now CONNECTED_SITE
    Aug 08 16:37:06 k2003734 NetworkManager[1177]: <info>  [1565275026.7549] policy: set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS
    Aug 08 16:37:06 k2003734.win.foi.se NetworkManager[1177]: <info>  [1565275026.7549] policy: set-hostname: set hostname to 'k2003734.win.foi.se' (from system configuration)
    Aug 08 16:37:06 k2003734.win.foi.se NetworkManager[1177]: <info>  [1565275026.8663] device (eth0): Activation: successful, device activated.
    Aug 08 16:37:06 k2003734.win.foi.se NetworkManager[1177]: <info>  [1565275026.8669] manager: startup complete
    How do I set this right?

  8. #8
    Join Date
    Apr 2011
    Location
    Stockholm
    Posts
    81

    Default Re: Problems with nfs server after upgrade to Leap 15.0

    The firewall is also blocking my shares from the other computer. I stopped it and my shares showed up on the other computer. Then I did:
    Code:
    sudo firewall-cmd --add-service=nfs --permanent
    FirewallD is not running
    gostal@k2003734:~> sudo systemctl start firewalld
    gostal@k2003734:~> sudo firewall-cmd --add-service=nfs --permanent
    Warning: ALREADY_ENABLED: nfs
    success
    gostal@k2003734:~> sudo firewall-cmd --reload
    success
    and the shares still show on the other computer but I suspect this won't survive reboot. I suspect this has to do with the nfs-kernel-server not available in yast2-nfs-server module but what shall I do about it?

    No, it doesn't even survive stopping and restarting nfs-server and then the only way to make the shares available is to stop firewalld and then it doesn't matter if the firewall is running or not. How do I fix these things?

  9. #9
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,514

    Default Re: Problems with nfs server after upgrade to Leap 15.0

    @gostal:

    For the case of a normal private “at home” LAN or WLAN, behind a DSL-Router with a built-in Firewall, the default Firewall zone for the Ethernet and WLAN interfaces can be “trusted” – if your LAN or WLAN interfaces have a direct connection to the “real” Internet, you'll have to come up to speed with the Firewall zone settings …
    Code:
     # firewall-cmd --get-default-zone
    trusted
     #
    Currently, with Leap 15.1, don't try this with a “normal” user – ‘sudo’ is currently broken but, it'll be repaired soon …

  10. #10
    Join Date
    Apr 2011
    Location
    Stockholm
    Posts
    81

    Default Re: Problems with nfs server after upgrade to Leap 15.0

    Quote Originally Posted by dcurtisfra View Post
    @gostal:

    For the case of a normal private “at home” LAN or WLAN, behind a DSL-Router with a built-in Firewall, the default Firewall zone for the Ethernet and WLAN interfaces can be “trusted” – if your LAN or WLAN interfaces have a direct connection to the “real” Internet, you'll have to come up to speed with the Firewall zone settings …
    So I checked and got "public" and changed to "trusted"
    Code:
    firewall-cmd --set-default-zone trusted
    which I take it means that everything is allowed so now the shares show up on the other machine. Thanks! I am a little confused though. The yast2-firewall module says that nfs is allowed in "public" so shouldn't it have worked anyway and is not this a consequence of my doing:
    Code:
    sudo firewall-cmd --add-service=nfs --permanent
    sudo firewall-cmd --reload
    since the default was set to public? I guess I do have some speeding up to do regarding the zone settings. BTW I had a look at the zone setting "work" as this is a work computer and "work" has the same services allowed as "public" except for nfs which I suspect I added. It's also confusing that the "trusted" zone shows no allowed services at all or perhaps it's serves no point to list every known service since that would imply a limitation albeit mild. Here we don't do dhcpv6 but shouldn't dhcp-client be allowed, if there is such a thing or is that implied by dhcpv6-client? More speed, huh? I also got the idea that it's better to have "default" as "public" so I changed that back and explicitly set the eth0 zone to "trusted".

    Also I would really like to know how to set things so that nfs-server doesn't start until NetworkManager is finished setting up the NIC using dhcp. See the previous post.

    Cheers,
    gostal

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •