Hi All,
I have a coupla queries about my 2 latest installs of CentOS 4-3. When I first installed and logged in as the initial user, everything went well, and the system was fast. A reboot, and 2nd login gave the same. But, upon connecting to the net, the system hung at sendmail for almost 4mins, and then gave an error at login about not finding the host, and that Gnome may not work correctly, with options of Continue or try Again. After that, the system has become extensively slow. Any ideas why this would be this way? This is the 2nd machine, different locations, different media, that this has happened. Rather annoying. Cheers.
Mark Sargent.
Mark Sargent wrote:
Hi All,
I have a coupla queries about my 2 latest installs of CentOS 4-3. When I first installed and logged in as the initial user, everything went well, and the system was fast. A reboot, and 2nd login gave the same. But, upon connecting to the net, the system hung at sendmail for almost 4mins, and then gave an error at login about not finding the host, and that Gnome may not work correctly, with options of Continue or try Again. After that, the system has become extensively slow. Any ideas why this would be this way? This is the 2nd machine, different locations, different media, that this has happened. Rather annoying. Cheers.
Do the affected boxes have a proper hostname?
cat /etc/sysconfig/network
I seem to recall seeing that gnome complaint under such circumstances...
-Andy
On Tuesday 02 May 2006 10:08, Andy Green wrote:
Mark Sargent wrote:
Hi All,
I have a coupla queries about my 2 latest installs of CentOS 4-3. When I first installed and logged in as the initial user, everything went well, and the system was fast. A reboot, and 2nd login gave the same. But, upon connecting to the net, the system hung at sendmail for almost 4mins, and then gave an error at login about not finding the host, and that Gnome may not work correctly, with options of Continue or try Again. After that, the system has become extensively slow. Any ideas why this would be this way? This is the 2nd machine, different locations, different media, that this has happened. Rather annoying. Cheers.
Do the affected boxes have a proper hostname?
cat /etc/sysconfig/network
I seem to recall seeing that gnome complaint under such circumstances...
-Andy
This sort of timeouts is usually due to nameresolution problems, either it's own name or other names, and Sendmail relies heavily on it. As I recall RedHat is known for not putting a proper entry for it's own name in /etc/hosts, so check this. Also check the output of the 'hostname' command. Then check that the entries in /etc/resolv.conf point to the right dns-servers, either your internal dns-server(s) or your isp's.
regards,
On 02/05/06, Paul Schoonderwoerd paul@pollux-it.nl wrote:
This sort of timeouts is usually due to nameresolution problems, either it's own name or other names, and Sendmail relies heavily on it. As I recall RedHat is known for not putting a proper entry for it's own name in /etc/hosts, so check this. Also check the output of the 'hostname' command. Then check that the entries in /etc/resolv.conf point to the right dns-servers, either your internal dns-server(s) or your isp's.
Seconded that. If your /etc/hosts is empty then add something like:
127.0.0.1 localhost.localdomain localhost youserver.yourdomain yourserver
You may ad more lines including other servers in format "IP ServerName.Server.Domain" One IP may have more than one name. Of course starting bind also is a help as by default it is set for cahing name server. HTH.
-- Sudev Barar Learning Linux
Paul Schoonderwoerd wrote:
On Tuesday 02 May 2006 10:08, Andy Green wrote:
Do the affected boxes have a proper hostname?
cat /etc/sysconfig/network
I seem to recall seeing that gnome complaint under such circumstances...
-Andy
This sort of timeouts is usually due to nameresolution problems, either it's own name or other names, and Sendmail relies heavily on it. As I recall RedHat is known for not putting a proper entry for it's own name in /etc/hosts, so check this. Also check the output of the 'hostname' command. Then check that the entries in /etc/resolv.conf point to the right dns-servers, either your internal dns-server(s) or your isp's.
Hi All,
/etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost
/etc/resolv.conf ; generated by /sbin/dhclient-script search BigPond nameserver 10.0.0.138
[ozboy@home-hehbbzsuy7 sysconfig]$ hostname home-hehbbzsuy7
The /etc/resolv.conf settings are correct. Cheers.
Mark Sargent.
On Tuesday 02 May 2006 10:45, Mark Sargent wrote:
Paul Schoonderwoerd wrote:
On Tuesday 02 May 2006 10:08, Andy Green wrote:
Do the affected boxes have a proper hostname?
cat /etc/sysconfig/network
I seem to recall seeing that gnome complaint under such circumstances...
-Andy
This sort of timeouts is usually due to nameresolution problems, either it's own name or other names, and Sendmail relies heavily on it. As I recall RedHat is known for not putting a proper entry for it's own name in /etc/hosts, so check this. Also check the output of the 'hostname' command. Then check that the entries in /etc/resolv.conf point to the right dns-servers, either your internal dns-server(s) or your isp's.
Hi All,
/etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost
/etc/resolv.conf ; generated by /sbin/dhclient-script search BigPond nameserver 10.0.0.138
[ozboy@home-hehbbzsuy7 sysconfig]$ hostname home-hehbbzsuy7
The /etc/resolv.conf settings are correct. Cheers.
Mark Sargent.
Try putting an entry for home-hehbbzsuy7 with the ip-address in /etc/hosts. Possibly also add the Fully Qualified Domain Name (fqdn) in there, something like 192.168.1.5 home-hehbbzsuy7.snow.email.ne.jp home-hehbbzsuy7
Is the dns-server really reachable on/via 10.0.0.138 ? Try 'dig ns.nl.net' and see if it resolves to 193.78.240.1. Check the last four lines of the output of this command for te query-time and the server which was queried.
Paul Schoonderwoerd wrote:
Try putting an entry for home-hehbbzsuy7 with the ip-address in /etc/hosts. Possibly also add the Fully Qualified Domain Name (fqdn) in there, something like 192.168.1.5 home-hehbbzsuy7.snow.email.ne.jp home-hehbbzsuy7
This is a local machine and there is no actual registered domain name, only localhost.localdomain. I also should add, that I was not trying to get sendmail to run at all, as I'm not using it. With the IP being dynamic, how would adding a static IP entry in /etc/hosts help?
Is the dns-server really reachable on/via 10.0.0.138 ?
yes, as it is the DSL router which acts as both Gateway and DHCP server as well as DNS
Try 'dig ns.nl.net' and see if it resolves to 193.78.240.1. Check the last four lines of the output of this command for te query-time and the server which was queried.
[ozboy@mumpc ~]$ dig ns.nl.net
; <<>> DiG 9.2.4 <<>> ns.nl.net ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3406 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION: ;ns.nl.net. IN A
;; ANSWER SECTION: ns.nl.net. 32324 IN A 193.78.240.1
;; Query time: 29 msec ;; SERVER: 10.0.0.138#53(10.0.0.138) ;; WHEN: Tue May 2 20:15:13 2006 ;; MSG SIZE rcvd: 43
hostname "name" changed the hostname,
[root@home-hehbbzsuy7 ~]# hostname mumpc [root@home-hehbbzsuy7 ~]# hostname mumpc
but it returned to original,
[ozboy@home-hehbbzsuy7 ~]$ hostname home-hehbbzsuy7
upon reboot. How is this changed permanently? Cheers.
Mark Sargent
Mark Sargent wrote:
but it returned to original,
[ozboy@home-hehbbzsuy7 ~]$ hostname home-hehbbzsuy7
upon reboot. How is this changed permanently? Cheers.
/etc/sysconfig/network
Your hostname looks like it is getting set by dhcp from your ISP though.
There's a magic keyword you can stick in /etc/dhcpcd.conf or somesuch to force the hostname not to get overwritten. If you have a look in fedora-list archives I recall posting about it a couple of months ago.
-Andy
Mark Sargent wrote on Tue, 02 May 2006 20:29:08 +1000:
I also should add, that I was not trying to get sendmail to run at all, as I'm not using it.
Then disable it! This at least helps with sendmail ;-)
Kai
Paul Schoonderwoerd wrote on Tue, 2 May 2006 11:06:20 +0200:
192.168.1.5 home-hehbbzsuy7.snow.email.ne.jp home-hehbbzsuy7
But he's using dhcp, isn't he? So putting static IPs in there, won't help much, won't it? That's also why this problem happened in the first place. If you don't use dhcp you enter all necessary data in the installation screen and all is well later on.
Kai
Kai Schaetzl wrote:
But he's using dhcp, isn't he? So putting static IPs in there, won't help much, won't it? That's also why this problem happened in the first place. If you don't use dhcp you enter all necessary data in the installation screen and all is well later on.
Hi All,
yes, that's correct, I'm using DHCP. I'm still confused, though, as I've used DHCP many times before, without this happening. How do I resolve this, Kai? Cheers.
Mark Sargent.
Mark Sargent wrote:
But he's using dhcp, isn't he? So putting static IPs in there, won't
yes, that's correct, I'm using DHCP. I'm still confused, though, as I've used DHCP many times before, without this happening. How do I resolve this, Kai? Cheers.
Your ISP DHCP server basically decides what it will overwrite in your network-related configuration. Here is the message I was thinking of earlier to allow you to defeat that for specific settings:
http://www.redhat.com/archives/fedora-list/2006-April/msg02598.html
-Andy
Andy Green wrote:
Your ISP DHCP server basically decides what it will overwrite in your network-related configuration.
The router @ my end serves the DHCP IPs, not the ISPs server. I can access the router and change the scope etc.
Here is the message I was thinking of earlier to allow you to defeat that for specific settings:
http://www.redhat.com/archives/fedora-list/2006-April/msg02598.html
Thanx
Mark Sargent
Mark Sargent wrote on Tue, 02 May 2006 21:29:56 +1000:
How do I resolve this, Kai?
I can't tell you since I almost never use dhcp. I can just say that this problem never happens with static IP setups. You can set the hostname with "hostname <put your hostname here>" and then "service network restart". This will be reset on next boot, though. To change it for longer you have to edit /etc/sysconfig/network if i recall right. However, I don't know if dhcp will interfere here as well.
Kai
Mark Sargent wrote on Tue, 02 May 2006 18:45:26 +1000:
The /etc/resolv.conf settings are correct.
But the hostname isn't. sendmail needs an FQDN to work correctly.
Kai
-
Andy Green -
Kai Schaetzl -
Mark Sargent -
Paul Schoonderwoerd -
Sudev Barar