| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 <2025> | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 <2025> |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Phoebus alarm tree shows stale configuration |
| From: | Majer Karel via Tech-talk <tech-talk at aps.anl.gov> |
| To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Wed, 30 Apr 2025 13:11:33 +0000 |
|
We have recently put Phoebus alarm server into operation and while the server seems to run OK, I have troubles with alarm tree view in Phoebus client. When I open alarm tree I often get incomplete configuration. It seems that the client has not reached the end of Kafka log. I usually get correct configuration after several tries. I run alarm server and Kafka in containers using Docker compose. I’m using apache/kafka:4.0.0 image for Kafka and ghcr.io/controlsystemstudio/phoebus/service-alarm-server:master for alarm server
service. I’m using Phoebus 4.7.3 release version as a client on Rocky Linux 9. Do you have any experience with similar behavior? Thanks, Karel Majer Karel Majer | Senior Software Developer
|
