show cluster task
Description
Show WildFire appliance
cluster task information for the local cluster node or for all cluster
nodes, or display the completed cluster task history or pending cluster
tasks.
Hierarchy Location
show cluster
Syntax
task {
current;
history;
local;
pending;
} Options
> current—Display
tasks currently allowed on the WildFire appliance cluster. Available
only on cluster controller nodes.
> history—Display
completed cluster tasks. Available only on cluster controller nodes.
>
local—Display pending tasks on the local WildFire
appliance cluster node.
> pending—Display
pending tasks for the entire WildFire appliance cluster. Available
only on cluster controller nodes.
Sample Output
admin@WF-500(active-controller)> show cluster task local
Request: reboot from WF-500 (009701000034/74702) at 2017-02-21 03:06:45 UTC
Reboot requested by admin
Queued: by WF-500
2/3 core servers available. reboot not allowed to maintain quorum
Request: reboot from WF-500 (009701000034/74704) at 2017-02-21 03:10:27 UTC
Reboot requested by admin
Queued: by WF-500
2/3 core servers available. reboot not allowed to maintain quorum
admin@WF-500(active-controller)> show cluster task current
no tasks found
admin@WF-500(active-controller)> show cluster task pending
Request: reboot from WF-500 (009701000034/74702) at 2017-02-21 03:06:45 UTC
Reboot requested by admin
Queued: by WF-500
2/3 core servers available. reboot not allowed to maintain quorum
Request: reboot from WF-500 (009701000034/74704) at 2017-02-21 03:10:27 UTC
Reboot requested by admin
Queued: by WF-500
2/3 core servers available. reboot not allowed to maintain quorum
admin@WF-500B(passive-controller)> show cluster task history
Request: reboot from WF-500 (009701000044/35533) at 2017-02-17 19:21:53 UTC
Reboot requested by admin
Response: permit by WF-500B at 2017-02-17 22:11:31 UTC
request not affecting healthy core server.
Progress: Wait for kv store ready for query...
KV store is ready, wait for cluster leader available...
Cluster leader is 10.10.10.100...
Checking is sysd and clusterd are alive...
Checking if cluster-mgr is ready...
Checking global-db-cluster readiness...
Stopping global-queue server and leaving cluster...
Stopping global-db servers and doing failover...
rebooting...
Finished: success at 2017-02-17 22:17:56 UTC
Required Privilege Level
superuser, deviceadmin
