Closed Bug 1824649 Opened 3 years ago Closed 3 years ago

NNTP stopped working with nntp.lore.kernel.org

Categories

(MailNews Core :: Networking: NNTP, defect)

Product:
MailNews Core
Component:
Networking: NNTP
Version:
Thunderbird 102
Type:
defect

Tracking

(thunderbird_esr102 affected)

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
thunderbird_esr102 --- affected

People

(Reporter: aik, Unassigned)

Details

(Keywords: regression)

Attachments

(1 file)

tb-nntp.log
40.16 KB, text/x-log
Details
Attached file tb-nntp.log —

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/109.0

Steps to reproduce:

Run TB as usual. 102.8.0 (64-bit) from Linux/Fedora36.

Actual results:

The message index updates correctly by messages do not open. A click on a message (to see it) produces such log. mailnews.nntp.jsmodule = true/false - makes no difference.

2023-03-27 04:10:41.743307 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) creating
2023-03-27 04:10:41.743320 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) initializing, so unset m_currentGroup
2023-03-27 04:10:41.743326 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) setting busy to 1
2023-03-27 04:10:41.743328 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) ParseURL
2023-03-27 04:10:41.743331 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) original message spec = news-message://nntp.lore.kernel.org/org.kernel.vger.kvm#324170
2023-03-27 04:10:41.743581 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) setting busy to 1
2023-03-27 04:10:41.743587 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) ParseURL
2023-03-27 04:10:41.743589 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) original message spec = news-message://nntp.lore.kernel.org/org.kernel.vger.kvm#324170
2023-03-27 04:10:41.743623 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) setting busy to 1
2023-03-27 04:10:41.743626 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) ParseURL
2023-03-27 04:10:41.743628 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) original message spec = news-message://nntp.lore.kernel.org/org.kernel.vger.kvm#324170
2023-03-27 04:10:41.743639 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) m_messageID =
2023-03-27 04:10:41.743641 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) group =
2023-03-27 04:10:41.743642 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) m_key = 324170
2023-03-27 04:10:41.793764 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa821ff1200) ClosingSocket()
2023-03-27 04:10:41.793780 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa821ff1200) CleanupAfterRunningUrl()
2023-03-27 04:10:41.793804 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa821ff1200) setting busy to 0
2023-03-27 04:10:41.793816 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa821ff1200) ClosingSocket()
2023-03-27 04:10:41.793818 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa821ff1200) CleanupAfterRunningUrl()
2023-03-27 04:10:41.793820 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa821ff1200) setting busy to 0
2023-03-27 04:10:41.794072 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) opening connection to nntp.lore.kernel.org on port 119
2023-03-27 04:10:42.319057 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Next state: NNTP_RESPONSE
2023-03-27 04:10:42.319073 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Receiving: 201 nntp.lore.kernel.org ready - post via email
2023-03-27 04:10:42.319081 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Next state: NNTP_LOGIN_RESPONSE
2023-03-27 04:10:42.319085 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Next state: NNTP_SEND_MODE_READER
2023-03-27 04:10:42.319089 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Sending: MODE READER
2023-03-27 04:10:42.521112 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Next state: NNTP_RESPONSE
2023-03-27 04:10:42.521144 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Receiving: 201 Posting prohibited
2023-03-27 04:10:42.521158 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Next state: NNTP_SEND_MODE_READER_RESPONSE
2023-03-27 04:10:42.521177 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Next state: SEND_FIRST_NNTP_COMMAND
2023-03-27 04:10:42.521186 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) current group = , desired group = org.kernel.vger.kvm
2023-03-27 04:10:42.521191 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Next state: NNTP_SEND_GROUP_FOR_ARTICLE
2023-03-27 04:10:42.521199 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Sending: GROUP org.kernel.vger.kvm
2023-03-27 04:10:42.725841 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Next state: NNTP_RESPONSE
2023-03-27 04:10:42.725903 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Receiving: 211 324191 1 324192 org.kernel.vger.kvm
2023-03-27 04:10:42.725921 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Next state: NNTP_SEND_GROUP_FOR_ARTICLE_RESPONSE
2023-03-27 04:10:42.725934 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) SetCurrentGroup to org.kernel.vger.kvm
2023-03-27 04:10:42.725940 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Next state: NNTP_SEND_ARTICLE_NUMBER
2023-03-27 04:10:42.725960 UTC - [Parent 1121167: Main Thread]: I/NNTP (7fa82347b100) Sending: ARTICLE 324170

Expected results:

Messages should just load.

102.9.0 (64-bit) from https://www.thunderbird.net/en-GB/download is broken too.

thunderbird-112.0b3.tar.bz2 does not load message too. But old-ish 108.0b1 does load them so the server seems to be fine.

status-thunderbird_esr102: --- → affected
Component: Untriaged → Networking: NNTP
Keywords: regression
Product: Thunderbird → MailNews Core

Oh it is even better - I can actually download any version, unpack, run with a fresh new profile, add NNTP account, fetch the index and messages will load just fine untiiiiiil I restart TB. I thought thunderbird-91.9.1.tar.bz2 works, did all that and then just restarted the same TB with the same profile - and it does not load messages anymore.

Turned out to be a temporal hiccup on the server. The bug is not the TB bug so this can be closed.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX

Thanks for the update

Resolution: WONTFIX → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: