There's an upgrade_to_SBBS_v3.21e.exe in that zip, I assume you ran it?
Not a lot of sysops use sbbsNTsvcs.exe, so first question would: do you have problems if you disable the NT services and just run sbbs.exe or sbbsctrl.exe directly? In the mean while, I'll do some more testing with sbbsNTsvcs.exe and sbbsctrl.exe together to see what I can find.
It sounds like the event thread is hung runing a QWKnet call-out event. How many hubs do you have setup in SCFG->Networks->QWK and what are their call-out command-lines? That doesn't explain the not answering incoming connections though.
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.
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 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.
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.
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. :-)
So is it still failing the vert.bat method even after you switched from NT services? The related log output (the "Events" window or the data/events.log file entries) might be helpful in diagnosing why.
No, the Synchronet FTP server (and Vertrauen) still support passive FTP: It appears Windows' ftp.exe has never supported passive mode:
https://learn.mic rosoft.com/en-us/answers/questions/1821850/ftp-exe-and-passive-mode
Maybe you were using a different ftp.exe (not from Microsoft) at some point?
Speaking of cruft, I still have a bunch of modem configuration files in my
CTRL folder (*.MDM). Does synchronet still support modems? Can I remove
these files?
No, you can remove them.
Old files are harmless (unless they're really large, e.g. log files). There's the exec/cleanup.js script (you can run with jsexec) and it'll delete many old/unused files, but not all of them.
| Sysop: | Morningstarr |
|---|---|
| Location: | Mt. Pleasant Nc |
| Users: | 35 |
| Nodes: | 250 (0 / 250) |
| Uptime: | 38:01:08 |
| Calls: | 161 |
| Calls today: | 161 |
| Files: | 613 |
| U/L today: |
614 files (5,824M bytes) |
| D/L today: |
13,064 files (168G bytes) |
| Messages: | 10,523 |
| Posted today: | 621 |