Does anyone know more regarding the recent network outage where half of the nodes went offline that was big on the news?
I haven’t really read a satisfactory answer yet in the news of what rally happened. Perhaps some of you had an experience of it who would like to share.
What triggered it? Will it happen again?
1 Like
hi,
there is a case opened on github
opened 12:36AM - 22 Jan 23 UTC
type: bug
**External**
*External*
**Area**
cardano-node exception leading to shutdown…
**Summary**
All my public nodes with incoming connections (active block producer and relays) shut down unexpectedly on 2022 January 22 at 00:09:01 UTC following the following fatal exception:
```
janv. 22 01:09:01 de cardano-node-1.35.4[24590]: {"app":[],"at":"2023-01-22T00:09:01.24Z","data":{"immtip":{"headerHash":"fae2d44113d1fb8b99171cc64983ff5dfb92f1d360f2460e6>
janv. 22 01:09:01 de cardano-node-1.35.4[24590]: cardano-node-1.35.4: ExceptionInLinkedThread "ThreadId 165" Failure in Data.Map.balanceR
janv. 22 01:09:01 de cardano-node-1.35.4[24590]: CallStack (from HasCallStack):
janv. 22 01:09:01 de cardano-node-1.35.4[24590]: error, called at src/Data/Map/Internal.hs:4157:30 in containers-0.6.5.1-EiES0HFUZ8PBGNrpVjoYRF:Data.Map.Internal
```
(time in UTC+1 above)
Some other operators confirmed this also happened to some of their nodes.
**Steps to reproduce**
No idea yet.
**Expected behavior**
No exception is expected in `cardano-node`.
**System info (please complete the following information):**
- OS Name: Ubuntu
- OS Version 20.04
- Node version
```
cardano-node 1.35.4 - linux-x86_64 - ghc-8.10
git rev ebc7be471b30e5931b35f9bbc236d21c375b91bb
```
- CLI version
```
cardano-cli 1.35.4 - linux-x86_64 - ghc-8.10
git rev ebc7be471b30e5931b35f9bbc236d21c375b91bb
```
**Screenshots and attachments**
Previous logs (UTC+1):
```
janv. 22 01:09:01 de cardano-node-1.35.4[24590]: {"app":[],"at":"2023-01-22T00:09:01.22Z","data":{"block":"77e81e9305859032fea6a8e79f5936e96723a1620608d2bd0100c2421f5ef667@82779850","kind":"TraceAddBlockEvent.AddBlockValidation.ValidCandidate"},"env":"1.35.4:ebc7b","host":"de","loc":null,"msg":"","ns":["cardano.node.ChainDB"],"pid":"24590","sev":"Info","thread":"157"}
janv. 22 01:09:01 de cardano-node-1.35.4[24590]: {"app":[],"at":"2023-01-22T00:09:01.22Z","data":{"chainLengthDelta":1,"kind":"TraceAddBlockEvent.AddedToCurrentChain","newtip":"77e81e9305859032fea6a8e79f5936e96723a1620608d2bd0100c2421f5ef667@82779850"},"env":"1.35.4:ebc7b","host":"de","loc":null,"msg":"","ns":["cardano.node.ChainDB"],"pid":"24590","sev":"Notice","thread":"157"}
janv. 22 01:09:01 de cardano-node-1.35.4[24590]: Shutting down..
```
**Additional context**
All my nodes without incoming connections (just outgoing ones) were not affected.
Thank you,
3 Likes
That is a really helpful lead thanks.
1 Like
Charles talked about this event in this recent YouTube video: Cardano Stall - YouTube
1 Like
maliky
3 February 2023 21:23
6
The term “Transient Anomaly” is not very explicit. :o)
There are some speculations in the internet that this might’ve been a malicious attack on the network. Does anyone have any lead if it is indeed the case?
maliky
6 February 2023 15:01
8
One needs to go on the github link referenced by @Alexd1985 to see that it was not an attack. Full report will come out in a few weeks when more nodes will have updated there software to correct this “Transient Anomaly”
