Re: Error in alarm-logger.sh

[Giovanni Savarese LNL via Tech-talk <tech-talk at aps.anl.gov>]

Hi,

I've worked on the same problem at the beginning of this year and what I understood is that not all phoebus alarm logger versions work well with all versions of elasticsearch. Also I noticed that to work with the provided alarm logger version some changes on the service port number are required (8080 instead 9000 if I remember correctly).

So far I tried different solutions and at this link https://github.com/giosava94/docker-phoebus-alarm you can find my dockerized solution.

I hope it helps you.
Regards,
Giovanni S

PS I did not try your configuration. I just give you some material for reference.

On 06/07/23 22:10, Eusebio Naif Al-Soliman Fuentes via Tech-talk wrote:

Hello everyone.

 

I have CSS-Phoebus working fine with the alarm-server (Kafka and Zookeeper are also working fine). However, I have encountered an issue while attempting to start the alarm-logger.sh service.

 

To provide some context, I am using Docker to run Elasticsearch and Kibana. Below it's the docker-compose file that I have been using to start these services:

 

version: "3.0"

services:
  elasticsearch:
    container_name: es-container
    image: docker.elastic.co/elasticsearch/elasticsearch:8.2.3
    environment:
      - xpack.security.enabled=false
      - "discovery.type=single-node"
    networks:
      - elastic
    ports:
      - 9200:9200  
      
  kibana:
    container_name: kb-container
    image: docker.elastic.co/kibana/kibana:8.2.3
    environment:
      - ELASTICSEARCH_HOSTS=http://es-container:9200
    networks:
      - elastic
    depends_on:
      - elasticsearch
    ports:
      - 5601:5601

networks:
  elastic:
    driver: bridge

I downloaded the alarm-logger from the following link: https://controlssoftware.sns.ornl.gov/css_phoebus/nightly/

 

When I try to launch the alarm-logger by running 'sh alarm-logger.sh' in the console, I encounter the following error logs:

 

2023-07-06 21:54:41 INFORMACIÓN [org.phoebus.alarm.logging.AlarmLoggingService] Alarm Logging Service (PID 14002)
jul 06, 2023 9:54:42 P. M. org.phoebus.framework.preferences.PreferencesReader <init>
GRAVE: Cannot read default preference settings for class org.phoebus.alarm.logging.AlarmLoggingService from /alarm_logging_service.properties
Commands:
    help             - Show help.
    shutdown         - Shut alarm logger down and exit.

 > jul 06, 2023 9:54:42 P. M. org.apache.kafka.common.config.AbstractConfig logUnused
ADVERTENCIA: The configuration 'admin.retries' was supplied but isn't a known config.
jul 06, 2023 9:54:42 P. M. org.apache.kafka.common.config.AbstractConfig logUnused
ADVERTENCIA: The configuration 'admin.retries' was supplied but isn't a known config.
jul 06, 2023 9:54:43 P. M. org.elasticsearch.client.RequestLogger logResponse
ADVERTENCIA: request [PUT http://localhost:9200/_template/alarms_state_template?master_timeout=30s&include_type_name=true&create=true] returned 1 warnings: [299 Elasticsearch-8.2.3-9905bfb62a3f0b044948376b4f607f70a8a151b4 "Legacy index templates are deprecated in favor of composable templates."]

I have been troubleshooting the issue, but so far, I haven't been able to resolve it. If anyone has any insights or suggestions on how to fix this issue, I would greatly appreciate your assistance. 

Maybe the issue is related to the configuration.

 

Thank you for your attention.

--

Saludos/Best regards

University of Granada  

Eusebio Naif Al-Soliman Fuentes
MSc. Data Science and Computer Engineering

eunaif at correo.ugr.es