Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNC_SYSOPS    |    Synchronet Multinode BBS Software Suppor    |    33,243 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 30,734 of 33,243    |
|    Digital Man to Nicholas Boel    |
|    Re: nntpserver not able to read articles    |
|    09 Nov 24 19:04:32    |
      TZUTC: -0800       MSGID: 56739.sync_sys@1:103/705 2b963663       REPLY: 14220.syncsyso@1:154/700 2b9587fe       PID: Synchronet 3.20a-Win32 master/e3f17e641 Nov 04 202 MSC 1916       TID: SBBSecho 3.21-Linux master/b8260ae62 Nov 08 2024 20:27 GCC 12.2.0       COLS: 80       BBSID: VERT       CHRS: CP437 2       NOTE: FSEditor.js v1.105        Re: Re: nntpserver not able to read articles after files closed        By: Nicholas Boel to Digital Man on Sat Nov 09 2024 08:29 pm               > On Sat, Nov 09 2024 18:01:07 -0600, you wrote:        >        > > > > A log from the nntpservice when this issues happens would be        > > > > helpful.        >        > Good thing, just as I saved the last message in this sub, it happened        > when trying to view this message. Here is the log:        >        > Nov 09 20:25:33 reaper synchronet[608]: srvc 0056 NNTP        > [Fidonet.SYNC_SYSOPS] cmd: A        > Nov 09 20:25:33 reaper synchronet[608]: srvc 0056 NNTP !unknown command        > Nov 09 20:25:33 reaper synchronet[608]: srvc 0056 NNTP        > [Fidonet.SYNC_SYSOPS] cmd: RTICLE 14218        > Nov 09 20:25:33 reaper synchronet[608]: srvc 0056 NNTP !unknown command        >        > Looks like somehow ARTICLE is getting split. This happened once prior        > just during that 5 minute session, in the Debate sub. This tends to        > happen more times than can be ignored.              Weird. You could try increasing the timeout values on this line in       nntpservice.js and see if that makes any difference:       cmdline = client.socket.recvline(/* maxlen: */1024, /* timeout: */(msgbase &&       msgbase.is_open) ? 10 : 300);              Those values are in seconds, so I'd be surprised if an NNTP client would send       'A' and then take more than 10 seconds to send the remaining characters of the       command, but worth experimenting with. A network packet capture (e.g. with       Wireshark) could also help tell what's happening there exactly.       --         digital man (rob)              This Is Spinal Tap quote #35:       Jeanine Pettibone: You don't do heavy metal in Dubly, you know.       Norco, CA WX: 65.7øF, 24.0% humidity, 2 mph NW wind, 0.00 inches rain/24hrs       --- SBBSecho 3.21-Linux        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 90/1 103/705 105/81 106/201 124/5016 128/187 153/757 7715       SEEN-BY: 154/10 30 203/0 218/700 221/0 226/30 227/114 229/110 114       SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 266/512       SEEN-BY: 280/464 5003 5006 282/1038 291/111 292/8125 301/1 320/219       SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124       SEEN-BY: 467/888 633/280 712/848 770/1 5020/400 8912 5054/30 5075/35       PATH: 103/705 280/464 460/58 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca