TZUTC: -0700   
   MSGID: 56267.sync_sys@1:103/705 2b42da0f   
   PID: Synchronet 3.20a-Linux master/e93b6dfa6 Aug 22 202 GCC 12.2.0   
   TID: SBBSecho 3.20-Linux master/984c371ae Sep 06 2024 20:48 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   https://gitlab.synchro.net/main/sbbs/-/issues/781#note_5579   
      
   I'm not clear on how this issue could happen. It looks like a race condition   
   between the broker connection attempt in the terminal server thread and   
   another thread (the event thread) attempting to publish (node status, in this   
   case). But the terminal server thread waits until the MQTT broker connection   
   is either successful or not before continuing and should log the result of the   
   broker-connection attempt:   
   ```   
   lprintf(lputs, LOG_DEBUG, "MQTT broker-connect (%s:%d) successful",   
   cfg->mqtt.broker_addr, cfg->mqtt.broker_port);   
   ```   
   or:   
   ```   
   lprintf(lputs, LOG_ERR, "MQTT broker-connect (%s:%d) failure: %d",   
   cfg->mqtt.broker_addr, cfg->mqtt.broker_port, result);   
   ```   
      
   Did you have debug-level log output enabled?   
   --- SBBSecho 3.20-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 90/1 103/705 105/81 106/201 124/5016 153/757 7715 154/10   
   SEEN-BY: 154/30 203/0 218/700 221/0 226/30 227/114 229/110 114 206   
   SEEN-BY: 229/317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 282/1038 291/111 292/8125 301/1 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888   
   SEEN-BY: 633/280 712/848 770/1 5020/400 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426