Closed djvine closed 6 years ago
Most likely your EPICS configuration needs to be fixed. The engine's logs will print out the details of the EPICS configuration like so...
You can check to see if this agrees with you configuration. All of these should come from the standard EPICS variables as defined here - https://epics.anl.gov/base/R3-14/12-docs/CAref.html#EPICS
Thank you for your fast reply!
I found the solution here: https://epics.anl.gov/tech-talk/2017/msg00695.php
I didn't realize the sampleStartup.sh needed to be run as root. Using sudo fixed the problem.
Thanks!
Ok; please let me know if this is still an issue.
No, you can close it thanks.
On Wed, May 23, 2018, 1:29 PM Murali Shankar notifications@github.com wrote:
Ok; please let me know if this is still an issue.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/slacmshankar/epicsarchiverap/issues/55#issuecomment-391485624, or mute the thread https://github.com/notifications/unsubscribe-auth/AFYw2ErqiTIxrqJmmvk5-kvq4h1_msUiks5t1caVgaJpZM4UK6Cu .
Hi,
I used the single machine install script and started the archiver using the sample startup script and there was no problems. I added some PVs but they never move from "appliance assigned" to "being archived".
The "May not exist" report does not currently show the PVs (although it did prior to restarting the appliance). "Recently modified PVs" shows no entries.
I guess it is unable to connect to the PVs. Running caget from the terminal connects no problem.
Can anyone recommend how to proceed to troubleshoot this problem?
Thanks, David