Does this look normal?

Yes, it’s going to take a while.
yah, iam having issues after upgrade…seems like relays are not connecting any more.
journal follow shows: leadership checks…slot 97180410, it seems to be attempting to sync but its been 8 hrs… showing zero incoming and outgoing.
did full csnapshot download last night…so i was hoping it would be quick…something weird going on, cant figure out.
BP zero outing/incoming (8.1.1 not synced yet)
R1 no incoming/ 16 outgoing. (synced. 8.1.1)
help!
![]()
What does your topology.json file look like?
something like this?
{
"Producers": [
{
"addr": "<BlockProducingNodeIPAddress>",
"port": 6000,
"valency": 1
},
{
"addr": "relays-new.cardano-mainnet.iohk.io",
"port": 3001,
"valency": 2
}
]
}
is that for BP?
my BP looks like this, (2 Relays)
{
"Producers": [
{
"addr": "xxxx",
"port": 6000,
"valency": 1
},
{
"addr": "xxxx",
"port": 6000,
"valency": 1
}
]
}
iam getting a
x,x.x.x.x:x000] Skipping peer x:6000
[b:cardano.node.IpSubscription:Error:227]
Check the relay Topology. Make sure it looks like this:
{
“Producers”: [
{
“addr”: “”,
“port”: 6000,
“valency”: 1
},
{
“addr”: “[relays-new.cardano-mainnet.iohk.io](http://relays-new.cardano-mainnet.iohk.io/)”,
“port”: 3001,
“valency”: 2
}
]
}
Then restart the node: using
cd $CNODE_HOME/scripts
sudo systemctl restart cnode
sudo systemctl status cnode
./gLiveView,.sh
I first got the relay going. Then I synced the BP afterwards. (after the relay was going)
thanks for info!
topos looks fine… both relays synced and on 8.1.1 wierd.
both relays see each other in gLiveView…just no BP on 6000.
![]()
is your BP showing as “core” on gLive?
are you starting the BP with:
./deploy-as-systemd.sh
yes sir
just no peers.
this was set up and working great until
i updated libsodium and cardano node.
versions look correct, including cabal and ghc
dbl checked config.json. mem=true…thats fine as well. topos look good. connection looks good. can ping both relays internally no prob.
finally synced…once it got to the Forge and Leadership checks it took an hour, once gLive rendered…out and an in peers populated.
thanks guys!
what is the diference between using
systemctl restart cnode
(which i historically have used–taking 20min)
vs
./deploy-as-systemd.sh
(took 8 hrs...so i exited)
thoughts?
Hey guys, can anyone help me?
I have updated my 2 relays to version 8.1.2 and they are working correctly, synced.
Now I went to update my Core (BP) but it wasn’t able to start, it only had the Starting status, and the Incoming and Outgoing values were zero.
I was checking some things and found that my core server version of Cabal was out of date. Even after I update cabal to version 3.10.1.0 my node still doesn’t boot.
I already checked the topologyUpdater files of the relays, and I already checked the topology file of the core (BP)
NOTE: Yesterday, as soon as I updated the Core server, it had the Incoming value equal to 1, but not for a long time, and then it was reset to zero.


Check your logs from your bp
tail -10f …/logs/node0.json
I can’t interpret the log. Copy the last lines to see if anyone can help…
{“app”:,“at”:“2023-08-18T21:15:59.00Z”,“data”:{“chainDensity”:7.272727e-2,“credentials”:“Cardano”,“delegMapSize”:1296767,“kind”:“TraceStartLeadershipCheck”,“slot”:100827068,“utxoSize”:10323359},“env”:“8.1.2:d2d90”,“host”:“vmi69559”,“loc”:null,“msg”:“”,“ns”:[“cardano.node.LeadershipCheck”],“pid”:“7526”,“sev”:“Info”,“thread”:“388”}
{“app”:,“at”:“2023-08-18T21:15:59.05Z”,“data”:{“credentials”:“Cardano”,“val”:{“kind”:“TraceNodeNotLeader”,“slot”:100827068}},“env”:“8.1.2:d2d90”,“host”:“vmi69559”,“loc”:null,“msg”:“”,“ns”:[“cardano.node.Forge”],“pid”:“7526”,“sev”:“Info”,“thread”:“388”}
{“app”:,“at”:“2023-08-18T21:16:00.00Z”,“data”:{“chainDensity”:7.272727e-2,“credentials”:“Cardano”,“delegMapSize”:1296767,“kind”:“TraceStartLeadershipCheck”,“slot”:100827069,“utxoSize”:10323359},“env”:“8.1.2:d2d90”,“host”:“vmi69559”,“loc”:null,“msg”:“”,“ns”:[“cardano.node.LeadershipCheck”],“pid”:“7526”,“sev”:“Info”,“thread”:“388”}
{“app”:,“at”:“2023-08-18T21:16:00.04Z”,“data”:{“credentials”:“Cardano”,“val”:{“kind”:“TraceNodeNotLeader”,“slot”:100827069}},“env”:“8.1.2:d2d90”,“host”:“vmi69559”,“loc”:null,“msg”:“”,“ns”:[“cardano.node.Forge”],“pid”:“7526”,“sev”:“Info”,“thread”:“388”}
{“app”:,“at”:“2023-08-18T21:16:01.00Z”,“data”:{“chainDensity”:7.272727e-2,“credentials”:“Cardano”,“delegMapSize”:1296767,“kind”:“TraceStartLeadershipCheck”,“slot”:100827070,“utxoSize”:10323359},“env”:“8.1.2:d2d90”,“host”:“vmi69559”,“loc”:null,“msg”:“”,“ns”:[“cardano.node.LeadershipCheck”],“pid”:“7526”,“sev”:“Info”,“thread”:“388”}
{“app”:,“at”:“2023-08-18T21:16:01.04Z”,“data”:{“credentials”:“Cardano”,“val”:{“kind”:“TraceNodeNotLeader”,“slot”:100827070}},“env”:“8.1.2:d2d90”,“host”:“vmi69559”,“loc”:null,“msg”:“”,“ns”:[“cardano.node.Forge”],“pid”:“7526”,“sev”:“Info”,“thread”:“388”}
I don’t think there is any problems with those logs you supplied. They just look like normal logs to me. Your BP node is running and doing leadership checks every second (ie. each slot).
By the way, your installed version of cabal doesn’t matter when running cardano-node. Cabal is only used when compiling the Haskell software. Once compiled, you don’t even need cabal installed on your system. For example, I compile my cardano-node software on a separate build machine and make it into a debian package. I then install this debian package on each of my relays and my BP. None of my relays or BP have ghc, or cabal, or the rest of the build chain and development libraries, even on them.
I would argue this is better from a security point of view because sometimes an attacker can leverage using various components of software on your system to escalate his ability. Having all these compilers, development libraries, and other extra installed software, on your running machines just provides an attacker with more tools at his disposal.
Thank you very much for your feedback, I’ll wait a few more hours then. I was finding it strange, because every time I updated my BP, it quickly synchronized the node, and this time, even though I had downloaded the updated Database, the node did not start.
Interesting the way you create the installation package for your servers, I’ll study it for the next few times, certainly the less we have installed on the server, the better from a security point of view.