Hi Kay,
I'm sorry for previous message. I solved the problem that was
easy. I changed "localhost" in kafka/config/server.properties to
host ip and I run alarm server with custom configuration with
server's ip.
Thanks for your helps.
Hasan
On 16.09.2021 13:08, Hasan SANSAR
wrote:
Hi Kay,
For alarms, you can export/import the
configuration, but the tools are not compatible at runtime
because we moved from RDB+JMS to Kafka.
Thanks for these reference documentations. I can built new
archive engine and alarm server from Phoebus source code and
so, I built archive engine service and alarm server service.
But there is a problem with alarm server service or maybe
with Kafka. Phoebus can connect to alarm server with
Accelerator config, but after 30 second, the connection is
failed and "No Alarm Server Connection" text appears and my
saved messages with key in JSON format in Kafka doesn't appear
in Phoebus Alarm UI tools.
And I'm sending the command for messages and I attached
outputs of Zookeeper, Kafka and Phoebus (outputKafka.txt,
outputZooKeeper.txt, outputPhoebus.txt).
commands for messages:
$ echo
'config:/Accelerator/Vacuum/TARLA:deneme,{"user":"osiloskop",
"host":"alarm_server", "description"="deneme", "delay"=2,
"count"=2}' | kafka/bin/kafka-console-producer.sh
--broker-list 192.168.56.10:9092 --topic Accelerator
--property parse.key=true --property key.separator=,
$ kafka/bin/kafka-console-consumer.sh --bootstrap-server
192.168.56.10:9092 --topic Accelerator --from-beginning
--property print.key=true --property key.separator=,
--
Hasan Sansar
--
Hasan Sansar
- References:
- Alarm Server and archiveEngine Hasan SANSAR via Tech-talk
- Re: [EXTERNAL] Alarm Server and archiveEngine Kasemir, Kay via Tech-talk
- Re: [EXTERNAL] Alarm Server and archiveEngine Hasan SANSAR via Tech-talk
- Re: [EXTERNAL] Alarm Server and archiveEngine Kasemir, Kay via Tech-talk
- Re: [EXTERNAL] Alarm Server and archiveEngine Hasan SANSAR via Tech-talk
- Navigate by Date:
- Prev:
Re: [EXTERNAL] Alarm Server and archiveEngine Hasan SANSAR via Tech-talk
- Next:
socketcan driver and the tudsocketcan 曹彪 via Tech-talk
- 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
- Navigate by Thread:
- Prev:
Re: [EXTERNAL] Alarm Server and archiveEngine Hasan SANSAR via Tech-talk
- Next:
SynApps sscan record: timestamp issue for BUSY DATA and EXSC fields; causing problem archiving with Phoebus Archive engine Kuldeep Joshi via Tech-talk
- 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
|