start_sockproc: line 55: kill: (47) - No such process

[byrnedo]

When I restart my container, there are still /tmp/ files lying around ( auto-ssl-sockproc.pid shell.sock ) and resty-auto-ssl throws this error:

start_sockproc: line 55: kill: (47) - No such process

I'm guessing that if exit code is 47 in start_sockproc then it should swallow the error.

I'm getting the same error. any hints?

[mayocream]

/usr/local/bin/resty-auto-ssl/start_sockproc: line 55: kill: (8134) - No such process
rm: cannot remove '/tmp/shell.sock': Operation not permitted
socket_path error: File exists
2018/01/21 18:04:32 [error] 8237#8237: *1 [lua] start_sockproc.lua:20: auto-ssl: failed to start sockproc, context: init_worker_by_lua*

Same error.

[GUI]

@mayocream: What user owns the /tmp/shell.sock file (ls -l /tmp/shell.sock)? And what user are the nginx workers configured to run as? If you changed the user nginx runs as, this could potentially lead to this error, since the new user may not be able to cleanup the old files. If you manually cleanup the files (as root or with sudo) and restart nginx, I think that should hopefully get things working again, but let me know if that's not the case.

@byrnedo, @aviatrix: Your cases might have been slightly different—were things working for you or was this a fatal errors? The kill command failing should not be a fatal error, but this message could end up in the output if the process was already dead. So I'm wondering if things were still working for you despite this error message, or if things were still somehow broken. If they were broken, were there any other errors in your log after this line?