Skip to content

Conversation

@johri21
Copy link

@johri21 johri21 commented Feb 2, 2018

Under restart the init script is stopping the process and starting it again.
When stopping it does not wait and issues a SIGTERM to the process, this causes trouble when the server was not able to shutdown within a minuscule time and a start is issued.
The same thing we encountered in production where under restart the server was not able to stop and a start was issued.
Logs:
[2018-01-30 15:40:45.198] nc.c:187 nutcracker-0.4.0 built for Linux 3.16.0-4-amd64 x86_64 started on pid 66313
[2018-01-30 15:40:45.199] nc.c:192 run, rabbit run / dig that hole, forget the sun / and when at last the work is done / don't sit down / it's time to dig another one
[2018-01-30 15:40:45.203] nc_stats.c:840 bind on m 4 to addr '0.0.0.0:15050' failed: Address already in use

Fix:
Waiting for the process to end and then issuing Kill if it does not stop.

@CLAassistant
Copy link

CLAassistant commented Feb 2, 2018

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants