On 14/10/2020 12.31, Carlos E. R. wrote:
On 14/10/2020 11.13, Carlos E. R. wrote:
I do again the edit to dnsmasq, but the name keeps. I check the log to see when did the name change:
...
At zero hours of Tuesday - that was when syslog became aware of the name change.
Another log shows the instant the problem happened: +++................ <7.7> 2020-10-12T20:28:01.430137+02:00 Telcontar fetchnews 32349 - - config: debugmode is 1 <7.7> 2020-10-12T20:28:01.430334+02:00 Telcontar fetchnews 32349 - - config: maxfetch is 5000 <7.7> 2020-10-12T20:28:01.430457+02:00 Telcontar fetchnews 32349 - - config: maxage is 0 <7.7> 2020-10-12T20:28:01.430572+02:00 Telcontar fetchnews 32349 - - config: postings have max. 500000 bytes <7.7> 2020-10-12T20:28:01.430683+02:00 Telcontar fetchnews 32349 - - config: timeout_long is 100 days <7.7> 2020-10-12T20:28:01.430801+02:00 Telcontar fetchnews 32349 - - config: timeout_fetchnews is 90 seconds <7.7> 2020-10-12T20:28:01.430914+02:00 Telcontar fetchnews 32349 - - config: newsadmin is postmaster@telcontar.valinor <7.7> 2020-10-12T20:28:01.431026+02:00 Telcontar fetchnews 32349 - - config: allow_8bit_headers is 1 <7.7> 2020-10-12T20:28:04.430540+02:00 Telcontar fetchnews 32349 - - leafnode 1.11.11: verbosity level is 2, debugmode is 1 <7.7> 2020-10-12T20:28:04.430792+02:00 Telcontar fetchnews 32349 - - try_lock(timeout=5), fqdn="Telcontar.valinor" <====== ... <7.7> 2020-10-12T20:32:02.145306+02:00 Telcontar fetchnews 32562 - - config: allow_8bit_headers is 1 <7.2> 2020-10-12T20:32:02.145361+02:00 Telcontar fetchnews 32562 - - #012Leafnode must have a fully-qualified and globally unique domain name,#012not just "localhost".#012Edit your /etc/hosts file to add a unique, fully qualified domain name.#012"localhost.localdomain" or thereabouts will not work;#012it's qualified, but not unique.#012Please see the README-FQDN file for details. ................++- So between 20:28:04 and 20:32:02 hours of Monday 12. If it were resolv.conf: cer@Telcontar:~> l /etc/resolv.conf -rw-r--r-- 1 root root 1204 Oct 12 19:39 /etc/resolv.conf cer@Telcontar:~> so that was not the culprit. Could be dnsmasq, but that one I don't have the significant timestamp of my edit (I changed it later more than once). Still, I think that was it, but I can't reproduce the problem.
So no idea what caused the problem... :-(
-- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)