Project

General

Profile

Actions
Copy link

Bug #16222

closed

Exception "fiberFailed" when running agent from UI

Added by Elaad FURREEDAN about 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Web - Nodes & inventories
Target version:
6.0.0
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
98
Name check:
To do
Fix check:
To do
Regression:

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

run_agent_failed_fiber.log (14.2 KB) run_agent_failed_fiber.log Elaad FURREEDAN, 2019-11-20 11:19

Related issues 1 (0 open — 1 closed)

Related to Rudder - Architecture #16237: Trigger agent run - improve errors displayResolvedElaad FURREEDANActions
Actions
Copy link
 #1

Updated by Elaad FURREEDAN about 5 years ago

It happens in 6.0

Actions
Copy link
 #2

Updated by François ARMAND about 5 years ago

  • 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
Actions
Copy link
 #3

Updated by François ARMAND about 5 years ago

Actions
Copy link
 #4

Updated by Elaad FURREEDAN almost 5 years ago

  • Status changed from New to In progress
Actions
Copy link
 #5

Updated by Elaad FURREEDAN almost 5 years ago

  • File connection_refused.log added
Actions
Copy link
 #6

Updated by Elaad FURREEDAN almost 5 years ago

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

Actions
Copy link
 #7

Updated by Elaad FURREEDAN almost 5 years ago

  • File deleted (connection_refused.log)
Actions
Copy link
 #8

Updated by François ARMAND almost 5 years ago

  • Assignee changed from Elaad FURREEDAN to François ARMAND
Actions
Copy link
 #10

Updated by François ARMAND almost 5 years ago

  • 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
Actions
Copy link
 #11

Updated by François ARMAND almost 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #12

Updated by Alexis Mousset almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.0.0 which was released today.

Actions
Copy link

Also available in: Atom PDF