Bug #16222
closed
Exception "fiberFailed" when running agent from UI
Added by Elaad FURREEDAN about 5 years ago.
Updated almost 5 years ago.
Category:
Web - Nodes & inventories
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Description
When I try to run the agent from the node details tab, I get the attached error.
The problem seems to be that an exception for connection refused is not correctly managed:
java.net.ConnectException: Connection refused (Connection refused)
...
at com.normation.rudder.rest.lift.NodeApiService8.$anonfun$runNode$5(NodeApi.scala:712)
...
at com.normation.rudder.rest.lift.NodeApiService8.runNode(NodeApi.scala:711)
Files
- Subject changed from Fiber failed when running agent run from UI to Exception "fiberFailed" when running agent from UI
- Description updated (diff)
- Category set to Web - Nodes & inventories
- Assignee set to Elaad FURREEDAN
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
- Effort required set to Very Small
- Priority changed from 0 to 98
- Status changed from New to In progress
- File connection_refused.log added
The exception in the main post seems to be raised when we try to execute the request in runNode.
- In first place when I was trying to run agent from the button in the webapp I had the previous error (see the main post), so I try to encapsuled ZioRuntime.unsafeRun(response) in Task.effect and I had an error telling me that the PipedInputStream was not connected.
---> I don't understand what can cause an unconnected input pipe
- File deleted (
connection_refused.log)
- Assignee changed from Elaad FURREEDAN to François ARMAND
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2653
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.0 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by