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: | Re: Use of elog inside Phoebus |
From: | "Wang, Lin via Tech-talk" <tech-talk at aps.anl.gov> |
To: | tech-talk at aps.anl.gov, "Florian Feldbauer" <florian at ep1.ruhr-uni-bochum.de> |
Date: | Tue, 13 May 2025 14:39:11 +0800 (GMT+08:00) |
Dear all,
It seems that a breaking change in 2021 caused the incompatibility issue, and I have created a PR which is trying to fix this issue.
https://github.com/ControlSystemStudio/phoebus/pull/3393
Although it works for me, it still need to be tested by other users, because the deployment of Elog is flexible and different deployments may behave differently.
If there is no Elog server available on hand, it can also be tested with the Elog official online demo with the following settings.ini,
https://elog.psi.ch/elogs/Linux%20Demo/
org.phoebus.logbook/logbook_factory=elog
org.phoebus.elog.api/elog_url=https://elog.psi.ch/elogs/Linux%20Demo/
org.phoebus.elog.api/categories=General, Hardware, Software, Network, Other
org.phoebus.elog.api/types=Routine, Software Installation, Problem Fixed, Configuration, Other
org.phoebus.elog.api/username=user
org.phoebus.elog.api/password=1234
Regards,
Lin
-----Original Messages-----
From: "Florian Feldbauer via Tech-talk" <tech-talk at aps.anl.gov>
Send time: Tuesday, 04/29/2025 15:39:25
To: tech-talk at aps.anl.gov
Subject: Re: Use of elog inside Phoebus
Hey all,
so my answer to Andrea is also visible for everyone else.
I wrote the elog client for Phoebus in 2020.
Some time later the abstract logbook API within Phoebus has been refactored but unfortunately I did not notice these changes.
By the time I noticed, I didn't have the time to work on this project as I'm working since several years mainly on the DAQ for our tracking detector instead of the detector control system.When I build the first version of the elog client, I dug through the code to find the interfaces I had to implement and to find all the files I needed to modify.
I'm usually not programming in Java so it that was quiet a time consuming task for me.Does some documentation exists, that explains how to write and integrate such plugins to Phoebus?
If someone could point me to such a documentation or maybe provide a simple example, I would try to find some time and update my elog client for the new phoebus version.Cheers,
Florian
On 4/26/25 10:38, Andrea Celentano via Tech-talk wrote:
Dear colleagues,I am trying to use the elog application inside Phoebus. The details I found about this are in these slides: https://indico.fhi-berlin.mpg.de/event/52/contributions/564/attachments/222/683/phoebus-elog-client.pdf
I did the following:
1. I compiled phoebus from scratch with maven (master from gitlab), adding the elog application to build.xml
<ant dir="app/logbook/ui"/>
<ant dir="app/logbook/elog"/> —-> My addiction
<ant dir="app/log-configuration"/>
2. I checked inside my elog installation to read the password:
<password encoding="SHA256”>My password</password>
3. I added the following to my settings file:
org.phoebus.logbook/logbook_factory=elogorg.phoebus.logbook.ui/logbook_factory=elogorg.phoebus.elog.api/elog_url=http://my_elog_host:8080/Mainorg.phoebus.elog.api/username=shiftorg.phoebus.elog.api/password=My passwordorg.phoebus.elog.api/categories=Info, Problem, Shift summary, Data quality, Micromegas, ECAL, MasterTime, MSADCorg.phoebus.elog.api/types=
When I start Phoebus with ./phoebus.sh -settings my_settings.ini and I open the logbook, I get the following error:
2025-04-26 10:37:40 INFO [org.phoebus.logbook.olog.ui.LogEntryTableViewController] Single search: *
2025-04-26 10:37:40 SEVERE [org.phoebus.logbook.olog.ui.LogbookSearchJob] Failed to obtain logs
org.phoebus.logbook.LogbookException: java.lang.UnsupportedOperationException
at org.phoebus.logbook.LogClient.search(LogClient.java:494)
at org.phoebus.logbook.olog.ui.LogbookSearchJob.lambda$getRunnable$0(LogbookSearchJob.java:59)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:842)
Caused by: java.lang.UnsupportedOperationException
... 9 more
What I do not understand is why the “olog” app is referred to in this error, since I am not using it at all..
Thanks,Bests,Andrea Celentano
-- Ruhr-Universität Bochum AG der Experimentalphysik I Dr. Florian Feldbauer NB 2/131 / Fach 125 Universitätsstr. 150 D-44801 Bochum Office: NB 2/134 Phone: (+49)234 / 32-23563 Fax: (+49)234 / 32-14170 https://paluma.ruhr-uni-bochum.de