All (And DM),
I did my usual every couple of months download of sbbs_dev.zip and sbbs_run.zip and copied over my exec and xtrn directories. I usually need to do a couple of tweaks here and there, and it's been painless the last times I've done this.
This time, when I restarted sbbs_ctrl.exe, I got the new BBS wizard.
Cancelled that and saw my usual config.
Everything is working now, except my
node list in sbbs_ctrl shows nodes 5 and 6 as 'Waiting for node 1 to finish external event'. Node 1 is listed as "Waiting for connection".
Is there a way to manually clear the node status of nodes 5 and 6?
poindexter FORTRAN wrote to All <=-
All (And DM),
I did my usual every couple of months download of sbbs_dev.zip
and sbbs_run.zip and copied over my exec and xtrn directories. I
usually need to do a couple of tweaks here and there, and it's
been painless the last times I've done this.
This time, when I restarted sbbs_ctrl.exe, I got the new BBS
wizard. Cancelled that and saw my usual config. Everything is
working now, except my node list in sbbs_ctrl shows nodes 5 and 6
as 'Waiting for node 1 to finish external event'. Node 1 is
listed as "Waiting for connection".
Is there a way to manually clear the node status of nodes 5 and
6?
Digital Man wrote to poindexter FORTRAN <=-
I did my usual every couple of months download of sbbs_dev.zip and sbbs_run.zip and copied over my exec and xtrn directories. I usually need to do a couple of tweaks here and there, and it's been painless the last times I've done this.
When was the last time you did this?
Yes, using the node utility (e.g. exec/node.exe), you can set any node
to any state. But you shouldn't have to if your terminal server's "lastnode" setting is set to node 6.
It sounds like maybe you upgrade from v3.19 to v3.20 but didn't run 'jsexec update' as part of that process. --
Digital Man wrote to poindexter FORTRAN <=-
I did my usual every couple of months download of sbbs_dev.zip and sbbs_run.zip and copied over my exec and xtrn directories. I usually need to do a couple of tweaks here and there, and it's been painless the last times I've done this.
When was the last time you did this?
Probably January? Not too long ago.
Yes, using the node utility (e.g. exec/node.exe), you can set any node to any state. But you shouldn't have to if your terminal server's "lastnode" setting is set to node 6.
That did it -- in SCFG under system, it was set to 4 nodes, not 6. Not
sure what I did. Nodes 5 and 6 reset when the system recycled.
It sounds like maybe you upgrade from v3.19 to v3.20 but didn't run 'jsexec update' as part of that process. --
I was definitely on 3.20 before.
I got cocky, usually I snapshot the VM or at least copy the directories
I'm overwriting elsewhere first. Live and Learn.
I was definitely on 3.20 before.
I got cocky, usually I snapshot the VM or at least copy the directories
I'm overwriting elsewhere first. Live and Learn.
Sysop: | Lmorchard |
---|---|
Location: | Portland, OR |
Users: | 58 |
Nodes: | 16 (0 / 16) |
Uptime: | 134:31:36 |
Calls: | 368 |
Files: | 1 |
Messages: | 22,590 |