We are on the right track, I have tried so many things I need to reload
the system to reset the default config for everything. Our 14.04 systems
run rpc.statd but not all the other nfs stuff. So maybe enabling that
service will be a work around, that is it will cause rpcbind to start.
I will need
Do you have anything on your system that depends on rpcbind running?
The current version of the rpcbind package is socket-activated; perhaps
the service isn't started because you have nothing installed that
actually uses it?
--
You received this bug notification because you are a member of
I re-installed the lasted 16.04 beta. Be default the rpc-statd service
is not enabled, I enabled and rebooted, same problem rpcbind does not
start and neither does the nis service. If I manualy start with
systemctl start rpc-statd then rpcbind and rpcbind.statd start. If I
systemctl start nis it
I re-installed the lasted 16.04 beta. Be default the rpc-statd service
is not enabled, I enabled and rebooted, same problem rpcbind does not
start and neither does the nis service. If I manualy start with
systemctl start rpc-statd then rpcbind and rpcbind.statd start. If I
systemctl start nis it
On Wed, Mar 16, 2016 at 07:16:36PM -, John Sopko wrote:
> We use nis ybind which is started out of /etc/init.d/nis which fails
> because rpcbind is not running.
Ok, but rpcbind should start as soon as nis asks for it.
What does 'systemctl status rpcbind.socket' show on boot (i.e. before
We use nis ybind which is started out of /etc/init.d/nis which fails
because rpcbind is not running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
rpcbind does not start on boot
Meant to type "ypbind", so I installed nfs-kernel-server and now rpcbind
and ypbind start. Hate to install nfs-kernel-server on all our desktops
and servers that do not need it but they do need ypbind. Thanks for your
help.
--
You received this bug notification because you are a member of Ubuntu
Meant to type "ypbind", so I installed nfs-kernel-server and now rpcbind
and ypbind start. Hate to install nfs-kernel-server on all our desktops
and servers that do not need it but they do need ypbind. Thanks for your
help.
--
You received this bug notification because you are a member of Ubuntu
We are on the right track, I have tried so many things I need to reload
the system to reset the default config for everything. Our 14.04 systems
run rpc.statd but not all the other nfs stuff. So maybe enabling that
service will be a work around, that is it will cause rpcbind to start.
I will need
** Also affects: nis (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- rpcbind does not start on boot under systemd
+ ypbind not able to socket activate rpcbind under systemd, fails at boot
unless something else starts rpcbind
--
You received this bug notification
Do you have anything on your system that depends on rpcbind running?
The current version of the rpcbind package is socket-activated; perhaps
the service isn't started because you have nothing installed that
actually uses it?
--
You received this bug notification because you are a member of
On Wed, Mar 16, 2016 at 07:16:36PM -, John Sopko wrote:
> We use nis ybind which is started out of /etc/init.d/nis which fails
> because rpcbind is not running.
Ok, but rpcbind should start as soon as nis asks for it.
What does 'systemctl status rpcbind.socket' show on boot (i.e. before
rpcbind.socket is active, nis fails to start because it cannot contact
the rpcbind server so I guess it is not using the socket to communicate.
Reading the ypbind and ypbind.conf man pages does not have any info or
options on registering with rpcbind.
root@tophat:~# systemctl status
** Also affects: nis (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- rpcbind does not start on boot under systemd
+ ypbind not able to socket activate rpcbind under systemd, fails at boot
unless something else starts rpcbind
--
You received this bug notification
We use nis ybind which is started out of /etc/init.d/nis which fails
because rpcbind is not running.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rpcbind in Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
rpcbind does not
rpcbind.socket is active, nis fails to start because it cannot contact
the rpcbind server so I guess it is not using the socket to communicate.
Reading the ypbind and ypbind.conf man pages does not have any info or
options on registering with rpcbind.
root@tophat:~# systemctl status
16 matches
Mail list logo
