guys, any idea why i cant run the “goal” command?
goal logging enable -n
nvm i fix it with:
./goal logging enable -n HadiboysOneyesoneno
Node = HadiboysOneyesoneno, Guid = 36b55939-dc87-477d-8be8-dedbe8885b4c
hmmm another problem as i wanna test out “goal node status”
root@ubuntu-s-2vcpu-4gb-sfo2-01:~/node# ./goal node status
Data directory not specified. Please use -d or set $ALGORAND_DATA in your environment. Exiting.
Hello!
Generally, with goal, you will need to specify the data directory. So: ./goal node status -d <path-to-node-data-dir>
Thanks you liz, it works now:
Last committed block: 14769
Time since last block: 3.3s
Sync Time: 0.0s
Last consensus protocol: v0
Next consensus protocol: v0
Round for next consensus protocol: 14770
Next consensus protocol supported: true
1 Like
./goal clerk send -a 100 -f CAGXX556ISDMV4EN6FG322V7KMK6NO2WWQKYVISUUCZWV3XFTQVPXVFBFA -t CU5QSBNCJDPHXTOLBFCEQKKXSM65PJQXTYTAIFEBOQZF62Q4HJ43AFG3BM
Sent 100 algos from account CAGXX556ISDMV4EN6FG322V7KMK6NO2WWQKYVISUUCZWV3XFTQVPXVFBFA
to address CU5QSBNCJDPHXTOLBFCEQKKXSM65PJQXTYTAIFEBOQZF62Q4HJ43AFG3BM, transaction ID: tx-7AOQLIHMMIP5LCIYQGFGEKX4OCMXFENJLWYGPFH67W42TSQX2FSA.
Fee set to 1
I think it sucess
hmmm looks my node is stuck at 24960, even though i have update it to the new version:
Last committed block: 24960
Time since last block: 0.0s
Sync Time: 0.0s
Last consensus protocol: v0
Next consensus protocol: v0
This is the force update log:
Stopping node...
... node not running
Backing up current binary files...
Backing up current data files from /root/node/data...
Installing new binary files...
Installing new data files into /root/node/data...
Checking for new ledger in /root/node/data
Applying migration fixups...
Deleting existing log files in /root/node/data
Starting node in /root/node/data...
Failed to start algorand@-root-node-data.service: Unit algorand@-root-node-data.service not found.
Algorand node successfully started!Looks like error, when running
./carpenter -d data
Watching file: data/node.log…
could not decode line from JSON: ++++++++++++++++++++++++++++++++++++++++
could not decode line from JSON: Logging Starting
could not decode line from JSON: Telemetry Enabled: 36b55939-dc87-477d-8be8-dedbe8885b4c:HadiboysOneyesoneno
could not decode line from JSON: Session: 36b55939-dc87-477d-8be8-dedbe8885b4c
could not decode line from JSON: ++++++++++++++++++++++++++++++++++++++++
could not decode line from JSON: Telemetry Enabled: 36b55939-dc87-477d-8be8-dedbe8885b4c:HadiboysOneyesoneno
could not decode line from JSON: Session: 36b55939-dc87-477d-8be8-dedbe8885b4c
24961.0.12: VoteAttest EDSKD- |
could not decode line from JSON: ++++++++++++++++++++++++++++++++++++++++
could not decode line from JSON: Logging Starting
could not decode line from JSON: Telemetry Enabled: 36b55939-dc87-477d-8be8-dedbe8885b4c:HadiboysOneyesoneno
could not decode line from JSON: Session: 36b55939-dc87-477d-8be8-dedbe8885b4c
could not decode line from JSON: ++++++++++++++++++++++++++++++++++++++++
could not decode line from JSON: Telemetry Enabled: 36b55939-dc87-477d-8be8-dedbe8885b4c:HadiboysOneyesoneno
could not decode line from JSON: Session: 36b55939-dc87-477d-8be8-dedbe8885b4c
24961.0.12: VoteAttest EDSKD- |
The network has stalled. We’ll have it running as soon as possible (we’re not in quick-response mode yet).
1 Like
thanks it works now… looks like it is restarted and i wonder if we need to do over again those task? collecting badge is fun
You should not have to do the task over.
1 Like
Jason is correct. No need to do the task over again.
When we validate, we will let you know if there are any issues with your submission.
Stay tuned - badges will be awarded this week. 
1 Like
hai liz is the network down?
root@ubuntu-s-2vcpu-4gb-sfo2-01:~/node# ./goal node status
Cannot contact Algorand node: Get http://127.0.0.1:8080/v1/status: dial tcp 127.0.0.1:8080: connect: connection refused.
oh nvm… fixed… turn out that somehow my node is not running.