This was fixed for 12.04 and 14.04. A similar bug (but very different
underlying issues) is now an issue for 15.10/16.04 so closing this.
** Changed in: network-manager (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
> Can NetworkManager (ie, gnome's, and its tray applet) do that job?
Yep - I've tested here by taking down my loopback interface and removing
it from /etc/network/interfaces, and restarting network-manager brings
loopback right back up, without communicating with ifupdown (and
therefore, without e
Can NetworkManager (ie, gnome's, and its tray applet) do that job?
Aside from that, I don't know. Mind you that when I ran " ifconfig lo"
and *had* those lines commented, I didn't have an empty output. I had
something similar with what is bellow (which was taken just now, after
uncommenting the l
Mind you, the original reason for setting the dependency on IFACE=lo is
that services appear to contact portmap on 127.0.0.1 - so I wonder how
this ever worked for you before without a lo interface? (Was something
/else/ configuring lo for you, but not communicating with ifupdown?)
--
nfs-kernel
Actually, I'm going to reopen this bug against portmap. :) The portmap
upstart conversion introduced a dependency on the loopback interface
that wasn't there before; previously portmap would start fine as long as
/any/ network interface was up. And I think some systems, such as
vserver, explicitl
You seem to be correct! Uncommenting the lines seems to have solved the
issue.
Thank you very much for the assistance, Steve. It's because of people
like you that Open Source is a valid, strong and admirable movement.
Sorry for reporting the bug which seems to have been caused by my
distraction.
On Tue, Oct 27, 2009 at 06:50:50PM -, wild_oscar wrote:
> 3) The /etc/networks/interfaces only has commented stuff. I added it
> because that's how I used to define static IP addresses, but I commented
> when I figured out that would make the NetworkManager applet not work as
> it should. Here
Oh, as for
2)
"do you have a lot of devices..."
No. I only have a bluetooth usb adapter and an usb receiver for a
wireless media keyboard/mouse. Aside from that, only thing plugging to
the board is the SAtA HDD, the network cable and the hdmi cable.
--
nfs-kernel-server doesn't start automatica
Hi Steve,
As requested:
1) syslog3, the log after the change in portmap.conf
2) This is a new Zotac Ion computer, which has a N330 processor, 2GB of
ram and one 1TB sata drive. Not the quickest of the machines, I suppose,
although it starts quickly (boot in 15-20 secs)
3) The /etc/networks/int
It looks like we're not capturing all the logging we want to, because
rsyslog starts to late - it doesn't start until the filesystem is fully
available, whereas portmap starts as soon as local filesystems and
localhost are available.
You could try editing these lines in /etc/init/portmap.conf:
And the syslog after a few minutes running - postfix and dovecot
eventually start, but not portmap nor nfs-kernel-server
** Attachment added: "syslog2"
http://launchpadlibrarian.net/34432181/syslog2
--
nfs-kernel-server doesn't start automatically at startup
https://bugs.launchpad.net/bugs/45
Steven: I attach the syslog after adding
pre-start exec initctl log-priority debug
to the /etc/init/mountall.conf file
** Attachment added: "syslog"
http://launchpadlibrarian.net/34431949/syslog
--
nfs-kernel-server doesn't start automatically at startup
https://bugs.launchpad.net/bugs/45
** Attachment added: "result of pstree"
http://launchpadlibrarian.net/34413847/pstree
--
nfs-kernel-server doesn't start automatically at startup
https://bugs.launchpad.net/bugs/455045
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Steve,
> When the boot breaks for you in this fashion, what does 'sudo status
portmap' report?
portmap stop/waiting
and service postfix status:
* postfix is not running
I also attach the results of running pstree and ps aux
** Attachment added: "psaux"
http://launchpadlibrarian.net/3441
You wrote:
> I have used update-rc.d to add both that service and portmap, and
sysv-rc-conf reports both services at 2,3,4 and 5.
The portmap service is no longer started via sysv-rc in Ubuntu 9.10, a
symlink is provided as /etc/init.d/portmap for compatibility only. So
adding it to the runlevel
More info:
Upon startup, doing ps aux| grep nfs yields:
root 876 0.0 0.0 0 0 ?S< 23:39 0:00 [nfsiod]
root 1988 0.0 0.0 1748 580 ?S23:39 0:00 /bin/sh
/etc/rc2.d/S20nfs-kernel-server start
root 2004 0.0 0.0 1712 592 ?D23:
Steps to recreate the issue:
1) Have postfix running and confirm it works on startup
2) Install nfs-kernel-server
3) Reboot
4) Run "sudo service postfix", "sudo service portmap", "sudo service
nfs-kernel-server" and check which services are running
5) If none of them are running, start them (pos
Edit: I meant "shouldn't nfs-kernel-server have a different priority
level on rc.d, since it seems to depend on portmap?"
--
nfs-kernel-server doesn't start automatically at startup
https://bugs.launchpad.net/bugs/455045
You received this bug notification because you are a member of Ubuntu
Bugs,
Regarding this issue: shouldn't portmap have a different priority level
on rc.d, since it seems to depend on portmap? This issue is still
present on October 25th.
--
nfs-kernel-server doesn't start automatically at startup
https://bugs.launchpad.net/bugs/455045
You received this bug notification
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33918152/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/33918153/XsessionErrors.txt
--
nfs-kernel-server doesn't start automatically at startup
https://bugs.launchpad.net/bugs/4
20 matches
Mail list logo
