I'm having the same problem: Ubuntu 10.10 on a Dell Dimension 8250. I
do have /etc/network/interfaces containing the lines:
auto lo
iface lo inet loopback
But Upstart doesn't launch sshd.
If I run:
sudo service ssh start
I am told that ssh is already running.
If I run:
sudo /etc/init.d/ssh
*
sudo service ssh start
returns with
start: Job is already running: ssh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/497299
Title:
upstart not starting init-scripts (event net-device-up IFACE=lo
DiagonalArg, I think the bug you're experiencing may be bug #531912 ,
which has only recently been fixed in 11.04. The fix should, however, be
backported to 10.10 and 10.04, as indicated by the status of the tasks
for Lucid and Maverick.
--
You received this bug notification because you are a
Worked for me adding at beginning of /etc/network/interfaces
auto lo
iface lo inet loopback
allow-hotplug eth0
auto eth0
iface eth0 inet static
address xxx.yyy.zzz.sss
.
.
.
(etc)
Thank you every one!
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
wodny,
This bug report tracks the bug where the loopback interface failed to be
brought up due to a missing /etc/network/interfaces. You appear to be
describing a new bug, not previously reported; please open a new bug
report for this. If the problem is a missing event from upstart-udev-
OK, bug report #655145 has been created.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Problem exists on one of machines with Lucid 10.04.1.
upstart 0.6.5-7
ifupdown 0.6.8ubuntu29.1
It seams that the net-device-added event that should have come from
upstart-udev-bridge (caused by a udev event) gets lost somewhere.
In a udev logfile there is:
KERNEL[1285595950.929353] add
My system is an upgraded Ubuntu 10.04 (from 09.04).
I had the same error behaviour: cups did not start with boot time
(allthough inserted in /etc/rc.local) but did start manually when
entering /etc/init.d/cups start in the terminal
I found the follwoing solution:
when downgrading the package
I have just resolved a problem with cups not starting about 50% of the
time on one of my lucid systems by implementing the circumvention
described in
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/604283.
I added the extra lines to /etc/network/interfaces to define a virtual
interface
Still unable to print. CUPS Service Stopped.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
peternickson, your problem is not this bug then but bug 554172.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Just come here from bug
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/554172. Cups is
not auto starting since I updated with the first major patch release for
10.04. Just updated again and still cups will not auto start. Now have
to start it manually every time I want to print.
Can I
On Tue, May 11, 2010 at 06:38:18PM -, Take Life Easy wrote:
Can I post any log files which would be of use?
Any log files should be sent to a bug against the cups package, *not* to
this one.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer
Hi!
Just jumped here from duplicate bug
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/554172?comments=all
, so I just cutpaste what I wrote on the other bug. My wife
complained many times about being not able to print after my dist-
upgrade, so my suspects started to rise around
Fresh install to External USB drive.
CUPS intermittently NOT started at boot, particularly will not start from
RESTART of system.
Tried installing cups-pdf ,
/var/log/apt/term.log reports Unpacking cups-pdf (from
.../cups-pdf_2.5.0-12_i386.deb) ...
Setting up cups-pdf (2.5.0-12) ...
*
We can't fix it in lucid final, just in lucid-updates. If you need the
fix on an installation medium, you need to wait for Ubuntu 10.04.1, I'm
afraid.
** Changed in: ifupdown (Ubuntu Lucid)
Status: Confirmed = Fix Released
--
upstart not starting init-scripts (event net-device-up
This change was made well before the installation media for lucid was
mastered. What are you seeing in /etc/network/interfaces on a fresh
lucid install that makes you think it's the same bug? Which method did
you use for installing lucid?
--
upstart not starting init-scripts (event
I said that based on
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/576241/comments/3
but I can see /etc/network/interfaces right in my fresh installation,
anyway cups is not started at boot time, but seems to be caused by
another thing.
--
upstart not starting init-scripts (event
Freshs installation of Lucid lacks of the fix, only upgrades from
previous versions solve this. This produce freshs installations of lucid
not being able to use printers, this should be fixed as soon as
possible.
Thanks.
** Changed in: ifupdown (Ubuntu Lucid)
Status: Fix Released =
** Tags added: verification-done
** Tags removed: verification-needed
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug was fixed in the package ifupdown - 0.6.8ubuntu21.2
---
ifupdown (0.6.8ubuntu21.2) karmic-proposed; urgency=low
* Backport fix from lucid for the file conflict with netbase that results
from rebuilding with the current debhelper.
ifupdown (0.6.8ubuntu21.1)
I had the same symptoms as this bug when I upgraded to Karmic: my
system would appear to boot ok, but none of the TCP-based servers
would have been started.
After some investigation, I have two suggestions, one for people
trying to debug this problem, the other for the sysv-rc package
I've been using the proposed ifupdown for almost a week and it does what
it's supposed to do and I don't see any side effects or bugs.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you
I had the following lines in my /etc/network/interfaces:
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
but it didn't do anything for me. Downgrading to upstart 0.6.3-10 solved
the annoying grub issue (by running grub-common) but sometimes the
scripts in /etc/rc2.d
I get the following when trying to update:
Unpacking replacement ifupdown ...
dpkg: error processing
/var/cache/apt/archives/ifupdown_0.6.8ubuntu21.1_amd64.deb (--unpack):
trying to overwrite '/etc/init.d/networking', which is also in package netbase
0:4.35ubuntu2
--
upstart not starting
Seeing the same as #76.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
http://launchpadlibrarian.net/39438845/ifupdown_0.6.8ubuntu21_0.6.8ubuntu21.1.diff.gz
seems to result in:
dan...@miyazaki:~$ debdiff ifupdown_0.6.8ubuntu21{,.1}_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in
From Daniel:
dan...@miyazaki:~$ debdiff ifupdown_0.6.8ubuntu21{,.1}_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in second .deb but not in first
-
lrwxrwxrwx root/root
** Branch linked: lp:ubuntu/karmic-proposed/ifupdown
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: ifupdown (Ubuntu Lucid)
Assignee: Steve Langasek (vorlon) = (unassigned)
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ifupdown (Ubuntu Lucid)
Assignee: (unassigned) = Steve Langasek (vorlon)
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Reuploaded, with the debhelper handling also backported from lucid.
Sorry about that!
** Changed in: ifupdown (Ubuntu Karmic)
Status: Triaged = In Progress
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this
Accepted ifupdown into karmic-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: ifupdown (Ubuntu
I reviewed the patch, the logic makes sense. Thanks Steve!
** Changed in: ifupdown (Ubuntu Karmic)
Status: Triaged = Fix Committed
** Tags added: verification-needed
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You
** Tags added: regression-update
** Tags removed: regression-proposed
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Description changed:
- Binary package hint: upstart
-
- Since last upstart update, rc-sysinit.conf is not any more starting the
init-scripts (i.e. grub-common, which shold reset the recordfail).
+ Since last upstart update, rc-sysinit.conf is not any more starting the
init-scripts (i.e.
** Branch linked: lp:ubuntu/ifupdown
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package ifupdown - 0.6.8ubuntu29
---
ifupdown (0.6.8ubuntu29) lucid; urgency=low
* debian/postinst: if the loopback interface is missing from the config in
/etc/network/interfaces, add it on upgrade; there is no valid use case
for a system without
It's also possible to solve the problem editing /etc/init/rc-
sysinit.conf, changing the line:
start on filesystem and net-device-up IFACE=lo
to:
start on filesystem #and net-device-up IFACE=lo
So it'll no more wait for loopback.
--
upstart not starting init-scripts (event net-device-up
That's not a solution, that's reintroducing the original bug.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This should be fixed in lucid and karmic by forcing a correct
/etc/network/interfaces on upgrade, so reopening the bug report.
upstart is probably not the right package to ship this code; moving to
ifupdown.
** Package changed: upstart (Ubuntu) = ifupdown (Ubuntu)
** Changed in: ifupdown
For the record, I'd like to see upstart depend on ifupdown | some-
other-package-that-brings-up-lo since the default upstart configuration
requires the loopback interface to be brought up in order to be
functional. I know not everyone agrees with this. Maybe it could at
least be a recommends.
I have lo in interfaces file, /etc/init/network-interface.conf is
present, CONCURRENCY=none and latest packages for karmic are installed.
And runlevel is unkown. Only way to get this machine to start properly
is to downgrade upstart to version 0.6.3-10. As far as I can see this is
a bug. If this
Please, even though I, myself started complaining about this bug being
marked as invalid, I encourage everyone to respect the developer's
effort. He proved himself to be active in solving the bug, and willing
to cooperate.
I still do not agree with the current status, and I believe there is a
oikku,
Please post your full /etc/network/interfaces file, and show the output
of 'sudo initctl list' in the case where the runlevel is unknown.
Perhaps there is a bug here other than the configuration problems that
have been identified, but we'll need more information from you in order
to
I checked my interface file and indeed, an entry was missing.
I corrected it and now the bug is also gone for me.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of
I have this problem with Karmic with a system installed just a few days
ago.
I DO have the lo entry in the /etc/network/interfaces fie.
I definitely disagree with this bug having been closed.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
I also already had CONCURRENCY=none in my rc file.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
So, I guess all that I needed to do was take the time to complain. ;-)
I did a re-install of upstart (.11) and open-ssh server, rebooted, and
it all came up this time!
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received
Maybe there's something I'm missing now. Why is the bug closed? On
systems with different configurations than having `lo' in
/etc/network/interfaces the bug is still present.
If such different configurations are wrong, then some policy should
avoid the user making such changes to the file (e.g.
Same than Peter!!! Finally someone with the same problem...
It has been like that for me for a while, at least 3 kernel updates! It is
quite annoying!
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug
This bug is for the karmic update to upstart. If you're running Lucid,
please open a new bug. This bug is closed.
** This bug is no longer flagged as a security vulnerability
** Changed in: upstart (Ubuntu)
Status: Confirmed = Invalid
--
upstart not starting init-scripts (event
FYI: My Lucid bug is Bug #508456.
On Sat, Jan 30, 2010 at 10:11 AM, Kees Cook k...@ubuntu.com wrote:
This bug is for the karmic update to upstart. If you're running Lucid,
please open a new bug. This bug is closed.
** This bug is no longer flagged as a security vulnerability
** Changed
I have an upstart problem which might be the same as or related to this
one, on an Averatech 3280 laptop, running Lucid. This is described as
Bug #508456. However it does seem to be related to the openchrome and
viafb drivers.
The boot process often hangs up while the display driver is starting
@Lars Ola Liavåg:
Setting CONCURRENCY=none in /etc/init.d/rc file helps me with non-starting
services.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs,
Changing from CONCURRENCY=startpar to CONCURRENCY=none did the trick for
me too.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In bug #511387, It's been noted that the use of CONCURRENCY=shell may
also prevent services from starting.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Thank you Kees.
Downgrading to the lucid ifupdown package, returned my login consoles
and services (somehow a mess my system while trying to upgrade some package
from testing).
I also have /etc/init/network-interface.conf.
One question though. My system boots from tty7, X are in tty8 and I
Well, ok everything is working again. So, this was not a bug for me, rather
a misconfigured system with wrong packages. Thank you.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are
Thanks for the replies:
You can see my /var/log/udev here: http://pastebin.com/f5b310f3d
Steve, /etc/init/network-interface.conf is not present in my system!
apt-cache policy ifupdown
ifupdown:
Installed: 0.7~alpha3
Candidate: 0.7~alpha3
Version table:
*** 0.7~alpha3 0
100
@Alfredo Pironti:
Yes. This file contains loopback interface declaration.
@Steve Langasek
/etc/init/network-interface.conf is not present in my system too.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug
If you lack /etc/init/network-interface.conf, something is very wrong
with your packages. This bug is about issues in Karmic resulting from
the update to fix bug 461725, and you seem to be running Lucid
(according to your apt-cache policy). However, on top of that, ifupdown
version 0.7~alpha3
Same here (cups, kvm). I'm rather surprised this bug isn't marked as
critical: we're talking about a large part of operating system services,
and this may also produce security issues (firewall not starting etc).
At least they could revert to version 0.6.3-10 as a temporary fix.
--
upstart not
Some thoughts about this issue.
1) When no /etc/network/interfaces is available, It seems that upstart is
waiting for lo to be brought up before starting services; however network
manager, responsible for bringing up lo is not started by upstart; creating the
circular dependency.
2) When
I have /etc/network/interfaces and upstart not start scripts from
/etc/init.d/.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Does your /etc/network/interfaces file contain the following lines?
auto lo
iface lo inet loopback
I have two machines where this workaround is actually working. (But your
experience may tell that my hints are in the wrong direction)
Anyway, I agree this bug is in fact critical, and my
I also agree that this bug is important, and am treating it seriously.
However, flip-flopping the upstart config will only bring back the real
bug that this upload was meant to solve: that for users who *do* have a
correctly configured /etc/network/interfaces, some services would fail
to start at
Well I have the following in my interface file, which seems correct,
but unfortunately I still have the problem.
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
When /etc/network/interfaces is available, some other program, not under
upstart control, brings lo up, and everything seems to work.
No, it's brought up by /etc/init/network-interface.conf.
When no /etc/network/interfaces is available, It seems that upstart is
waiting for lo to be brought
On Fri, Jan 22, 2010 at 08:06:07PM -, Papadakos Panagiotis wrote:
Well I have the following in my interface file, which seems correct,
but unfortunately I still have the problem.
Please attach the output of the command 'sudo initctl list' from the
affected system.
--
Steve Langasek
alsa-mixer-save stop/waiting
avahi-daemon start/running, process 3236
mountall-net stop/waiting
rc stop/waiting
rsyslog start/running, process 2896
tty4 stop/waiting
udev start/running, process 2901
upstart-udev-bridge start/running, process 2859
ureadahead-other stop/waiting
apport start/running
notably absent from the list of services is any mention of 'network-
interface' instances. Please post /var/log/udev from this system.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because
Please also confirm the file /etc/init/network-interface.conf is present
on your system.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Also, what is the output of these commands:
apt-cache policy ifupdown
apt-cache policy upstart
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have 32-bit ubuntu (I realise this isn't relevant, but I don't want
people to get the idea it is a 64-bit problem).
The killer on my own system was bind - when it didn't start all my
custom services on the system were completely wrecked. I am surprised
bind9 wasn't mentioned by anyone else...
same here. downgrading seemed to solve it...
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This is a serious security bug in my opinion. Many network security
processes are started on boot by init via upstart. If you have a server
running fail2ban, for instance, and ssh/etc is not set to be dependent
on fail2ban with the understanding that fail2ban will be initialized on
boot... this
I managed to have access to a machine where the bug does not show up.
That machine has a /etc/network/interfaces file containing exactly the
auto lo \\ iface lo inet loopback lines.
So this seems to be a relevant clue to bug hunting. In which way this
file interferes with localhost being brought
downgrading upstart fixed mine - not sure what the real problem is
though. Wait see?
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Please increase the importance of the bug, since it is really critical
for remotely administrated server systems! If for any reason the server
is rebooted, it cannot be administrated remotely (sshd does not start),
nor other services (e.g. web servers, sql servers etc) are started,
making the
Here are my observations,
Downgrading does NOT solve my problem.
I DO have a /etc/network/interfaces file:
cat /etc/network/interfaces
auto lo
iface lo inet loopback
My install was directly 9.10 (no upgrade) 64 bit.
uname -a : Linux name 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10
If downgrading upstart doesn't solve the problem for you, then you're
experiencing an unrelated issue. Please file a separate bug report.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because
I added the
auto lo
iface lo inet loopback
lines to /etc/network/interfaces file to one of the two server machines
(still no access to the other one, one day downtime now...): now the
services are starting up normally at boot -- but network manager
disappeared from the control panel (NM service
my ssh-service and libvirt-bin service does not start. i downgraded
upstart but both services do not start.
it is really a problem, because the system is a server with a few
virtual images. everything worked until 9.10. now i have the problem,
that i have to start the services manually on reboot.
I just installed 9.10 on a spare drive and sshd would not start on boot;
finally found this downgrade upstart to fix (whew).
I noticed Jon White mentioned in comment #9 of a duplicate of this bug
(500520):
Most notably, the system is never put in a proper runlevel even though
sulogin pops up
I can't use synaptic to downgrade this package (because ssh -X doesn't work any
more).
I thought that this:
apt-get install upstart =0.6.3-10
should work, but apt-get said:
r...@idaho:/home/mateusz# apt-get install upstart =0.6.3-10
Reading package lists... Done
Building dependency tree
nieproszenieja, apt-get install upstart=0.6.3-10 no space - right way.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Thank you very much, now it works.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Just want to confirm same symptoms and same workaround.
A couple of weeks ago dad's Kubuntu doesn't print anymore.
Recognize that cups isn't running.
Verify that it should be (ls /etc/rc*/*cups)
Diagnose some more, realise that runlevel returns unknown
Eventually find this bug
Downgrade to
Yes, well actually guys after I have downgraded to previous version of
upstart, my system was restored back to normal. So looks like at least
sysf.conf is affected. And other users might have the same problem.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
Guys, is this bug responsible for some scripts in sysf.conf and
modprobe.d to be ignored during boot? I am using an ASUS laptop which
has an ambient light sensor problem and I had a script that turned the
sensor off on boot - after latest upgrade it stiooed working and I can
only turn off the
I don't know what you mean by sysf.conf, but no, this bug is unrelated
to any processing of /etc/modprobe.d.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
sysf is a tool that lets you configure some things, in the sys/devices/
folder.
Is there any similar tool that loads scripts of modprobe.d and that
might've been screwed up, at least theoretically?
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
On Tue, Dec 22, 2009 at 07:56:48PM -, Louigi Verona wrote:
sysf is a tool that lets you configure some things, in the sys/devices/
folder.
There is no tool of this name in Ubuntu, so I can't say whether this bug
would affect it.
Is there any similar tool that loads scripts of modprobe.d
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = Steve Langasek (vorlon)
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Solved for me by changing a wrong file /etc/network/interfaces from
auto lo
iface lo inet loopback
post-up iptables-restore /etc/iptables.up.rules
to:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see
Solved for me too. I noticed I was missing my /etc/network/interfaces
file, so I restored it, changed back to the latest version of upstart
and confirmed it's all working correctly.
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
Fails here also. I downgraded upstart to to 0.6.3-10, works again now.
Using Karmic 32bits/PAE
my /etc/network/interfaces (which looks me correct) below:
---
auto lo
iface lo inet loopback
iface eth0
pre-up /usr/sbin/ethtool -s eth0 advertise 0x02b
---
--
upstart not starting
Mine was already looking like your corrected version...
Everything is still broken :s
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
https://bugs.launchpad.net/bugs/497299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
O yes I forgot to mention than downgrading did not work for me, I even got a
seg fault before mount all at boot!
But I'm on lucid amd64 and 0.6.3-10 is not a lucid package (took it from karmic
tree)
--
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
1 - 100 of 110 matches
Mail list logo
