Reporting as directed in the moonbeam logs... about moonbeam

[perltk45]

Ubuntu 18.04 LTS, Name -a = "Linux localhost 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux” Running from systemd: [Unit] Description="Moonbase Alpha systemd service" After=network.target StartLimitIntervalSec=0 [Service] Type=simple Restart=on-failure RestartSec=10 User=moonbase_service SyslogIdentifier=moonbase SyslogFacility=local7 KillSignal=SIGHUP ExecStart=/var/lib/alphanet-data/moonbeam \ --parachain-id 1000 \ --port 30333 \ --rpc-port 9933 \ --ws-port 9944 \ --pruning=archive \ --execution=Native \ --state-cache-size 1 \ --unsafe-rpc-external \ --unsafe-ws-external \ --rpc-methods=Safe \ --rpc-cors all \ --log rpc=info \ --base-path /var/lib/alphanet-data \ --chain alphanet \ --name "Premagine" \ --in-peers 200 \ --out-peers 200 \ -- \ --port 30334 \ --rpc-port 9934 \ --ws-port 9945 \ --pruning=archive \ --name="Premagine (Embedded Relay)" [Install] WantedBy=multi-user.target Built with cargo "cargo 1.52.0 (69767412a 2021-04-21)" If you need anything, just ask. —Daniel

…

On May 17, 2021, at 7:36 AM, Joshy Orndorff ***@***.***> wrote: @perltk45 <https://github.com/perltk45> Thanks for reporting. I see you were using Moonbeam Version: 0.7.0-ab035b2-x86_64-linux-gnu and you node paniced with Digest item must match that calculated. It looked like this happened while you were syncing Moonbase Alpha, right? Could you share what command you used to run the node, and what OS you are using? Any other info that may help us? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#416 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETU54QSOUVMAEUKF25XVYDTOESWJANCNFSM4464ZCQQ>.

[JoshOrndorff]

@perltk45 Thanks for reporting. I see you were using Moonbeam Version: 0.7.0-ab035b2-x86_64-linux-gnu and you node paniced with Digest item must match that calculated.

It looked like this happened while you were syncing Moonbase Alpha, right? Could you share what command you used to run the node, and what OS you are using? Any other info that may help us?

[perltk45]

Josh, it occurs to me that the preceding lines might be useful for context of this error.
Here's another example leading into the same panic error:

May 19 18:36:10 moonbeam moonbase[1686]: 2021-05-19 18:36:10 [Relaychain] 💤 Idle (10 peers), best: #676544 (0x9bbd…96d3), finalized #676541 (0xdd37…9739), ⬇ 83.8kiB/s ⬆ 36.1kiB/s
May 19 18:36:10 moonbeam moonbase[1686]: 2021-05-19 18:36:10 ⚙️ Syncing 26.6 bps, target=#335247 (131 peers), best: #325794 (0xd68b…1dd0), finalized #284999 (0x7ea2…4e85), ⬇ 69.9kiB/s ⬆ 3.1MiB/s
May 19 18:36:10 moonbeam moonbase[1686]: DigestItem: given=DigestItem::Consensus([102, 114, 111, 110], [1, 237, 217, 40, 206, 98, 4, 4, 215, 1, 94, 95, 180, 220, 159, 149, 187, 101, 242, 213, 152, 161, 31, 179, 73, 115, 136, 158, 135, 111, 94, 223, 49, 0]), expected=DigestItem::Consensus([102, 114, 111, 110], [1, 187, 129, 153, 214, 0, 204, 112, 16, 186, 117, 213, 29, 187, 102, 4, 238, 56, 190, 64, 199, 50, 206, 126, 11, 110, 78, 123, 127, 127, 13, 25, 12, 0])
May 19 18:36:10 moonbeam moonbase[1686]: ====================
May 19 18:36:10 moonbeam moonbase[1686]: Version: 0.7.0-ab035b2-x86_64-linux-gnu
May 19 18:36:10 moonbeam moonbase[1686]: 0: sp_panic_handler::set::{{closure}}

Thanks!

[perltk45]

fwiw -- I pulled down the latest and recompiled -- problem went away.