WebDev | Stake.Works
WebDev | Stake.Works
Collator: bifrost 0.9.43-b767dc6-x86_64-linux-gnu Ubuntu 20.04 LTS VPS 8 core, RAM 30GB, 400 GB NVMe disk ``` Jun 03 09:22:48 mn12 bifrost[2386398]: 2022-06-03 09:22:48 [Parachain🌈] Starting collation. relay_parent=0xba63063d76632501e224647ea6f1b3ba1883dd9c25c3620b853522984a921506 at=0xc16516512a5ecb64c27afe2c4e9dd49348bdce75dcddb8fab5eac7a53fb738fb Jun 03...
AMD Ryzen 9 5950X 128 GB RAM Ubuntu 22.04 LTS Bitsongd 0.11.0 I came accross these marshaling errors in the bitsongd log: 7:53PM INF acknowledgement written dst_channel=channel-0 dst_port=transfer module=x/ibc/channel sequence="marshaling...
I'm getting these alerts on both Darwinia & Crab nodes: - alertname = UnboundedChannelPersistentlyLarge - chain = crab2 - entity = mpsc_import_notification_stream - instance = localhost:19615 - job = crab-collator...
**bifrost-v0.9.88** 
Thread 'tokio-runtime-worker' panicked at 'header is last in set and contains standard change signal
Collator crashed with this error: ``` 2023-03-24 14:30:17 [Relaychain] Idle (40 peers), best: #17179110 (0xd99d8ab6), finalized #17179107 (0x27714209), 797.1kiB/s 762.0kiB/s 2023-03-24 14:30:18 [Relaychain] Imported #17179111 (0xd4363021) 2023-03-24 14:30:18 Off-chain worker...
Binary: bifrost 0.9.96-f707a9199b8, also in v0.9.98 Ubuntu: 22.04  ExecStart=/bifrost \ --collator \ --base-path /PATH/ \ --name 'StakeWorks | Bifrost | HDS05' \ --chain bifrost-kusama.json \ --trie-cache-size=134217728 \ --max-runtime-instances 32...
Mangata backup node crashed with this error, also happened with Bifrost and Litentry node: ``` Version: 0.1.0-unknown 0: sp_panic_handler::set::{{closure}} 1: ::call at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/alloc/src/boxed.rs:2032:9 std::panicking::rust_panic_with_hook at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/std/src/panicking.rs:692:13 2: std::panicking::begin_panic_handler::{{closure}} at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/std/src/panicking.rs:579:13...
After upgrade to v1.7.0 these errors showed up: 2024-05-09 18:38:19 [Parachain] Evicting failed runtime instance error=Runtime panicked: Slot must increase 2024-05-09 18:38:19 [Parachain] err=Error { inner: Proposing 0: Error at...
Peers get disconnected continously, also in previously version of tinkernet-collator. Collator  Backup node   Only by using reserved-nodes can we maintain synchronization. Ubuntu 22.04 LTS tinkernet-collator 1.6.2-906e59161d7 ExecStart=tinkernet-collator...
Version release v1.7.0-tinkernet -> tinkernet-collator 1.6.2-906e59161d7