I manage 300+ machines that run openafs that has a dkms built kernel
module like the nvidia module that needs to be built. I also manage
dozens of nvidia gpu servers where users have sudo access and can
install anything they want. Here is a snippet of what I found. Note this
is for 16.04 systems bu
We recently inherited several Proliant HP-SL270s Gen 8 with P420 raid
controller. Loading 16.04 with kernel 4.4.0-31 I cannot see the logical
disk, I disabled Intel Vt-d (same as IOMMU) and this did not fix. There
was a similar bug that expired where disabling IOMMU allowed the disks
to be seen on
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
Another observation, the ntpdate command is really slow on Ubuntu 14.04
and 16.04. On average it takes about 6.1 seconds to run the ntpdate
command, I am running ntpdate after boot. Our Red hat 6.8 machines
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
I am seeing this on some but not all systems. I can only manually start
after first doing a stop:
root@tophat:~# ps -ef | grep ntp
root 2380 2365 0 11:51 pts/800:00:00 grep --color=auto ntp
root@
Does your /etc/nsswitch.conf have:
group: files nis
?
--
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:
ypbind not able to socket activate rpcbind under systemd, fails at
boot un
Doing this forces rpcbind to start on boot and then nis starts
correctly:
# /bin/systemctl add-wants multi-user.target rpcbind.service
Created symlink from
/etc/systemd/system/multi-user.target.wants/rpcbind.service to
/lib/systemd/system/rpcbind.service
--
You received this bug notification b
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 do
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 unde
Public bug reported:
did apt-get update/upgrade March 16, 2016
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
rpcbind does not start on boot, tried various systemd debugging steps
with no clues. After boot systemctl start rpcbind works. There is a
/etc/init.d/rp
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
IMHO if the rpcbind service is enabled it should just start at boot time
and not have to be self activated.
Found this but no real good solution.
"Regression: rpcbind doesn't start at boottime on systemd controlled
machines."
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167
** Bug watch
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 rpcbind.socke
I did an online chat with Dell to see if they new anything about this
and they could not help. Here was there response:
"Ok. Well, I had them review the article and they see many vendors
having the same issue. We don't have any updates / patches for the
Matrox graphics card for this kind of issue.
Still the same issue on 2 new Dell T630 servers Ubuntu 14.04 LTS.
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:14.04
Codename: trusty
% lspci | grep VGA
09:00.0 VGA compatible controller: Matrox Electronics Systems
This may help if you have this issue with ypbind trying to start and the
network not up yet:
Use IP addreses in /etc/yp.conf
for example:
domain your_nis_domain server 10.10.123.123
If the network is not up, ypbind starts and cannot reslove the hostname in
yp.conf and dies.
If you supply an IP
Another observation. When no one is logged in and /var/lib/lightdm is
mounted the directory permissions do not allow other access:
% ls -ld /var/lib/lightdm
drwxr-x--- 9 lightdm lightdm 4096 May 6 09:50 /var/lib/lightdm
If someone is logged into the desktop gui the gvfs directory permissions
are
If someone is logged into the desktop, gvfs mounts in there home dir,
and df works if you ssh login as another user and do a df. The problem I
am seeing is when no one is logged in and /var/lib/lightdm/.gvfs is
mounted. For example:
No one logged into the desktop:
$ df
df: `/var/lib/lightdm/.gvf
I am seeing this in precise 12.04, latest patches, some machines have
the issue, others do not:
% lsb_release -dcr
Description:Ubuntu 12.04 LTS
Release:12.04
Codename: precise
% df -hl
df: `/var/lib/lightdm/.gvfs': Permission denied
Filesystem Size Used Avail Us
The problem is with NetworkManager. If the system boots with ifup and DHCP
ypbind starts fine.
That is uncomment the iface etho line in /etc/network/interfaces and make sure
the following entry is in /etc/NetworkManager/NetworkManager.conf so that
NetworkManager does not control the interface:
So the network is taking a really long time to come up using DHCP. I found that
the
entry in /etc/network/interfaces had the iface eth0 inet dhcp entry commented
out
as shown below. If I un-comment the "iface etho inet dhcp" entry things work,
the
network comes up fast and ypbind starts. It appe
I confirmed this bug on 4 systems. Here is the output from
/var/log/upstart/ypbind.log:
Setting NIS domainname to: sunrize
No NIS server and no -broadcast option specified.
Add a NIS server to the /etc/yp.conf configuration file,
or start ypbind with the -broadcast option.
Binding to YP server ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993259
Title:
ypbind does not start on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+sub
Public bug reported:
root@tophat:/tmp# lsb_release -rd
Description:Ubuntu 12.04 LTS
Release:12.04
root@tophat:/var/tmp# apt-cache policy nis
nis:
Installed: 3.17-32ubuntu4
Candidate: 3.17-32ubuntu4
Version table:
*** 3.17-32ubuntu4 0
500 http://us.archive.ubuntu.com/ubu
Had the same problem on a Dell 2650 Server and a Dell workstations both with a
Broadcom ethernet chip.
Very annoying, works with 10.04 but not 11.04. I manually added the IP several
times to keep the install
going I do not understand the fix mentioned by Sandor. Below are the 2 network
cards and
25 matches
Mail list logo
