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
When I input incorrect OTEL configurations in the remote configuration, opampsupervisor frequently prints restart error messages instead of printing according to the restartTimer settings. As shown in the picture below:
Steps to Reproduce
Fill in the correct configuration to ensure that the opampsupervisor can connect to the backend normally
Start the backend OpAMP sample server
Start opampsupervisor
Providing incorrect remote configurations via the OpAMP UI.
View the stdout of opampsupervisor
Expected Result
Printing error messages according to the time set by the restartTimer.
2024-04-07T17:25:08.990+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.991+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.991+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.991+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.991+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.991+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.991+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.991+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.992+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.992+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.992+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.992+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.992+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.992+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.993+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.993+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.993+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.993+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.993+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
2024-04-07T17:25:08.993+0800 DEBUG supervisor/supervisor.go:758 Agent process exited unexpectedly. Will restart in a bit... {"pid": 19071, "exit_code": 1}
Additional context
Frequently printing error messages is due to the problem of source code, which can be solved by changing it to c.doneCh <- struct{}{}.
But I don't know why to use close(c.doneCh), is there any other consideration?
The text was updated successfully, but these errors were encountered:
Component(s)
cmd/opampsupervisor
What happened?
Description
When I input incorrect OTEL configurations in the remote configuration,
opampsupervisor
frequently prints restart error messages instead of printing according to therestartTimer
settings. As shown in the picture below:Steps to Reproduce
Expected Result
Printing error messages according to the time set by the
restartTimer
.Actual Result
Continuously printing error messages.
Collector version
all
Environment information
OS: Darwin
Compiler: go 1.21
OpenTelemetry Collector configuration
Log output
Additional context
Frequently printing error messages is due to the problem of source code, which can be solved by changing it to
c.doneCh <- struct{}{}
.But I don't know why to use
close(c.doneCh)
, is there any other consideration?The text was updated successfully, but these errors were encountered: