Debian upgrade gone wrong - hostname: Name or service not known
lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org
Wed Nov 4 23:40:29 UTC 2009
On Wed, Nov 04, 2009 at 03:07:58PM -0500, William O'Higgins Witteman wrote:
> On Wed, Nov 04, 2009 at 02:57:58PM -0500, William O'Higgins Witteman wrote:
> >On Tue, Nov 03, 2009 at 04:24:06PM -0500, Madison Kelly wrote:
> >>William O'Higgins Witteman wrote:
> >>>I have encountered one of the rare occasions where a Debian upgrade goes
> >>Check that '/etc/hostname' contains just the name of your system
> >>followed by a new line and nothing else. Then try running 'hostname
> >><machinename>' and hit enter. Then try again.
> >Interestingly, though I got around this problem by stomping on netatalk,
> >it is still broken and causing problems with amavis.
> ># hostname
> > returns the subdomain (this machine is a subdomain - this is as expected)
> ># hostname --fqdn [-f]
> > returns hostname: Name or service not known
> >/etc/hosts looks fine, as does /etc/hostname
> >This stopped working because of a dist-upgrade, no changes to any
> >How does "hostname" work? Why could it be barfing? Thanks again.
> Amusing sidebar - Python is not having any trouble figuring out my
> >>> import socket
> >>> socket.gethostname()
> >>> socket.getfqdn()
> As a side question, why is the 2nd level and top level domain repeated?
Because in fact your configuration is broken.
The Toronto Linux Users Group. Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
More information about the Legacy