Debugging Lite Node issues

If you find a problem with the Lite Node on your system, please report the relevant console output, the results of diode-node.info, the results of snap get diode-node, and the logs from snap logs diode-node

ulimit problem → in v1.5.16 and earlier, the node always sets ulimit to 120,000 TCP connections. If your system has ulimit set to a small maximum connections, the node will not start. in v1.15.17 and later, the node sets ulimit tcp max to the system max instead. Be aware that your node’s performance may suffer if you restrict TCP connections too much.

rpc connection problem → in v1.15.16 and earlier, there would sometimes be an RPC connection error that was a result of the system hostname being changed without a reboot. In v.1.15.17 and later, the node detects a changed hostname and uses the updated name even without a reboot.

port conflicts → you can set the ports your node uses in case you are running it on a box/vm that already uses the default ports.

checkout snap get diode-node - this shows how to change all ports

that said these are very important ports you shouldn’t remove:

  1. 8545 - is used for network uptime monitoring. so if your node doesn’t respond it’s considered dead
  2. 41046 - this is the primary device port, all devices will check this one first. not having this port will still allow devices to connect but the likelihood is very much reduced.