Listen on the socket systemd hands over, so a restart never answers 502 (#194)

OP OpenVibers committed 13 days ago · b9ac63e930 · 1 file, +4 −1

When the service is socket-activated (LISTEN_FDS=1 for this process), it listens on fd 3, the listener a
systemd .socket unit holds across restarts: requests that arrive during a deploy wait in the kernel's accept
queue and are served by the new process. Without the socket unit it listens on its port as before. The same
three lines Network, Media, Chat and Live use. 2026-10-31: a Codes deploy gave the owner a Cloudflare 502.

Changes

ddiff --git a/server/index.js b/server/index.js
iindex ed3f42e..1978626 100644
---- a/server/index.js
++++ b/server/index.js
@@@ -30,7 +30,10 @@ const { createPgTelemetrySink, startTelemetryRetention } = require('openvibe-sdk
          const r = await require('./forum/starters').syncFromFile(require('./db').getDb());
          if (r && (r.created || r.updated)) console.log(`[Starters] ${r.created} thread(s) added, ${r.updated} updated`);
      } catch (err) { console.warn('[Starters] not synced:', err.message); }
--    const server = app.listen(config.port, config.host, () => {
++    // Socket activation (2026-10-31): systemd's .socket unit holds the listener across restarts, so a deploy
++    // queues requests in the kernel instead of answering 502. Without the socket unit, the usual listen.
++    const socketActivated = process.env.LISTEN_FDS === '1' && Number(process.env.LISTEN_PID) === process.pid;
++    const server = app.listen(...(socketActivated ? [{ fd: 3 }] : [config.port, config.host]), () => {
          console.log(`[Community] ${config.nodeEnv} on http://${config.host}:${config.port} → ${config.baseUrl}`);
          console.log(`[Community] pastes: this site is the authority (PostgreSQL), identity via ${config.networkUrl}`);
      });