lsb_release -a
LSB Version:
Hi Yufei, thanks for your concerns. Hoever, this is not the appropriate
bug to comment on as it has been marked released for a long time, and is
probably not relevant to current versions of Ubuntu. If you are
experiencing an issue with networking, you should file a new bug against
the ifupdown
It seems Ubuntu want us to use network-interface to bring up/down the
interface, i wonder:
after my some tests:
we can use these commands to bring up/down the network INTERFACE, and
not the whole networking service.
restart network-interface INTERFACE=eth0
ifdown eth0; ifup eth0 (your own risk
I'm also still stuck on this problem.
Only way to stop networking that works on 12.04.2 LTS is /etc/init.d/networking.
Restarting networking is also done only by /etc/init.d/networking.
skomatsu@tokito:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu
I've missed writing sysv-rc and sysvinit-utils version.
$ dpkg -l | grep sysv
ii sysv-rc 2.88dsf-13.10ubuntu11.1
System-V-like runlevel change mechanism
ii sysvinit-utils2.88dsf-13.10ubuntu11.1
System-V-like utilities
--
You received
I am also still having this issue as well:
$ service networking restart
stop: Unknown instance:
networking stop/waiting
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04.1 LTS
Release:12.04
Codename: precise
$ dpkg -l sysvinit\* |
** Changed in: sysvinit (Ubuntu)
Assignee: Girish Sanenahalli (girish-cs7036) = Clint Byrum (clint-fewbar)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/440179
Title:
service fails to
** Changed in: sysvinit (Ubuntu)
Assignee: Clint Byrum (clint-fewbar) = Girish Sanenahalli (girish-cs7036)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/440179
Title:
service fails to
I still have the same problem on Precise:
$ sudo service networking restart
stop: Unknown instance:
networking stop/waiting
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04.1 LTS
Release:12.04
Codename: precise
$ uname -a
Linux
Seems like the 'service' command should be smarter, and map to the
sysvinit way in the same way that invoke-rc.d does for packages.
restart is usually expected to start the service if it isn't started,
but by passing directly through to upstart's restart, we are breaking
that assumption, leading
** Changed in: sysvinit (Ubuntu)
Status: Triaged = In Progress
** Changed in: sysvinit (Ubuntu)
Assignee: (unassigned) = Clint Byrum (clint-fewbar)
--
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 sysvinit - 2.88dsf-13.10ubuntu5
---
sysvinit (2.88dsf-13.10ubuntu5) precise; urgency=low
* d/service/service: Updated to use 'stop/start' instead of passing
restart directly through to upstart. (LP: #440179)
* d/service/service.8: Updated man
Running Ubuntu Server 64-bit 11.04. Same issue with the idmapd service
when calling:
service idmapd restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/440179
Title:
service fails to
I submitted a question on this to source package upstart. The problem
seems to stem from 'service' using the upstart command 'restart' whose
documentation states (man restart):
Note that this command can only be used when there is an instance of
JOB, if there is none then it returns an error
Same issue here with OpenSSH (sudo service ssh ...), running Ubuntu Server
10.04 on a VM.
Using /etc/init.d/ssh ... instead
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/440179
Title:
service
I have this problem as wekk. Ubuntu 10.10 (Desktop).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/440179
Title:
service fails to start/stop/restart networking daemon
To manage notifications
Any solution to this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/440179
Title:
service fails to start/stop/restart networking daemon
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have this issue as well
Ubuntu Server 10.10
/etc/init.d/networking restart -- works
service networking restart -- unknown instance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/440179
Title:
I'm also seeing this with several guest machines that I moved to a
different host. I change the networking config and then this started to
occur. I removed two NICs and added a new one. It currently has only one
NIC. This was needed for virt-manager to associate the guest with the
proper network
Seeing the same as Simone F. in #5 (note: /etc/init.d/networking start
does work)
Seeing output of initctl list | grep network as Jon Watte (#9) ... but
not the other things (e.g. ifup workin as expected. nothing in
/var/log/boot)
meanwhile starting/stopping each interface manually as follows
I'm seeing the same symptoms as Jon Watte in a clone of a KVM VM running
10.04. The original VM works fine.
--
service fails to start/stop/restart networking daemon
https://bugs.launchpad.net/bugs/440179
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am also stuck on this problem. I installed 10.04 LTS x64 in a basic (text
mode) install on a VMWare vCenter virtual machine.
The initial machine works.
When I clone this machine, and boot the clone, the clone does not get working
networking.
As part of trying to diagnose/fix this, I'm running
More information. Apparently, the system has gotten into a confused
state:
initctl list | grep network shows:
network-interface (lo) start/running
network-interface (eth1) start/running
network-interface-security start/running
networking stop/waiting
ifup eth1 prints:
Ignoring unknown inteface
The same here. How is supossed that we can restart networking
configuration Neither /etc/init.d/networking or stop networking
works.
--
service fails to start/stop/restart networking daemon
https://bugs.launchpad.net/bugs/440179
You received this bug notification because you are a member of
24 matches
Mail list logo
