[Eisfair] Leafnode. Merkwürdige Fetchnews meldung
Kay Martinen
usenet at martinen.de
Fr Jan 3 21:35:01 CET 2025
Am 03.01.25 um 20:41 schrieb Marcus Röckrath:
> Hallo Kay,
>
> Kay Martinen wrote:
>
>>> Active has not been fetched completely in previous run
>>> or has never been fetched, forcing active fetch.
>>> Newsgroup name conflict: de.alt.folklore.computer vs.
>>> de.alt.folklore.computer Newsgroup name conflict, chose
>>> de.alt.folklore.computer Newsgroup name conflict: spline.eisfair.dev vs.
>>> spline.eisfair.dev Newsgroup name conflict, chose spline.eisfair.dev
>>> Newsgroup name conflict: spline.fli4l.dev vs. spline.fli4l.dev
>>> Newsgroup name conflict, chose spline.fli4l.dev
>>> Newsgroup name conflict: spline.fli4l.flohmarkt vs.
>>> spline.fli4l.flohmarkt Newsgroup name conflict, chose
>>> spline.fli4l.flohmarkt Newsgroup name conflict: spline.fli4l.geschnatter
>>> vs. spline.fli4l.geschnatter Newsgroup name conflict, chose
>>> spline.fli4l.geschnatter Newsgroup name conflict: spline.fli4l.opt vs.
>>> spline.fli4l.opt Newsgroup name conflict, chose spline.fli4l.opt
>>
>> -snap-
>>
>> Ich sehe da keinen erkennbaren unterschied von wg. "name conflict" aber
>> ich sehe auch nicht was der da mit was vergleichen will.
>>
>> Weiß jemand wodurch das ausgelöst sein könnte?
>>
>> Weder host noch dienst wurden neu gestartet, internet-ausfälle gab es
>> m.w. auch nicht und mein NUA zeigt nach wie vor auch neue Posts in
>> seinen abonnierten Gruppen an. Scheint alles zu laufen.
>
> Im leafnode-Quelltext kommt die Fehlermeldung aber dann, wenn es genau einen
> solchen Unterschied gibt:
>
> static void picklesscaps(struct newsgroup *d, struct newsgroup *s)
> {
> ln_log(LNLOG_SERR, LNLOG_CTOP, "Newsgroup name conflict: %s vs. %s",
> d->name, s->name);
> if (countcaps(s->name) < countcaps(d->name)) {
> newsgroup_freedata(d);
> newsgroup_copy(d,s);
> } else {
> newsgroup_freedata(s);
> }
> ln_log(LNLOG_SERR, LNLOG_CTOP, "Newsgroup name conflict, chose %s",
> d->name);
> }
Könnte das ein Problem mit einer zu hohen Prozess ID sein?
In 'messages' sehe ich das der vorige lauf um 18:30 endet mit
fetchnews[32655] child hast process ID 32657
Und sowohl fcron als auch nächster fetchnews lauf haben danach wieder
dreistellige PID's.
Oder könnte ein zeitgleicher lauf von /var/install/bin/mail-check-queue
relevant sein? Nur FYI!
Unter den oben schon geposteten (gemailten) Meldungen steht im log
darunter noch ein
<215 Newsgroup descriptions in form "group description"
und darunter der nntp-server und die datei aus der es gelesen wurde.
> Bitte poste zunächst mal deine eisfair-leafnode-Konfiguration, so kann ich
> mir auch keinen Reim drauf machen.
>
-snip-
#------------------------------------------------------------------------------
# Basic configuration
#------------------------------------------------------------------------------
START_LEAFNODE='yes' # Start leafnode yes/no
LEAFNODE_EXPIRE='128' # Keep News for xx days
LEAFNODE_FETCH_CRON='*/10 * * * *'
# Crontab for fetching news
LEAFNODE_EXPIRE_CRON='15 1 * * *' # Crontab for deleting old messages
LEAFNODE_FQDN='news.martinen.de' # Your FQDN see docu
LEAFNODE_FETCH_VERBOSE='1' # More or less output of fetchnews 0=off
LEAFNODE_FETCH_INITIAL='0' # Defines how many articles from a newly
# subscribed group should be fetched
# default=0 (all)
#------------------------------------------------------------------------------
# Configuration of external news servers
#------------------------------------------------------------------------------
LEAFNODE_SERVERS_N='1' # Number of news servers
LEAFNODE_SERVER_1_SERVER='****.*****.de'
# Name of news server
LEAFNODE_SERVER_1_PORT='119' # Ports of news server default=119
LEAFNODE_SERVER_1_AUTH='yes' # Server needs authentication yes/no
LEAFNODE_SERVER_1_USER='Kay_Martinen'
# Username
LEAFNODE_SERVER_1_PASS='#######' # Password
#------------------------------------------------------------------------------
# Groupexpire setup
#------------------------------------------------------------------------------
LEAFNODE_GROUPEXPIRE_N='3' # Number of groupexpire settings
LEAFNODE_GROUPEXPIRE_1_MASK='spline.eisfair.*'
# Name of news group with special expire
# setup (wildcards allowed)
LEAFNODE_GROUPEXPIRE_1_DAYS='-1' # Number of days to keep messages in this
# news group (-1=never expire)
LEAFNODE_GROUPEXPIRE_2_MASK='spline.fli4l.*'
# Name of news group with special expire
# setup (wildcards allowed)
LEAFNODE_GROUPEXPIRE_2_DAYS='-1' # Number of days to keep messages in this
# news group (-1=never expire)
LEAFNODE_GROUPEXPIRE_3_MASK='de.alt.folklore.computer'
# Name of news group with special expire
# setup (wildcards allowed)
LEAFNODE_GROUPEXPIRE_3_DAYS='-1' # Number of days to keep messages in this
# news group (-1=never expire)
#------------------------------------------------------------------------------
# Fine tuning
#------------------------------------------------------------------------------
LEAFNODE_FINETUNING='yes' # Leafnode Finetuning yes/no
LEAFNODE_FETCH_MAX='0' # Specifies the max. number of articles
# fetchnews should fetch from the
upstream
# server in each group default=0 (all)
LEAFNODE_FETCH_MAX_CROSSPOST='10' # Fetch only those posting, which are
xposted
# to max. x groups default=0 (off)
LEAFNODE_FETCH_MAX_AGE='0' # Fetch only those posting, which are max.
# days old default=10
LEAFNODE_FETCH_MAX_LINES='0' # Fetch only those posting, which are max.
# xxx lines long default=0 (off)
LEAFNODE_FETCH_MIN_LINES='0' # Fetch only those posting, which are min.
# xxx lines long default=0 (off)
LEAFNODE_FETCH_MAX_BYTES='0' # Fetch only those posting, which are max.
# xxx bytes big default=0 (off)
LEAFNODE_FETCH_TIMEOUT_SHORT='3' # A group that has been accidentally
touched
# is being fetched for two days default=2
LEAFNODE_FETCH_TIMEOUT_LONG='64' # A group that has not been read at all is
# being fetched for seven days before
being
# unsubscribed
-snap-
Bye/
/Kay
--
Posted via Leafnode
Mehr Informationen über die Mailingliste Eisfair