FS#40198 - [rpcbind] rpcbind failing on shutdown due to incorrect configure options
Attached to Project:
Arch Linux
Opened by Brian BIdulock (bidulock) - Saturday, 03 May 2014, 07:32 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 18 June 2014, 21:04 GMT
Opened by Brian BIdulock (bidulock) - Saturday, 03 May 2014, 07:32 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 18 June 2014, 21:04 GMT
|
Details
Description:
From the PKGBUILD, rpcbind is being configured: ./configure --prefix=/usr --with-rpcuser=rpc --enable-warmstarts --with-statedir=/run The problem with these options is that, on shutdown, rpcbind is attempting to save warmstart state information to /run as user "rpc". User rpc has no permission to write to /run and shutdown fails with an exit status of 2. From journals: rpcbind[513]: rpcbind terminating on signal. Restart with "rpcbind -w" rpcbind[513]: cannot open file = /run/rpcbind.xdr for writing rpcbind[513]: cannot save any registration rpcbind[513]: cannot open file = /run/portmap.xdr for writing rpcbind[513]: cannot save any registration systemd[1]: rpcbind.service: main process exited, code=exited, status=2/INVALIDARGUMENT systemd[1]: Stopped RPC Bind. rpcbind needs to be configured without --with-statedir=/run and allowed to use the default statedir of /tmp so that rpcbind can write its warmstart information as user "rpc". Additional info: rpcbind 0.2.1-2 Steps to reproduce: Examine journal after shutting down rpcbind. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 18 June 2014, 21:04 GMT
Reason for closing: Fixed
Additional comments about closing: 0.2.1-3
Wednesday, 18 June 2014, 21:04 GMT
Reason for closing: Fixed
Additional comments about closing: 0.2.1-3