A function for reopening a winston File logging transport post logrotation on a HUP signal. To send a HUP to your node service, use the postrotate configuration option from logrotate. `postrotate kill -HUP ‘cat /var/run/mynodeservice.pid‘`

winston-logrotate.js

function reopenTransportOnHupSignal(fileTransport) {
  process.on('SIGHUP', function() {
    var fullname = path.join(fileTransport.dirname, fileTransport._getFile(false));

    function reopen() {
      if (fileTransport._stream) {
        fileTransport._stream.end();
        fileTransport._stream.destroySoon();
      }

      var stream = fs.createWriteStream(fullname, fileTransport.options);
      stream.setMaxListeners(Infinity);

      fileTransport._size = 0;
      fileTransport._stream = stream;

      fileTransport.once('flush', function () {
        fileTransport.opening = false;
        fileTransport.emit('open', fullname);
      });

      fileTransport.flush();
    }

    fs.stat(fullname, function (err) {
      if (err && err.code == 'ENOENT') {
        return reopen();
      }
    });

  });
}

Have you considered using copytruncate instead of executing kill -HUP... in postrotate. copytruncate will copy the current log file to the rotated file and then truncate the original log file to 0 bytes. This allows node to keep writing to the same stream.

I would avoid using logrotatecopytruncate if you are worried about logging log data. Per the logrotate docs:

copytruncate
Truncate the original log file in place after creating a copy,
instead of moving the old log file and optionally creating a new
one, It can be used when some program can not be told to close
its logfile and thus might continue writing (appending) to the
previous log file forever. Note that there is a very small time
slice between copying the file and truncating it, so some log-
ging data might be lost. When this option is used, the create
option will have no effect, as the old log file stays in place.

please, can you show who is fileTransport param?