[BUG] Closing stale open session for new outgoing prekey bundle / Closing session: SessionEntry

[oscarguindzberg]

Describe the bug I have a server with 15 connected whatsapp users. I find this on the log from time to time:

Closing stale open session for new outgoing prekey bundle
Closing session: SessionEntry {
  _chains: {
    xxx: { chainKey: [Object], chainType: 1, messageKeys: {} }
  },
  registrationId: 149285497,
  currentRatchet: {
    ephemeralKeyPair: {
      pubKey: <Buffer xx xx xx ...>,
      privKey: <Buffer xx xx xx ...>
    },
    lastRemoteEphemeralKey: <Buffer xx xx xx ...>,
    previousCounter: 0,
    rootKey: <Buffer xx xx xx ...>
  },
  indexInfo: {
    baseKey: <Buffer xx xx xx ...>,
    baseKeyType: 1,
    closed: -1,
    used: xxx,
    created: 1718893928273,
    remoteIdentityKey: <Buffer xx xx xx ...>
  },
  pendingPreKey: {
    signedKeyId: 7192122,
    baseKey: <Buffer xx xx xx ...>,
    preKeyId: 1310
  }
}

I know this is printed by libsignal, I guess these lines are the culprits:

• https://github.com/adiwajshing/libsignal-node/blob/11dbd962ea108187c79a7c46fe4d6f790e23da97/src/session_builder.js#L46
• https://github.com/adiwajshing/libsignal-node/blob/11dbd962ea108187c79a7c46fe4d6f790e23da97/src/session_record.js#L273

To Reproduce Steps to reproduce the behavior: Don't know how to reproduce, it happens from time to time on a server with 15 connected whatsapp users.

Expected behavior No errors on the log

Environment (please complete the following information):

• Is this on a server? yes

• What do your connectOptions look like?

  const { version, isLatest } = await fetchLatestBaileysVersion()
  const { state, saveCreds } = await useMultiFileAuthState('myPath')
  const msgRetryCounterCache = new NodeCache()
  
      async function getMessage(key)  {
          if(store) {
              const msg = await store.loadMessage(key.remoteJid, key.id)
              return msg?.message || undefined
          }
          // only if store is present
          return proto.Message.fromObject({})
      }
  
  makeWASocket({
          version,
          logger,
          printQRInTerminal: false,
          mobile: false,
          auth: {
              creds: state.creds,
              keys: makeCacheableSignalKeyStore(state.keys, logger),
          },
          msgRetryCounterCache,
          generateHighQualityLinkPreview: true,
          // ignore broadcast and newsletter messages
          shouldIgnoreJid: jid => !jid || isJidBroadcast(jid) || isJidNewsletter(jid),
          // implement to handle retries & poll updates
          getMessage,
          shouldSyncHistoryMessage: () => true,
          markOnlineOnConnect: false
      })

• Do you have multiple clients on the same IP? yes, 15 clients
• Are you using a proxy? no

Additional context Using baileys v6.7.5

[oscarguindzberg]

These bugs may be related https://github.com/WhiskeySockets/Baileys/issues/885 https://github.com/WhiskeySockets/Baileys/issues/886 https://github.com/WhiskeySockets/Baileys/issues/888

[oscarguindzberg]

I don't understand why was the issue closed.

[PurpShell]

I don't understand why was the issue closed.

i think he closed due to duplicate

[Anshuljai]

Any solution?

[DanNisenson]

Same, using SQL

[lucianodltec]

+1

[lucas-linvix]

hello I have this problem too.

[andre-mr]

I'm experiencing the same issue and have an additional question: Where in the library is this log being generated? When I initialize the socket, I set the logger level to silent using the pino module to prevent any logs from being printed to the terminal:

const sock = makeWASocket({
  auth: state,
  version: currentVersion,
  printQRInTerminal: true,
  logger: pino({ level: 'silent' }),
});

However, this specific error is still being printed. What part of the library is outputting this log and ignoring the silent parameter?

[andre-mr]

I know this is printed by libsignal, I guess these lines are the culprits:

• https://github.com/adiwajshing/libsignal-node/blob/11dbd962ea108187c79a7c46fe4d6f790e23da97/src/session_builder.js#L46
• https://github.com/adiwajshing/libsignal-node/blob/11dbd962ea108187c79a7c46fe4d6f790e23da97/src/session_record.js#L273

Sorry, I hadn't seen that part of your post. I went into those files and simply commented out those lines, because those logs aren't interfering with the bot's operation, they're just polluting the terminal I use to see messages from my own code.

Developers could check if those logs are necessary maybe. Thanks!