Hi all,
I have a CentOS 5.4 server-only installation, i.e. no X installed, and for some odd reason /etc/resolve.conf gets overwritten by NetworkManager on a constant basis. I haven't been able to track down how often, but I think it's on the hour, or something.
This is the conents of the file right now:
# Generated by NetworkManager
# No nameservers found; try putting DNS servers into your # ifcfg files in /etc/sysconfig/network-scripts like so: # # DNS1=xxx.xxx.xxx.xxx # DNS2=xxx.xxx.xxx.xxx # DOMAIN=lab.foo.com bar.foo.com
So, I change it to the following:
nameserver 192.168.1.254, save it, and all network functions work fine. But, later on it get's changed again. Running "system-config-network", I can see that the nameserver that I have specified is in there, yet it doesn't show up in /etc/resolve.conf.
I have searched a bit on google, but all the results reveal how to use NetworkManager to setup the nameservers, but now how it get's set automatically. Why does this happen, and how do I stop it from happening?
At Sun, 29 Nov 2009 22:57:23 +0200 CentOS mailing list centos@centos.org wrote:
Hi all,
I have a CentOS 5.4 server-only installation, i.e. no X installed, and for some odd reason /etc/resolve.conf gets overwritten by NetworkManager on a constant basis. I haven't been able to track down how often, but I think it's on the hour, or something.
This is the conents of the file right now:
# Generated by NetworkManager
# No nameservers found; try putting DNS servers into your # ifcfg files in /etc/sysconfig/network-scripts like so: # # DNS1=xxx.xxx.xxx.xxx # DNS2=xxx.xxx.xxx.xxx # DOMAIN=lab.foo.com bar.foo.com
So, I change it to the following:
nameserver 192.168.1.254, save it, and all network functions work fine. But, later on it get's changed again. Running "system-config-network", I can see that the nameserver that I have specified is in there, yet it doesn't show up in /etc/resolve.conf.
I have searched a bit on google, but all the results reveal how to use NetworkManager to setup the nameservers, but now how it get's set automatically. Why does this happen, and how do I stop it from happening?
You probably DON'T want NetworkManager running on a server!
Do this:
# Stop NetworkManager sudo /sbin/service NetworkManager stop # Disable it from starting at boot time sudo /sbin/chkconfig NetworkManager off
And then *manually* set things up.
NetworkManager is meant for things like laptops that are (randomly) connected to this or that WiFi at this or that Internet Cafe, Library, School, Home WiFi, whatever. NetworkManager automagically adjusts things as it encounters different networks, etc. A server will have fixed / static networking and needs no dynamic adjustments.
Rudi Ahlers wrote:
Hi all,
I have a CentOS 5.4 server-only installation, i.e. no X installed, and for some odd reason /etc/resolve.conf gets overwritten by NetworkManager on a constant basis. I haven't been able to track down how often, but I think it's on the hour, or something.
This is the conents of the file right now:
# Generated by NetworkManager
# No nameservers found; try putting DNS servers into your # ifcfg files in /etc/sysconfig/network-scripts like so: # # DNS1=xxx.xxx.xxx.xxx # DNS2=xxx.xxx.xxx.xxx # DOMAIN=lab.foo.com bar.foo.com
So, I change it to the following:
nameserver 192.168.1.254, save it, and all network functions work fine. But, later on it get's changed again. Running "system-config-network", I can see that the nameserver that I have specified is in there, yet it doesn't show up in /etc/resolve.conf.
I have searched a bit on google, but all the results reveal how to use NetworkManager to setup the nameservers, but now how it get's set automatically. Why does this happen, and how do I stop it from happening?
Rudi, As I recall there was a thread about this a few weeks ago. Please show your /etc/sysconfig/network-scripts/ifcfg-ethX contents. Thanks
On 29/11/09 22:43, Rob Kampen wrote:
Rudi Ahlers wrote:
Hi all,
I have a CentOS 5.4 server-only installation, i.e. no X installed, and for some odd reason /etc/resolve.conf gets overwritten by NetworkManager on a constant basis. I haven't been able to track down how often, but I think it's on the hour, or something.
As I recall there was a thread about this a few weeks ago. Please show your /etc/sysconfig/network-scripts/ifcfg-ethX contents.
Add to /etc/sysconfig/network-scripts/ifcfg-ethX The following 2 lines : PEERDNS=no NM_CONTROLLED=no
Line 1 tells the the if commands not to override /etc/resolv.conf Line 2 tells NetworkManager that it doens't have control over that ethernet controller
On Mon, Nov 30, 2009 at 12:13 AM, Tosh toshlinux@gmail.com wrote:
Add to /etc/sysconfig/network-scripts/ifcfg-ethX The following 2 lines : PEERDNS=no NM_CONTROLLED=no
Line 1 tells the the if commands not to override /etc/resolv.conf Line 2 tells NetworkManager that it doens't have control over that ethernet controller
--
Hi Tosh,
As matter of interest, since I don't see those options on our other servers (which doesn't have this behaviour and they're also on CentOS 5.4), are these settings new? OR do I have something else installed that is causing this?
At Mon, 30 Nov 2009 00:55:28 +0200 CentOS mailing list centos@centos.org wrote:
On Mon, Nov 30, 2009 at 12:13 AM, Tosh toshlinux@gmail.com wrote:
Add to /etc/sysconfig/network-scripts/ifcfg-ethX The following 2 lines : PEERDNS=no NM_CONTROLLED=no
Line 1 tells the the if commands not to override /etc/resolv.conf Line 2 tells NetworkManager that it doens't have control over that ethernet controller
--
Hi Tosh,
As matter of interest, since I don't see those options on our other servers (which doesn't have this behaviour and they're also on CentOS 5.4), are these settings new? OR do I have something else installed that is causing this?
You either
A) Don't have NetworkManager installed on the other servers (eg 'rpm -q NetworkManager' yields 'package NetworkManager is not installed')
OR
B) Don't have NetworkManager running on the other servers (eg '/sbin/chkconfig NetworkManager --list' yields 'NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off')
On Mon, Nov 30, 2009 at 1:56 AM, Robert Heller heller@deepsoft.com wrote:
You either
A) Don't have NetworkManager installed on the other servers (eg 'rpm -q NetworkManager' yields 'package NetworkManager is not installed')
OR
B) Don't have NetworkManager running on the other servers (eg '/sbin/chkconfig NetworkManager --list' yields 'NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off')
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
Thanx Robert, so it's safe to remove NetworkManager then? I have done so, and will see if any issues arise. The only files that was removed is:
Removing: NetworkManager i386 1:0.7.0-9.el5 installed 3.3 M NetworkManager x86_64 1:0.7.0-9.el5 installed 3.4 M Removing for dependencies: NetworkManager-glib i386 1:0.7.0-9.el5 installed 154 k NetworkManager-glib x86_64 1:0.7.0-9.el5 installed 161 k
On Mon, Nov 30, 2009 at 2:27 AM, Rudi Ahlers rudiahlers@gmail.com wrote:
On Mon, Nov 30, 2009 at 1:56 AM, Robert Heller heller@deepsoft.com wrote:
You either
A) Don't have NetworkManager installed on the other servers (eg 'rpm -q NetworkManager' yields 'package NetworkManager is not installed')
OR
B) Don't have NetworkManager running on the other servers (eg '/sbin/chkconfig NetworkManager --list' yields 'NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off')
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
Thanx Robert, so it's safe to remove NetworkManager then? I have done so, and will see if any issues arise. The only files that was removed is:
Removing: NetworkManager i386 1:0.7.0-9.el5 installed 3.3 M NetworkManager x86_64 1:0.7.0-9.el5 installed 3.4 M Removing for dependencies: NetworkManager-glib i386 1:0.7.0-9.el5 installed 154 k NetworkManager-glib x86_64 1:0.7.0-9.el5 installed 161 k
-- Kind Regards Rudi Ahlers CEO, SoftDux Hosting Web: http://www.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532 _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
i uninstall NetworkManager as well, but i would think you have bigger problems since it appears you have both the 64bit and 32bit versions of software installed?
On Mon, Nov 30, 2009 at 11:08 AM, Rob Townley rob.townley@gmail.com wrote:
i uninstall NetworkManager as well, but i would think you have bigger problems since it appears you have both the 64bit and 32bit versions of software installed? _______________________________________________
Well, I use a x64 system, and AFAIK, a lot of application automatically instell the i386 version of the files needed, but I could be wrong?
At Mon, 30 Nov 2009 03:08:01 -0600 CentOS mailing list centos@centos.org wrote:
On Mon, Nov 30, 2009 at 2:27 AM, Rudi Ahlers rudiahlers@gmail.com wrote:
On Mon, Nov 30, 2009 at 1:56 AM, Robert Heller heller@deepsoft.com wrote:
You either
A) Don't have NetworkManager installed on the other servers (eg 'rpm -q NetworkManager' yields 'package NetworkManager is not installed')
OR
B) Don't have NetworkManager running on the other servers (eg '/sbin/chkconfig NetworkManager --list' yields 'NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off')
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
Thanx Robert, so it's safe to remove NetworkManager then? I have done so, and will see if any issues arise. The only files that was removed is:
Removing: NetworkManager i386 1:0.7.0-9.el5 installed 3.3 M NetworkManager x86_64 1:0.7.0-9.el5 installed 3.4 M Removing for dependencies: NetworkManager-glib i386 1:0.7.0-9.el5 installed 154 k NetworkManager-glib x86_64 1:0.7.0-9.el5 installed 161 k
-- Kind Regards Rudi Ahlers CEO, SoftDux Hosting Web: http://www.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532 _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
i uninstall NetworkManager as well, but i would think you have bigger problems since it appears you have both the 64bit and 32bit versions of software installed?
For shared libraries this is normal. Generally NOT for programs though -- one or the other, yes (eg 64 bit of this and 32 bit of that).
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Nov 30, 2009, at 7:18 AM, Robert Heller heller@deepsoft.com wrote:
At Mon, 30 Nov 2009 03:08:01 -0600 CentOS mailing list <centos@centos.org
wrote:
On Mon, Nov 30, 2009 at 2:27 AM, Rudi Ahlers rudiahlers@gmail.com wrote:
On Mon, Nov 30, 2009 at 1:56 AM, Robert Heller heller@deepsoft.com wrote:
You either
A) Don't have NetworkManager installed on the other servers (eg 'rpm -q NetworkManager' yields 'package NetworkManager is not installed')
OR
B) Don't have NetworkManager running on the other servers (eg '/sbin/chkconfig NetworkManager --list' yields 'NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off')
Thanx Robert, so it's safe to remove NetworkManager then? I have done so, and will see if any issues arise. The only files that was removed is:
Removing: NetworkManager i386 1:0.7.0-9.el5 installed 3.3 M NetworkManager x86_64 1:0.7.0-9.el5 installed 3.4 M Removing for dependencies: NetworkManager-glib i386 1:0.7.0-9.el5 installed 154 k NetworkManager-glib x86_64 1:0.7.0-9.el5 installed 161 k
i uninstall NetworkManager as well, but i would think you have bigger problems since it appears you have both the 64bit and 32bit versions of software installed?
For shared libraries this is normal. Generally NOT for programs though -- one or the other, yes (eg 64 bit of this and 32 bit of that).
Some apps install 64-bit and 32-bit versions for ABI compatibility and plugins (or IPC). Maybe the OP had a 32-bit gnome app installed?
Firefox is a perfect example of this (wish there were icons for both the 64-bit and 32-bit versions so one could choose which to launch).
With NetworkManager though one can only run one or the other. I believe the default for all dual arch installs is to run the 64-bit version if installed, otherwise the 32-bit version.
-Ross
At Mon, 30 Nov 2009 10:27:27 +0200 CentOS mailing list centos@centos.org wrote:
On Mon, Nov 30, 2009 at 1:56 AM, Robert Heller heller@deepsoft.com wrote:
You either
A) Don't have NetworkManager installed on the other servers (eg 'rpm -q NetworkManager' yields 'package NetworkManager is not installed')
OR
B) Don't have NetworkManager running on the other servers (eg '/sbin/chkconfig NetworkManager --list' yields 'NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off')
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
Thanx Robert, so it's safe to remove NetworkManager then? I have done
For a server, yes. NetworkManager is the system deamon that works with the GNome network management applet that provides the UI to finding and connecting to things like wireless networks. It is mainly only really useful for laptops with wireless networking. It could also be used for things like Air Cards and 'hard networks' (laptops and 'roving' desktops which get pluged into different networks).
so, and will see if any issues arise. The only files that was removed is:
Removing: NetworkManager i386 1:0.7.0-9.el5 installed 3.3 M NetworkManager x86_64 1:0.7.0-9.el5 installed 3.4 M Removing for dependencies: NetworkManager-glib i386 1:0.7.0-9.el5 installed 154 k NetworkManager-glib x86_64 1:0.7.0-9.el5 installed 161 k
Hi,
On Mon, 2009-11-30 at 00:55 +0200, Rudi Ahlers wrote:
On Mon, Nov 30, 2009 at 12:13 AM, Tosh toshlinux@gmail.com wrote:
Add to /etc/sysconfig/network-scripts/ifcfg-ethX The following 2 lines : PEERDNS=no NM_CONTROLLED=no Line 1 tells the the if commands not to override /etc/resolv.conf Line 2 tells NetworkManager that it doens't have control over that ethernet controller
As matter of interest, since I don't see those options on our other servers (which doesn't have this behaviour and they're also on CentOS 5.4), are these settings new? OR do I have something else installed that is causing this?
They are rather old config options. See /usr/share/doc/initscripts-*/sysconfig.txt. It's explain all options using in most of the /etc/sysconfig files.
On Sun, Nov 29, 2009 at 11:43 PM, Rob Kampen rkampen@kampensonline.com wrote:
Rudi, As I recall there was a thread about this a few weeks ago. Please show your /etc/sysconfig/network-scripts/ifcfg-ethX contents. Thanks
Hi Rob,
Here's the contents:
[root@intranet OpenQRM]# more /etc/sysconfig/network-scripts/ifcfg-eth0 # Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ DEVICE=eth0 BOOTPROTO=none HWADDR=00:16:e6:69:49:9a ONBOOT=yes NETMASK=255.255.255.0 IPADDR=192.168.1.250 GATEWAY=192.168.1.254 TYPE=Ethernet DNS=192.168.1.254 DNS=192.168.1.1
-
Rob Kampen -
Rob Townley -
Robert Heller -
Ross Walker -
Rudi Ahlers -
Rudi Ahlers -
Szabo Akos -
Tosh