Experimental Physics and Industrial Control System
Hello Michael
Thank you for the tips, the proxy is now running as you pointed out:
Twistd -n a2aproxy -P 8888 -A localhost:8888/retrieval
but I think I missed something on the client side.
I have EPICS Qt 3.2.4 with Qt 5.6.0 installation on the same server as the AA and I exported QE_ARCHIVE_LIST as "localhost:8888/retrieval but running Archive Status in QEGui tool still gives me:
INFO: Requesting PV name info from http://localhost:8888/retrieval
ERROR: request failure from http://localhost:8888/retrieval
Best Regaerds,
Abdalla.
-----Original Message-----
From: Michael Davidsaver [mailto:[email protected]]
Sent: Wednesday, April 26, 2017 4:17 PM
To: Abdalla Ahmad <[email protected]>
Cc: [email protected]
Subject: Re: EpicsQT and Archiver Appliance
On 04/26/2017 06:50 AM, Abdalla Ahmad wrote:
> Dear Michael
>
> Can you please elaborate more on installing the proxy you wrote? I'm having difficulties running it on Scientific Linux 7 machine.
>
> First I have the requirements (numpy, twisted and protocol-buffer), then I did:
>
> python setup.py build
> sudo python setup.py install
>
> After that I ran the command as in the README:
>
> twistd -n a2aproxy -P 8888 AA-SERVER-URL:17665
>
> And then I get "Wrong number of arguments".
oops, the README was wrong! '-A' is missing. Now fixed.
An known working example from nsls2 can be seen in debian/channelarchiver-a2aproxy.default in the source tree.
> twistd a2aproxy -P 8889 -A
> http://capp01.cs.nsls2.local:17665/mgmt/bpl/getApplianceInfo -d
> Running "twistd a2aproxy" gives an error like "No module named EPICSEvent_pb2". Also when reordering the arguments it does not recognize the "-n" option.
twistd is picky about ordering of arguments as these are parsed by different code. Arguments before the application name ('a2aproxy' in this case) are for twisted itself (run 'twistd -h'). The remaining arguments are for the application. (run 'twistd a2aproxy -h')
> "No module named EPICSEvent_pb2"
Switch to some other directory and retry.
By default python searches the current directory before /usr/local. I would guess that, after installation, your shell is still in the source directory, so 'import carchive' finds the copy in the source tree which doesn't contain the generated files.
> python -c 'import carchive; print carchive.__file__'
Will show the path of the module which was imported.
- Replies:
- Re: EpicsQT and Archiver Appliance Michael Davidsaver
- References:
- RE: EpicsQT and Archiver Appliance Abdalla Ahmad
- Re: EpicsQT and Archiver Appliance Michael Davidsaver
- Navigate by Date:
- Prev:
CA gatway runs away when zero length PV name in UDP search request Shuei YAMADA
- Next:
Re: Control System Studio: Final value can't be of type PVANTNDArray Heinz Junkes
- 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: EpicsQT and Archiver Appliance Michael Davidsaver
- Next:
Re: EpicsQT and Archiver Appliance Michael Davidsaver
- 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