* upas/fs imap fetch failed
@ 2020-10-22 20:20 nicolagi
2020-10-22 20:52 ` [9front] " Kurt H Maier
0 siblings, 1 reply; 3+ messages in thread
From: nicolagi @ 2020-10-22 20:20 UTC (permalink / raw)
To: 9front
Hi all, I ran into a problem with upas/fs (latest 9front).
I don't mean for anyone to debug it for me, but maybe the debug
logging below rings a bell to someone, and they could share hints?
Nic
term% upas/fs -l -d -f /imaps/mail.sdf.org/nicolagi
newmessage 1 0 426ba0
newmessage 2 426ba0 4274a0
newmessage 3 426ba0 427700
newmessage 4 426ba0 427960
newmessage 5 426ba0 427bc0
newmessage 6 426ba0 427e20
newmessage 7 426ba0 428080
newmessage 8 426ba0 4282e0
newmessage 9 426ba0 428540
newmessage 10 426ba0 4287a0
newmessage 11 426ba0 428a00
newmessage 12 426ba0 428c60
newmessage 13 426ba0 428ec0
newmessage 14 426ba0 429120
newmessage 15 426ba0 429380
newmessage 16 426ba0 4295e0
newmessage 17 426ba0 429840
newmessage 18 426ba0 429aa0
newmessage 19 426ba0 429d00
newmessage 20 426ba0 429f60
newmessage 21 426ba0 42a1c0
newmessage 22 426ba0 42a420
newmessage 23 426ba0 42a680
newmessage 24 426ba0 42a8e0
newmessage 25 426ba0 42ab40
cachebody 3 [1603127289.00] 0 2134 stalefetch 0 sz 2134 o 0 l 2134 badchars 0
50 more badchars
reducing size 2134 2084
3 d528dcd68903a3d95635fa698bc7cc2b15acf82d
→stale header body
cachebody 4 [1603127664.00] 0 5465 stalefetch 0 sz 5465 o 0 l 5465 badchars 0
115 more badchars
reducing size 5465 5350
4 672cd87109cbd23830ea5e46cd0bd2866e6d6c40
parseattachments 42d380 5350 bonudary --000000000000a53d3b05b2093efc
newmessage 26 427700 42ce20
newmessage 27 427700 42e900
→stale header body
cachebody 5 [1603128646.00] 0 1564 stalefetch 0 sz 1564 o 0 l 1564 badchars 0
upas/fs: imap: fetchrsp: read: tls hungup
upas/fs: imap: imap fetch failed
cachebody 6 [1603132582.00] 0 4694 stalefetch 0 sz 4694 o 0 l 4694 badchars 0
upas/fs: imap: imap fetch failed
cachebody 7 [1603136677.00] 0 2499 stalefetch 0 sz 2499 o 0 l 2499 badchars 0
upas/fs: imap: imap fetch failed
cachebody 8 [1603147169.00] 0 2778 stalefetch 0 sz 2778 o 0 l 2778 badchars 0
upas/fs: imap: imap fetch failed
cachebody 9 [1603165621.00] 0 4147 stalefetch 0 sz 4147 o 0 l 4147 badchars 0
upas/fs: imap: imap fetch failed
cachebody 10 [1603170564.00] 0 3167 stalefetch 0 sz 3167 o 0 l 3167 badchars 0
upas/fs: imap: imap fetch failed
cachebody 11 [1603170603.00] 0 3661 stalefetch 0 sz 3661 o 0 l 3661 badchars 0
upas/fs: imap: imap fetch failed
cachebody 12 [1603182747.00] 0 1640 stalefetch 0 sz 1640 o 0 l 1640 badchars 0
upas/fs: imap: imap fetch failed
cachebody 13 [1603252583.00] 0 4453 stalefetch 0 sz 4453 o 0 l 4453 badchars 0
upas/fs: imap: imap fetch failed
cachebody 14 [1603253357.00] 0 1527 stalefetch 0 sz 1527 o 0 l 1527 badchars 0
upas/fs: imap: imap fetch failed
cachebody 15 [1603254467.00] 0 3354 stalefetch 0 sz 3354 o 0 l 3354 badchars 0
upas/fs: imap: imap fetch failed
cachebody 16 [1603288425.00] 0 1517 stalefetch 0 sz 1517 o 0 l 1517 badchars 0
upas/fs: imap: imap fetch failed
cachebody 17 [1603305563.00] 0 4236 stalefetch 0 sz 4236 o 0 l 4236 badchars 0
upas/fs: imap: imap fetch failed
cachebody 18 [1603318853.00] 0 2204 stalefetch 0 sz 2204 o 0 l 2204 badchars 0
upas/fs: imap: imap fetch failed
cachebody 19 [1603319590.00] 0 4077 stalefetch 0 sz 4077 o 0 l 4077 badchars 0
upas/fs: imap: imap fetch failed
cachebody 20 [1603329537.00] 0 11087 stalefetch 0 sz 11087 o 0 l 11087 badchars 0
upas/fs: imap: imap fetch failed
cachebody 21 [1603368703.00] 0 4287 stalefetch 0 sz 4287 o 0 l 4287 badchars 0
upas/fs: imap: imap fetch failed
cachebody 22 [1603390680.00] 0 1786 stalefetch 0 sz 1786 o 0 l 1786 badchars 0
upas/fs: imap: imap fetch failed
cachebody 23 [1603394238.00] 0 3384 stalefetch 0 sz 3384 o 0 l 3384 badchars 0
upas/fs: imap: imap fetch failed
cachebody 24 [1603394371.00] 0 2578 stalefetch 0 sz 2578 o 0 l 2578 badchars 0
upas/fs: imap: imap fetch failed
cachebody 25 [1603395426.00] 0 5234 stalefetch 0 sz 5234 o 0 l 5234 badchars 0
upas/fs: imap: imap fetch failed
cachebody 26 [1603395846.00] 0 1531 stalefetch 0 sz 1531 o 0 l 1531 badchars 0
upas/fs: imap: imap fetch failed
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [9front] upas/fs imap fetch failed
2020-10-22 20:20 upas/fs imap fetch failed nicolagi
@ 2020-10-22 20:52 ` Kurt H Maier
2020-10-23 7:05 ` nicolagi
0 siblings, 1 reply; 3+ messages in thread
From: Kurt H Maier @ 2020-10-22 20:52 UTC (permalink / raw)
To: 9front
On Thu, Oct 22, 2020 at 09:20:36PM +0100, nicolagi@sdf.org wrote:
> parseattachments 42d380 5350 bonudary --000000000000a53d3b05b2093efc
I pushed a fix for this typo ("bonudary") but of course it is not the
problem.
> upas/fs: imap: fetchrsp: read: tls hungup
Something is getting disconnected. Do you know what?
khm
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [9front] upas/fs imap fetch failed
2020-10-22 20:52 ` [9front] " Kurt H Maier
@ 2020-10-23 7:05 ` nicolagi
0 siblings, 0 replies; 3+ messages in thread
From: nicolagi @ 2020-10-23 7:05 UTC (permalink / raw)
To: 9front
> On Thu, Oct 22, 2020 at 09:20:36PM +0100, nicolagi@sdf.org wrote:
>> parseattachments 42d380 5350 bonudary --000000000000a53d3b05b2093efc
>
> I pushed a fix for this typo ("bonudary") but of course it is not the
> problem.
☺
>> upas/fs: imap: fetchrsp: read: tls hungup
>
> Something is getting disconnected. Do you know wha
Hmm. I'm not sure this is a symptom or a cause.
I don't know if you'll agree with my thoughts:
Seeing that fetchrsp's job seems to be parsing a response from the
server, I thought maybe there was a problem parsing one of the
responses, and that sent the server into a bad state, unable to parse
further responses. To put this theory to the test, I went in and
deleted the attachment delimited by --000000000000a53d3b05b2093efc
(with mutt) and started upas/fs again. Now I see all mail. (BUT:
Also note how your e-mail text was clipped. It wasn't me. "bad
chars" and "reducing size" seem to be good hints.)
When this happens again, what's the best way to step through the
response parsing? On another system I would perhaps capture the
packets and look at them and at fetchrsp() at the same time, but I
don't know if that can be done here. And I'm sure there are smarter
ways. :-)
Thank you
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-10-23 7:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-22 20:20 upas/fs imap fetch failed nicolagi
2020-10-22 20:52 ` [9front] " Kurt H Maier
2020-10-23 7:05 ` nicolagi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).