gLiveView Error after 1.34 upgrade

Hey there -

Upgraded one of my relays to 1.34 and unfortunately gLiveView isn’t loading. It immediately reports it can’t connect to a running node and then terminates as:

COULD NOT CONNECT TO A RUNNING INSTANCE, 3 FAILED ATTEMPTS IN A ROW!

cnode service is running according to systemctl…

1 Like

Downlod the newest script and try again

wget https://raw.githubusercontent.com/cardano-community/guild-operators/alpha/scripts/cnode-helper-scripts/gLiveView.sh

chmod 750 gLiveView.sh

Thanks Alex, unfortunately same result…

I have the same issue, wait 1 min to check something

Did u waited for the node to start? I believe it’s because the node socket file was deleted during the upgrade because the node was more minutes offline.

You mean leave it running for a while and try again? Or that I should stop/start the node again and wait for a longer period before starting gLiveView initially?

Is yours working?

Start glive and press enter after first error… you should see something… still checking the glive

I am seeing the same. Although my 1.34 node seems to have synced per grafana. maybe it is isolated to gliveview

I am also seeing the same with gLiveView

Yeah, and also no tx processed… it’s related with the new version of node…

anyway the node is running… it’s only an issue with the outputs

They did say that anyone with Windows should NOT install node 1.34.0. Maybe the issue is not localized to only Windows servers/OS?
Quote:
“To avoid increased synchronisation times, we recommended that Windows users DO NOT upgrade to node version 1.34.0. We recommend instead that they continue to run node 1.33.0. Future releases will address this issue which is specific to Windows.”

Source:

I don’t think…

We should wait for a new version (glive)… anyway the node is running… also the MEMPOOL CHANGED and tx processed are not shown anymore

1 Like

Agreed with @Alexd1985 - Even though gLiveView won’t start, I can confirm the node is running fine. I am able to mint NFTs on it, and the BP is showing it as alive.

2 Likes

Ok, i found a solution

l believe it’s line 649


 # Gather some data
getNodeMetrics
[[ ${RETRIES} -gt 0 && ${fail_count} -eq ${RETRIES} ]] && myExit 1 "${style_status$

comment this line and add if false; then like bellow


 #if [[ ${nodeStartTime} -le 0 ]]; then
  if false; then   
((fail_count++))

Save the file and next time press N for glive update

4 Likes

Seems to work for me!

It does, however, now report my node uptime being around 20k days. :muscle:

Thanks for the solution!

Yeah, strange uptime … but it’s fine till next version :slight_smile:

1 Like

This is my diff output from my running 1.26.0 version against the downloaded from your link

59c59
< GLV_VERSION=v1.26.2
---
> GLV_VERSION=v1.26.0
78c78
< SKIP_UPDATE=N
---
> SKIP_UPDATE=Y
132c132
<   checkUpdate "${PARENT}"/env N N N
---
>   checkUpdate env N N N
146c146
<   checkUpdate "${PARENT}"/gLiveView.sh "${ENV_UPDATED}"
---
>   checkUpdate gLiveView.sh "${ENV_UPDATED}"
649c649
<   if [[ ${uptimes} -le 5 ]]; then
---
>   if false; then

Thank you Alex that worked for me as well!

Should work now without modifications in 1.26.3!