Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pysmurf issue of epics failed to respond #368

Open
yaqiongl opened this issue Jul 10, 2023 · 1 comment
Open

pysmurf issue of epics failed to respond #368

yaqiongl opened this issue Jul 10, 2023 · 1 comment

Comments

@yaqiongl
Copy link

yaqiongl commented Jul 10, 2023

Hello,

We are currently having this issue of running S = cfg.get_smurf_control() in jupyter notebook
Command failed: smurf_server_s2:AMCc:SmurfApplication:EnabledBays, that's related to epics failed to respond
and in ipython it shows

In [1]: CA.Client.Exception...............................................
    Warning: "Virtual circuit disconnect"
    Context: "localhost:5064"
    Source File: ../cac.cpp line 1223
    Current Time: Mon Jul 10 2023 18:06:59.475148447

i think this might be related to issues #353 that happened a month ago, which was fixed by hammering for several times(!!). and it's kind of random. After rerunning S=cfg.get_smurf_control(), it 's back to normal

@jlashner
Copy link
Collaborator

So the issue in #353 I believe was caused due to a change in pysmurf which unintentially reduced the PV timeout from 5 seconds down to 2 seconds, which made failures a lot more comment. This should have been fixed in this PR: slaclab/pysmurf#781

Can you try to upgrade to the most recent version of pysmurf and re-hammer? Also can you verify that it gets through the entirety of the setup procedure after hammering? I think that may fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants