Bug 135754 - Networkmanager problem
Summary: Networkmanager problem
Status: RESOLVED DUPLICATE of bug 134170
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Alpha 3
Hardware: x86-64 Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Timo Hoenig
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-28 22:05 UTC by Joop Boonen
Modified: 2005-11-30 12:32 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
/var/log/messages (281.56 KB, text/plain)
2005-11-30 12:24 UTC, Martin Mrazik 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joop Boonen 2005-11-28 22:05:04 UTC 
When bothnetworkmanager and ifplugd are running the network isn't working properly. This is the deafult set-up by the way. When dhcp is selected the network works for a short while. After some time it's down again. A /etc/init.d/network restart will let it work again. Than it will back to the  169.254.0.0/16 network. 

Message in /var/log/messages: 
Nov 28 22:54:03 sempron NetworkManager: <information>   Caught SIGINT/SIGTERM
Nov 28 22:54:03 sempron NetworkManager: <information>   Caught terminiation signal
Nov 28 22:54:03 sempron NetworkManager: <debug info>    [1133214843.373265]  (): Open Sockets List:
Nov 28 22:54:03 sempron NetworkManager: <debug info>    [1133214843.373298]  (): Open Sockets List Done.
Nov 28 22:54:03 sempron NetworkManager: <information>   Deactivating device eth0.
Nov 28 22:54:03 sempron NetworkManager: <WARNING>         (): Could not remove forwarders for zone '.'.  Error: 'The name com.redhat.named was not provided by any .service files'.

This might also be a misconfig.

When i shutdown networkmanager this problem doesn't appear anymore /etc/init.d/networkmanager stop

I  presume this problem also occurs in i386. I will try this later.
Comment 1 Timo Hoenig 2005-11-29 11:13:26 UTC 
Since YaST does not yet set network devices to "managed" by default you have to do it manually.  You can set a device to "managed" by using the "Managed by NetworkManager" button in the network configuration for YaST.

Afterwards rcnetwork will not touch the interfaces and NetworkManager does the configuration.

Robert, any idea about the named warning?
Comment 2 Martin Mrazik 2005-11-30 12:21:50 UTC 
I have the same problem with alpha3 and default installation with dhcp.

However my /var/log/messages looks slightly diferent - no SIGINT/SIGTERM no named warning (see the attachment). After I have killed NetworkManager it seems to be working fine (i've killed it about "Nov 30 12:15:49").
Comment 3 Martin Mrazik 2005-11-30 12:24:08 UTC 
Created attachment 59167 [details]
/var/log/messages
Comment 4 Timo Hoenig 2005-11-30 12:32:06 UTC 
Closing as duplicate of #134170.

Joop, please report if you still encounter the named issue.

*** This bug has been marked as a duplicate of 134170 ***