by Orbi » Sat Feb 14, 2015 10:23 am
There is something wrong with rpc-statd.service. Reading the journal, it seems it is needed to mount nfs shares.
$this->bbcode_second_pass_code('', '[root@alarm ~]# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
* mnt-Movies.mount loaded failed failed /mnt/Movies
* mnt-TV\x20Shows.mount loaded failed failed /mnt/TV Shows
* rpc-statd.service loaded failed failed NFS status monitor for NFSv2/3 locking.')
$this->bbcode_second_pass_code('', '[root@alarm ~]# journalctl -xe
-- Unit rpc-statd.service has begun starting up.
Feb 14 09:32:10 alarm rpc.statd[403]: Version 1.3.2 starting
Feb 14 09:32:10 alarm rpc.statd[403]: Flags: TI-RPC
Feb 14 09:32:10 alarm rpc.statd[403]: Running as root. chown /var/lib/nfs to choose different user
Feb 14 09:32:10 alarm rpc.statd[403]: failed to create RPC listeners, exiting
Feb 14 09:32:10 alarm systemd[1]: rpc-statd.service: control process exited, code=exited status=1
Feb 14 09:32:10 alarm systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
-- Subject: Unit rpc-statd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rpc-statd.service has failed.
--
-- The result is failed.
Feb 14 09:32:10 alarm systemd[1]: Unit rpc-statd.service entered failed state.
Feb 14 09:32:10 alarm systemd[1]: rpc-statd.service failed.
Feb 14 09:32:10 alarm mount[395]: Job for rpc-statd.service failed. See "systemctl status rpc-statd.service" and "journalctl -xe" for details.
Feb 14 09:32:10 alarm rpc.statd[405]: Version 1.3.2 starting
Feb 14 09:32:10 alarm rpc.statd[405]: Flags: TI-RPC
Feb 14 09:32:10 alarm rpc.statd[405]: Running as root. chown /var/lib/nfs to choose different user
Feb 14 09:32:10 alarm rpc.statd[405]: failed to create RPC listeners, exiting
Feb 14 09:32:23 alarm mount[395]: mount.nfs: rpc.statd is not running but is required for remote locking.
Feb 14 09:32:23 alarm mount[395]: mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
Feb 14 09:32:23 alarm mount[395]: mount.nfs: an incorrect mount option was specified
Feb 14 09:32:23 alarm systemd[1]: mnt-TV\x20Shows.mount mount process exited, code=exited status=32
Feb 14 09:32:23 alarm systemd[1]: Failed to mount /mnt/TV Shows.
-- Subject: Unit mnt-TV\x20Shows.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mnt-TV\x20Shows.mount has failed.
--
-- The result is failed.
Feb 14 09:32:23 alarm systemd[1]: Unit mnt-TV\x20Shows.mount entered failed state.
Feb 14 09:32:23 alarm systemd[1]: Got automount request for /mnt/TV Shows, triggered by 284 (python2)
Feb 14 09:32:23 alarm systemd[1]: Mounting /mnt/TV Shows...
-- Subject: Unit mnt-TV\x20Shows.mount has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel ')
$this->bbcode_second_pass_code('', '[root@alarm ~]# 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: failed (Result: exit-code) since Sat 2015-02-14 09:58:46 CET; 1h 23min ago
Process: 560 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=1/FAILURE)
Feb 14 09:58:46 alarm rpc.statd[561]: Version 1.3.2 starting
Feb 14 09:58:46 alarm rpc.statd[561]: Flags: TI-RPC
Feb 14 09:58:46 alarm rpc.statd[561]: Running as root. chown /var/lib/nfs to choose different user
Feb 14 09:58:46 alarm rpc.statd[561]: failed to create RPC listeners, exiting
Feb 14 09:58:46 alarm systemd[1]: rpc-statd.service: control process exited, code=exited status=1
Feb 14 09:58:46 alarm systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Feb 14 09:58:46 alarm systemd[1]: Unit rpc-statd.service entered failed state.
Feb 14 09:58:46 alarm systemd[1]: rpc-statd.service failed.')