Your message dated Tue, 1 Nov 2016 19:13:51 +0100
with message-id <[email protected]>
and subject line Re: Bug#832397: tin, debian bug #832397
has caused the Debian Bug report #832397,
regarding tin: fails after reconnection, losing all downloaded data
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
832397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832397
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tin
Version: 1:2.3.2-1
Severity: important
On a large newsgroup, tin starts to download the headers, but at
some point, there's a disconnection. And tin always fails after a
reconnection. However, if I start tin again, the connection succeeds,
showing the problem occurs only for a reconnection.
With "tin -D 1", here's how /tmp/NNTP looks like.
nntp_open() BEGIN
nntp_open() news.gandi.net:119
<<< [01:26:48.881604] 200 groups.gandi.net Papercut server ready (posting
allowed)
nntp_open() groups.gandi.net Papercut server ready (posting allowed)
new_nntp_command(CAPABILITIES)
>>> [01:26:48.881811] CAPABILITIES
<<< [01:26:48.892438] 500 command not recognized
new_nntp_command(CAPABILITIES) NOT_OK - Expected: 101, got: 500
mode_reader() MODE READER
>>> [01:26:48.892535] MODE READER
<<< [01:26:48.901426] 200 Hello, you can post
new_nntp_command(XOVER)
>>> [01:26:48.901856] XOVER
<<< [01:26:48.910319] 412 no newsgroup has been selected
new_nntp_command(XOVER) OK
new_nntp_command(XHDR)
>>> [01:26:48.910404] XHDR
<<< [01:26:48.918940] 501 command syntax error (or un-implemented option)
new_nntp_command(XHDR) OK
ACTIVE host=[news.gandi.net] time=[1469407358]
nntp_command(LIST OVERVIEW.FMT)
>>> [01:26:48.919081] LIST OVERVIEW.FMT
<<< [01:26:48.927923] 215 information follows
nntp_command(LIST OVERVIEW.FMT) OK
<<< [01:26:48.928000] Subject:
<<< [01:26:48.928015] From:
<<< [01:26:48.928025] Date:
<<< [01:26:48.928035] Message-ID:
<<< [01:26:48.928045] References:
<<< [01:26:48.928055] Bytes:
<<< [01:26:48.928065] Lines:
<<< [01:26:48.928075] Xref:
nntp_command(LIST)
>>> [01:26:50.929886] LIST
<<< [01:26:51.136585] 215 list of newsgroups follows
nntp_command(LIST) OK
<<< [01:26:51.136650] gandi.en.api 166 1 y
<<< [01:26:51.136661] gandi.en.blog 429 1 y
<<< [01:26:51.136668] gandi.en.domain 1803 1 y
<<< [01:26:51.136675] gandi.en.domain.dns 545 1 y
<<< [01:26:51.136682] gandi.en.hosting 578 1 y
<<< [01:26:51.136688] gandi.en.hosting.api 21 2 y
<<< [01:26:51.136694] gandi.en.hosting.autoinstall 105 1 y
<<< [01:26:51.136701] gandi.en.hosting.expert 522 1 y
<<< [01:26:51.136707] gandi.en.hosting.simple 744 2 y
<<< [01:26:51.136713] gandi.en.hosting.sitemaker 98 1 y
<<< [01:26:51.136719] gandi.en.mail 557 1 y
<<< [01:26:51.136726] gandi.en.mail.webmail 121 1 y
<<< [01:26:51.136732] gandi.en.reseller 8 1 y
<<< [01:26:51.136738] gandi.en.ssl 120 1 y
<<< [01:26:51.136744] gandi.es.alojamiento 8 2 y
<<< [01:26:51.136750] gandi.es.alojamiento.api 0 0 y
<<< [01:26:51.136757] gandi.es.alojamiento.expert 3 2 y
<<< [01:26:51.136763] gandi.es.alojamiento.gandiai 0 0 y
<<< [01:26:51.136769] gandi.es.alojamiento.simple 0 0 y
<<< [01:26:51.136775] gandi.es.alojamiento.sitemaker 3 2 y
<<< [01:26:51.136781] gandi.es.api 0 0 y
<<< [01:26:51.136788] gandi.es.blog 2 2 y
<<< [01:26:51.136794] gandi.es.dominio 36 2 y
<<< [01:26:51.136800] gandi.es.dominio.dns 15 2 y
<<< [01:26:51.136806] gandi.es.mail 12 2 y
<<< [01:26:51.136812] gandi.es.mail.webmail 4 2 y
<<< [01:26:51.136818] gandi.es.revendedor 0 0 y
<<< [01:26:51.136836] gandi.es.ssl 0 0 y
<<< [01:26:51.136847] gandi.fr.api 383 1 y
<<< [01:26:51.136854] gandi.fr.blog 4174 1 y
<<< [01:26:51.136861] gandi.fr.domaine 8478 1 y
<<< [01:26:51.136876] gandi.fr.domaine.dns 2587 1 y
<<< [01:26:51.136883] gandi.fr.hebergement 3550 1 y
<<< [01:26:51.136889] gandi.fr.hebergement.api 93 2 y
<<< [01:26:51.136895] gandi.fr.hebergement.autoinstall 1220 1 y
<<< [01:26:51.136901] gandi.fr.hebergement.expert 1779 1 y
<<< [01:26:51.136908] gandi.fr.hebergement.simple 4077 2 y
<<< [01:26:51.136914] gandi.fr.hebergement.sitemaker 605 1 y
<<< [01:26:51.136920] gandi.fr.mail 3759 1 y
<<< [01:26:51.136926] gandi.fr.mail.webmail 617 3 y
<<< [01:26:51.136932] gandi.fr.revendeur 87 1 y
<<< [01:26:51.136938] gandi.fr.ssl 430 1 y
<<< [01:26:51.136944] gandi.test 92 3 y
read_newsrc_active_file() GROUP gandi.en.api
>>> [01:26:51.137161] GROUP gandi.en.api
read_newsrc_active_file() GROUP gandi.en.domain
>>> [01:26:51.137183] GROUP gandi.en.domain
read_newsrc_active_file() GROUP gandi.en.domain.dns
>>> [01:26:51.137195] GROUP gandi.en.domain.dns
read_newsrc_active_file() GROUP gandi.en.hosting
>>> [01:26:51.137206] GROUP gandi.en.hosting
read_newsrc_active_file() GROUP gandi.en.hosting.api
>>> [01:26:51.137216] GROUP gandi.en.hosting.api
read_newsrc_active_file() GROUP gandi.en.hosting.expert
>>> [01:26:51.137233] GROUP gandi.en.hosting.expert
read_newsrc_active_file() GROUP gandi.en.ssl
>>> [01:26:51.137252] GROUP gandi.en.ssl
read_newsrc_active_file() GROUP gandi.fr.api
>>> [01:26:51.137263] GROUP gandi.fr.api
read_newsrc_active_file() GROUP gandi.fr.domaine
>>> [01:26:51.137274] GROUP gandi.fr.domaine
read_newsrc_active_file() GROUP gandi.fr.domaine.dns
>>> [01:26:51.137284] GROUP gandi.fr.domaine.dns
read_newsrc_active_file() GROUP gandi.fr.hebergement
>>> [01:26:51.137295] GROUP gandi.fr.hebergement
read_newsrc_active_file() GROUP gandi.fr.hebergement.api
>>> [01:26:51.137305] GROUP gandi.fr.hebergement.api
read_newsrc_active_file() GROUP gandi.fr.hebergement.expert
>>> [01:26:51.137315] GROUP gandi.fr.hebergement.expert
read_newsrc_active_file() GROUP gandi.fr.ssl
>>> [01:26:51.137326] GROUP gandi.fr.ssl
read_newsrc_active_file() GROUP gandi.test
>>> [01:26:51.137336] GROUP gandi.test
<<< [01:26:51.205098] 211 122 1 166 gandi.en.api group selected
<<< [01:26:51.270487] 211 1518 1 1803 gandi.en.domain group selected
<<< [01:26:51.332254] 211 545 1 545 gandi.en.domain.dns group selected
<<< [01:26:51.391668] 211 572 1 578 gandi.en.hosting group selected
<<< [01:26:51.446600] 211 20 2 21 gandi.en.hosting.api group selected
<<< [01:26:51.505753] 211 520 1 522 gandi.en.hosting.expert group selected
<<< [01:26:51.563883] 211 120 1 120 gandi.en.ssl group selected
<<< [01:26:51.623985] 211 368 1 383 gandi.fr.api group selected
<<< [01:26:51.734119] 211 8317 1 8478 gandi.fr.domaine group selected
<<< [01:26:51.807478] 211 2554 1 2587 gandi.fr.domaine.dns group selected
<<< [01:26:51.881664] 211 3524 1 3550 gandi.fr.hebergement group selected
<<< [01:26:51.937803] 211 91 2 93 gandi.fr.hebergement.api group selected
<<< [01:26:52.003739] 211 1769 1 1779 gandi.fr.hebergement.expert group selected
<<< [01:26:52.061643] 211 428 1 430 gandi.fr.ssl group selected
<<< [01:26:52.119415] 211 86 3 92 gandi.test group selected
Newnews old=[1469407358] new=[1469410012]
nntp_command(NEWGROUPS 160725 024238)
>>> [01:26:52.119730] NEWGROUPS 160725 024238
<<< [01:26:52.153406] 231 list of new newsgroups follows
nntp_command(NEWGROUPS 160725 024238) OK
nntp_command(LIST NEWSGROUPS)
>>> [01:26:52.153928] LIST NEWSGROUPS
<<< [01:26:52.189150] 215 information follows
nntp_command(LIST NEWSGROUPS) OK
nntp_command(LISTGROUP gandi.fr.domaine)
>>> [01:26:54.579698] LISTGROUP gandi.fr.domaine
<<< [01:26:54.935979] 211 8317 1 8478 gandi.fr.domaine Article numbers follow
(multiline)
nntp_command(LISTGROUP gandi.fr.domaine) OK
setup_hard_base(LISTGROUP gandi.fr.domaine)
nntp_command(XOVER 1-8478)
>>> [01:26:54.980474] XOVER 1-8478
<<< [01:27:06.850014] 224 Overview information follows
nntp_command(XOVER 1-8478) OK
nntp_command(XHDR XREF 1-8478)
>>> [01:27:06.850150] XHDR XREF 1-8478
<<< [01:27:06.860971] 501 command syntax error (or un-implemented option)
nntp_command(XHDR XREF 1-8478) NOT_OK
nntp_command(HEAD 1)
>>> [01:27:06.861101] HEAD 1
<<< [01:27:06.920651] 221 1 <[email protected]>
article retrieved - head follows
nntp_command(HEAD 1) OK
nntp_command(HEAD 2)
>>> [01:27:06.920916] HEAD 2
<<< [01:27:06.980840] 221 2 <[email protected]>
article retrieved - head follows
nntp_command(HEAD 2) OK
nntp_command(HEAD 3)
>>> [01:27:06.980982] HEAD 3
<<< [01:27:07.038084] 221 3 <[email protected]>
article retrieved - head follows
nntp_command(HEAD 3) OK
nntp_command(HEAD 4)
>>> [01:27:07.038243] HEAD 4
<<< [01:27:07.099363] 221 4 <[email protected]>
article retrieved - head follows
nntp_command(HEAD 4) OK
[...]
nntp_command(HEAD 4700)
>>> [01:31:51.791983] HEAD 4700
<<< [01:31:51.851174] 221 4700
<[email protected]> article retrieved - head
follows
nntp_command(HEAD 4700) OK
nntp_command(HEAD 4701)
>>> [01:31:51.851505] HEAD 4701
<<< [01:31:51.906318] 221 4701
<[email protected]> article retrieved - head
follows
nntp_command(HEAD 4701) OK
nntp_command(HEAD 4702)
>>> [01:31:51.906590] HEAD 4702
<<< [01:31:51.967943] 221 4702
<[email protected]> article retrieved - head
follows
nntp_command(HEAD 4702) OK
nntp_command(HEAD 4703)
>>> [01:31:51.968080] HEAD 4703
nntp_open() BEGIN
nntp_open() news.gandi.net:119
<<< [01:31:56.086614] 200 groups.gandi.net Papercut server ready (posting
allowed)
nntp_open() groups.gandi.net Papercut server ready (posting allowed)
new_nntp_command(CAPABILITIES)
>>> [01:31:56.086681] CAPABILITIES
<<< [01:31:56.097158] 500 command not recognized
new_nntp_command(CAPABILITIES) NOT_OK - Expected: 101, got: 500
mode_reader() MODE READER
>>> [01:31:56.097220] MODE READER
<<< [01:31:56.105973] 200 Hello, you can post
new_nntp_command(XOVER)
>>> [01:31:56.106029] XOVER
<<< [01:31:56.114813] 412 no newsgroup has been selected
new_nntp_command(XOVER) OK
new_nntp_command(XHDR)
>>> [01:31:56.114875] XHDR
<<< [01:31:56.123639] 501 command syntax error (or un-implemented option)
new_nntp_command(XHDR) OK
>>> [01:31:56.123696] GROUP gandi.fr.domaine
<<< [01:31:56.252672] 211 8317 1 8478 gandi.fr.domaine group selected
>>> [01:31:56.252717] HEAD 4703
And then tin quits with no error messages, and exit status 3, which is
not possible according to its man page (in interactive mode, there are
only 0 and 1).
If I restart tin and retry on the same newsgroup, it starts again
to download the headers from 1! Thus it is impossible to read this
newsgroup.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages tin depends on:
ii debconf [debconf-2.0] 1.5.59
ii libc6 2.23-2
ii libcanlock2 2b-7
ii libicu55 55.1-7
ii libncursesw5 6.0+20160625-1
ii libpcre3 2:8.38-3.1
ii libtinfo5 6.0+20160625-1
ii libuu0 0.5.20-7
Versions of packages tin recommends:
ii postfix [mail-transport-agent] 3.1.0-4
Versions of packages tin suggests:
ii gnupg 1.4.20-6
ii ispell 3.4.00-5
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Version: 1:2.4.0-1
On 2016-11-01 10:05:15 +0100, Urs Janßen wrote:
> I belive that #832397 (opened by you) is fixed in debian as of the upload
> of 1:2.4.0-1 in unstable (medium). From tin's changelog:
>
> | U027) Urs Janssen <[email protected]>
> | Dennis Preiser <[email protected]>
> | ADD. log reconnect limit reached (debian bug #832397)
> | ADD. document NNTP_ERROR_EXIT code (debian bug #832397)
> | ADD. give error messages on exit after curses has ended (debian bug
> | #832397)
>
> which addresses most of the issues you had except the data loss (which
> is caused by unexpected connection termination by the server, it's not the
> clients fault IMHO). If you share this opinion could you please close the
> issue
Thanks for the information. So, let's close the bug. Note that
I can't test as the NNTP server no longer exists (it was an old
server, apparently not much maintained).
> or at least specify what else is missing to close the issue.
IIRC, one problem was that tin was fetching again since the beginning.
I'm not sure whether the only cause was the "bug" in the server, or
something could be improved. What I'm thinking of is: if the download
takes a long time and there's a disconnect without a possible immediate
reconnect (e.g. due to a network problem, or a lack of time and the
machine needs to be rebooted), is everything lost or could the download
be resumed later from the point where the disconnect occurred?
--
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
