Bug #26081
openOn every node page, a waiting wheel is turning for a long time before timeout
Description
Hello,
When the web gui is used to display the page of any node (https://rudder.example.com/rudder/secure/nodeManager/node/716931d4-82ce-43b5-af58-5250a1fd28f5/...), a central turning waiting wheel is turning for a long time, before a popup is showing "The server cannot be contacted at this time".
Clicking OK on this popup gives back control to a classical use.
In Firefox dev tools, I see that amongst the sent queries, one is falling into timeout :
https://rudder.example.com/rudder/lift/ajax/F92342300211914LZXU-10/
with the answer:
NS_BINDING_ABORTED
This behaviour is affecting every node. It appeared maybe around mid-September (I'm writing that, knowing that I'm strictly following every upgrade)
One thing I noticed was that when trying to reach https://rudder.example.com/rudder/secure/nodeManager/node/716931d4-82ce-43b5-af58-5250a1fd28f5/..., I'm also seeing in /var/log/daemon.log this message :
rudder-relayd[505]: ERROR report{queue_id=node_uuid_123456789}: rudder_relayd::processing::reporting: refused: report from "716931d4-82ce-43b5-af58-5250a1fd28f5", unknown id
/var/log/rudder/webapp/2024_12_17.stderrout.log is also showing :
WARN net.liftweb.http.LiftRules - Unmapped Lift-like parameter seen in request [/lift/ajax/F92342300211914LZXU-10/]: F923423002129US4ZQL
and /var/log/rudder/apache2/error.log is showing:
[Tue Dec 17 09:09:26.356076 2024] [proxy_http:error] [pid 2468307:tid 2468361] (70007)The timeout specified has expired: [client a.b.c.d:36484] AH01102: error reading status line from remote server localhost:8080, referer: https://rudder.example.com/rudder/secure/nodeManager/node/716931d4-82ce-43b5-af58-5250a1fd28f5?displayCompliance=false [Tue Dec 17 09:09:26.356720 2024] [proxy:error] [pid 2468307:tid 2468361] [client a.b.c.d:36484] AH00898: Error reading from remote server returned by /rudder/lift/ajax/F923423002481QZW2Z2-10/, referer: https://rudder.example.com/rudder/secure/nodeManager/node/716931d4-82ce-43b5-af58-5250a1fd28f5?displayCompliance=false
What may I check further? what could be solved?
Thank you.
Nicolas
Updated by Nicolas Ecarnot 2 days ago
Nicolas Ecarnot wrote:
This behaviour is affecting every node.
Well, after digging deeper, it appears that it is only affecting nodes which state is "ignored". Though, this is still an issue anyway.
Updated by Alexis Mousset 2 days ago
Thanks for the precision.
I could not reproduce it for now.
Which server version are you using? Do you have plugins installed?
Updated by Nicolas Ecarnot 2 days ago
Alexis Mousset wrote in #note-2:
Which server version are you using?
8.1.7
Do you have plugins installed?
No