mirror of https://github.com/zulip/zulip.git
start-server: More gracefully handle only starting part of the server.
While the previous commit handles the common case of all of the server being started already, it still produces ERROR output lines from supervisorctl when most of the server is already running. Take the case where one worker is stopped: ``` $ supervisorctl stop zulip-workers:zulip_events_deferred_work zulip-workers:zulip_events_deferred_work: stopped $ ./scripts/start-server 2023-04-04 15:50:28,505 start-server: Running syntax and database checks System check identified no issues (15 silenced). 2023-04-04 15:50:31,977 start-server: Starting Tornado process on port 9800 zulip-tornado:zulip-tornado-port-9800: ERROR (already started) 2023-04-04 15:50:32,283 start-server: Starting Tornado process on port 9801 zulip-tornado:zulip-tornado-port-9801: ERROR (already started) 2023-04-04 15:50:32,592 start-server: Starting django server zulip-django: ERROR (already started) 2023-04-04 15:50:33,340 start-server: Starting workers zulip-workers:zulip_events_deferred_work: started zulip_deliver_scheduled_emails: ERROR (already started) zulip_deliver_scheduled_messages: ERROR (already started) process-fts-updates: ERROR (already started) 2023-04-04 15:50:34,659 start-server: Done! Zulip started successfully! ``` More gracefully handle these cases: ``` $ ./scripts/start-server 2023-04-04 15:52:39,815 start-server: Running syntax and database checks System check identified no issues (15 silenced). 2023-04-04 15:52:43,270 start-server: Starting Tornado process on port 9800 2023-04-04 15:52:43,287 start-server: zulip-tornado:zulip-tornado-port-9800 already started! 2023-04-04 15:52:43,287 start-server: Starting Tornado process on port 9801 2023-04-04 15:52:43,300 start-server: zulip-tornado:zulip-tornado-port-9801 already started! 2023-04-04 15:52:43,300 start-server: Starting django server 2023-04-04 15:52:43,316 start-server: zulip-django already started! 2023-04-04 15:52:43,793 start-server: Starting workers zulip-workers:zulip_events_deferred_work: started 2023-04-04 15:52:45,111 start-server: Done! Zulip started successfully! ```
This commit is contained in:
parent
cb097760b9
commit
dd5dbcabcb
|
@ -127,8 +127,13 @@ elif action == "start":
|
|||
|
||||
def restart_or_start(service: str) -> None:
|
||||
our_verb = action
|
||||
if our_verb == "restart" and len(list_supervisor_processes([service], only_running=True)) == 0:
|
||||
existing_services = list_supervisor_processes([service])
|
||||
running_services = list_supervisor_processes([service], only_running=True)
|
||||
if our_verb == "restart" and len(running_services) == 0:
|
||||
our_verb = "start"
|
||||
elif our_verb == "start" and existing_services == running_services:
|
||||
logging.info("%s already started!", service)
|
||||
return
|
||||
subprocess.check_call(["supervisorctl", our_verb, service])
|
||||
|
||||
|
||||
|
@ -202,7 +207,9 @@ if has_application_server():
|
|||
# If we were doing this non-gracefully, or starting as opposed to
|
||||
# restarting, we need to turn the workers (back) on. There's no
|
||||
# advantage to doing this not-all-at-once.
|
||||
if (action == "start" or args.less_graceful) and len(workers) > 0:
|
||||
if action == "start" or args.less_graceful:
|
||||
workers = list_supervisor_processes(workers, only_running=False)
|
||||
if workers:
|
||||
logging.info("Starting workers")
|
||||
subprocess.check_call(["supervisorctl", "start", *workers])
|
||||
|
||||
|
|
Loading…
Reference in New Issue