WARNING [Chuck the postman's dispatching thread.7] com.ibm.rtc.stproxy.cluster.ServerLogin.loggedOut CLFRX0011W: Unable to log in to the Sametime community server CN=ALTERSAMETIME/OU=SRV/O=Company Error message is 8000021c
Du weiss aber schon, dass aktuell MongoDB nur in Version 3.6 supported ist?@Tode: es scheint, dass die Systemvoraussetzungen aktualisiert wurden, wenn "HCL Sametime® 11.0 FP2 | HCL Sametime® Meetings Pre-Release 11.5 System Requirements" genutzt wird. mongodb 3.6 und höher.
Du weiss aber schon, dass aktuell MongoDB nur in Version 3.6 supported ist? Hast Du alle Schritte aus dieser Anleitung (https://help.hcltechsw.com/sametime/11.0.0/admin/t_configure_mongodb.html) EXAKT befolgt?
Stimmen die Inhalte der dbconfig.properties auf dem Proxy?
MONGO_HOST=127.0.0.1
MONGO_CONNECT_TIMEOUT=1000
OFFLINE_DATABASE=MONGO
MONGO_WRITE_CONCERN_W_VAL=1
MONGO_AUTHID=c2FtZXRpbWVVc2VyLHNhbWV0aW1l
MONGO_PORT=27017
MONGO_WRITE_CONCERN_J_VAL=0
MONGO_IMG_LIMIT=20480
MONGO_DBNAME=mobileOffline
HTTP_CLIENT_TOTAL_CONNECTION=100
MONGO_USER=
DOMINO_TARGET_SERVER=stcommunity.domain.de
MONGO_GFS_CONNECT_TIMEOUT=2000
MONGO_PASSWORD=
MONGO_AUTH_DBNAME=admin
HTTP_CLIENT_MAX_CONNECTION_PER_ROUTE=20
HTTP_CLIENT_MAX_FOR_HOST=5
rs0:PRIMARY> rs.conf()
{
"_id" : "rs0",
"version" : 1,
"protocolVersion" : NumberLong(1),
"writeConcernMajorityJournalDefault" : true,
"members" : [
{
"_id" : 0,
"host" : "127.0.0.1:27017",
"arbiterOnly" : false,
"buildIndexes" : true,
"hidden" : false,
"priority" : 1,
"tags" : {
},
"slaveDelay" : NumberLong(0),
"votes" : 1
}
],
"settings" : {
"chainingAllowed" : true,
"heartbeatIntervalMillis" : 2000,
"heartbeatTimeoutSecs" : 10,
"electionTimeoutMillis" : 10000,
"catchUpTimeoutMillis" : -1,
"catchUpTakeoverDelayMillis" : 30000,
"getLastErrorModes" : {
},
"getLastErrorDefaults" : {
"w" : 1,
"wtimeout" : 0
},
"replicaSetId" : ObjectId("5f7ad1968fd76ab2c3dbad64")
}
}
"host" : "vsametime.dmz.firma.de:27017",
"host" : "127.0.0.1:27017",
MONGO_HOST=localhost
MONGO_CONNECT_TIMEOUT=1000
OFFLINE_DATABASE=MONGO
MONGO_WRITE_CONCERN_W_VAL=1
MONGO_AUTHID=...
MONGO_PORT=27017
MONGO_WRITE_CONCERN_J_VAL=0
MONGO_IMG_LIMIT=20480
MONGO_DBNAME=mobileOffline
HTTP_CLIENT_TOTAL_CONNECTION=100
MONGO_USER=
DOMINO_TARGET_SERVER=127.0.0.1
MONGO_GFS_CONNECT_TIMEOUT=2000
MONGO_PASSWORD=
MONGO_AUTH_DBNAME=admin
HTTP_CLIENT_MAX_CONNECTION_PER_ROUTE=20
HTTP_CLIENT_MAX_FOR_HOST=5
# network interfaces
net:
port: 27017
ipv6: true
bindIp: 127.0.0.1,192.168.1.23,::1
Das MongoDb Replica Set ist in meiner Konfiguration an den Hostnamen gebunden. Ich kann mich nicht mehr erinnern warum, aber es wird schon einen Grund haben warum ich das geändert habe ;-)Henning, vermutlich wegen diesem KB Artikel ;)
When MonogDB is deployed to a different host than the Community and the REPLICA_SET has the wrong hostname for the MongoDb server, the following symptoms will be reported by HCL Sametime 11 clients.The above scenarios suggest Persistent Chat, specifically the connection to MongoDB, is not working correctly. One common reason for this is the MongoDB replication configuration is providing a hostname that is incorrect or unresolvable by the Community or Sametime Proxy servers.
- Webclients using /chat will not see messages sent or received. History may load on login, but messages after that will not be seen.
- HCL Sametime 11 Mobile Clients will not log in successfully. There will be a long delay attempting to login, before any error is returned.
cfg = rs.conf()
cfg.members[0].host = "meinedomain.de:27017"
rs.reconfig(cfg)
No host described in new configuration 2 for replica set rs0 maps to this node.
use admin
db.shutdownServer()
service mongod start
ST_TOKEN_TYPE=LtpaToken Sametime^M
ST_ORG_NAME=^M
# Sametime configuration file
[AuthToken]
STAuthenticationMethod=0
[Config]
ST_COMMUNITY_ID=Augsburg
VP_SECURITY_LEVEL=7000
VPMX_CAPACITY=20000
VPS_IGNORE_UNKNOWN_CLIENT_IP=1
[...]
VP_PRIV_SYM=1
ClusterGroupAffinity=Isolation
VPS_PREFERRED_LOGIN_TYPES=14C4,14C3,14C2,14C1,14B6,14B4,14B2,14AF,14AD,14A2,14A0,1454,1453,1452,1451,1443,143F,143E,143D,143C,
143B,143A,1439,1438,1437,1436,1435,1434,1312,1311,130F,130E,130D,130C,130B,130A,1308,1306,1304,12A2,129D,129C,129B,129A,122B,122A
ST_BRANDING_INFO=standard
EnableUnyteHomepageUI=1
ST_JAVA_LIB_PATH=/opt/hcl/domino/notes/11000000/linux
IMOnly=0
STOFFLINE_MSGS_EXCLUDE_CLIENT_TYPES=100A,101A,1200,1431,1432,1434,1435,1437,143E,143F
ST_CL_MONGODB=1
VP_ONLY_SINGLE_LOGIN_ALLOWED=0
VP_NEWER_LOGIN_WINNER=1
[...]
# ST_CONFIG_XML=/local/notesdata/StCommunityConfig.xml
HTMLRootDirectory=/local/notesdata/domino/html
ConfigurationHost=vsametime.dmz.company.de
VPS_LOCALHOST=vsametime.dmz.company.de
[...]
# 2020-01-07 HH eingefügt
VPS_NAME=CN=Sametime/OU=Srv/O=Company
ConfigurationPort=8080
SametimeCluster=CN=Sametime/OU=Srv/O=Company
SametimeDirectory=/local/notesdata
Locale=de
SametimeEventServerPort=9092
[...]
VPMX_SINGLE_IP_PORT=80,443,563
ST_CONFIG_XML=/local/notesdata/StCommunityConfig.xml
[...]
[ST_BB_NAMES]
ST_CHAT_DATABASE=mongodb
NWAY_PRIMARY_KEY=OrigSId
FLEXNET_URL=
ST_CHAT_LOG=mongodb
ST_AUTH_TOKEN=notes
[...]
Failed to load libstchatloggingmongodb (libssl.so.10: cannot open shared object file: No such file or directory)Konnte ich auch einen Knowledgebase-Eintrag bei HCL (https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0076238&sys_kb_id=f64f1c931b071454a2f48661cd4bcb45) finden.