Log levels can also be adjusted on a partition-by-partition basis through the administrative interface. $ stellar-core http-command 'll?level=debug' The log level can be controlled by configuration, the -ll command-line flag, or adjusted dynamically by administrative (HTTP) commands. The logging system only emits those messages at or above its configured logging level.

Log messages are classified by progressive priority levels: TRACE, DEBUG, INFO, WARNING, ERROR and FATAL.

Stellar Core sends logs to standard output and stellar-core.log by default, configurable as LOG_FILE_PATH. You should see authenticated_count increase.

Your node will go through the following phases as it joins the network: Establishing Connection to Other Peers. See commands for a description of the available commands. It's typically accessed by administrators, or by a mid-tier application to submit transactions to the Stellar network. That HTTP endpoint is not intended to be exposed to the public internet. Commands can be submitted using command-line HTTP tools such as curl, or by running a command such as When your node is running, you can interact with Stellar Core via an administrative HTTP endpoint. You may want to skip ahead and review the logging section to familiarize yourself with Stellar Core's output. Once you've set up your environment, configured your node, set up your quorum set, and selected archives to get history from, you're ready to start Stellar Core.Īt this point, you're ready to observe your node's activity as it joins the network.

Instal the new Stellar Interface