12/3/2023 0 Comments Dcommand xmon 5.1 outpursprimary-level represents the primary log level of EMQX, which is used to specify the default log level for the entire system. This command can be used to manage log handlers states, such as setting logging level etc. Ram_copies = 414 transactions committed, 32 aborted, 6 restarted, 250 logged to discĠ held locks, 0 in queue 0 local transactions, 0 remoteĠ transactions waits for other nodes: = > System info in version "4.20.4.1", debug level = none <=īackend types = null_copies - mria_mnesia_null_storage Useful for monitoring and debugging the health of the cluster. The optional -json parameter displays the cluster status in JSON format. Use this command to view the status of the EMQX cluster. Note that this operation may cause cluster state inconsistency, so use it with caution. Use this command to forcefully remove the specified node from the EMQX cluster. Use this command to remove the node from the current EMQX cluster.įorcefully remove a node from the cluster. Ensure that the specified node is active and accessible. Use this command to join a node to the EMQX cluster where the specified node is located. In other words, the command emqx ctl cluster join is used to send a request to join the cluster of the node specified by, rather than having that node join its own cluster. Note that the join command in EMQX for joining a cluster is a "request" sent to the node specified in the parameters, rather than an "invitation". This command is used to view and manage the cluster status of nodes. The following example shows viewing the content of the second modification (tnxid=2), which is an operation to enable a TLS listener. This ID strictly increases within the cluster scope, and every modification, such as changing a configuration from the Dashboard, is recorded in the database. If for some reason, this replication can not apply in a peer node, this command can be used to inspect and even fix the replication so it can move forward.ĮMQX generates an ID (tnxid) for each configuration modification within the cluster scope. Then, the same operation is recorded in the database and asynchronously forwarded to other nodes in the cluster. When an API is called, for example, through operations in the Dashboard, the node receiving the request first writes the modified content locally to data/configs/cluster.hocon. This old command is still available in EMQX 5.1 but it is not displayed in the help information.ĮMQX HTTP API can be used to modify many configurations. In EMQX 5.0.x, this command was named cluster_call. This command is a quick inspection to see if the broker is up and running. This section aims to introduce the functionality of the commands, while detailed parameter information can be viewed using the help command. Therefore, it is advised to avoid excessive usage of the ctl command.īelow is a list of all the subcommands of the ctl command along with their brief descriptions. The ctl command remotely connects to the specified EMQX node by starting a hidden Erlang node, executes an Erlang remote call, and then prints the returned result. The ctl command needs to be run after the EMQX service is started.ĮMQX also provides emqx_ctl command, which is an alias of emqx ctl. The EMQX ctl command provides multiple subcommands for managing and monitoring EMQX. Validate if the EMQX configuration file is correct.Ĭlear the output of the interactive shell console.Įxecute an Escript script on the EMQX node. Retrieve the process ID of the running EMQX node. Retrieve the path of the EMQX root directory. Retrieve the path of the EMQX Erlang library. The following are advanced commands for development and debugging, and ordinary users usually don't need to care about them: CommandĬonnect to the interactive shell of a remote EMQX node.Īttach to a running EMQX node to perform interactive operations. Executing emqx ctl help can get more detailed information. Used to start EMQX in a development environment without running it in the background. Start EMQX in foreground mode, without using an interactive shell. Used for debugging EMQX in a development environment, requiring interaction with EMQX. Start EMQX in Erlang or Elixir interactive shell. Start EMQX in daemon mode, without requiring an interactive shell during runtime. Here are some commonly used startup and administrative commands: Command # Startup CommandsĮMQX supports some basic startup and administrative commands, which can be executed using the emqx command. This page introduces all kinds of startup and administrative commands supported by EMQX and gives detailed introductions to ctl administrative commands.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |