Re: No address associated with hostname

A bit strange: I did not see messages for a few days and now I get a lot.

2017-05-24 0:14 GMT+02:00 Matthias Andree <[email protected]>:

> Am 24.05.2017 um 00:01 schrieb Cecil Westerhof:
> > 2017-05-23 23:20 GMT+02:00 Matthias Andree <[email protected]>:
> >
> >> Am 23.05.2017 um 21:20 schrieb Cecil Westerhof:
> >>> 2017-05-22 20:47 GMT+02:00 Cecil Westerhof <[email protected]>:
> >>>
> >>>> I migrated to another machine and now leafnode does not work anymore.
> >>>>
> >>>> With ‘fetchnews -vvvv’ I get (I renamed my fqdn):
> >>>> leafnode 1.11.10: verbosity level is 4, debugmode is 0
> >>>> try_lock(timeout=5), fqdn="demo.example.com"
> >>>> news: connecting to port nntp...
> >>>> warning: news: cannot resolve host name: No address associated with
> >>>> hostname
> >>>> news: connection failed.
> >>>> WARNING: some servers have not been queried!
> >>>> wrote active file with 29971 lines
> >>>> Started process to update overview data in the background.
> >>>> Network activity has finished.
> >>>>
> >>>>
> >>>> What is happening here and how do I solve that?
> >>>>
> >>> ​Also is there a way to display the value of hostname?
> >>>
> >> I appears in verbose logging (syslog, through DEBUG severity) if you run
> >> one of the nontrivial leafnode programs with the environment variable
> >> LN_DEBUG_QUALIFICATION set and not empty. texpi
> ​​
> re or fetchnews should
> >> work for that.
> >>
> >> Be sure to set up your syslog to capture debug logging, most default
> >> syslog configurations discard debug severity.
> >>
> > ​When I try that I get to see:
> >     May 23 23:51:14 munus.decebal.nl fetchnews[25709]: canonical
> hostname:
> > munus.decebal.nl
>
> That's your own, and could be resolved at least locally. I'm not
> authoritative for decebal.nl, but it looks plausible.
>
> >     May 23 23:51:14 munus.decebal.nl fetchnews[25709]: warning: news:
> > cannot resolve host name: No address associated with hostname
> That is for an upstream server. There seems to be a "server = news" line
> in your leafnode configuration, and that name "news" cannot be resolved
>

​No the only server line is:
    server   = news.eternal-september.org

​


> given your current resolver configuration (predominantly
> /etc/resolv.conf, but also /etc/host.conf and /etc/nsswitch.conf and
> possibly unbound/bind/dnsmasq DNS configuration).  This is where you put
> the name of your upstream news server that you intend to download news
> from.


​I do not think that this is the problem, because when I give:
    ​telnet news.eternal-september.org nntp
I get:
    Trying 213.239.209.88...
    Connected to news.eternal-september.org.
    Escape character is '^]'.
    200 news.eternal-september.org InterNetNews NNRP server INN 2.7.0
(20170224 snapshot) ready (posting ok)​



Easiest to put a FQDN on the "server = ..." line.
>

​news.eternal-september.org is a FQDN.

-- 
Cecil Westerhof
-- 
_______________________________________________
leafnode-list mailing list
[email protected]
https://krusty.dt.e-technik.tu-dortmund.de/mailman/listinfo/leafnode-list
http://leafnode.sourceforge.net/