Feature #886
Add option to delay starting of frontend or Slave BE
| Status: | Closed | Start date: | 12/20/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  jams |
% Done: | 0% |
|
| Category: | Other | Spent time: | 5.00 hours | |
| Target version: | 8.0 | Estimated time: | 3.00 hours |
Description
Check if the MasterBe is ready before starting the frontend of Slave.
Associated revisions
runit-scripts: Dont' start a slave backend until a connection to master is established.
-remove delay on the frontend service waiting on the backend. The delay for mythfrontend has now been moved into frontend startup session script.
refs #886
LinHES-system: add be_check.py and modify LinHES-session to use it.
This will stop mythfrontend/mythwelcome from starting if be_check can't connect to the master backend.
Mostly this was done to stop mythfronted from complaining about not being able to contact the MBE and in the worst case displaying the DB connection configuration screen.
refs #886
mythdb-initial, mythinstall: add option for BEwait and enable it in the initial database.
refs #886
History
Updated by jams almost 12 years ago
- Status changed from In Progress to Closed
Added option in mythinstall / advanced to enable or disable the delay of starting the frontend.
When delayed and a connection could not be established a msg will be displayed stating that fact.
Connections are tested with be_check.py which is a simple check of connecting to the master BE using the python bindings.