-
Notifications
You must be signed in to change notification settings - Fork 22
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
v2 sr_audit starts instance 0 when instances >= 100 #1183
Comments
On further investigation it is determined that instance 0 is being started because:
workaround: reduce instances to lower number. e.g. instances 75 |
tried to reproduce this with sr3, and it works fine, issue not present at all
tested at 120 and it seems fine. |
OK did find some weird behaviour after I kill instance 100 in sr3, not the same as v2. made a patch to correct it. |
The fix in #1226 caused a problem :(
Edit: I realized this issue is specific to v2, I'm talking about sr3 here. |
It's getting stuck on a cpost:
Is it normal for cpost pid files to be named iXX.pid? Edit: I realized this issue is specific to v2, I'm talking about sr3 here. |
uh... yeah... but I fixed in sarrac also: MetPX/sarrac#161 |
in v2, when running foreground, it will create a .pid file for instance 0 as well as for the other instances (>=1.) sr_audit looks for all the .pid files, and since the foreground instance is "missing" will re-start it. instance 0 should never be restarted.
work around:
The text was updated successfully, but these errors were encountered: