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

Set process title in supervisor after a package is updated #25

Open
henokgetachew opened this issue Nov 12, 2017 · 2 comments
Open

Set process title in supervisor after a package is updated #25

henokgetachew opened this issue Nov 12, 2017 · 2 comments
Labels

Comments

@henokgetachew
Copy link
Contributor

This is after a package update.

vm@medic:/srv/storage/gardener/logs $ sudo ps aux | grep package-update
14048 root     {package-update} /bin/sh /boot/package-update medic-core-v17000-x64.vpkg
14083 root     {package-update} /bin/sh /boot/package-update medic-core-v17000-x64.vpkg
14130 root     {package-update} /bin/sh /boot/package-update medic-core-v17000-x64.vpkg
14186 root     {package-update} /bin/sh /boot/package-update medic-core-v17000-x64.vpkg
14238 root     {package-update} /bin/sh /boot/package-update medic-core-v17000-x64.vpkg

@SCdF and I have noticed this with package-install as well.
A reboot is required in order to get the processes to quit.

@ghost
Copy link

ghost commented Nov 13, 2017

This is a process titling issue IIRC; ps is showing the process name under which the job was invoked despite the fact that the process has forked, detached, and is now running in the background. We could look into doing something like setproctitle or otherwise passing through a better-named exec call.

Those are the supervisor processes IIRC – one for each supervised service beneath medic-core. It just sucks to look at.

@ghost ghost changed the title Package update service lingers on after upgrade has been done Set process title in supervisor after a package is updated Jun 20, 2018
@ghost
Copy link

ghost commented Jun 20, 2018

I've updated the title to reflect the action that I think needs to be taken here.

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

No branches or pull requests

1 participant