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

Transactions failed after upgrading to v2.49.0 #2220

Open
wensheng opened this issue Feb 10, 2025 · 4 comments
Open

Transactions failed after upgrading to v2.49.0 #2220

wensheng opened this issue Feb 10, 2025 · 4 comments
Assignees

Comments

@wensheng
Copy link

Problem

After upgrading to v2.49.0, all transactions fail! The failure is 'INVALID_SIGNATURE'.

I tried both testnet and previewnet.

I have valid .env in examples/ folder.

Here's the example of CreateAccount:

Create Account Example Start!
Future account private key: 302e0201003[redacted]c285b5030a215719ccd36cf2f976
Future account public key: 302[redacted]8cb0798e2597c8127929
Creating new account...
[main] WARN com.hedera.hashgraph.sdk.logger.Logger - Retrying in 250 ms after failure with node 0.0.34 during attempt #1: BUSY
Exception in thread "main" com.hedera.hashgraph.sdk.PrecheckStatusException: Hedera transaction `[email protected]` failed pre-check with the status `INVALID_SIGNATURE`
        at com.hedera.hashgraph.sdk.Executable$GrpcRequest.mapStatusException(Executable.java:962)
        at com.hedera.hashgraph.sdk.Executable.execute(Executable.java:449)
        at com.hedera.hashgraph.sdk.Transaction.execute(Transaction.java:35)
        at com.hedera.hashgraph.sdk.Executable.execute(Executable.java:353)
        at com.hedera.hashgraph.sdk.Transaction.execute(Transaction.java:35)
        at com.hedera.hashgraph.sdk.examples.CreateAccountExample.main(CreateAccountExample.java:79)

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':examples:runCreateAccount'.
> Process 'command '/usr/lib/jvm/java-17-openjdk-amd64/bin/java'' finished with non-zero exit value 1

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.

BUILD FAILED in 3s

v2.48.0 is the same.

After reverting back to v2.47.0, everthing works again:

$ git checkout v2.47.0
Previous HEAD position was 0132d0b5b release: v2.49.0 (#2215)
HEAD is now at bf896f897 release: v2.47.0 (#2211)
$ ./gradlew -q :examples:runCreateAccount                                                    [v2.47.0]  [12:02:51]
Create Account Example Start!
Future account private key: 302e02010[redacted]2c687ffb6d79f03530d73b7ba630
Future account public key: 302a30[redacted]b77727d4817953ae
Creating new account...
[main] WARN com.hedera.hashgraph.sdk.logger.Logger - Retrying in 250 ms after failure with node 0.0.3 during attempt #1: OK
[main] WARN com.hedera.hashgraph.sdk.logger.Logger - Retrying in 500 ms after failure with node 0.0.3 during attempt #2: OK
Created account with ID: 0.0.5492457
[main] WARN com.hedera.hashgraph.sdk.logger.Logger - Retrying in 250 ms after failure with node 0.0.7 during attempt #1: OK
[main] WARN com.hedera.hashgraph.sdk.logger.Logger - Retrying in 500 ms after failure with node 0.0.7 during attempt #2: OK
Create Account Example Complete!
@0xivanov
Copy link
Contributor

Might be caused by #2190 , strangely it works on local node.
I will investigate.

@0xivanov
Copy link
Contributor

Actually, it turns out the address books were generated incorrectly.

@0xivanov
Copy link
Contributor

The testnet.pb and previewnet.pb files got corrupted and are with the same data. Mainnet should work though.

@0xivanov
Copy link
Contributor

0xivanov commented Feb 10, 2025

We migrated the address books update script a couple weeks ago from a python script to gradle script. It turns out gradle is running the 3 network updates in parallel, which causes race conditions in the common file address-book.proto.bin.

I've added additional options to make the tasks run one after the other.

@0xivanov 0xivanov self-assigned this Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants