Closed ahmadnassri closed 9 years ago
I think it's this line: https://github.com/Mashape/kong/blob/master/kong/cli/utils/signal.lua#L342
os.execute("kill -0 "..pid) == 0
This is what I see now:
kong|master ⇒ kong stop
[INFO] Using configuration: /etc/kong/kong.yml
[ERR] Not running. Could not find pid at: /usr/local/kong/kong.pid
has this been resolved?
It happens on an edge case scenario (not sure, but maybe when Kong is being killed but the PID file still has the old process id), and it also happens in the test: https://travis-ci.org/Mashape/kong/builds/69369029#L1028
should probably remove the second and third (empty) lines: