Join GitHub today
ProxySQL is not able to perform a proper shutdown if scheduler scripts are still running #1723
If you try to shutdown ProxySQL and it contains a long running or hung scheduler script, it doesn't kill those running processes. You will need to manually kill them to be able to start ProxySQL again
To simulate the issue:
However, proxysql.log has this error:
It's also a bit strange that port 6032 running process is bash:
I'm currently using Percona rpm: proxysql-1.4.10-1.1.el7.x86_64
This is expected, I don't think there is a valid reason to kill scheduler scripts (note also, that scheduler script could be a wrapper around some other process, so these won't be killed anyway).
This is something we can try to optimize.
referenced this issue
Oct 5, 2018
Hello @renecannao ,
IMHO the parent should always kill its children and not leave orphan processes running. The scheduler scripts are forked from the proxysql process as we can see here:
It should be an easy change in the /etc/init.d script. Instead of looping the "pgrep -x proxysql" or the PID file and killing the processes it would be better to get the process group ID and kill the group. It will make sure that all processes forked from proxysql will be killed, including the scheduler scripts. See the below example: