Project

General

Profile

Bug #3233

Rudder restarts jetty every two promise execution if we change the webapp context URL

Added by Vincent MEMBRÉ over 7 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
3
Assignee:
-
Category:
System techniques
Target version:
Pull Request:
Severity:
User visibility:
Effort required:
Priority:

Description

If we change Rudder webapp context URL (by changing jetty and apache files), the distribute-policy Rule could not find check if the status of the webapp is OK, so it thinks its not running and force jetty restart on the next run.

I changed my context URL to "myLittleRudder" so access to my webapp is http://server.rudder.local/myLittleRudder and the url the API status is http://server.rudder.local/myLittleRudder/api/status

but the promise keeps on checking rudder/api/status because the context URL is hardcoded in the distribute policy

Here is the extract of alive-check and the bundle root-alive-check which cause the problem:

bundle agent root_alive_check {

        vars:

                "apps_to_check" slist => { "rudder", "endpoint" };

        methods:

                "any" usebundle => generic_alive_check("$(apps_to_check)");

}

bundle agent generic_alive_check(app) {

        vars:

                        "site_to_check" string => "http://localhost:8080/$(app)/api/status";
                        "sitename" string => canonify("$(site_to_check)");

                        "cleanup_failed_classes" slist => { "site_down_once_$(sitename)", "site_alivecheck_restart_jetty_$(sitename)" };

                        "failed_result_class" string => "site_down_once_$(sitename)",
                                ifvarclass => "!site_down_once_$(sitename).!first_iteration_passed";

                        "site_failure_persist_time" string => "10",
                                ifvarclass => "!site_down_once_$(sitename).!first_iteration_passed";

                        "failed_result_class" string => "site_alivecheck_restart_jetty_$(sitename)",
                                ifvarclass => "site_down_once_$(sitename).!first_iteration_passed";

                        "site_failure_persist_time" string => "0",
                                ifvarclass => "site_down_once_$(sitename).!first_iteration_passed";

        classes:

                        "first_iteration_passed" expression => "any";

        methods:

                        "any" usebundle => generic_process_check_process(".*java.*/opt/rudder/jetty7/start.jar", "jetty", "true"),
                                ifvarclass => "site_alivecheck_restart_jetty_$(sitename)",
                                classes => set_persist_classes("site_alivecheck_jetty_restarted_$(sitename)", "site_down_once_$(sitename)" ,"0");

 [...]

The context URL should not be hardcoded in that promise

I target 2.4.3 as i saw it happen in 2.5 and 2.4.3, it may be the case to in 2.3 too.

#1

Updated by Matthieu CERDA over 7 years ago

  • Target version changed from 2.4.3 to 2.4.4
#2

Updated by François ARMAND about 7 years ago

So, the problem only occures when the user change the context on jetty (and so, it means that the user also change the apache proxy config).

We can't only explain in the doc that the "rudder" variable has to be changed without also upgrading the "upgrade" scrip, because for now, system promises are just erased.

A solution may be to use an external file to set the context as it is done for password, and use it to set the context for jetty, system promises, and Apache.

#3

Updated by Nicolas PERRON about 7 years ago

  • Target version changed from 2.4.4 to 2.4.5
#4

Updated by Nicolas PERRON about 7 years ago

  • Target version changed from 2.4.5 to 2.4.6
#5

Updated by Nicolas PERRON almost 7 years ago

  • Target version changed from 2.4.6 to 2.4.7
#6

Updated by Nicolas PERRON almost 7 years ago

  • Target version changed from 2.4.7 to 2.4.8
#7

Updated by Nicolas PERRON almost 7 years ago

  • Target version changed from 2.4.8 to 2.4.9
#8

Updated by Nicolas PERRON over 6 years ago

  • Target version changed from 2.4.9 to 2.4.10
#9

Updated by Nicolas PERRON over 6 years ago

  • Target version changed from 2.4.10 to 2.4.11
#10

Updated by Nicolas PERRON over 6 years ago

  • Target version changed from 2.4.11 to 2.4.12
#11

Updated by Nicolas PERRON over 6 years ago

  • Target version changed from 2.4.12 to 2.4.13
#12

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 2.4.13 to 2.6.11

Since Support for 2.4 branch is over, retargeting this issue to 2.6

#13

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 2.6.11 to 2.6.12
#14

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 2.6.12 to 2.6.13
#15

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 2.6.13 to 2.6.14
#16

Updated by Jonathan CLARKE almost 6 years ago

  • Target version changed from 2.6.14 to 2.6.16
#17

Updated by Jonathan CLARKE almost 6 years ago

  • Target version changed from 2.6.16 to 2.6.17
#18

Updated by Nicolas PERRON almost 6 years ago

  • Target version changed from 2.6.17 to 2.6.18
#19

Updated by Matthieu CERDA over 5 years ago

  • Target version changed from 2.6.18 to 2.6.19
#20

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.6.19 to 2.6.20
#21

Updated by François ARMAND over 5 years ago

  • Target version changed from 2.6.20 to 2.10.10
#22

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.10.10 to 2.10.11
#23

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.10.11 to 2.10.12
#24

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.10.12 to 2.10.13
#25

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.10.13 to 2.10.14
#26

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.10.14 to 2.10.15
#27

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.10.15 to 2.10.16
#28

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.10.16 to 2.10.17
#29

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.17 to 2.10.18
#30

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.18 to 2.10.19
#31

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.19 to 2.10.20
#32

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.20 to 2.11.18
#33

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.18 to 2.11.19
#34

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.19 to 2.11.20
#35

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 2.11.20 to 2.11.21
#36

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 2.11.21 to 2.11.22
#37

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.11.22 to 2.11.23
#38

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.11.23 to 2.11.24
#39

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.11.24 to 308
#40

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 308 to 3.1.14
#41

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.14 to 3.1.15
#42

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.15 to 3.1.16
#43

Updated by Benoît PECCATTE over 3 years ago

  • Status changed from New to Discussion

There is no reason for a user to change the context url.
- the procedure it not documented
- the context url is part of the api now
- the context url is part of the documentation
- the context url is now hardcoded in rudder agent

So shouldn't we just ignore this issue ?

#44

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.16 to 3.1.17
#45

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.17 to 3.1.18
#46

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.18 to 3.1.19
#47

Updated by François ARMAND about 3 years ago

  • Status changed from Discussion to Rejected

Yeah, closing that. People doing that king of things should be meriting their achievment to make it works :)

Also available in: Atom PDF