Bummer. Hours wasted... and counting.
Using wackou's bts_tools (run command) I don't think you don't see the actual stdout of the client. I think the python script scarfs that up. If I'm wrong about that I never noticed any unusual messages. info returned 0.01% of delegate participation, which I thought was normal until the node sync was complete, but if nathan's chain server was offline it probably went right to p2p connections.
I just restarted it with liondani's chain server, but I need to restart it once again as I see there are 27 net connections but it isn't synced yet. I am repeating the deletion of the 3 folders I mentioned above, this time with liondani's chainserver in the config.
Is there a way to check if liondani's chainserver is online?
This is a real PITA! After removing the exceptions,logs & peers.leveldb folders and restarting the client with liondani's chain_server IP, I still get 9 connections. Upon looking at the config.json file closer I see a list of 17 default peers. The wiki didn't say a word about those, should they be removed? If the code goes 1st the chainserver before any peers until the blkchn is synced, why are there 9 connections right off the bat?
Ha ha!!! After removing all but liondani's IP address from the list of default peers & restarting, the first msg to appear was:
merging 16 peers into config.json
so if one of those default peers is on a short fork I may not get back onto the main fork! It's on blk 2041604, 12 days old. I'll check it again in a couple of hrs I need to be somewhere else now.