-
Notifications
You must be signed in to change notification settings - Fork 184
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
can't manage grouped process(2.6.5) #57
Comments
I had the same problem, so I made a quick fix, and tested on my own server, it works... |
Hi, it's my fault. I just tested for a few programs. I didn't define any group while i was testing. It is interesting that if you create a group in supervisor, Supervisor XmlRpc runs with group name and process name for processes which belongs this group. :)))) The process name ain't already unique. Why are they doing this? |
@f9n done :) another interesting thing is, if you did not put a program in a group, rpc service will give it a group which named by its name ,then you still can manage it with group_name (same as program_name):program_name... I think it's a design for consistency? |
I merged the pull request 👍 Thanks again. I'll publish the new version soon. |
Hi,
When i do a grouped config in supervisord,and i can't do any thing in the browers with that group's member, the background log file show:
<Fault 10: 'BAD_NAME: test1'>
/api/v2/nodes/api/processes/test1/stop/
i think it shoud be groupname:test1 ?
thank you!
The text was updated successfully, but these errors were encountered: