Unable to process clotho Kafka topics

[bnesbitt]

We're seeing a flood of issues on our development instance and we've had no luck to this point pinpointing exactly what the cause is.  We just updated to Utah Patch 1 but were seeing this while on Tokyo.  Any ideas on how to suppress this?

Unable to process clotho Kafka topics
com.glide.hermes.client.glide.util.HermesStatusUtil.throwIfDisabled(HermesStatusUtil.java:37)
com.glide.hermes.client.glide.util.HermesStatusUtil.throwIfUnavailable(HermesStatusUtil.java:41)
com.glide.hermes.client.glide.GlideHermesTopicManager.<init>(GlideHermesTopicManager.java:50)
com.glide.hermes.client.glide.GlideHermesTopicManager.<init>(GlideHermesTopicManager.java:43)
com.snc.clotho.kafka.KafkaTopicDAO.fetchKafkaTopics(KafkaTopicDAO.java:45)
com.snc.clotho.kafka.ClothoKafkaTopicPublisher.publishTopics(ClothoKafkaTopicPublisher.java:52)
com.snc.clotho.kafka.ClothoKafkaTopicPublisher.run(ClothoKafkaTopicPublisher.java:43)

[SusanWinKY]

Hi @bnesbitt - can you provide details of that PRB? It's not accessible to me in Now Support. Thanks.

We also don't use any of the mentioned products (hermes, clotho, kafka, metric base).

[Dale Hynes]

The system properties did not exist on our instances so I have added them but;

1) I assume it should be 'kafka' and not 'kakfa'?

2) The underscores versus dots placement is not the same - can you check and update?

3) Are the 60 and 120 values strings or integers or ?

Thanks.

[geoffcox]

I tried looking up PRB1634353, got "No problem found.".

[Bert_c1]

You may only see that if you have a Support Case where that PRB is responsible.

[JC Moller]

I had previously openend a PRB-ticket with the SN Support. I still have a few of these errors in the logs per day and have set the system property values to 86400 (both). The PRB-ticket is closed and a fix is targeted for the Washington DC version. More info:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1290495

BR, Jan

Originally received this from the support after opening the ticket:

Issue:
Errors in the localhost after recent Utah upgrade "ERROR *** Hermes is installed but isn't fully configured yet"

2023-06-14 12:10:32 (366) glide.clotho.kafka.topic_publisher SYSTEM SEVERE *** ERROR *** Hermes is installed but isn't fully configured yet

Cause:
We have observed this issue in latest release family and already have defect PRB1634353 for this issue.
Also, please note that below plugins were installed automatically when you upgrade to Utah as Hermes Messaging Service is a NEW feature in Utah.

com.glide.rollback
com.glide.highcharts
com.snc.clotho

MetricBase plugin will try to sync Hermes topic configuration with Clotho server every 1 minute by default, As this plugins are installed automatically these were not configured which is the defect.

Temp relief:
These logs will not get any functionality degrade, but to reduce frequency of logging ,You can add/update below 2 properties.
(Note:Message will be written in the logs in any case if you update this property or not , This property is to reduce the frequency of logging.)

You can change below properties as per your requirement, But please do note OOB values if you need to revert back in future. . You might need to create properties if not already exist with TYPE as INTEGER
-glide.clotho.kakfa.topic_publisher.interval.seconds
- sync interval in seconds
-
glide.clotho.kakfa_topic_publisher.longer.interval.seconds
- fallback internal in seconds (if operation does not finish during the first interval)

Example if you set the value as 60 , you will be seeing logs for every 60 sec if you provide as 120 then logs will be seen every 2 min interval.