Project

General

Profile

Actions

Bug #12034

closed

On a fresh Rudder 4.3 centos6 install, error about ncf API in logs

Added by Nicolas CHARLES over 3 years ago. Updated about 3 years ago.

Status:
Released
Priority:
N/A
Category:
-
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
69

Description

On centos 6, with Rudder 4.3, i get the errors

[2018-01-23 22:19:30] WARN  bootchecks - Could not authenticate in ncf API, maybe it was not initialized yet, retrying in 5 seconds
[2018-01-23 22:19:35] ERROR com.normation.rudder.rest.RestAuthentication - Authentication API forbids read access to Techniques for user REST Account: "Rudder system account" (rudder-system-
api-account)

not sure yet of the impact

Actions #1

Updated by François ARMAND over 3 years ago

  • Description updated (diff)
  • Target version changed from 4.3.0~beta1 to 4.2.4

It's not 4.3 specific; in 4.2 we get at boot:

[2018-01-24 14:12:38] INFO  application - Application Rudder started
2018-01-24 14:12:38.347:INFO:oejs.AbstractConnector:Started SelectChannelConnector@127.0.0.1:8080
[2018-01-24 14:12:45] WARN  bootchecks - Could not authenticate in ncf API, maybe it was not initialized yet, retrying in 5 seconds
[2018-01-24 14:12:50] WARN  bootchecks - Could not authenticate in ncf API, maybe it was not initialized yet, retrying in 5 seconds
[2018-01-24 14:12:55] WARN  bootchecks - Could not authenticate in ncf API, maybe it was not initialized yet, retrying in 5 seconds
[2018-01-24 14:13:00] WARN  bootchecks - Could not authenticate in ncf API, maybe it was not initialized yet, retrying in 5 seconds
[2018-01-24 14:13:05] WARN  bootchecks - Could not authenticate in ncf API, maybe it was not initialized yet, retrying in 5 seconds
[2018-01-24 14:13:10] WARN  bootchecks - Could not authenticate in ncf API, maybe it was not initialized yet, retrying in 5 seconds
....

And after a 2 or 3 minutes, it stops. In 4.2, I didn't see the "Authentication API forbids read access ..."

Actions #2

Updated by Benoît PECCATTE over 3 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 32
Actions #3

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 4.2.4 to 4.2.5
Actions #4

Updated by Nicolas CHARLES about 3 years ago

in 4.3, I get this message every 5 secondes in the log, and it never ends

Actions #5

Updated by François ARMAND about 3 years ago

  • Target version changed from 4.2.5 to 4.3.0~rc1
  • Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
  • User visibility changed from Operational - other Techniques | Technique editor | Rudder settings to Getting started - demo | first install | level 1 Techniques
  • Priority changed from 32 to 69

I'm not sure about 4.2, it will need to be retested. In 4.3, the problem is that it never disapear and it forbid the system API token to access rudder.

Actions #6

Updated by François ARMAND about 3 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #7

Updated by François ARMAND about 3 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/1869
Actions #8

Updated by Rudder Quality Assistant about 3 years ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND
Actions #9

Updated by François ARMAND about 3 years ago

  • Status changed from Pending technical review to Pending release
Actions #10

Updated by Vincent MEMBRÉ about 3 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.3.0~rc1 which was released today.

Actions

Also available in: Atom PDF