Project

General

Profile

Actions

Bug #10380

closed

Dashboard do not load due to stackoverflow error in 4.1

Added by Nicolas CHARLES almost 8 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
17
Name check:
Fix check:
Regression:

Description

On restarting Rudder 4.1, with 2000 nodes, dashboard stays blank because of a stackoverflow error

[2017-03-08 22:14:43] DEBUG debug_timing - Get node info (1997 ldap node info): 25ms
[2017-03-08 22:14:56] DEBUG debug_timing - Start timing homepage
[2017-03-08 22:14:57] DEBUG debug_timing - Cache for nodes info expire ?: 24ms
[2017-03-08 22:14:57] DEBUG debug_timing - Get node info (all nodes info): 25ms
[2017-03-08 22:14:57] DEBUG debug_timing - Getting node infos: 26ms
[2017-03-08 22:14:57] DEBUG debug_timing - Get agent software entries: 23ms
[2017-03-08 22:14:57] DEBUG debug_timing - Cache for nodes info expire ?: 31ms
[2017-03-08 22:14:57] DEBUG debug_timing - Get node info (all nodes info): 32ms
[2017-03-08 22:14:57] DEBUG debug_timing - Get nodes for agent: 154ms
Exception in thread "pool-6-thread-3" java.lang.StackOverflowError
        at scalaz.Apply.$anonfun$ap2$2(Apply.scala:49)
        at scalaz.Bind.ap(Bind.scala:20)
        at scalaz.Bind.ap$(Bind.scala:18)
        at scalaz.FreeInstances$$anon$3.ap(Free.scala:424)
        at scalaz.Apply.$anonfun$ap2$1(Apply.scala:49)
        at scalaz.Bind.ap(Bind.scala:20)
        at scalaz.Bind.ap$(Bind.scala:18)
        at scalaz.FreeInstances$$anon$3.ap(Free.scala:424)
        at scalaz.Apply.ap2(Apply.scala:49)
        at scalaz.Apply.ap2$(Apply.scala:48)
        at scalaz.FreeInstances$$anon$3.ap2(Free.scala:424)
        at scalaz.Applicative.apply2(Applicative.scala:32)
        at scalaz.Applicative.apply2$(Applicative.scala:31)
        at scalaz.FreeInstances$$anon$3.apply2(Free.scala:424)
        at scalaz.syntax.ApplyOps.$times$greater(ApplySyntax.scala:12)
        at doobie.util.composite$LowerPriorityComposite$$anon$6.$anonfun$set$4(composite.scala:109)
        at doobie.util.composite$Composite$$anon$2.$anonfun$set$2(composite.scala:56)
        at doobie.util.composite$Composite$$anon$2.$anonfun$set$2$adapted(composite.scala:56)
        at doobie.util.composite$Composite$$anon$2.$anonfun$set$2(composite.scala:56)
        at doobie.util.composite$Composite$$anon$2.$anonfun$set$2$adapted(composite.scala:56)
        at doobie.util.composite$Composite$$anon$2.$anonfun$set$2(composite.scala:56)
        at doobie.util.composite$Composite$$anon$2.$anonfun$set$2$adapted(composite.scala:56)
        at doobie.util.composite$Composite$$anon$2.$anonfun$set$2(composite.scala:56)
        at doobie.util.composite$Composite$$anon$2.$anonfun$set$2$adapted(composite.scala:56)

Reloading the page solves the issue


Related issues 1 (0 open1 closed)

Is duplicate of Rudder - Bug #10456: Several core features don't work anymore with more than 1000 nodesReleasedAlexis MoussetActions
Actions #2

Updated by Jonathan CLARKE almost 8 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Actions #3

Updated by François ARMAND almost 8 years ago

  • Status changed from New to In progress
Actions #4

Updated by Jonathan CLARKE almost 8 years ago

  • Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
Actions #5

Updated by François ARMAND almost 8 years ago

  • Related to Bug #10456: Several core features don't work anymore with more than 1000 nodes added
Actions #6

Updated by François ARMAND almost 8 years ago

  • Related to deleted (Bug #10456: Several core features don't work anymore with more than 1000 nodes)
Actions #7

Updated by François ARMAND almost 8 years ago

  • Is duplicate of Bug #10456: Several core features don't work anymore with more than 1000 nodes added
Actions #8

Updated by François ARMAND almost 8 years ago

Let's group all of them under #10456

Actions #9

Updated by François ARMAND almost 8 years ago

  • Status changed from In progress to Rejected
Actions #10

Updated by Benoît PECCATTE over 7 years ago

  • Priority set to 17
Actions

Also available in: Atom PDF