No route to host, despite being pingable

Issues related to configuring your network
Post Reply
Quitch
Posts: 76
Joined: 2006/04/28 16:50:40

No route to host, despite being pingable

Post by Quitch » 2007/03/26 13:27:39

The mailq on a CentOS 4.4 machine I look at has become... pretty big. It is filled with messages about [i]Deferred: machine.domain.com.: No route to host[/i]

This made sense at first because while this machine had a hosts entry for the machinename, it didn't have one for the fully qualified domain name. I added this to the hosts entry for the machine and was now able to ping it.

However, running sendmail -q -v I still receive "No route to host" messages.

Help.

pjwelsh
Posts: 2620
Joined: 2007/01/07 02:18:02
Location: Central IL USA

Re: No route to host, despite being pingable

Post by pjwelsh » 2007/03/26 15:27:08

Check to see if sendmail is "chrooted". If so, you may have some old files in there that do not have correct info and need to be updated. I'm not sure about sendmail, but postfix warns when file are outdated in /var/log/maillog

Quitch
Posts: 76
Joined: 2006/04/28 16:50:40

Re: No route to host, despite being pingable

Post by Quitch » 2007/03/26 15:40:15

I don't believe sendmail is operating in a chroot environment. I was unable to find any evidence of one, though I am not sure how to make a conclusive check. Certainly when I ran /usr/sbin/sendmail -q -v I received the same error as before, though I don't know if there could be a config somewhich which causes the chroot environment being called, being fairly new to this.

Post Reply

Return to “CentOS 4 - Networking Support”