Subj : Synchronet 3.21e upgrade
To   : hax0r
From : Digital Man
Date : Wed Apr 22 2026 10:39 pm

  Re: Synchronet 3.21e upgrade
  By: hax0r to Digital Man on Wed Apr 22 2026 06:57 pm

 >   Re: Synchronet 3.21e upgrade
 >   By: Digital Man to hax0r on Tue Apr 21 2026 09:35 pm
 >
 >  > What's the log output from some or one of the servers while it's doing
 >  > that?
 > That's the thing, there really isn't anything happening in the Terminal
 > Server output while that is happening when sbbsntsvc.exe is running and its
 > toggling between "Running NT Service" and "Down". There is some noise every
 > now and then, likely related to some sort of spam script trying to logon but
 > nothing that i could see of significance. Also, while it is doing that, I
 > can connect (and stay connected). After a while, though theserver does top
 > accepting any new connections even though in the GUI it looks like
 > everything is fine.

I pinned that bug down and fixed it. That particular issue appears to have been 
just been cosmetic - no negative impact other than maybe failure to stop or 
restart the server/service.

 >  > Likely. That's what *I* do. But still, it sounds like a bug
 > If the recommended way to run it these days is to do an auto logon and auto
 > stat of Syncrhonet Control Panel I can make that happen. I always thought
 > that the service was a much more native feel since no one had to physically
 > be loggged onto the box.
 >
 >  >  > ftp -s:c:\sbbs\exec\vert.ftp | find /v "Upload complete"
 >  >  > if not errorlevel 1 del c:\sbbs\data\vert.rep
 >
 >  > So that's a really old way to perform a QWK network call-out. It *should*
 >  > still work, so I'm not telling you to change it, but the new/supported
 >  > way is using exec/qnet-ftp.js:
 >  > https://wiki.synchro.net/module:qnet-ftp
 >
 > I will work on updating to that new method. Its been working for decades. I
 > think it stopped somewhere late last year. When I look at my messages, I
 > don't see anything new since late 2025. If you want, I can try to pin down a
 > more exact date before I try and fix things.

Oh? That's actually good news if it started failing with v3.19. That likely 
means it was something else that changed that caused that script/method to stop 
working for QWK packet transfers and *not* the upgrade to v3.21.

 > Also, what do you expect... I'm old. I've been here for a long time and you
 > know, if its not broke, don't fix it :)

I know, no judgment. :-) Yours is one of the longest running Synchronet 
systems, so I'd expect there to be plenty of cruft (running the chksetup.js 
could help identify some of it). I'll see if I can repro the isue with that old 
QWK/FTP method, but there's really no reason for you to keep using it. We moved 
from that batch file/sript to the qnet-ftp.bin Baja module like 25 years ago 
and then to the JavaScript module like 6 years ago. :-)
-- 
                                            digital man (rob)

Rush quote #54:
He'd love to spend the night in Zion, he's been a long, long while in Babylon
Norco, CA WX: 56.5øF, 70.0% humidity, 3 mph WNW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.37-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.