Endless loop in scim_persistence.log when in Couchbase

[jgomer2001]

In CE 4.2.2 when tailing scim_persistence.log the following repeats endlessly even at idle (no request sent to SCIM service):

2021-01-07 21:04:09,598 DEBUG [cb-computations-3] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - Completed refreshing config for bucket "gluu_token"
2021-01-07 21:04:09,600 DEBUG [cb-io-1-2] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:85) - [localhost/127.0.0.1:18093][QueryEndpoint]: Connected Endpoint.
2021-01-07 21:04:09,600 DEBUG [cb-io-1-2] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:85) - [localhost]: Connected (DEGRADED) to Node
2021-01-07 21:04:09,615 DEBUG [cb-io-1-2] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:85) - [localhost/127.0.0.1:18093][QueryEndpoint]: Channel Active.
2021-01-07 21:04:09,656 DEBUG [cb-io-1-2] [deps.io.netty.handler.ssl.SslHandler] (SslHandler.java:1759) - [id: 0xd59355e7, L:/127.0.0.1:37280 - R:localhost/127.0.0.1:18093] HANDSHAKEN: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
2021-01-07 21:04:09,895 DEBUG [cb-computations-1] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - New Bucket gluu_user config proposed.
2021-01-07 21:04:09,895 DEBUG [cb-computations-1] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - Completed refreshing config for bucket "gluu_user"
2021-01-07 21:04:09,897 DEBUG [cb-computations-2] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - New Bucket gluu_token config proposed.
2021-01-07 21:04:09,897 DEBUG [cb-computations-2] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - Completed refreshing config for bucket "gluu_token"
2021-01-07 21:04:09,898 DEBUG [cb-computations-3] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - New Bucket gluu config proposed.
2021-01-07 21:04:09,898 DEBUG [cb-computations-3] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - Completed refreshing config for bucket "gluu"
2021-01-07 21:04:09,899 DEBUG [cb-computations-3] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - New Bucket gluu_site config proposed.
2021-01-07 21:04:09,900 DEBUG [cb-computations-3] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - Completed refreshing config for bucket "gluu_site"
2021-01-07 21:04:09,900 DEBUG [cb-computations-1] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - New Bucket gluu_cache config proposed.
2021-01-07 21:04:09,900 DEBUG [cb-computations-1] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - Completed refreshing config for bucket "gluu_cache"
2021-01-07 21:04:09,901 DEBUG [cb-computations-2] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - New Bucket gluu_session config proposed.
2021-01-07 21:04:09,901 DEBUG [cb-computations-2] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:90) - Completed refreshing config for bucket "gluu_session"

It repeats over and over with no pauses. This seems abnormal. Log level is set to DEBUG

[jgomer2001]

The same goes with oxauth_persistence.log

[yurem]

I'm not sure that these are errors. These are just DEBUG. Can you try to tail and add command grep 'com.couchbase' | grep 'ERROR' ?

[jgomer2001]

I don't mean these are errors, however the rate at which they are shown is suspicious. If refreshing config for buckets at a very high speed is a expected behvior, then we can simply try not to log certain messages to avoid excesive noise.

[yurem]

I checked persistence log on another server with 4.2.1 which we installed long time.

It also has "suspicious" frequent logs messages:

2021-01-11 15:36:16,268 INFO  [cb-io-1-3] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:120) - [cb-bench-backend.gluu.org/68.183.56.12:18093][QueryEndpoint]: Got notified from Channel as inactive, attempting reconnect.
2021-01-11 15:36:16,970 INFO  [cb-io-1-4] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:120) - [cb-bench-backend.gluu.org/68.183.56.12:18093][QueryEndpoint]: Got notified from Channel as inactive, attempting reconnect.
2021-01-11 15:36:17,200 INFO  [cb-io-1-1] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:120) - [cb-bench-backend.gluu.org/68.183.56.12:18093][QueryEndpoint]: Got notified from Channel as inactive, attempting reconnect.
2021-01-11 15:36:17,634 INFO  [cb-io-1-2] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:120) - [cb-bench-backend.gluu.org/68.183.56.12:18093][QueryEndpoint]: Got notified from Channel as inactive, attempting reconnect.
2021-01-11 15:36:21,426 INFO  [cb-io-1-3] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:120) - [cb-bench-backend.gluu.org/68.183.56.12:18093][QueryEndpoint]: Got notified from Channel as inactive, attempting reconnect.
2021-01-11 15:36:22,125 INFO  [cb-io-1-4] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:120) - [cb-bench-backend.gluu.org/68.183.56.12:18093][QueryEndpoint]: Got notified from Channel as inactive, attempting reconnect.
2021-01-11 15:36:22,344 INFO  [cb-io-1-1] [com.couchbase.client.core.logging.Slf4JLogger] (Slf4JLogger.java:120) - [cb-bench-backend.gluu.org/68.183.56.12:18093][QueryEndpoint]: Got notified from Channel as inactive, attempting reconnect.

[yurem]

I still think that these are internal CB server and CB SDK communication messages. We need to send question to CB about them to clarify if it's issue or not.