ok, u are using cntools or coincashew guide?
I used cntools.
Then inaide the scripts folder u have deploy-as-systemd script
Run it an choose N for topology updater
1 Like
Perfect. Thank you! 
1 Like
Hello, writing in this topic so its not duplicate. I have a strange issue with gLiveView.sh since I updated cardano-node to 1.33.
I get this:
And then:
BUT what I found out by accident. If I press the UP Arrow Key during this “Connection to node lost, retrying (1/3)!” countdown phase, I get to see a fully working gLiveView page. But just in between the refresh intervals, it terminates after the “three” attempts are done. So it is actually working, but it thinks that it is not, or something? 
So if I start it, press UP when it shows the “connection to node lost” and then CTRL+C to quit it I can see the data, here is a screen capture:
Any idea on this anyone? 
The block producer, relays are working fine otherwise…
Edit: not using cntools for anything. Just cardano-node and the gLiveView script (followed the coincashew guide)
Did u started the node with another port than 6000?
Also check inside the env file the path to the socket file
Cheers,
No, its on 6000. Path to socket file is ok as well.
It I understand correctly, if any of those two were wrong, I would not see a fully working gLiveView page? (albeit just intermittently by pressing the UP key…)
Try to download the latest glive file
Did a
curl -s -o gLiveView.sh https://raw.githubusercontent.com/cardano-community/guild-operators/master/scripts/cnode-helper-scripts/gLiveView.sh
No difference 
hmm, check inside /.bashrc (cat $HOME/.bashrc) file if u exported the socket path
If not, run
echo export CARDANO_NODE_SOCKET_PATH="$NODE_HOME/db/socket" >> $HOME/.bashrc
source $HOME/.bashrc
Also no difference…
Just to make it clear again, it actually works, if I press the UP arrow key. So it is not a connection issue or some other kind of total failure.
I am not really sure what happens when the UP key is pressed thought, like it refreshes the screen or something…? And the data it shows is accurate, it is not some stale data, so it does connect to port 6000, and it does connect to the db socket it just thinks for some unknown reason that it is not working and it does the connection time out thing.
But I guess I will just wait it out, maybe it just starts working again with the next update. I might play around with one of the relays, and try to reset everything from scratch… But this was all working perfectly fine before the 1.33 update…
if it’s working then is fine, perhaps there are few issues with the glive… did u increased (with the mouse) the glive windows?
Yup, running full screen, no change. Looks like some bug, probably has to do something with my environment if nobody else has this problem. But this is a difficult one to debug…
- do u still have the old binaries file?
- can u type
nano envand share the first 10 lines?
Still have them yes.
env file:
#CNODEBIN="${HOME}/.cabal/bin/cardano-node" # Override automatic detection of cardano-node executable
#CCLI="${HOME}/.cabal/bin/cardano-cli" # Override automatic detection of cardano-cli executable
#CNCLI="${HOME}/.cargo/bin/cncli" # Override automatic detection of executable (https://github.com/AndrewWestberg/cncli)
#CNODE_HOME="/opt/cardano/cnode" # Override default CNODE_HOME path (defaults to /opt/cardano/cnode)
CNODE_PORT=6000 # Set node port
CONFIG="${NODE_HOME}/mainnet-config.json" # Override automatic detection of node config path
#SOCKET="${NODE_HOME}/db/socket" # Override automatic detection of path to socket
#TOPOLOGY="${CNODE_HOME}/files/topology.json" # Override default topology.json path
#LOG_DIR="${CNODE_HOME}/logs" # Folder where your logs will be sent to (must pre-exist)
#DB_DIR="${CNODE_HOME}/db" # Folder to store the cardano-node blockchain db
#UPDATE_CHECK="Y" # Check for updates to scripts, it will still be prompted before proceeding (Y|N).
#TMP_DIR="/tmp/cnode" # Folder to hold temporary files in the various scripts, each script might create additional subfolders
#USE_EKG="Y" # Use EKG metrics from the node instead of Prometheus. Prometheus metrics yield slightly better performance but can $
#EKG_HOST=127.0.0.1 # Set node EKG host IP
I have the same issue. I have been working on this error for about a week now. My relay node is up and running, I can query tip ok, and cntools is ok, but gLiveView always gives me the same error. I just found this response and decided to give the up arrow a try, like you suggested, and it f@#king worked ! 
Thank you Krilson!
The up arrow does load the visuals of gLiveView, but it’s not functioning. I cannot acess peers with p or quit with q. it’s interesting buggy behavior, but did not solve my gLiveView issues. 
Glad I made your day
I still have not found a solution though. Even with the latest update of gLiveview to 1.26, still the same behaviour…
I am experiencing the same issue as you (pressing up allows me to see the liveview until it runs out of tries. A quick work around is to modify the script at line 649:
Comment out: #if [[ ${nodeStartTime} -le 0 ]]; then
Add in: if false; then
This worked for me!
1 Like
Same problem after the update to cardano node 1.34.0 and Guild Live View 1.26.0.
But the mentioned workaround from a_purple_llama fixed the problem. 
1 Like