Anvil-manage-server

From Alteeve Wiki
Revision as of 15:20, 1 October 2024 by Digimer (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

 Alteeve Wiki :: Man Pages :: Anvil-manage-server

NAME

anvil-manage-server - Tool used to manage a server, like resyncing servers on a rebuilt host.

SYNOPSIS

anvil-manage-server <command> [options]

DESCRIPTION

anvil-manage-server - This tool allow the management of a server.

OPTIONS

-?, -h, --help Show this man page.

--log-secure
When logging, record sensitive data, like passwords.
-v, -vv, -vvv
Set the log level to 1, 2 or 3 respectively. Be aware that level 3 generates a significant amount of log data.

Commands:

--boot-after <'none', 'stay-off', name or uuid>

This will control the boot order of the server when booting all servers (ie: after restoring power). If this is set to 'none', then the server will not wait on any other servers. When shutting down all servers, the boot order is reversed! That is to say, the specified server will shut down before the "--boot-after" server.
If this is set to "--boot-after stay-off", the server will not be booted, unless specifically asked to boot by the user.
If no server name or UUID is given, the current configuration will be reported. This requires "--server" to be passed with a specific name or UUID.
--delay <seconds, default '30'>
This can be used along with "--boot-after" to control the minimum amount of time to wait after the dependant server boots. Note that this is the minimum delay. The actual delay could be longer in practice.
Note
When shutting down all servers, the delay is ignored. Dependant servers will not shut down until this server is off, regardless of how long that takes.
--job-uuid
This is the jobs -> job_uuid of the job to run, if it exists.
--server <'all', name or uuid>
This is the server to work on.
--resync
This will check to see if the server is syncing on this host. If it is not, and if there are sufficient free resources, the server will be configured locally. This will create a local logical volume, which will be used to connect to the peer's replicated storage. The definition file will be written out, if needed. If "--server" isn't used, all servers will be synced (alphabetically, stopping if there are insufficient resources).

AUTHOR

Written by Madison Kelly, Alteeve staff and the Anvil! project contributors.

REPORTING BUGS

Report bugs to users@clusterlabs.org

 

Any questions, feedback, advice, complaints or meanderings are welcome.
Alteeve's Niche! Alteeve Enterprise Support Community Support
© 2025 Alteeve. Intelligent Availability® is a registered trademark of Alteeve's Niche! Inc. 1997-2025
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions.