auto-ssl / auto-ssl/lua-resty-auto-ssl
start_sockproc: line 55: kill: (47) - No such process
- Dominant language
- Lua
- Stars
- 2k
- Forks
- 184
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the start_sockproc entry point and inspect line 55, then reproduce a container restart with auto-ssl-sockproc.pid and shell.sock left in /tmp. Check how the process cleanup handles a missing PID, and consider the issue resolved when restart no longer emits the kill error while stale files are handled safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, nginx
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100