-
Notifications
You must be signed in to change notification settings - Fork 15
tt start/stop commands does not always work #325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Log messages for dead processes:
router:
|
vr009
added a commit
that referenced
this issue
Feb 2, 2023
vr009
added a commit
that referenced
this issue
Feb 2, 2023
vr009
added a commit
that referenced
this issue
Feb 3, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 3, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 3, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 4, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 4, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 6, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 7, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the signals handling strategy. Now there is only one handling loop for all signals. Added two fields for controlling a state of the instance being watched and a mutex for synchronizing the goroutines changing them. Part of #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the signals handling strategy. Now there is only one handling loop for all signals. Added two fields for controlling a state of the instance being watched and a mutex for synchronizing the goroutines changing them. Part of #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the signals handling strategy. Now there is only one handling loop for all signals. Added two fields for controlling a state of the instance being watched and a mutex for synchronizing the goroutines changing them. Part of #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the signals handling strategy. Now there is only one handling loop for all signals. Added two fields for controlling a state of the instance being watched and a mutex for synchronizing the goroutines changing them. Part of #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the signals handling strategy. Now there is only one handling loop for all signals. Added two fields for controlling a state of the instance being watched and a mutex for synchronizing the goroutines changing them. Part of #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the signals handling strategy. Now there is only one handling loop for all signals. Added a field for controlling a state of the watchdog and a mutex for synchronizing the goroutines changing this field. Part of #325
vr009
added a commit
that referenced
this issue
Feb 8, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
vr009
added a commit
that referenced
this issue
Feb 10, 2023
This patch fixes the signals handling strategy. Now there is only one handling loop for all signals. Added a field for controlling a state of the watchdog and a mutex for synchronizing the goroutines changing this field. Part of #325
vr009
added a commit
that referenced
this issue
Feb 10, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
LeonidVas
pushed a commit
that referenced
this issue
Feb 10, 2023
This patch fixes the signals handling strategy. Now there is only one handling loop for all signals. Added a field for controlling a state of the watchdog and a mutex for synchronizing the goroutines changing this field. Part of #325
LeonidVas
pushed a commit
that referenced
this issue
Feb 10, 2023
This patch fixes the problem, which was occurring when the watchdog process received a signal SIGURG from go runtime[1][2] and passed it to the forked process before the exec call. Fixed by adding a call of the Ignore function. Receiving this signal is unexpected, cause tt doesn't work with sockets at all. [1] - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md [2] - golang/go#37942 Closes #325
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like this is some kind of race in start command. It does not start all instances under high load:
tt stop
does not stop all instances:This issue reproduces on my system after the following commit:
4b0d12d tt: fix a race condition between tt start and tt stop
The text was updated successfully, but these errors were encountered: