Could not acquire the NetworkManager service as it is already taken

Bug #264543 reported by moose
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

To get an ip address I have to
restart the network manager. Once this is done everything works.

This was found in syslog:
Aug 29 14:39:53 strap NetworkManager: <WARN>
nm_dbus_manager_start_service(): Could not acquire the NetworkManager
service as it is already taken.
Aug 29 14:39:53 strap NetworkManager: <info> disconnected by the system
bus.

that just repeats until I restart NetworkManager.

see attached part of syslog showing from broken to working. did this:
sudo invoke-rc.d NetworkManager restart
in between.

this is on intrepid alpha 4 with all updates as of AUG 30, 2008 including 2.6.27-2 kernel.

Revision history for this message
moose (snyderra) wrote :
Revision history for this message
moose (snyderra) wrote :

just updated on 6 sept 2008 which should be alpha 5. rebooted. still the same repeating 2 lines. did the restart and noticed this in the logs.

Sep 6 14:30:36 strap kernel: [ 118.641130] skge eth0: disabling interface
Sep 6 14:30:36 strap kernel: [ 118.647171] NetworkManager[4878]: segfault at 18 ip b7e3b154 sp bf925800 error 4 in libdbus-1.so.3.4.0[b7e1f000+36000]
Sep 6 14:30:41 strap kernel: [ 123.716387] skge eth0: enabling interface
Sep 6 14:30:41 strap kernel: [ 123.721308] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 6 14:30:43 strap kernel: [ 125.562251] skge eth0: Link is up at 100 Mbps, full duplex, flow control none
Sep 6 14:30:43 strap kernel: [ 125.563418] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Revision history for this message
Alexander Sack (asac) wrote :

how many NetworkManager processes are running when you see this message?

is this happening after a clean reboot top?

Changed in network-manager:
status: New → Incomplete
Revision history for this message
moose (snyderra) wrote : Re: [Bug 264543] Re: Could not acquire the NetworkManager service as it is already taken

one. clean reboot.
I rebooted then did the following:
snyderra@strap:~$ ps aux | grep NetworkManager
root 4749 0.6 0.1 14684 2492 ? Ssl 20:36 0:00
/usr/sbin/NetworkManager
root 4759 0.2 0.1 6716 2924 ? S 20:36 0:00
/usr/sbin/nm-system-settings --config
/etc/NetworkManager/nm-system-settings.conf
snyderra 5606 0.0 0.0 3236 788 pts/0 R+ 20:37 0:00 grep
NetworkManager
snyderra@strap:~$
snyderra@strap:~$ dmesg > before.txt
snyderra@strap:~$ sudo invoke-rc.d NetworkManager restart
[sudo] password for snyderra:
Restarting Network connection manager daemon: NetworkManager.
snyderra@strap:~$ dmesg > after.txt
snyderra@strap:~$ diff before.txt after.txt
455a456,461
> [ 176.334289] skge eth0: disabling interface
> [ 176.339917] NetworkManager[4749]: segfault at 18 ip b7eba154 sp
bfca4a70 error 4 in libdbus-1.so.3.4.0[b7e9e000+36000]
> [ 181.377207] skge eth0: enabling interface
> [ 181.382786] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 183.100008] skge eth0: Link is up at 100 Mbps, full duplex, flow
control none
> [ 183.100008] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
snyderra@strap:~$

before.txt and after.txt attached.

On Sat, Sep 6, 2008 at 7:48 PM, Alexander Sack <email address hidden> wrote:

> how many NetworkManager processes are running when you see this message?
>
> is this happening after a clean reboot top?
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>
> --
> Could not acquire the NetworkManager service as it is already taken
> https://bugs.launchpad.net/bugs/264543
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
moose (snyderra) wrote :

is this a dupe of 261808. I just submitted one and apport says that it was a
dupe. I cannot check because launchpad says that I dont have permission to
view https://bugs.launchpad.net/bugs/261808

I booted up alpha 5 live cd. it does the same thing in live session mode.
installed alpha 5 and it still acts the same but segfaults in a different
location. see below.

Sep 7 10:51:59 strap kernel: [ 140.423174] NetworkManager[5142]: segfault
at 18 ip b7fb0154 sp bfc998c0 error 4 in libdbus-1.so.3.4.0[b7f94000+36000]

On Sat, Sep 6, 2008 at 8:44 PM, Rob Snyder <email address hidden> wrote:

> one. clean reboot.
> I rebooted then did the following:
> snyderra@strap:~$ ps aux | grep NetworkManager
> root 4749 0.6 0.1 14684 2492 ? Ssl 20:36 0:00
> /usr/sbin/NetworkManager
> root 4759 0.2 0.1 6716 2924 ? S 20:36 0:00
> /usr/sbin/nm-system-settings --config
> /etc/NetworkManager/nm-system-settings.conf
> snyderra 5606 0.0 0.0 3236 788 pts/0 R+ 20:37 0:00 grep
> NetworkManager
> snyderra@strap:~$
> snyderra@strap:~$ dmesg > before.txt
> snyderra@strap:~$ sudo invoke-rc.d NetworkManager restart
> [sudo] password for snyderra:
> Restarting Network connection manager daemon: NetworkManager.
> snyderra@strap:~$ dmesg > after.txt
> snyderra@strap:~$ diff before.txt after.txt
> 455a456,461
> > [ 176.334289] skge eth0: disabling interface
> > [ 176.339917] NetworkManager[4749]: segfault at 18 ip b7eba154 sp
> bfca4a70 error 4 in libdbus-1.so.3.4.0[b7e9e000+36000]
> > [ 181.377207] skge eth0: enabling interface
> > [ 181.382786] ADDRCONF(NETDEV_UP): eth0: link is not ready
> > [ 183.100008] skge eth0: Link is up at 100 Mbps, full duplex, flow
> control none
> > [ 183.100008] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> snyderra@strap:~$
>
> before.txt and after.txt attached.
>
>
> On Sat, Sep 6, 2008 at 7:48 PM, Alexander Sack <email address hidden> wrote:
>
>> how many NetworkManager processes are running when you see this message?
>>
>> is this happening after a clean reboot top?
>>
>> ** Changed in: network-manager (Ubuntu)
>> Status: New => Incomplete
>>
>> --
>> Could not acquire the NetworkManager service as it is already taken
>> https://bugs.launchpad.net/bugs/264543
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>

Revision history for this message
Alexander Sack (asac) wrote :

i opened bug 261808 up now. Does this still happen in latest intrepid?

Revision history for this message
moose (snyderra) wrote :

this happened in a fresh install of alpha 5 plus updates. restarted
the network manager and the crash report tool took over from there and
reported bug 267508. following emails reported that it was a dupe of
bug 261808. so short answer is yes it's still happening. only
difference is that for me networking was not working to start with,
but after restarting network manager it does work.

should this bug be separate or is it related to the original bug report?

On Wed, Sep 10, 2008 at 8:59 PM, Alexander Sack <email address hidden> wrote:
>
> i opened bug 261808 up now. Does this still happen in latest intrepid?
>
> --
> Could not acquire the NetworkManager service as it is already taken
> https://bugs.launchpad.net/bugs/264543
> You received this bug notification because you are a direct subscriber
> of the bug.

Revision history for this message
Robb Munson (r.munson) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Revision history for this message
vbdanl (vbdanl-yahoo) wrote :

I get the same error with the latest 2.6.27.11 kernel. When the wireless connection is active on my desktop, i can ping google.com successfully, but will see nm-system-setti[xxx] errors in dmesg. if i try to open up firefox or a new terminal, the circle hourglass appears for a few seconds, then goes away and the terminal or firefox is not opened (as if i didn't try to open it in the first place). continue to see additional nm-system-setti segfault errors in dmesg. same pc works fine with 8.04.

Revision history for this message
moose (snyderra) wrote :

sorry new computer with different hardware. cant help.

Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

tags: added: needs-devrelease-testing
Changed in network-manager (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.