Project

General

Profile

Actions

Bug #10567

closed

Infinite "rudder is loading" page if rudder-init didn't run

Added by François ARMAND about 4 years ago. Updated almost 4 years ago.

Status:
Released
Priority:
N/A
Category:
System integration
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:
54

Description

If rudder-init is not run for reason, the webapp can't run (init data are not set). So it's completly broken, leading to #1974 (which is particulary bad with #10430).
We need to display a clean error message to the user in that case.


Subtasks 2 (0 open2 closed)

Bug #10657: Warning during compilationReleasedNicolas CHARLESActions
Bug #10658: Modify Rudder 404 page to speak about rudder-initReleasedFrançois ARMANDActions

Related issues

Related to Rudder - Bug #1974: If an error happen during boostrap, the webapp starts but is in a zombie state and the error page is not displayedReleasedNicolas CHARLESActions
Related to Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)RejectedActions
Related to Rudder - Bug #15387: Clean-up Jetty abort on bootReleasedVincent MEMBRÉActions
Actions #1

Updated by François ARMAND about 4 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Getting started - demo | first install | level 1 Techniques

I'm setting the severity to "major", because if you are not accustomed to Rudder, it is very hard to understand what the problem is from the symptoms or the logs.

Actions #2

Updated by François ARMAND about 4 years ago

  • Related to Bug #1974: If an error happen during boostrap, the webapp starts but is in a zombie state and the error page is not displayed added
Actions #3

Updated by François ARMAND about 4 years ago

  • Related to Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server) added
Actions #4

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #5

Updated by François ARMAND about 4 years ago

  • Priority changed from 0 to 54
Actions #6

Updated by François ARMAND about 4 years ago

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

Updated by François ARMAND about 4 years ago

Since correction of #1974, we now cleanly unregister the service when there is a bootstrap check that fail. There is one which check that ALL mandatory DIT entries are present, and so that rudder-init ran.

Actually, I removed one such entry and the service return a 503:

--2017-04-25 14:36:03--  http://localhost:8080/rudder
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8080... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
2017-04-25 14:36:03 ERROR 503: Service Unavailable.

But in https://xxx.xxx.xxx.xxx/rudder/ I'm getting the "Rudder is currently loading, please wait..." infinite page. We should have an other one for 503.

Actions #8

Updated by François ARMAND about 4 years ago

  • Status changed from In progress to New
  • Assignee deleted (François ARMAND)
Actions #9

Updated by François ARMAND about 4 years ago

Regarding the previous message, on Rudder 3.1, when loading we have the following return:

--2017-04-25 15:05:35--  http://localhost:8080/rudder
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8080... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8080... failed: Connection refused.
Actions #10

Updated by Alexis MOUSSET about 4 years ago

When Rudder is loading, jetty does not answer, and apache returns a 503 too.

We can at least modify the "loading" message to include a reminder about rudder-init.

Actions #11

Updated by François ARMAND about 4 years ago

  • Subject changed from There is no clear warning if rudder-init didn't run (and webapp is broken) to Infinite "rudder is loading" page is rudder-init didn't run
Actions #12

Updated by François ARMAND about 4 years ago

  • Subject changed from Infinite "rudder is loading" page is rudder-init didn't run to Infinite "rudder is loading" page if rudder-init didn't run
Actions #13

Updated by François ARMAND about 4 years ago

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

Updated by François ARMAND about 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/1646
Actions #15

Updated by François ARMAND about 4 years ago

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

Updated by Vincent MEMBRÉ almost 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.20, 4.0.5 and 4.1.2 which were released today.

Actions #17

Updated by François ARMAND almost 2 years ago

  • Related to Bug #15387: Clean-up Jetty abort on boot added
Actions

Also available in: Atom PDF