Connecting to seed. Node started just hangs.

Question

This is happening a lot in my test environment. I start up a genesis node then try to connect to it and the second node hangs. The second node asks for permissions so I grant the node permissions. Then I try to connect and it hangs at "Node started".  It does say users can connect to the node using the ip address of the node. A Ctrl-c exits out but and trying to run multichain-cli commands the node never connected. This problem is happening a lot lately and I am not sure what is the cause other than maybe port blocking issues.

Comments

Thanks for reporting this - what version are you using?

---

I am using the latest version.  Alpha 22.  I just lost connection to one chain which was having the same problems. In that chain assets would send but the receiver would never receive. I srt permissions and only the genesis node would see the permissions changesm.

I started a new test chain and I'm having the same issues with nodes hanging on start. It's strange because this node hanging even happened when I started up the Genesis node. I did a server reboot and then it started up without hanging.  Alpha 21 was also having these node hang problems. I'm running the nodes on CentOs 64 bit. I tried changing ports but still intermittent node hanging occurs.

---

Started a brand new genesis block chain and again just freezes on "Node started". This is not a port issue because its using a different set of ports.  Cannot really get past making a genesis node with Alpha 22.

---

Started a brand new fresh node.  Installed version Alpha 22 for the first time.  Created a new blockchain using the default params.dat values and again freezes after it finds the genesis block at "Node Started".  I think there is some major bug in Alpha 22 that needs to be addressed or Multichain is really pretty much non-functional. I was running other tests on CentOS for a few weeks and Alpha 21 seemed stable until it crashed the other day and I lost the entire blockchain because the Genesis node would not connect.

---

Doing some more trials to see where the bug is.  I found something strange when trying to run the -deamon command to start the chain it seems that the system hangs when I physically type "multichaind mychainname -daemon" but if I copy paste it from your output text after creating a new chain it seems to work without hanging. Something to do with new line characters in your command parsing or my editor maybe?  I am using putty. I bet the chain is running in the background but the -deamon command is not working correctly. This has been happening for a lot of my test nodes now. Please have a look at the way you are parsing after the -deamon tag.  I will keep checking to see if this is the real problem.

Answer 1

Based on what you wrote, I think the problem may simply be that you are spelling daemon incorrectly.

If you don't run MultiChain in the background, you also have the option of pressing Ctrl-Z then using the bg command in Unix.

Comments

Yup that was it.  Didn't realize it because I wrote a script to automate some of the commands and it was a stupid spelling error crashing all the startups. Nodes are starting up without any problems now.  Not sure what happened last week with two nodes not receiving native assets.  Running more tests this week. If it happens again I will open a new discussion.

---

Great - thanks for the update.