Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
ref:mqtt [2024/01/12 17:30] – [Servers] Add pause and resume server topics digital manref:mqtt [2024/07/11 18:37] (current) – [Servers] Add server/+/highwater topic digital man
Line 92: Line 92:
 The control and monitoring of a specific Synchronet instance is done through this "host sub-topic" tree.  The control and monitoring of a specific Synchronet instance is done through this "host sub-topic" tree. 
  
-Publishing any message to the **recycle** sub-topic of any host topic will initiate a recycling of that host's servers (all of them).+^ Host sub-topic ^ Description  ^ 
 +| recycle        | Publishing any message to the **recycle** sub-topic of any host topic will initiate a recycling of that host's servers (all of them). | 
 +| pause          | Publishing any message to the **pause** sub-topic of any host topic will initiate pause that host's servers (all of them), preventing the acceptance of any new incoming client connections. | 
 +| resume         | Publishing any message to the **resume** sub-topic of any host topic will un-pause that host's servers (all of them), that we previously paused via the **pause** topic. |
  
 ===== Servers ===== ===== Servers =====
Line 118: Line 121:
 The server status contains more details/statistics and is published more often when "High" MQTT->Publish Verbosity is enabled in [[util:SCFG]]. The server status contains more details/statistics and is published more often when "High" MQTT->Publish Verbosity is enabled in [[util:SCFG]].
  
-Publishing any message to the **recycle** sub-topic of any server topic will initiate a recycling of that server. +^ Server sub-topic ^ Description  ^ 
-Publishing any message to the **pause** sub-topic of any server topic will prevent that server from accepting any new incoming client connections. +| recycle          | Publishing any message to the **recycle** sub-topic of any server topic will initiate a recycling of that server. | 
-Publishing any message to the **resume** sub-topic of any server topic will un-pause that server, returning to the "ready" state, accepting incoming client connections.+| pause            | Publishing any message to the **pause** sub-topic of any server topic will prevent that server from accepting any new incoming client connections. | 
 +| resume           | Publishing any message to the **resume** sub-topic of any server topic will un-pause that server, returning to the "ready" state, accepting incoming client connections. |
  
 Each server topic has the following sub-topics for status reporting: Each server topic has the following sub-topics for status reporting:
Line 130: Line 134:
   * sbbs/+/host/+/server/+/**client/action/#** - client actions (e.g. connect, disconnect)   * sbbs/+/host/+/server/+/**client/action/#** - client actions (e.g. connect, disconnect)
   * sbbs/+/host/+/server/+/**served** - total clients served since server was started   * sbbs/+/host/+/server/+/**served** - total clients served since server was started
 +  * sbbs/+/host/+/server/+/**highwater** - highest concurrent client count since server was started
   * sbbs/+/host/+/server/+/**error_count** - total errors logged since server was started   * sbbs/+/host/+/server/+/**error_count** - total errors logged since server was started
  

Trace: