Re: Recycle semaphore?
  By: Va7aqd to Digital Man on Tue Mar 26 2019 10:28 am

 >   Re: Recycle semaphore?
 >   By: Digital Man to Va7aqd on Mon Mar 25 2019 06:47 pm
 >
 >  > The terminal server cannot recycle until there are:
 >  > 1. no nodes in use
 >  > 2. no foreground events (e.g. timed events) running in the event thread
 >
 >  > Your log output will tell you what's happening.
 >
 > Unfortunately, the logs aren't being terribly helpful, from what I can see.

Perhaps it's useful to compare your log output with what a successful recycle
looks like (as far terminal server log messages). This is a successful start-up
and recycle:

  3/26  03:59:02p  Synchronet Terminal Server Version 3.17 Revision C Debug
  3/26  03:59:02p  Compiled Mar 24 2019 03:30:33 with MSC 1800
  3/26  03:59:02p  Initializing on Tue Mar 26 15:59:02 2019 with options:
800070aa
  3/26  03:59:02p  Loading configuration files from s:\sbbs\ctrl\
  3/26  03:59:03p  Verifying/creating data directories
  3/26  03:59:03p  Verifying/creating node directories
  3/26  03:59:03p  Telnet Server listening on socket 71.95.196.34 port 23
  3/26  03:59:03p  Telnet Server listening on socket ::1 port 23
  3/26  03:59:03p  Telnet Server listening on socket 127.0.0.1 port 23
  3/26  03:59:03p  Telnet Server listening on socket 71.95.196.34 port 64
  3/26  03:59:03p  Telnet Server listening on socket 71.95.196.34 port 128
  3/26  03:59:03p  RLogin Server listening on socket 71.95.196.34 port 513
  3/26  03:59:03p  RLogin Server listening on socket :: port 513
  3/26  03:59:04p  SSH Server listening on socket 71.95.196.34 port 22
  3/26  03:59:04p  SSH Server listening on socket ::1 port 22
  3/26  03:59:04p  SSH Server listening on socket 127.0.0.1 port 22
  3/26  03:59:04p  Terminal Server thread started for nodes 1 through 4
  3/26  03:59:12p  Recycle semaphore signaled
  3/26  03:59:12p  Waiting for events thread to terminate...
  3/26  03:59:13p  Done waiting for events thread to terminate
  3/26  03:59:13p  Terminal Server thread terminating
  3/26  03:59:13p  1408 Telnet Server closing socket 71.95.196.34 port 23
  3/26  03:59:13p  1500 Telnet Server closing socket ::1 port 23
  3/26  03:59:13p  1508 Telnet Server closing socket 127.0.0.1 port 23
  3/26  03:59:13p  1512 Telnet Server closing socket 71.95.196.34 port 64
  3/26  03:59:13p  1524 Telnet Server closing socket 71.95.196.34 port 128
  3/26  03:59:13p  1248 RLogin Server closing socket 71.95.196.34 port 513
  3/26  03:59:13p  1532 RLogin Server closing socket :: port 513
  3/26  03:59:13p  1328 SSH Server closing socket 71.95.196.34 port 22
  3/26  03:59:13p  1280 SSH Server closing socket ::1 port 22
  3/26  03:59:13p  1480 SSH Server closing socket 127.0.0.1 port 22
  3/26  03:59:13p  Recycling server...
  3/26  03:59:15p  Reading s:\sbbs\ctrl\sbbs.vert.ini
  3/26  03:59:15p  Synchronet Terminal Server Version 3.17 Revision C Debug
  3/26  03:59:15p  Compiled Mar 24 2019 03:30:33 with MSC 1800
  3/26  03:59:15p  Initializing on Tue Mar 26 15:59:15 2019 with options:
800070aa
  3/26  03:59:15p  Loading configuration files from s:\sbbs\ctrl\
  3/26  03:59:16p  Verifying/creating data directories
  3/26  03:59:16p  Verifying/creating node directories
  3/26  03:59:16p  Telnet Server listening on socket 71.95.196.34 port 23
  3/26  03:59:16p  Telnet Server listening on socket ::1 port 23
  3/26  03:59:16p  Telnet Server listening on socket 127.0.0.1 port 23
  3/26  03:59:16p  Telnet Server listening on socket 71.95.196.34 port 64
  3/26  03:59:16p  Telnet Server listening on socket 71.95.196.34 port 128
  3/26  03:59:16p  RLogin Server listening on socket 71.95.196.34 port 513
  3/26  03:59:16p  RLogin Server listening on socket :: port 513
  3/26  03:59:16p  SSH Server listening on socket 71.95.196.34 port 22
  3/26  03:59:16p  SSH Server listening on socket ::1 port 22
  3/26  03:59:16p  SSH Server listening on socket 127.0.0.1 port 22
  3/26  03:59:17p  Terminal Server thread started for nodes 1 through 4

 > Currently the terminal server seems to be waiting to recycle - all nodes
 > have an [R] status - and will have been that way overnight.

How many nodes is "all nodes"? What do you have set for the FirstNode and
LastNode values in the [bbs] section of you ctrl/sbbs.ini file?

 > As far as the
 > log goes, it's not reporting on any event doing any work aside from the
 > events that are coming up and finishing as things come along here.

So long as you can see when the last event completed and it's still executing
new events, then the event thread isn't the problem.

 > I could post the logs somewhere if that would be useful - or if there's
 > something in particular I should be seeing in the logs that would explain
 > this, I'd be greatful to know what, exactly.  It sounds like if there were a
 > stuck event I should see some fairly constant logging about it?

No, but the last event log message would say something to the effect of
"Running timed event: suchandsuch" and then no more log messages.

What OS are you running? If *nix, then whether or not you run as root and
change user-IDs (configured in the [unix] section of sbbs.ini) and if Linux,
what version, all these things play a role in whether or not recycling is
supported.

How are you initiating the recycle?

                                            digital man

Synchronet "Real Fact" #14:
SBBSecho was originally written by Allen Christiansen (King Drafus) in 1994.
Norco, CA WX: 73.4°F, 36.0% humidity, 4 mph ENE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.07-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)