Re: [External] AW: phoebus alarm-logging UI blank

[Paul Sichta via Tech-talk <tech-talk at aps.anl.gov>]

Hello Malte,

Changing the es_host from an IP#  130.... to localhost made the UI work, thanks.   I thought I had tried that already, but your vote made me try again.   

Some further googling revealed the SLF4J error message as a bug in m2e.

"The above error came after updating the m2e to version 1.1".  It should be fixed in v1.5

Regards,

-ps

On Fri, Feb 18, 2022 at 4:47 AM Gotz, Malte <malte.gotz at helmholtz-berlin.de> wrote:

Hello Paul,

 

your problem is more likely to be client side. Did you set the es_host preference? Since you see documents in the elastic index, the alarm-logging service is at least doing something.

Regarding the missing binding: It should not affect the functionality of the logger-service, just your ability to figure out if it has problems. Furthermore, the alarm-logger pom already has the slf4j-jdk14 dependency which provides the required binding. So, I don’t know why you are seeing this error.

 

>  I was hoping maven v3 isn't the problem.

 

Maven v3 should not be a problem. I am using maven 3.6.3 and it is working fine. Rather 3.0.5 might be a bit out of date.

 

Regards,

Malte

 

 

Von: Tech-talk <tech-talk-bounces at aps.anl.gov> Im Auftrag von Paul Sichta via Tech-talk
Gesendet: Donnerstag, 17. Februar 2022 23:15
An: tech-talk at aps.anl.gov
Betreff: Re: phoebus alarm-logging UI blank

 

I should add I am using Maven 3.0.5.  

 

The phoebus README said to use Maven 2.x .... but that uses http to access maven central plugins, so you get 501 code.

I was hoping maven v3 isn't the problem.

 

 

I also tried openJDK 11.0.2, same SLF4J issue

-ps

 

On Thu, Feb 17, 2022 at 12:23 PM Paul Sichta <psichta at pppl.gov> wrote:

I cannot get the Alarm Log Table to show anything.  I'm using the default phoebus installation with the Accelerator topic, everything on localhost.

 

Versions:

current phoebus from git

openJDK 14.0.1

Kafka 2.12-2.4.0,  running zk and kafka in separate terminals

elasticsearch 6.8.4,  this running as a service

 

The kafka and alarm-logger terminals show the alarm events, and the Elasticsearch shows the indices:

curl -XGET localhost:9200/_cat/indices/

yellow open accelerator_alarms_cmd_2022-02-01    6fGn4YdqS-OfVnnzYl8-lQ 5 1    3 0  14.4kb  14.4kb

yellow open accelerator_alarms_config_2022-02-01 jPrWr4h-SYqr-yiW29W_fw 5 1   77 0 179.5kb 179.5kb

yellow open accelerator_alarms_state_2022-02-01  gF3U7_gpQSGf3zilts2nkQ 5 1 3991 0 544.3kb 544.3kb

 

 

What is suspicious: During maven build there is a complaint about SLF4J:

 

[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) @ service-alarm-logger ---

[INFO] Building jar: /opt/phoebus/phoebus/services/alarm-logger/target/service-alarm-logger-4.6.6-SNAPSHOT.jar

[INFO]

[INFO] --- spring-boot-maven-plugin:2.1.6.RELEASE:repackage (default) @ service-alarm-logger ---

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

[INFO] Replacing main artifact with repackaged archive

[INFO]

[INFO] --- maven-assembly-plugin:3.2.0:single (make-assembly) @ service-alarm-logger ---

 

 

Do I need to add a dependency in the alarm-logger pom.xml file to get StaticLoggerBinder to be visible?  

 

Regards,

-ps

 

---

Helmholtz-Zentrum Berlin für Materialien und Energie GmbH

Mitglied der Hermann von Helmholtz-Gemeinschaft Deutscher Forschungszentren e.V.

Aufsichtsrat: Vorsitzender Dr. Volkmar Dietz, stv. Vorsitzende Dr. Jutta Koch-Unterseher
Geschäftsführung: Prof. Dr. Bernd Rech, Thomas Frederking

Sitz Berlin, AG Charlottenburg, 89 HRB 5583

Postadresse:
Hahn-Meitner-Platz 1
14109 Berlin
Deutschland