Log4j: WARN No Appenders could be found for logger

HCL Sametime Sametime Forum
,
1

Hi to All,

I have Sametime V11 SP1, Domino V11.01 run on CentosOS 8 VM. After all services started successfully the following messages are displayed in the console (red color)

[079733:000002-00007F4FC0FD8740] 04/14/2020 04:11:09 PM Sametime Server: Starting services
Building service start order from dependencies...
Found event server service.
Starting services...
Starting event server service.
[079733:000002-00007F4FC0FD8740] 04/14/2020 04:11:11 PM Sametime Server: Running
Starting service [Java Services].
Process 80782 created.
Service [Java Services] started successfully.
Starting service [Community Server].
Process 80814 created.
Service [Community Server] started successfully.
All services started successfully.
[080721:000002-00007FD0AEC3E300] 04/14/2020 04:11:13 PM Sametime: Server startup successful. ......
MongoDB Change Stream Listener [com.mongodb.MongoDatabaseImpl@d2b34d48] [com.mongodb.MongoCollectionImpl@79ae53ef]
log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.params.DefaultHttpParams).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Cache() - Mongo based cache client uri[mongodb://127.0.0.1:27017] db[chatlogging] collection[CONVOMAP]

Any idea why it may be?

No another messages of error are displayed.

Thanks.

2

Hello,

Can you open a HCL Support Case so we can review what is causing this. I would start with a stdiagzip collection and information about if this server was Domino 11.0/Sametime 11.0 and upgraded to Domino 11.0.1/Sametime 11.0 FP1. Or a new base install with Domino 11.0.1 and Sametime 11.0 FP1.

Thanks,
Trevor Tallackson
Sametime Support

3

Hi Trevor,

all is a new fresh installation.

  • CentosOS 8.1.1911
  • Domino 11.0.1
  • Sametime 11.0 FP1
  • Sametime ProxyServer 11 FP1
  • Mongo DB 4.2.5 (It is not the version that the documentation says)

All in vmware ESXi 6.7.x

4

The version of Mongo you are using is not supported. You must use the version specified in the documentation.

5

Hi Roberto,

i downgrade the version of Mongo to 3.6.X, but the message continue.

Thanks

6

I know is a stupid question, but have you created the log directory in Mongo ?

7

Hi Roberto.

Yes the directory was created according to the image of the configuration file of Mongo

Community-Pasted-Attachment-1587451271728.png672×107 3.54 KB

Community-Pasted-Attachment-1587451405898.png1085×104 14 KB

8

No idea then. Try to open a case with Support

9

I have the same problem.

Support notified. Will post update here when receive answer

10

Hi Eric,

The Trevor's question is critical because if you have upgraded your domino server to 11.0.1 after a previous sametime comunity server 11.0 installation, you may have issues as the paths used by domino 11.0.1 are not the same as 11.0

https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0077949

11

Hi Jacques,

I install MongoDB first, then Domino 11.0.1, then Sametime 11.0 followed by FP1.

And finally Sametime Proxy 11 followed by FP1

With this config, only the Sametime Chat StandAlone or Embedded (1533) is functionally.

Regards.

12

Here's an answer from HCL Support:

For the log4j prints, I have created this ticket to address - they can be ignored as it is a warning only and simply means that the part we were trying to get prints from isnt there - so its also deprecated.