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
{{ message }}
Repository navigation
Cannot change node or run any command after entering a dead node #236
steempy set nodes [Node that doesn't respond] steempy set nodes [Any nodes] or any other command
Stack Trace
Warning:root:Retry in 1s -- ReadTimeoutError: HttpsConnectionPool(host='[DEAD NODE]',port='[DEAD NODE'S PORT]'): Read timed out. (read timeout=60)
This repeats for as long as I've tested with the secound count going up
changed the title [-]Cannot change node after entering a dead node[/-][+]Cannot change node or run any command after entering a dead node[/+]on May 13, 2018
I was able to change the node by setting the --expires flag to 1 but now nothing happens at all when I run any command EDIT: I found out that the dead node I set came online EDIT 2: I manually updated the config file so my current problem is fixed
Looked into the code a little bit, looks like the connection is started before it is completely needed. In cli.py, there's a line steem = stm.Steem(no_broadcast=args.no_broadcast, **options) before any commands run. I'm not 100% sure how the code is working but I think it could probably be moved down after it checks for the config command because the first reference to the steem variable is in the command info.
Activity
[-]Cannot change node after entering a dead node[/-][+]Cannot change node or run any command after entering a dead node[/+]roadscape commentedon May 14, 2018
Thanks for the report. Last I checked, steem-python attempts to connect to a node prior to updating config. This needs to be fixed.
RoboticMind commentedon May 15, 2018
I was able to change the node by setting the --expires flag to 1 but now nothing happens at all when I run any command EDIT: I found out that the dead node I set came online EDIT 2: I manually updated the config file so my current problem is fixed
DerekRay commentedon Apr 1, 2019
Is this solved?I just meet this problem.
bobinson commentedon Apr 2, 2019
I have been deleting the SQLite file to get out of the dead node scenario.
RoboticMind commentedon May 10, 2019
Looked into the code a little bit, looks like the connection is started before it is completely needed. In cli.py, there's a line
steem = stm.Steem(no_broadcast=args.no_broadcast, **options)before any commands run. I'm not 100% sure how the code is working but I think it could probably be moved down after it checks for the config command because the first reference to the steem variable is in the command info.nnnarvaez commentedon Nov 29, 2019
open cli.py navigate to line 776 comment the line connecting to the steem network, save.
run the command
steempy set nodes "live.node" <enter>Now the dead node has been replaced
Uncomment cly.py line 776 and save, have fun.