severalnines/s9s-tools

Repository for tools (e.g the s9s command line client) helping to manage and monitor your Severalnines clusters.

s9s-tools

Repository for tools helping to manage and monitor your Severalnines clusters. The repository contains the following tools:

• s9s (cli)

Important

This git repository contains the sources of a development version of s9s-tools, this might doesn't work with the current publicly avaible clustercontrol-controller version, please check relevant versioned branches (1.4.2_release).

APT and YUM repositories

See http://repo.severalnines.com/s9s-tools/

You can use the following script to install s9s-tools automated:

http://repo.severalnines.com/s9s-tools/install-s9s-tools.sh

Download and run the script as sudo (it will set up the repository, installs and initializes the s9s CLI).

Some screenshots

s9s-tools's Issues

Allow to create backups without specifying a hostname

Hi,
it must be possible to take backups without specifying:
--nodes=NODELIST The list of nodes involved in the backup.

In that case, it is cmon that will auto-select the node to backup .

Thus, i would like to be able to create a backup like. i.e, omitting --node/--nodes as an argument:

s9s backup --create --cluster-id=1 --backup-method=mariabackupfull --parallellism=2 --on-node

BR
johan

s9s job : short option -G for show job log is not handled.

s9s job --help
...
-G, --log Show job log
...

How to repeat:

s9s job --controller=localhost:9500 --job-id=79 -G
s9s: invalid option -- 'G'
Error in command line options.

Whereas

s9s job --controller=localhost:9500 --job-id=79 --log

prints out the expected job messages

cmon creating defunct processes

CMON process creates a number of defunct processes which takes up a lot of CPU and effectively hangs until restarted. Then it sends out a lod of emails which are not relevant currently

Unable to create remote dba user

Hi everybody,

If I try to create a remote dba user, I'll always get an error 256 like this:

s9s user --generate-key --create --cmon-user=username --controller="https://controller-IP:9501"
Connection to controller-IP closed.
SSH command exited with non-zero status: 256
ssh -tt -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -oBatchMode=yes -oPasswordAuthentication=no -oConnectTimeout=30 'controller-IP' 'echo "{
"pubkey": "-----BEGIN RSA PUBLIC KEY-----[......]n-----END RSA PUBLIC KEY-----\n",
"user_name": "username"
}" | sudo -n tee /var/lib/cmon/usermgmt.fifo 2>/dev/null >/dev/null'

Passwordless authentication from the remote client and the controller is enabled and working .... so I've no clue why the command fails :-(