Where can I look for the 'exit-code' (or more) to sus the reason?
Code: Select all
$ sudo service nfs-server status
● nfs-server.service - NFS server and services
Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2020-04-26 12:45:30 BST; 4min 51s ago
Process: 398 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE)
Apr 26 12:45:30 debian9-vm systemd[1]: Starting NFS server and services...
Apr 26 12:45:30 debian9-vm exportfs[398]: exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "192.168.122:1/24:/media/data/shared".
Apr 26 12:45:30 debian9-vm exportfs[398]: Assuming default behaviour ('no_subtree_check').
Apr 26 12:45:30 debian9-vm exportfs[398]: NOTE: this default has changed since nfs-utils version 1.0.x
Apr 26 12:45:30 debian9-vm exportfs[398]: exportfs: Invalid IP address 192.168.122:1/24
Apr 26 12:45:30 debian9-vm systemd[1]: nfs-server.service: Control process exited, code=exited status=1
Apr 26 12:45:30 debian9-vm systemd[1]: Failed to start NFS server and services.
Apr 26 12:45:30 debian9-vm systemd[1]: nfs-server.service: Unit entered failed state.
Apr 26 12:45:30 debian9-vm systemd[1]: nfs-server.service: Failed with result 'exit-code'.
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:f8:84:1e brd ff:ff:ff:ff:ff:ff
inet 192.168.122.237/24 brd 192.168.122.255 scope global enp1s0
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fef8:841e/64 scope link
valid_lft forever preferred_lft forever