Project

General

Profile

Actions

Architecture #16051

open

Re-authentication error in postgres doesn't kill existing pool

Added by Elaad FURREEDAN over 4 years ago. Updated 11 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Server components
Target version:
Effort required:
Name check:
To do
Fix check:
To do
Regression:

Files

thread_jvm.log (125 KB) thread_jvm.log Elaad FURREEDAN, 2019-10-24 14:30

Related issues 2 (0 open2 closed)

Related to Rudder - Bug #16055: java.lang.Error null in PooledConnectionProviderRejectedActions
Related to Rudder - Bug #12489: Cannot login into 2 different Rudder with the same URL - apocalypse ensuesRejectedActions
Actions #1

Updated by Nicolas CHARLES over 4 years ago

there are no obvious locking there

Actions #2

Updated by Elaad FURREEDAN over 4 years ago

  • File before_error.log added
Actions #3

Updated by Elaad FURREEDAN over 4 years ago

  • File deleted (before_error.log)
Actions #4

Updated by François ARMAND over 4 years ago

  • Related to Bug #16055: java.lang.Error null in PooledConnectionProvider added
Actions #5

Updated by François ARMAND over 4 years ago

  • Subject changed from Rudder is very slow to Authentication error to postgres cause major slowdown
  • Category set to System integration
  • Target version changed from 6.0.0~beta1 to 6.0.0

The problem is linked to Postgres DB connexion dying and the pool does not seems to notice. We can see it very clearly in the log here: https://issues.rudder.io/attachments/1549

So we have the connexion starting to fails around 2019-10-24 12:35:38+0200 - most likely rudder agent is running and reconfigured something on pg, restarting the db after that.
Then, at 2019-10-24 14:16:20+0200 we finaly have:

ERROR com.normation.rudder.rest.v1.RestTechniqueReload - Root exception cause was:
org.postgresql.util.PSQLException: FATAL: password authentication failed for user "rudder" 
    at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:520)
    at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:141)
    at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:192)

And then, everything related to PG fails. It's as if PG was restarted to take care of new auth info, but the connexion didn't noticed the pb. Moreover, Rudder should have been restarted to get the new info, but wasn't.

Actions #6

Updated by Elaad FURREEDAN over 4 years ago

  • Related to Bug #12489: Cannot login into 2 different Rudder with the same URL - apocalypse ensues added
Actions #7

Updated by Elaad FURREEDAN over 4 years ago

When I have two Rudder's env running, after ~10mins the bug occurs

Actions #8

Updated by Elaad FURREEDAN over 4 years ago

  • Category changed from System integration to Web - Technique editor
Actions #9

Updated by Alexis Mousset over 4 years ago

  • Target version changed from 6.0.0 to 6.0.1
Actions #10

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.1 to 6.0.2
Actions #11

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.2 to 6.0.3
Actions #12

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.3 to 6.0.4
Actions #13

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.4 to 6.0.5
Actions #14

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.5 to 6.0.6
Actions #15

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.0.6 to 6.0.7
Actions #16

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.0.7 to 6.0.8
Actions #17

Updated by François ARMAND almost 4 years ago

  • Subject changed from Authentication error to postgres cause major slowdown to Re-authentication error in postgres doesn't kill existing pool
  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 46
Actions #18

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.8 to 6.0.9
  • Priority changed from 46 to 45
Actions #19

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.9 to 6.0.10
  • Priority changed from 45 to 44
Actions #20

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.10 to 798
  • Priority changed from 44 to 43
Actions #21

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 798 to 6.1.14
Actions #22

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #23

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #24

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #25

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #26

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #27

Updated by Alexis Mousset over 2 years ago

  • Category changed from Web - Technique editor to Server components
Actions #28

Updated by François ARMAND about 2 years ago

  • Tracker changed from Bug to Architecture
  • Severity deleted (Major - prevents use of part of Rudder | no simple workaround)
  • User visibility deleted (Operational - other Techniques | Rudder settings | Plugins)
  • Priority deleted (43)
Actions #29

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions #30

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions #31

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions #32

Updated by Alexis Mousset about 1 year ago

  • Target version changed from old 6.1 issues to relocate to 8.0.0~alpha1
Actions #33

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 8.0.0~alpha1 to 8.0.0~beta1
Actions #34

Updated by Alexis Mousset 9 months ago

  • Target version changed from 8.0.0~beta1 to 8.1.0~alpha1
Actions #35

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.0~alpha1 to 8.1.0~beta1
Actions #36

Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 8.1.0~beta1 to 8.1.0~beta2
Actions #37

Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 8.1.0~beta2 to 8.1.0~rc1
Actions #38

Updated by Vincent MEMBRÉ 17 days ago

  • Target version changed from 8.1.0~rc1 to 8.1.0
Actions #39

Updated by Vincent MEMBRÉ 11 days ago

  • Target version changed from 8.1.0 to 8.1.1
Actions

Also available in: Atom PDF