No, that message is from TWS/Gateway.

?

Nearly all messages from the IBC program start with a timestamp and “IBC: “ like this:

?

2024-10-22 22:12:26:085 IBC: Login has completed

?

The exceptions are the “IBC Settings” list and the “System Properties” list.

?

All other messages are either from the IBC scripts, or from TWS/Gateway.

?

It seems that IBKR are somewhat undisciplined about their logging: the vast majority of it is sensibly logged to the TWS/Gateway logfile (via the open source Log4J package), which is fine. But some things are just written out to stderr or stdout, and anything sent there ends up in the IBC logfile. Sometimes this information is useful, but most of the time it’s of no relevance to the end user and can be rather intrusive when trying to look through the IBC logfile.

?

My advice is to not worry about log messages from TWS/Gateway, unless they are clearly related to some issue with them (in which case you might consider reporting them to IBKR). However if you’re reporting a problem with IBC to me, always include the full IBC logfile: don’t try to weed out the stuff from TWS/Gateway.

?

As far as this particular message is concerned. If it’s preventing TWS/Gateway running properly you probably need to address it. I hit this when I was setting up a minimal Ubuntu Server a year or so ago, and had to ferret around to find out what (and how) to install. The libnss libraries is a Network Security Services component. I’m afraid I can’t offer any advice on what you should do.

?

?

?