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
/v1/control/sendoutboundmessage just hangs. And it blocks any other requests from going through.
I didn’t kill it and just let it run to see what would happen and eventually it stops w/ this message
[07-19|20:55:14.034] INFO local/network.go:780 done stopping network
[07-19|20:55:14.034] INFO ux/output.go:13 terminated network
[07-19|20:55:14.034] DEBUG server/server.go:1186 SendOutboundMessage
[07-19|20:55:14.034] DEBUG server/server.go:1117 Stop
[07-19|20:55:14.034] INFO server/server.go:818 removing network
[07-19|20:55:14.035] DEBUG server/server.go:822 async err node "node3" failed to become healthy within timeout, or network stopped not returned to user
So it did get through SendOutboundMessage because it says Stop which was the command I called after it that was also hanging.
So does that mean that sendoutboundmessage was successful?
The text was updated successfully, but these errors were encountered:
cgcardona
changed the title
Check sendoutboutmessage functionality
Check sendoutboutmessage functionality
Jul 21, 2023
From @cgcardona
/v1/control/sendoutboundmessage just hangs. And it blocks any other requests from going through.
I didn’t kill it and just let it run to see what would happen and eventually it stops w/ this message
[07-19|20:55:14.034] INFO local/network.go:780 done stopping network
[07-19|20:55:14.034] INFO ux/output.go:13 terminated network
[07-19|20:55:14.034] DEBUG server/server.go:1186 SendOutboundMessage
[07-19|20:55:14.034] DEBUG server/server.go:1117 Stop
[07-19|20:55:14.034] INFO server/server.go:818 removing network
[07-19|20:55:14.035] DEBUG server/server.go:822 async err node "node3" failed to become healthy within timeout, or network stopped not returned to user
So it did get through SendOutboundMessage because it says Stop which was the command I called after it that was also hanging.
So does that mean that sendoutboundmessage was successful?
The text was updated successfully, but these errors were encountered: