ChainDB notice 442

English Community Technical Support
1

Hi guys,

I had a power outtage today and just restarted the nodes, my relay is having troubles and giving me the following errors, screenshot attached. Its saying something about chaindb and im assuming the socket file is corrupted?

My pool was selected to mint tmrw afternoon (13:00UTC) and dont have too much time to trouble shoot and if i have to re sync id like to do it asap

Thank you for your help, i really apprecitiate it

image
image1912×436 46.4 KB 

Copy/Paste of error: 
May 21 23:01:00 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Info:442] [2023-05-22 06:01:00.88 UTC] Valid candidate e767c6c6719e0d0547608644d744aeb877822ddd4a48387cbcd4e8df95a1f718 at slot 93168968
May 21 23:01:00 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Notice:442] [2023-05-22 06:01:00.88 UTC] Chain extended, new tip: e767c6c6719e0d0547608644d744aeb877822ddd4a48387cbcd4e8df95a1f718 at slot 93168968
May 21 23:01:03 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Notice:442] [2023-05-22 06:01:03.25 UTC] Chain extended, new tip: 1dbe561feeafdde1de392560137db75f9f85d574c8c2a9c7fce339a748e7f44d at slot 93168972
May 21 23:01:08 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Notice:442] [2023-05-22 06:01:08.56 UTC] Chain extended, new tip: b914d5de32808697345de705440851b8d85acda07db1f45e1623caf39293a065 at slot 93168977
May 21 23:01:21 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Info:442] [2023-05-22 06:01:21.80 UTC] Valid candidate 51efe4afbde68e3944ed4afbf87978672b3787e4e1655b08a8cd384570c1d7cc at slot 93168990
May 21 23:01:21 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Notice:442] [2023-05-22 06:01:21.80 UTC] Chain extended, new tip: 51efe4afbde68e3944ed4afbf87978672b3787e4e1655b08a8cd384570c1d7cc at slot 93168990
2

Please do not post screen shots, they are unreadable on some systems (lile mine).

Instead cut and paste the text.

1 Like
3

Error messages:

May 21 23:01:00 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Info:442] [2023-05-22 06:01:00.88 UTC] Valid candidate e767c6c6719e0d0547608644d744aeb877822ddd4a48387cbcd4e8df95a1f718 at slot 93168968
May 21 23:01:00 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Notice:442] [2023-05-22 06:01:00.88 UTC] Chain extended, new tip: e767c6c6719e0d0547608644d744aeb877822ddd4a48387cbcd4e8df95a1f718 at slot 93168968
May 21 23:01:03 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Notice:442] [2023-05-22 06:01:03.25 UTC] Chain extended, new tip: 1dbe561feeafdde1de392560137db75f9f85d574c8c2a9c7fce339a748e7f44d at slot 93168972
May 21 23:01:08 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Notice:442] [2023-05-22 06:01:08.56 UTC] Chain extended, new tip: b914d5de32808697345de705440851b8d85acda07db1f45e1623caf39293a065 at slot 93168977
May 21 23:01:21 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Info:442] [2023-05-22 06:01:21.80 UTC] Valid candidate 51efe4afbde68e3944ed4afbf87978672b3787e4e1655b08a8cd384570c1d7cc at slot 93168990
May 21 23:01:21 Tareqs-relay-node cardano-node[242944]: [Tareqs-r:cardano.node.ChainDB:Notice:442] [2023-05-22 06:01:21.80 UTC] Chain extended, new tip: 51efe4afbde68e3944ed4afbf87978672b3787e4e1655b08a8cd384570c1d7cc at slot 93168990

will update posts to include copy/pastes!

4

Much better. I can actually read that.

There are no errors in that, only log messages. Seems to be operating normally to me. Why do you think otherwise?

5

relay only has 1 incoming (BP) and 21 outgoing, updated the topology file after the crash.

Here is a cp/pst fo the glive for the relay (Note looks like the BP node is Propogating blocks and shows 1 incoming and outgoing, so that working): ┌────────────────────────────────┬────────────┬────────────────────────┐
│ Uptime: 02:10:06 │ Port: 6000 │ Guild LiveView v1.27.4 │
│--------------------------------└────────────┴────────────────────────┤
│ Epoch 413 [27.2%], 3d 15:17:37 remaining │
│ ▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖ │
│ │
│ Block : 8805005 Tip (ref) : 93170543 Forks : 7 │
│ Slot : 93170501 Tip (diff) : 42 :expressionless: Total Tx : 0 │
│ Slot epoch : 117701 Density : 5.139 Pending Tx : 0/0K │
│- CONNECTIONS --------------------------------------------------------│
│ P2P : disabled Incoming : 1 Outgoing : 23 │
│- BLOCK PROPAGATION --------------------------------------------------│
│ Last Delay : 7.39s Served : 422 Late (>5s) : 4 │
│ Within 1s : 86.47% Within 3s : 98.55% Within 5s : 99.03% │
│- NODE RESOURCE USAGE ------------------------------------------------│
│ CPU (sys) : 1.48% Mem (Live) : 3.6G GC Minor : 7761 │
│ Mem (RSS) : 11.1G Mem (Heap) : 11.0G GC Major : 27 │
└──────────────────────────────────────────────────────────────────────┘

6

I suspect that is a problem with the topology file, but I am only guessing.

7

Solved the issue, Port 6000 was removed from the forwarding list on my router setup. I could speak but not listen!

Thanks for your help @erikd :slight_smile:

1 Like