You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Linux, when I issue a TERM or INT signal to NGINX Agent, I frequently see that Agent has segfaulted instead of exiting gracefully. Upon error, the following is frequently outputted:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x11a4b4c]
goroutine 81 [running]:
main.handleSignals.func1()
/home/elijah/Development/Open_Source/nginx-agent/main.go:139 +0x24c
created by main.handleSignals
/home/elijah/Development/Open_Source/nginx-agent/main.go:125 +0x251
As best as I can tell, this is caused by not checking if cmder is nil before main.go:133.
The text was updated successfully, but these errors were encountered:
dekobon
added a commit
to dekobon/agent
that referenced
this issue
Jun 6, 2023
On Linux, when I issue a TERM or INT signal to NGINX Agent, I frequently see that Agent has segfaulted instead of exiting gracefully. Upon error, the following is frequently outputted:
As best as I can tell, this is caused by not checking if
cmder
isnil
beforemain.go:133
.The text was updated successfully, but these errors were encountered: