Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Panics with Bad input data provided to validate_transaction: Codec error #5936

Open
AndreiEres opened this issue Oct 5, 2024 · 4 comments
Open
Assignees
Labels
I3-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue.

Comments

@AndreiEres
Copy link
Contributor

A Polkadot validator (1.16.0-87971b3e927) reported 439404 not continuous error messages between Sep 14 15:11:57 and Oct 04 23:56:26:

Bad input data provided to validate_transaction: Codec error 
2024-10-04 23:56:26 panicked at /build/relay/polkadot/src/lib.rs:2095:1:
More logs
Oct 04 23:56:36 polkadot polkadot[253731]: 2024-10-04 23:56:36 🏆 Imported #22825876 (0x5fae…0dcc → 0x41bb…a0de)
Oct 04 23:56:35 polkadot polkadot[253731]: 2024-10-04 23:56:35 💤 Idle (37 peers), best: #22825875 (0x5fae…0dcc), finalized #22825873 (0x79fd…0a05), ⬇ 1.3MiB/s ⬆ 489.3kiB/s
Oct 04 23:56:30 polkadot polkadot[253731]: 2024-10-04 23:56:30 🏆 Imported #22825875 (0xd911…f18c → 0x5fae…0dcc)
Oct 04 23:56:30 polkadot polkadot[253731]: 2024-10-04 23:56:30 💤 Idle (37 peers), best: #22825874 (0xd911…f18c), finalized #22825872 (0xf165…09b0), ⬇ 1.2MiB/s ⬆ 796.4kiB/s
Oct 04 23:56:28 polkadot polkadot[253731]: 2024-10-04 23:56:28 Report 12D3KooWGJijhP6pDMJGGAPfjWWKLi5mTqsisiSZFV5nPTHnW8d7: -2147483648 to -2147483648. Reason: Same block request multiple times. Banned, disconnect>
Oct 04 23:56:26 polkadot polkadot[253731]: Bad input data provided to validate_transaction: Codec error
Oct 04 23:56:26 polkadot polkadot[253731]: 2024-10-04 23:56:26 panicked at /build/relay/polkadot/src/lib.rs:2095:1:
Oct 04 23:56:36 polkadot polkadot[253731]: 2024-10-04 23:56:36 🏆 Imported #22825876 (0x5fae…0dcc → 0x41bb…a0de)
Oct 04 23:56:35 polkadot polkadot[253731]: 2024-10-04 23:56:35 💤 Idle (37 peers), best: #22825875 (0x5fae…0dcc), finalized #22825873 (0x79fd…0a05), ⬇ 1.3MiB/s ⬆ 489.3kiB/s
Oct 04 23:56:30 polkadot polkadot[253731]: 2024-10-04 23:56:30 🏆 Imported #22825875 (0xd911…f18c → 0x5fae…0dcc)
Oct 04 23:56:30 polkadot polkadot[253731]: 2024-10-04 23:56:30 💤 Idle (37 peers), best: #22825874 (0xd911…f18c), finalized #22825872 (0xf165…09b0), ⬇ 1.2MiB/s ⬆ 796.4kiB/s
Oct 04 23:56:28 polkadot polkadot[253731]: 2024-10-04 23:56:28 Report 12D3KooWGJijhP6pDMJGGAPfjWWKLi5mTqsisiSZFV5nPTHnW8d7: -2147483648 to -2147483648. Reason: Same block request multiple times. Banned, disconnect>
Oct 04 23:56:26 polkadot polkadot[253731]: Bad input data provided to validate_transaction: Codec error
Oct 04 23:56:26 polkadot polkadot[253731]: 2024-10-04 23:56:26 panicked at /build/relay/polkadot/src/lib.rs:2095:1:

It seems to be a known a harmless thing: paritytech/polkadot#7555 (comment)

Shouldn't we translate it into a warning to avoid scaring validators?

@AndreiEres AndreiEres added the I3-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue. label Oct 5, 2024
@ScepticMatt
Copy link

ScepticMatt commented Oct 17, 2024

We are getting a large number of these messages on an active validator on release stable2409

Oct 17 09:11:16 dot1 taskset[1376352]: Bad input data provided to validate_transaction: Codec error
Oct 17 09:11:16 dot1 taskset[1376352]: 2024-10-17 09:11:16 panicked at /build/relay/polkadot/src/lib.rs:2316:1:
Oct 17 09:11:24 dot1 systemd-journald[4038732]: [🡕] Suppressed 2038 messages from polkadot.service

@AndreiEres AndreiEres self-assigned this Oct 17, 2024
@dbpatty
Copy link

dbpatty commented Feb 17, 2025

Hi @AndreiEres, I am also getting a large number of these messages. May I do anything to avoid this error message? I updated my nodes to the latest release (2412-1).

@bkchr
Copy link
Member

bkchr commented Feb 17, 2025

This error is not problematic. It basically just means that someone send an invalid transaction.

@dbpatty
Copy link

dbpatty commented Feb 17, 2025

Ty, I read the replies on the chats, but I was wondering if this error continues to be not problematic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I3-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue.
Projects
None yet
Development

No branches or pull requests

4 participants