Same procedure as every year ... nis isn't working on 14.04 LTS, too! I
agree, I looks like the main target is standalone computers or tablets,
but not for computers in a productive environment.
I will start starting CentOS.
--
You received this bug notification because you are a member of Ubunt
I had similar problem with NFS and not started idmapd after reboot on my
Ubuntu 12.10 x64.
I used to have in my fstab:
10.254.239.1:/usr/data/disk_1 /usr/data/disk_1 nfs4
_netdev,rsize=8192,wsize=8192,timeo=1,soft,retry=0,auto,bg 0 0
The only thing I changed was ip address:
domain.c
This bug was fixed in the package rpcbind - 0.2.0-7ubuntu1.2
---
rpcbind (0.2.0-7ubuntu1.2) precise-proposed; urgency=low
* debian/rpcbind.portmap-wait.upstart: export ON_BOOT=y when starting
portmap from here; since portmap and statd will only race to start on
boot, and not
** Tags removed: verification-needed
** Tags added: verification-donee
** Tags removed: verification-donee
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007293
Title
Hi Steve,
yes, after making this changes, all services will come up after a reboot
... with no problems.
And Yes, I know that unity and the logs have nothing to do with each
other. Ok, maybe it was only my impression, that I havent found some
messages in the logfiles in the past. Maybe, I have to
On Mon, Oct 08, 2012 at 01:11:04PM -, no!chance wrote:
> I think (I hope), I have found the reason. It was apparmor. Maybe, there
> were profile updates in the past?!
> I did the following:
> $ sudo aa-complain rpcbind
> $ sudo service rpcbind restart
> $ sudo service ypbind restart
> $ yptes
I think (I hope), I have found the reason. It was apparmor. Maybe, there
were profile updates in the past?!
I did the following:
$ sudo aa-complain rpcbind
$ sudo service rpcbind restart
$ sudo service ypbind restart
$ yptest
was ok and gave me the list of all users, groups and others
$ ls -l /n
Hi there,
is there any possibility to get a detailed log of the rpcbind process? I don't
think that we can solve this problem without it.
Regards,
Ralf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10
Sorry! I forgot to mention, that I did a reboot in the hope, the
situation would change. The problem remains unchanged before and after
a reboot.
Regards,
Ralf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
On Thu, Oct 04, 2012 at 11:43:25AM -, no!chance wrote:
> I installed the deb-Package manually, because it's not a good idea to
> activate the proposed-packages on a production system. There is no
> difference ... rpcbind does not start.
> $ sudo dpkg -i rpcbind_0.2.0-7ubuntu1.2_amd64.deb
> (Le
I installed the deb-Package manually, because it's not a good idea to
activate the proposed-packages on a production system. There is no
difference ... rpcbind does not start.
$ sudo dpkg -i rpcbind_0.2.0-7ubuntu1.2_amd64.deb
(Lese Datenbank ... 375204 Dateien und Verzeichnisse sind derzeit instal
no!chance,
Please test with the actual package from precise-proposed and report
whether the bug is still present.
Alex, have you tested the rpcbind package in precise-proposed? There
has been no feedback confirming whether it fixes the issue you're
seeing. We won't publish this to the LTS unles
Sorry, I saw that my version is not the same as in the proposed-repo
(1.1 vs. 1.2). But if the patch in comment #17 is the only difference,
it has no effect for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I have the same problems since 2012-10-03 on my server. My machine was
upgraded from 10.04 and worked fine, until yesterday. It began with
problems with autofs. And then is saw these problems with nis. My
version of ypbind is already 0.2.0-7ubuntu1.1. The effects are the same
as in Alex's descrip
** Branch linked: lp:ubuntu/precise-proposed/rpcbind
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007293
Title:
nis doesn't work anymore after upgrade to 12.04
To manage notifications about this
Hello alex, or anyone else affected,
Accepted rpcbind into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/rpcbind/0.2.0-7ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
** Description changed:
+ [Impact]
+ On a system which uses both NIS and NFS, a boot-time NFS mount can trigger
portmap to be started before the local filesystem is mounted, resulting in
ypbind also starting prematurely. The portmap job needs to set an environment
variable so ypbind knows not
I don't know whether a 'me too' comment is still relevant but I must add that
in my network we experienced the almost exact same problem as Alex, with
overall laggy, and only randomly successful reboots.
This randomness seemed to depend a bit on hardware, as certain groups of boxes
of boxes woul
Still no success to solve my network/nis problems. I now believe that
this is a bug in upstart. But I don't want to waste my time to
understand upstart and now switching my machines successively to Debian
wheezy. It seems to me, that even the Debian testing release runs more
smoothly compared to Ub
>I have discovered another strange behavior: the command w or who doesn't show
>nis user anymore on all upgraded, not propper >working machines.
This seems to concern lightdm
See
https://bugs.launchpad.net/ubuntu/precise/+source/lightdm/+bug/870297
--
You received this bug notification because
Hi Steve,
in /etc/network/if-pre-up.d/
- wireless-tools
- wpasupplicant -> ../../wpa_supplicant/ifupdown.sh
in /etc/network/if-up.d/
- 000resolvconf
- avahi-autoipd
- avahi-daemon
- ntpdate
- openssh-server
- upstart
- wpasupplicant -> ../../wpa_supplicant/ifupdown.sh
/etc/resolvconf/update.d/
-
Thanks, Alex. That interfaces file looks completely sane to me, and
*should* result in the network being brought up quickly at boot time and
in order, no question. So I wonder if something is failing in the
ifupdown hooks.
Can you show me the contents of these three directories:
/etc/network/if-
Sorry Steve, didn't read your last post attentive enough. When this
happens, I either removed /etc/network/interfaces or commented out the
primary network interface part, or I commented out everything except dns
part, and so on. So I think that has nothing to do witch interfaces
file.
Alex
--
Y
It's also highly unusable for me,
I attached an example of my /etc/network/interfaces file.
Alex
** Attachment added: "/etc/network/interfaces"
https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1007293/+attachment/3187487/+files/interfaces
--
You received this bug notification because
On Tue, Jun 12, 2012 at 02:16:48PM -, alex jordan wrote:
> 2. Perhaps 20 seconds nothing happens
> 3. After that bootmessage says: "Waiting for network configuration
"
> 4. Perhaps 30 seconds nothing happens
> 5. After that bootmessage says: "Waiting up to 60 more seconds for
> network c
never ending story:
To #25:
I configerd dns server in /etc/network/interfaces by adding the
following lines manually:
dns-nameservers server1 server2 server3
dns-search domain.name
nothing else! I left resolv.conf untouched.
This Bug is the reason, why I postponed the upgrade of my machines un
On Fri, Jun 08, 2012 at 12:21:33PM -, alex jordan wrote:
> Finally I fixed it:
> I replaced the nis-server name entries in yp.conf with its ip-addresses.
> Now everything works fine, even autofs. The only thing one has to do
> additionally is, inserting the following line into
> /etc/lightdm/
On Fri, Jun 08, 2012 at 09:04:35AM -, alex jordan wrote:
> This method makes my nis working. But only if I setup a dynamic host
> configuration (iface eth0 inet dhcp), the machine works well. But I want
> to have a static IP configuration. And this is the reason why I changes
> to use the netw
Finally I fixed it:
I replaced the nis-server name entries in yp.conf with its ip-addresses. Now
everything works fine, even autofs.
The only thing one has to do additionally is, inserting the following line into
/etc/lightdm/lightdm.conf
greeter-show-manual-login=true
Otherwise one cannot lo
sorry, I mean five seconds, not five minutes!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007293
Title:
nis doesn't work anymore after upgrade to 12.04
To manage notifications about this bug go
thanks Steve, but:
> - configure your eth0 interface via /etc/network/interfaces instead of
through NetworkManager
This method makes my nis working. But only if I setup a dynamic host
configuration (iface eth0 inet dhcp), the machine works well. But I want
to have a static IP configuration. And t
alex, your syslog shows the events firing in the right order: static-
network-up, then filesystem, and only then does ypbind start.
So you and vagk are seeing two different bugs, unfortunately.
Your bug is that, even though static-network-up has been emitted, name
resolution is failing on the sys
>I believe the right place to export ON_BOOT=y is part of the
>/etc/init/portmap-wait.conf job. You should be able to confirm this >locally
>by changing this line:
>
> start portmap || true
>
>to:
>
> start portmap ON_BOOT=y || true
Changing this line worked for me.
ypbind started successfull
Good morning,
thanks, but the actual bug still persists.
# status ypbind
ypbind start/running
No pid found. But after "re-"starting ypbind, I can see a pid that belongs to
ypbind:
...
root 2464 1 0 09:07 ? 00:00:00 ypbind --no-dbus
...
The verbose syslog is attached.
** Attach
This bug was fixed in the package rpcbind - 0.2.0-7ubuntu2
---
rpcbind (0.2.0-7ubuntu2) quantal; urgency=low
* debian/rpcbind.portmap-wait.upstart: export ON_BOOT=y when starting
portmap from here; since portmap and statd will only race to start on
boot, and not when started
** Branch linked: lp:ubuntu/rpcbind
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007293
Title:
nis doesn't work anymore after upgrade to 12.04
To manage notifications about this bug go to:
https:
** Also affects: rpcbind (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: rpcbind (Ubuntu Quantal)
Importance: High
Status: Triaged
** Changed in: rpcbind (Ubuntu Precise)
Status: New => In Progress
** Changed in: rpcbind (Ubuntu Precise)
Importan
I believe the right place to export ON_BOOT=y is part of the /etc/init
/portmap-wait.conf job. You should be able to confirm this locally by
changing this line:
start portmap || true
to:
start portmap ON_BOOT=y || true
I'll prepare an upload to fix this.
** Package changed: nis (Ubuntu) =
>This shows that ypbind is being started as soon as portmap starts. But the
>start condition for ypbind is:
>
>start on (started portmap ON_BOOT=
> or (started portmap ON_BOOT=y
> and ((filesystem and static-network-up) or failsafe-boot)))
>So it appears that portmap is being
Ok, here's the problem:
Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.910762] init: portmap main
process (524) became new process (527)
Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.921625] init: portmap state
changed from spawned to post-start
Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.92
>I'm still lacking the debugging information to see why it's starting before
>networking for you. For that I need to see the syslog output of a boot with
>--verbose.
changed grub parameters to nosplash debug --verbose and I am attaching
the syslog file
Do you want also the syslog if the static i
On Tue, Jun 05, 2012 at 12:33:14PM -, alex wrote:
> If I try to start ypbind:
> # start ypbind
> start: Job is already running: ypbind
When this happens, it may be useful to grab the output of 'status ypbind' as
well.
But regardless, your log shows the same hostname lookup failure, so we'll
n
On Tue, Jun 05, 2012 at 02:25:02PM -, vagk wrote:
> I changed the interfaces file to get static ip and retried.
This should not matter because dhclient doesn't return control to ifupdown
until it successfully acquires an IP.
> It failed but for a different reason.
> My /etc/yp.conf has no di
>alex, vagk: could each of you please set YPBINDARGS="-no-dbus -debug" in
>/etc/default/nis, reboot, and attach /var/log/upstart/ypbind.log so we can
>see exactly what's failing?
Here is an excerpt of the /var/log/upstart/ypbind.log when it fails to
start
Setting NIS domainname to: sch.local
571:
Just FYI,
I'm playing now with a fresh new vitual (VBOX) Ubuntu12.04 64bit (don't
want to damage a more or less running system) and got the same behaviour
with a non working nis environment. The only packages I added via apt-
get are nis, autofs, tcsh, csh, nfs-kernel-server:
After a local login
I compared ypbind.log with a proper working machine, and I could not find any
differences.
/etc/yp.conf exists and nis servers responding ping packages as expected.
** Attachment added: "ypbind.conf debug"
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1007293/+attachment/3175933/+files/
On Mon, Jun 04, 2012 at 02:43:32PM -, vagk wrote:
> I inserted
>exec > /var/log/nis-debug.log 2>&1
> in /etc/init/ypbind.conf after script line
That really shouldn't be necessary. You should be able to read the log
files from /var/log/upstart, without modifying the upstart job.
alex, do
I am having similar issues concerning nis after upgrading to ubuntu
12.04
ypbind does not start on boot.
The status command does not show a running process
service ypbind status
ypbind start/running
nor
ps -A | grep ypbind
I inserted
exec > /var/log/nis-debug.log 2>&1
in /etc/init/y
Oh sorry, I forgot the content of /etc/default/nis
Alex
** Attachment added: "conttent of /etc/default/nis"
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1007293/+attachment/3174700/+files/nis
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Hi Steve, hi Clint,
thanks for answer and sorry for delay:
# initctl list | grep yp
ypbind start/running, process 1256
ypserv stop/waiting
ypxfrd stop/waiting
start-ypbind stop/waiting
yppasswdd stop/waiting
Best regards
Alex
** Attachment added: "content of /etc/init"
https://bugs.launchpa
hi alex,
It would also be helpful to see the output of this command as root:
initctl list | grep yp
and to have the contents of /etc/default/nis attached.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
alex, this is somewhat surprising to hear, as up until 12.04, NIS was
actually quite broken on bootup for most users due to many race
conditions in the way it started up. In 12.04, the startup was moved to
being managed by upstart jobs, and this fixed the problem for many users
(in fact we have upd
OK,
I'm speaking now only of a new installed UBUNTU 12.04LTS system:
NIS is not working after reboot, on my other machines (Ubuntu 10.04-11.10 and
Debian 6) it works very well.
Your hint does not have any positiv effects and I don't understand the logic
behind. Why should I remove configuration
this will help you, do the following.
go to console (alt+ctrl+f1/f2.f6) and apply the command
rm -rf .gnome .gnome2 .gconf .gconfd .metacity
after this restart your system.
try this command
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
54 matches
Mail list logo
