You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following is just a list of common configuration options. Many configuration options need to be adjusted according to your own conditions, and the corresponding configurations of different clusters change greatly, so it is difficult to give a reference value, but if you understand their role, you can make adjustments according to your own conditions
ListenAddress and RemoteListenAddress do not participate in order transactions and chain interactions. There is no need to use public addresses. It is recommended to listen to internal addresses. If you want other machines in the intranet to interact with Lotus miner, please change the address to the intranet address of the machine, such as:ListenAddress = "/IP4/ 192.168.0.100/TCP/2345/HTTP" and restart Lotus miner
[Backup] section
[Backup]
# Note that in case of metadata corruption it might be much harder to recover# your node if metadata log is disabled## type: bool# env var: LOTUS_ BACKUP_ DISABLEMETADATALOG#DisableMetadataLog = false
If you really don't have so much space to store metadata log, you can disable it in the following ways: DisableMetadataLog = true
[Libp2p]
[Libp2p]
# Binding address for the libp2p host - 0 means random port.# Format: multiaddress; see https://multiformats.io/multiaddr/## type: []string# env var: LOTUS_ LIBP2P_ LISTENADDRESSES#ListenAddresses = ["/ip4/0.0.0.0/tcp/0", "/ip6/::/tcp/0"]# Addresses to explicitally announce to other peers. If not specified,# all interface addresses are announced# Format: multiaddress## type: []string# env var: LOTUS_ LIBP2P_ ANNOUNCEADDRESSES#AnnounceAddresses = []# Addresses to not announce# Format: multiaddress## type: []string# env var: LOTUS_ LIBP2P_ NOANNOUNCEADDRESSES#NoAnnounceAddresses = []# When not disabled (default), lotus asks NAT devices (e.g., routers), to# open up an external port and forward it to the port lotus is running on.# When this works (i.e., when your router supports NAT port forwarding),# it makes the local lotus node accessible from the public internet## type: bool# env var: LOTUS_ LIBP2P_ DISABLENATPORTMAP#DisableNatPortMap = false# ConnMgrLow is the number of connections that the basic connection manager# will trim down to.## type: uint# env var: LOTUS_ LIBP2P_ CONNMGRLOW#ConnMgrLow = 150# ConnMgrHigh is the number of connections that, when exceeded, will trigger# a connection GC operation. Note: protected/recently formed connections don't# count towards this limit.## type: uint# env var: LOTUS_ LIBP2P_ CONNMGRHIGH#ConnMgrHigh = 180# ConnMgrGrace is a time duration that new connections are immune from being# closed by the connection manager.## type: Duration# env var: LOTUS_ LIBP2P_ CONNMGRGRACE#ConnMgrGrace = "20s"
If you run the markets subsystem, this area can be deleted from the Lotus miner node. This area only needs to be configured on the markets node. The main configuration items are ListenAddresses = ["/ip4/0.0.0.0/tcp/0", "/ip6/::/tcp/0"]and AnnounceAddresses = []. Please configure these two items as your Public address. At the same time, sometimes your node may be behind the firewall, After configuration, you must check your port mapping and ensure that the node can be accessed externally. It should be noted that after you configure these, you need to update your node address with the following command:
lotus-miner actor set-addrs /ip4/<ip>/tcp/<port>
Check the node public access status with the following command
Separating the subsystems will be a major improvement in overall stability and security, so it is recommended to separate the subsystems as soon as possible, while currently you can only separate the Markets subsystem, the separation process can be found in this link.
SealerApiInfoand SectorIndexApiInfo only need to be configured in the markets node. You can obtain them through the following command. Note that this command needs to be executed in the mining/sealing/proving node
lotus-miner auth api-info --perm=admin
[Addresses] section
# Addresses to send PreCommit messages from## type: []string# env var: LOTUS_ ADDRESSES_ PRECOMMITCONTROL#PreCommitControl = []# Addresses to send Commit messages from## type: []string# env var: LOTUS_ ADDRESSES_ COMMITCONTROL#CommitControl = []# type: []string# env var: LOTUS_ ADDRESSES_ TERMINATECONTROL#TerminateControl = []# type: []string# env var: LOTUS_ ADDRESSES_ DEALPUBLISHCONTROL#DealPublishControl = []# DisableOwnerFallback disables usage of the owner address for messages# sent automatically## type: bool# env var: LOTUS_ ADDRESSES_ DISABLEOWNERFALLBACK#DisableOwnerFallback = false# DisableWorkerFallback disables usage of the worker address for messages# sent automatically, if control addresses are configured.# A control address that doesn't have enough funds will still be chosen# over the worker address if this flag is set.## type: bool# env var: LOTUS_ ADDRESSES_ DISABLEWORKERFALLBACK#DisableWorkerFallback = false
PreCommitControl,CommitControl,TerminateControl,DealPublishControl before configuring these options, please add the address to the Lotus miner control address list. You can add the control wallet address through the following command:
lotus-miner actor control set [command options] [...address]
Among them, DealPublishControl needs to be configured in all nodes. If you separate the markets subsystem, please don't forget to keep the same configuration in the markets node.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The following is just a list of common configuration options. Many configuration options need to be adjusted according to your own conditions, and the corresponding configurations of different clusters change greatly, so it is difficult to give a reference value, but if you understand their role, you can make adjustments according to your own conditions
[API] section
ListenAddress
andRemoteListenAddress
do not participate in order transactions and chain interactions. There is no need to use public addresses. It is recommended to listen to internal addresses. If you want other machines in the intranet to interact withLotus miner
, please change the address to the intranet address of the machine, such as:ListenAddress = "/IP4/ 192.168.0.100/TCP/2345/HTTP"
and restartLotus miner
[Backup] section
If you really don't have so much space to store
metadata log
, you can disable it in the following ways:DisableMetadataLog = true
[Libp2p]
If you run the markets subsystem, this area can be deleted from the
Lotus miner
node. This area only needs to be configured on the markets node. The main configuration items areListenAddresses = ["/ip4/0.0.0.0/tcp/0", "/ip6/::/tcp/0"]
andAnnounceAddresses = []
. Please configure these two items as your Public address. At the same time, sometimes your node may be behind the firewall, After configuration, you must check your port mapping and ensure that the node can be accessed externally. It should be noted that after you configure these, you need to update your node address with the following command:Check the node public access status with the following command
[Subsystems] section
Separating the subsystems will be a major improvement in overall stability and security, so it is recommended to separate the subsystems as soon as possible, while currently you can only separate the Markets subsystem, the separation process can be found in this link.
SealerApiInfo
andSectorIndexApiInfo
only need to be configured in the markets node. You can obtain them through the following command. Note that this command needs to be executed in themining/sealing/proving
node[Addresses] section
PreCommitControl
,CommitControl
,TerminateControl
,DealPublishControl
before configuring these options, please add the address to theLotus miner
control address list. You can add the control wallet address through the following command:lotus-miner actor control set [command options] [...address]
Among them,
DealPublishControl
needs to be configured in all nodes. If you separate the markets subsystem, please don't forget to keep the same configuration in the markets node.Beta Was this translation helpful? Give feedback.
All reactions