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

supervisorctl died after upgrade #43

Closed
ctheune opened this issue Apr 25, 2020 · 1 comment
Closed

supervisorctl died after upgrade #43

ctheune opened this issue Apr 25, 2020 · 1 comment
Milestone

Comments

@ctheune
Copy link
Collaborator

ctheune commented Apr 25, 2020

This happened and didn't get unstuck on its own:

     ManagedMySQL > Grant(GRANT ALL)
     Supervisor > Buildout > File(work/supervisor/buildout.cfg) > Content(work/supervisor/buildout.cfg)
     Supervisor > Buildout > VirtualEnv(3) > VirtualEnvPy
     Supervisor > Buildout > VirtualEnv(3) > Package(setuptools==46.1.3)
     Supervisor > Buildout > VirtualEnv(3) > Package(zc.buildout==2.13.3)
     Supervisor > Buildout
     Supervisor > RunningSupervisor(<Service (default) "Supervisor > Service(bin/supervisord)">)
default: Deploying component instanceadmin ...
     InstanceAdmin > Instance > Buildout
     InstanceAdmin > Instance > Program(admin-instance)
ERROR: /home/vagrant/deployment/work/supervisor/bin/supervisorctl reread
     Return code: 1
STDOUT
     error: <class 'xmlrpc.client.ProtocolError'>, <ProtocolError for 127.0.0.1/RPC2: 500 Internal Server Error>: file: /home/vagrant/deployment/work/supervisor/eggs/supervisor-4.1.0-py3.7.egg/supervisor/xmlrpc.py line: 545

STDERR

I had to kill and restart supervisor. I guess the upgrade didn't really properly shutdown/restart supervisor here ... not sure how that was intended. Normally we want upgrades to be as quiet as possible and I guess a full restart isn't always needed anyway ...

@ctheune ctheune added this to the batou 2 milestone May 7, 2020
@ctheune
Copy link
Collaborator Author

ctheune commented May 11, 2020

I can't reproduce this. I've found the same instance and down- and upgraded it but can't repeat it. Maybe this was something that was broken in between ... hmm. Not quite satisfied, but nowhere to go either.

@ctheune ctheune closed this as completed May 11, 2020
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

1 participant