In some of the cases I did set up /etc/hosts. In all cases I did not change the VM setting. All hosts are bridged. I did change the DNS servers. In the dynamic IP, both servers are in Toronto, where on the static systems, one of the DNS servers is in New York. The DNS servers I am using is the ones I am using in all our systems. The VMs are RHEL systems not using network manager.
One possible clue is that these systems are all cloned. There is an eth0 and eth0.bak. In most of the VMs I manually delete the eth0.bak (from /etc/sysconfig/devices and /etc/sysconfig/profiles/default as these are hard linked. Additionally, I found that the systems had an incorrect /etc/resolv.conf. system-config-network should hard link /etc/resolv.conf and /etc/sysconfig/profiles/default/resolv.conf But since these systems were cloned VMs, VMWare made some changes, so it looks like /etc/resolv.conf was incorrect even though system-config-network had the correct data. On 05/04/2011 01:04 PM, Matthew Gillen wrote: > On 05/04/2011 12:39 PM, Jerry Feldman wrote: >> At work I have a number of VMs. When these VMs were configured with >> dynamic IP addresses, they booted very quickly, but now they tend to >> wait on sendmail and sm_client to time out. Everything else is fine. I >> can even ssh into the VM while it is waiting for sendmail. Sendmail is >> not configured. >> >> Why would sendmail (and sm_client) timeout on a static IP but not with a >> dynamic IP. > Because sendmail is obnoxious in it's use of dns/name-resolution on > startup. I've had this problem with sendmail going back as long as I've > been using it where if it can't look up the local hostname (or if the > hostname is misconfigured), then it just hangs on startup. > > So I'm guessing you were using network manager when you used the DHCP > addresses, and NM rewrites the /etc/hosts file when it gets an address. > > If you're still using NM with your static addresses, be aware that NM > has (until very recently) had some obnoxious behavior w.r.t. /etc/hosts > and static ip configurations (e.g. re-writing /etc/hosts such that the > hostname always pointed to 127.0.0.1 instead of the public IP). > > In short, I think it's a DNS/name resolution issue. Setting /etc/hosts > correctly should fix it, but watch out for NM rewriting it (and > re-breaking it in many cases). > On 05/04/2011 01:08 PM, Mark Komarinski wrote: > On 05/04/2011 12:39 PM, Jerry Feldman wrote: >> At work I have a number of VMs. When these VMs were configured with >> dynamic IP addresses, they booted very quickly, but now they tend to >> wait on sendmail and sm_client to time out. Everything else is fine. I >> can even ssh into the VM while it is waiting for sendmail. Sendmail is >> not configured. >> >> Why would sendmail (and sm_client) timeout on a static IP but not with a >> dynamic IP. > It's likely DNS. I don't know how you had it set up before, but did you > happen to change from NAT to Bridge at the same time as you went to > static IP addresses? -- Jerry Feldman <[email protected]> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
_______________________________________________ Discuss mailing list [email protected] http://lists.blu.org/mailman/listinfo/discuss
