You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Show information like ps -ef by reading the PID file & systemctl status
backend.ai ag status* Show information like ps -ef by reading the PID file & systemctl status
backend.ai strg status (we need to apply backend.ai-cli to storage-proxy)* Show information like ps -ef by reading the PID file & systemctl status
backend.ai web status (we need to apply backend.ai-cli to web)* Show information like ps -ef by reading the PID file & systemctl status
Once done, we could wrap these commands as a shell script like show_status.sh which configures the activation of virtualenvs, etc. and execute the above commands.
Note that systemd configuration is only done in production setups, reading the result of systemctl status should be done as an opt-in feature.If we combine sd_notify to report the server startup/terminating process to systemd, it will be able to provide a little bit richer information.
Let's add a pretty table-like display for console:
backend.ai mgr status* As a part of feat(BA-75): IntroduceRaftifyand refactorDistributedGlobalTimerwith Raft #2105, let's include the raft node status of the current manager node and other manager nodes (e.g., leader/follower, raft term, etc.)Show information like
ps -efby reading the PID file &systemctl statusbackend.ai ag status* Show information likeps -efby reading the PID file &systemctl statusbackend.ai strg status(we need to applybackend.ai-clito storage-proxy)* Show information likeps -efby reading the PID file &systemctl statusbackend.ai web status(we need to applybackend.ai-clito web)* Show information likeps -efby reading the PID file &systemctl statusOnce done, we could wrap these commands as a shell script like
show_status.shwhich configures the activation of virtualenvs, etc. and execute the above commands.Note that systemd configuration is only done in production setups, reading the result of
systemctl statusshould be done as an opt-in feature.If we combine sd_notify to report the server startup/terminating process to systemd, it will be able to provide a little bit richer information.Example:
JIRA Issue: BA-188