<p>The disconnect came from gLiveView reporting the version number of the cardano-node that it found, not the one that's actually running.</p>
<p>Here's a more complete answer:
<a href="https://forum.cardano.org/t/1-35-3-stuck-in-epoch-364/108111/22" rel="nofollow noreferrer">https://forum.cardano.org/t/1-35-3-stuck-in-epoch-364/108111/22</a></p>

CC BY-SA 4.0
2022-09-26T21:38:05.980Z
2022-09-26T21:38:05.980Z
Matthias Sieber
<p>I think what I am about to say is correct but check it out. If you are talking about a mainnet pool you are running the wrong node version. The correct git rev for mainnet is 950c4e222086fed5ca53564e642434ce9307b0b9. The node version you are running is for the test environments.</p>
<p>To get up and running quickly, when you're on the correct node version you could download a db snapshot from here:</p>
<p><a href="https://csnapshots.io/" rel="nofollow noreferrer">https://csnapshots.io/</a></p>

CC BY-SA 4.0
2022-09-25T12:04:22.533Z
2022-09-25T12:04:22.533Z
OYSTR Pool
<p>For those getting stuck with updating fully to 1.35.x.
This guide assumes that your user directory is named <code>cardano</code>, your git directory is in <code>cardano/git</code>, your working directory is in $NODE_HOME, and your systemd service is <code>cardano-node</code>.</p>
<p>Check your installed cardano-node version</p>
<p><code>cardano-node --version</code></p>
<p>now compare if it is the same as being executed by systemd</p>
<pre><code>which cardano-node  
/home/cardano/.local/bin/cardano-node --version
</code></pre>
<p>Assuming you're not sure where your 1.35.x file is located you are finding it by running:</p>
<p><code>find ~/ -name cardano-node</code></p>
<p>This list will also list directories with the name cardano-node.</p>
<p>Look for a path similar to this, where [YOUR_GIT] is the cloned repository.</p>
<p><code>/home/cardano/git/dist-newstyle/build/x86_64-linux/ghc-8.10.7/cardano-node-1.35.3/x/cardano-node/build/cardano-node/cardano-node </code></p>
<p>Now test this node's version</p>
<p><code>/home/cardano/git/dist-newstyle/build/x86_64-linux/ghc-8.10.7/cardano-node-1.35.3/x/cardano-node/build/cardano-node/cardano-node --version</code></p>
<p>Copy this cardano-node if the version is 1.35.x</p>
<p><code> cp /home/cardano/git/cardano-node/dist-newstyle/build/x86_64-linux/ghc-8.10.7/cardano-node-1.35.3/x/cardano-node/build/cardano-node/cardano-node /home/cardano/.local/bin/cardano-node</code></p>
<p>and</p>
<p><code> cp /home/cardano/git/cardano-node/dist-newstyle/build/x86_64-linux/ghc-8.10.7/cardano-node-1.35.3/x/cardano-node/build/cardano-node/cardano-node /usr/local/bin/cardano-node</code></p>
<p>Limit the permissions</p>
<p><code>sudo chmod 644 /etc/systemd/system/cardano-node.service</code></p>
<p>Check version</p>
<p><code>/home/cardano/.local/bin/cardano-node --version</code>
<code>/usr/local/bin/cardano-node --version</code></p>
<p>Reboot <code>sudo reboot</code></p>
<p>or reload the daemon</p>
<pre><code>sudo systemctl daemon-reload
sudo systemctl enable cardano-node.service
</code></pre>
<p>If it doesn't run now.</p>
<p>Stop the cardano-node.</p>
<p><code>sudo system stop cardano-node</code></p>
<p>Backup your old database.</p>
<p><code>mv db db_bak</code></p>
<p>Download your snapshot from <a href="https://csnapshots.io/mainnet" rel="nofollow noreferrer">cSnapshots.io</a> and reboot.</p>
<p><code>sudo curl -o - https://downloads.csnapshots.io/mainnet/$(curl -s https://downloads.csnapshots.io/mainnet/mainnet-db-snapshot.json| jq -r .[].file_name ) | lz4 -c -d - | tar -x -C $NODE_HOME; sudo reboot</code></p>
<p>Your node should now hopefully be running again and you can delete the backup with</p>
<p><code>rm -r $NODE_HOME/db_bak</code></p>

CC BY-SA 4.0
2022-09-27T02:18:38.067Z
2022-09-27T02:18:38.067Z
larissamarcus
<p>I moved our stake pool LOXE to 1.35.3 (git rev 80b5637a5520648d50b0763d7677ddbe374cd598) on August 20th and it was producing blocks regularly. I noticed yesterday that our block producer was up as a slot leader, but the block was not adopted by the chain. Only later did I realize that our pool was stuck in Alonzo at the last block of epoch 364 (7791698).</p>
<p>I stopped the nodes and deleted some recent files from the db, fo force replaying of blocks on restart with no difference.</p>
<p>I complied cardano-node and cardano-cli - this time from commit ea6d78c7 - transferred the binaries and configs to my nodes and compiled the libsodium on the nodes as well. I changed the topology on the relays to just connect to the IOHK servers for the moment to try and just sync up, but I’m still getting nowhere with it.</p>
<p>Attached is a view from my journalctl from the relay in question.
<a href="https://i.sstatic.net/nPbhY.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/nPbhY.png" alt="journalctl for cardano-node" /></a></p>
<p><strong>UPDATE: Fixed!</strong></p>
<p>Will compose and link a write-up</p>

CC BY-SA 4.0
2022-09-25T04:22:41.150Z
You say you upgraded the block producer machine, but did you also upgrade the relays? They must all be upgraded. Also, you should use the git tag rather than just using a particular commit near the tag.
Erik de Castro Lopo
CC BY-SA 4.0
2022-09-25T05:21:35.217Z
I upgraded all nodes.
Matthias Sieber
CC BY-SA 4.0
2022-09-25T13:50:48.780Z
To be of help I would need a bit more info.
Are you running in P2P mode, how many incoming/outgoing connections for your block producer and relays?
Was the block you were leader for accepted in gLiveView but not by other pools?
ADA Capital - ADACT
CC BY-SA 4.0
2022-09-25T16:28:14.017Z
Connections between BP and relays were stable. Connections to other nodes are impermanent and break soon after they were registered in gLiveView. I don't have any indication that the block was accepted by other pools as the tip is on the las slot in epoch 364.
Matthias Sieber
<cardano-node><stake-pool><syncing><vasil-hard-fork>
1.35.3 not syncing since epoch 365
# 1.35.3 not syncing since epoch 365

(Asked by: username_0 on 2022-09-25)

I moved our stake pool LOXE to 1.35.3 (git rev 80b5637a5520648d50b0763d7677ddbe374cd598) on August 20th and it was producing blocks regularly. I noticed yesterday that our block producer was up as a slot leader, but the block was not adopted by the chain. Only later did I realize that our pool was stuck in Alonzo at the last block of epoch 364 (7791698).

I stopped the nodes and deleted some recent files from the db, fo force replaying of blocks on restart with no difference.

I complied cardano-node and cardano-cli - this time from commit ea6d78c7 - transferred the binaries and configs to my nodes and compiled the libsodium on the nodes as well. I changed the topology on the relays to just connect to the IOHK servers for the moment to try and just sync up, but I’m still getting nowhere with it.

Attached is a view from my journalctl from the relay in question.
[![journalctl for cardano-node](https://i.sstatic.net/nPbhY.png)](https://i.sstatic.net/nPbhY.png)

**UPDATE: Fixed!**

Will compose and link a write-up

**Tags:** cardano-node, stake-pool, syncing, vasil-hard-fork
> **Comments:**
> **username_1**: You say you upgraded the block producer machine, but did you also upgrade the relays? They must all be upgraded. Also, you should use the git tag rather than just using a particular commit near the tag.  
> **username_0**: I upgraded all nodes.  
> **username_2**: To be of help I would need a bit more info. Are you running in P2P mode, how many incoming/outgoing connections for your block producer and relays? Was the block you were leader for accepted in gLiveView but not by other pools?  
> **username_0**: Connections between BP and relays were stable. Connections to other nodes are impermanent and break soon after they were registered in gLiveView. I don't have any indication that the block was accepted by other pools as the tip is on the las slot in epoch 364.  

---

## 3 answers

### Answer by username_0 on 2022-09-26. Score: 1 | Accepted answer

The disconnect came from gLiveView reporting the version number of the cardano-node that it found, not the one that's actually running.

Here's a more complete answer:
<https://forum.cardano.org/t/1-35-3-stuck-in-epoch-364/108111/22>


---

### Answer by username_3 on 2022-09-25. Score: 0

I think what I am about to say is correct but check it out. If you are talking about a mainnet pool you are running the wrong node version. The correct git rev for mainnet is 950c4e222086fed5ca53564e642434ce9307b0b9. The node version you are running is for the test environments.

To get up and running quickly, when you're on the correct node version you could download a db snapshot from here:

<https://csnapshots.io/>


---

### Answer by username_4 on 2022-09-27. Score: 0

For those getting stuck with updating fully to 1.35.x.
This guide assumes that your user directory is named cardano, your git directory is in cardano/git, your working directory is in $NODE_HOME, and your systemd service is cardano-node.
Check your installed cardano-node version
cardano-node --version
now compare if it is the same as being executed by systemd
which cardano-node  
/home/cardano/.local/bin/cardano-node --version

Assuming you're not sure where your 1.35.x file is located you are finding it by running:
find ~/ -name cardano-node
This list will also list directories with the name cardano-node.
Look for a path similar to this, where [YOUR_GIT] is the cloned repository.
/home/cardano/git/dist-newstyle/build/x86_64-linux/ghc-8.10.7/cardano-node-1.35.3/x/cardano-node/build/cardano-node/cardano-node 
Now test this node's version
/home/cardano/git/dist-newstyle/build/x86_64-linux/ghc-8.10.7/cardano-node-1.35.3/x/cardano-node/build/cardano-node/cardano-node --version
Copy this cardano-node if the version is 1.35.x
 cp /home/cardano/git/cardano-node/dist-newstyle/build/x86_64-linux/ghc-8.10.7/cardano-node-1.35.3/x/cardano-node/build/cardano-node/cardano-node /home/cardano/.local/bin/cardano-node
and
 cp /home/cardano/git/cardano-node/dist-newstyle/build/x86_64-linux/ghc-8.10.7/cardano-node-1.35.3/x/cardano-node/build/cardano-node/cardano-node /usr/local/bin/cardano-node
Limit the permissions
sudo chmod 644 /etc/systemd/system/cardano-node.service
Check version
/home/cardano/.local/bin/cardano-node --version
/usr/local/bin/cardano-node --version
Reboot sudo reboot
or reload the daemon
sudo systemctl daemon-reload
sudo systemctl enable cardano-node.service

If it doesn't run now.
Stop the cardano-node.
sudo system stop cardano-node
Backup your old database.
mv db db_bak
Download your snapshot from cSnapshots.io and reboot.
sudo curl -o - https://downloads.csnapshots.io/mainnet/$(curl -s https://downloads.csnapshots.io/mainnet/mainnet-db-snapshot.json| jq -r .[].file_name ) | lz4 -c -d - | tar -x -C $NODE_HOME; sudo reboot
Your node should now hopefully be running again and you can delete the backup with
rm -r $NODE_HOME/db_bak


---

