Truffle: Truffle cannot migration with the latest Geth 1.8

Created on 15 Dec 2017 · 53Comments · Source: trufflesuite/truffle

[x] I've asked for help in the Truffle Gitter before filing this issue.

Issue

When using the latest geth-unstable from the official debian ethereum repo (http://ppa.launchpad.net/ethereum/ethereum/ubuntu artful main), Truffle fails with even the most basic migrations.

It is worth noting that:

everything works fine with the geth package 1.7.3-stable.
you can observe the crash using the geth-unstable package 1.8.0-unstable.

Steps to Reproduce

Create the most simplistic project with only theMigration.sol contract and a migration to deploy it. Run truffle migrate --network geth, assuming that you configured a geth network somewhere in your truffle.js. Mine looks like so:

    geth: {
      host:       '127.0.0.1',
      port:       '7545',
      network_id: '1802',
      from:       '...'
    },

I'm using a set of scripts to get Geth to run correctly.

Expected Behavior

A successful migration with the last ID published.

Actual Results

Running migration: 20171201_010000_deploy_migrations.js
  Deploying Migrations...
  ... 0xc1dfca48204f704444a31539d83b53c1afc1baaf4e4f55352d31b8c406937178
  Migrations: 0x8cdaf0cd259887258bc13a92c0a6da92698644c0
Saving successful migration to network...
  ... 0x02b8ed4ab56dd0ae7656f99415f968fed333c20b22261193d18b5c07e2468b97
Error encountered, bailing. Network state unknown. Review successful transactions manually.
Error: unknown transaction
    at Object.InvalidResponse (/home/doodloo/.nvm/versions/node/v8.9.1/lib/node_modules/truffle/build/cli.bundled.js:41484:16)
    at /home/doodloo/.nvm/versions/node/v8.9.1/lib/node_modules/truffle/build/cli.bundled.js:328866:36
    at /home/doodloo/.nvm/versions/node/v8.9.1/lib/node_modules/truffle/build/cli.bundled.js:176178:11
    at /home/doodloo/.nvm/versions/node/v8.9.1/lib/node_modules/truffle/build/cli.bundled.js:324536:9
    at XMLHttpRequest.request.onreadystatechange (/home/doodloo/.nvm/versions/node/v8.9.1/lib/node_modules/truffle/build/cli.bundled.js:327565:7)
    at XMLHttpRequestEventTarget.dispatchEvent (/home/doodloo/.nvm/versions/node/v8.9.1/lib/node_modules/truffle/build/cli.bundled.js:176407:18)
    at XMLHttpRequest._setReadyState (/home/doodloo/.nvm/versions/node/v8.9.1/lib/node_modules/truffle/build/cli.bundled.js:176697:12)
    at XMLHttpRequest._onHttpResponseEnd (/home/doodloo/.nvm/versions/node/v8.9.1/lib/node_modules/truffle/build/cli.bundled.js:176852:12)
    at IncomingMessage.<anonymous> (/home/doodloo/.nvm/versions/node/v8.9.1/lib/node_modules/truffle/build/cli.bundled.js:176812:24)
    at emitNone (events.js:111:20)

Environment

Operating System: Xubuntu 17.10.
Truffle version: 4.0.3, same issue with 4.0.1.
Ethereum client: See issue ticket.
node version: 8.9.1
npm version: 5.6.0

Source

hickscorp

👍18

Most helpful comment

Having the exact same issue also on geth 1.8.0-unstable. Was rectified by using geth 1.7.3.

jleeh on 23 Jan 2018

❤4 👍4

All 53 comments

I have the same issue. It happens when Truffle tries to get the recipient of the transaction.

yograterol on 26 Dec 2017

Fixed in this commit https://github.com/ethereum/go-ethereum/pull/15714/files

yograterol on 26 Dec 2017

I'm still having this issue.

yograterol on 30 Dec 2017

I have the same problem. My contracts don't change but now migrations don't work with above error. Do you have any update of this issue?

drootnar on 4 Jan 2018

👍1

same issue , who can help me

hqxluoyang on 15 Jan 2018

same issue, cant deploy my contracts to rinkeby network.
Truffle version 4.0.3, Geth Version: 1.8.0-unstable
Running migration: 1_initial_migration.js
Deploying Migrations...
... 0x23828749b08047265fcccff7481aae8b8fe81879639e7337dc2bd96ee48407dc
Migrations: 0xee57862b9c9216957fdff614c34ef94117a01449
Saving successful migration to network...
... 0x37a4f528dc8d31ec60cc4e420780dc7846771519949d17630a0b8516b36180de
Error encountered, bailing. Network state unknown. Review successful transactions manually.
Error: unknown transaction
at Object.InvalidResponse (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:41484:16)
at /usr/local/lib/node_modules/truffle/build/cli.bundled.js:328866:36
at /usr/local/lib/node_modules/truffle/build/cli.bundled.js:176178:11
at /usr/local/lib/node_modules/truffle/build/cli.bundled.js:324536:9
at XMLHttpRequest.request.onreadystatechange (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:327565:7)
at XMLHttpRequestEventTarget.dispatchEvent (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:176407:18)
at XMLHttpRequest._setReadyState (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:176697:12)
at XMLHttpRequest._onHttpResponseEnd (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:176852:12)
at IncomingMessage. (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:176812:24)
at emitNone (events.js:91:20)

jsdu on 16 Jan 2018

👍5

Having the same error inside our app when running on Rinkeby with Geth built from master.

skozin on 16 Jan 2018

Having the same problem when deploying contracts to a private geth node built off 1.8.0-unstable. It fails after a response from the geth node.

What is interesting is that if I only deploy 1_initial_migration.js without any other follow-up migrations, no error occurs.

Artificial-Idiocy on 20 Jan 2018

👍1

Having the exact same issue also on geth 1.8.0-unstable. Was rectified by using geth 1.7.3.

jleeh on 23 Jan 2018

❤4 👍4

@hickscorp After trying lots of stuff, I got it past migration successfully by running miner.start() on the node that I am deploying the contract on. This seems to solve this issue.

ahester57 on 27 Jan 2018

😄1 👍1

@ahester57 Being able to get past it with an active mining process is a bi-product of something else.
As I was suggesting in my original post, using geth 1.7.3 solves this issue. Hopefully this will be fixed before 1.8 gets out.

hickscorp on 29 Jan 2018

@hickscorp This is actually on 1.7.3-stable as well. When deploying a newly initialized contract using truffle, it stalls right at the first migration, unless the node is mining.

ahester57 on 29 Jan 2018

👍3 👎2

@ahester57 Well that's not new, and unrelated to the issue here. "Deploying" is just asking for data to be mined. I'd recommend you having a look at this tool. This is what we use to have "on-demand" mining local nodes with 0-difficulty, so our CPU just doesn't get busy non-stop.

hickscorp on 8 Feb 2018

seeing the same issue here

fabdarice on 13 Feb 2018

Same issue here.
Issue exists with: geth-1.8.0-stable and truffle-4.0.6
Miner.start()does not solve the problem.

geth-1.7.3 works fine.

marwand on 15 Feb 2018

I'd like to emphasize something here, what @ahester57 said about this problem being present on 1.7 is erroneous, it's a completelly different thing he's describing, not even an error (No transaction can be mined... Unless the node is mining). The 1.8 problem is indeed not solved by mining.

hickscorp on 15 Feb 2018

Same issue while trying to deploy on Rinkeby testnet with:
geth-1.8.0-stable
truffle-4.0.6
What I don't understand is why is it working fine with Ganache and not with Rinkeby ?

darioAnongba on 15 Feb 2018

@darioAnongba I think you might be confused here.

It works fine with Rinkeby. It just doesn't work with geth 1.8, those are two different things.

Your question might instead be "What I don't understand is why is it working fine with Ganache and not with Geth 1.8?", and the answer would be that Geth is just an implementation of Ethereum, while Ganache is another, and while Ganache returns something that Truffle expects during the migrations as well as Geth 1.7, Geth 1.8 doesn't.

Therefore, using Geth 1.7 you should get it to work regardless of the network you're deploying to.

hickscorp on 15 Feb 2018

Thanks @hickscorp ! So if I understand correctly, Truffle is just not compatible with geth 1.8 yet.

darioAnongba on 15 Feb 2018

I'm encountering this issue as well. I've installed a private blockchain using geth 1.8 and am also encountering the unknown transaction error.

Can this be given priority given 1.8 is now out? https://blog.ethereum.org/2018/02/14/geth-1-8-iceberg%C2%B9/

Some additional notes:

I've been using truffle 3.4.11 (hadn't upgraded to v4.x yet) and also encountered the unknown transaction, so it seems there is some relative old/stable code that does not work with geth 1.8.
Verified also occurs with truffle 4.0.6 against geth 1.8

starlabs007 on 16 Feb 2018

👍1

@hickscorp Thanks so much for all your work on this issue, much appreciated.
@starlabs007 Beginning investigation now. . .

cgewecke on 16 Feb 2018

👍3

@cgewecke Don't mention it. It's worth noting that I've started talking to the Geth devs, but I don't think it's a bug as per say, it's more likely a different behaviour that Truffle would have to accomodate for. Tell me if you need anything else.

I would say that this now might need a bit of attention from the devs, as @starlabs007 pointed out 1.8 has been out for a small while now.

Keep up the good work ;)

hickscorp on 16 Feb 2018

truffle-contract 99 contains a small fix for this.

Not sure when our next patch release will be but should be resolved then.

cgewecke on 19 Feb 2018

👍3

https://github.com/ethereum/go-ethereum/releases/tag/v1.8.1
i think that nothing has changed?

vecheslav on 19 Feb 2018

@vecheslav I just tested 1.8.1, still errored. Downgrading to 1.7.3 seems to be the way to go for now.

Here are some easy instructions for those who are desperate to deploy a contract. OSX only, though it would be similar on other OSs.

# OSX instructions to get 1.7.3
git clone [email protected]:ethereum/go-ethereum.git;
cd go-ethereum;
git checkout tags/v1.7.3; # checkout 1.7.3
# brew switch go 1.9.4; # install a version of go that 1.7.3 is happy with.
make geth;
ln -s ${PWD}/build/bin/geth /usr/local/bin/geth-173; # or geth if you want to use it in scripts etc...
geth-173 version; # version check

I had a hard time getting it to install with go 1.10 because make checks the version of go, and doesn't properly sort the versions. It things 1.10 < 1.7. So if make geth fails, you may have to run brew switch go 1.9.4 before make geth.

EDIT: forgot to checkout the right version in the script.

ericwooley on 19 Feb 2018

👍3

@cgewecke I'm not sure why this is closed? Was some progress made?

ericwooley on 19 Feb 2018

@ericwooley I didn't close and FWIW am in favor of re-opening until we publish the fix. It's @hickscorp's issue. [EDIT] I DID close it, sorry mistake. Wrote the wrong words in the commit message I guess.

cgewecke on 19 Feb 2018

👍1

Same issue for me.

nicolasburtey on 19 Feb 2018

👍1

i think this to be helpful go-ethereum discussion:
https://github.com/ethereum/go-ethereum/issues/16092

nakajo2011 on 20 Feb 2018

👍1

So now I am using geth 1.8 stable .
How to use geth 1.7 ?

kosnet2 on 20 Feb 2018

You should checkout appropriate branch

git checkout origin/release/1.7

and compile this one

make

virtonomics on 20 Feb 2018

👍1

I can deploy fine but any contracts method transactions fail. Rolled back to geth 1.7.3 fixed it.

andy-mcewan-artos-io on 21 Feb 2018

👍1

Any plan to support new geth ^1.8? Or we need to rollback to ^1.7?

lerer00 on 23 Feb 2018

@lerer00 There's a fix for this at truffle-contract 99 that should be released next Monday.

cgewecke on 23 Feb 2018

🎉2

@cgewecke sweet thanks for the info.

lerer00 on 23 Feb 2018

How to roll back to 1.7.3?

OfStone on 23 Feb 2018

@OfStone https://github.com/trufflesuite/truffle/issues/721#issuecomment-366754953

ericwooley on 23 Feb 2018

Pls suggest what is fix for this am also using Geth 1.8.1 and Truffle 4.0.6.
Contracts are deploying but .json file is not updated in build/contracts folder.

Error encountered, bailing. Network state unknown. Review successful transactions manually.
Error: unknown transaction

marshaln on 24 Feb 2018

@marshaln Downgrade to 1.7.3 and watch this issue for when it's fixed

JohnAllen on 24 Feb 2018

@marshaln The fix for this is not to downgrade. The fix is to be mining on
the node you're migrating to. I had some backlash after I suggested this
earlier since it's a separate issue, but it is the only way I am able to
migrate contracts successfully to geth. Some people may not know you have
to be mining, and if this isn't true, then please provide some evidence
that we are able to deploy a contract on a light node.

On Feb 24, 2018 00:22, "marshaln" notifications@github.com wrote:

Pls suggest what is fix for this am also using Geth 1.8.1 and Truffle
4.0.6.
Contracts are deploying but .json file is not updated in build/contracts
folder.

Error encountered, bailing. Network state unknown. Review successful
transactions manually.
Error: unknown transaction

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/trufflesuite/truffle/issues/721#issuecomment-368204272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARya1fVjFCRGGVJbZ7FhDFNcBM0cgfCVks5tX6qSgaJpZM4RDt8z
.

ahester57 on 24 Feb 2018

@ahester57 If you're mining on Ropsten with a CPU it might take a while to migrate/mine a tx, right? Probably more than the timeout? Mining also used to not be necessary and is wasteful on testnets. So having to mine on a testnet instead of just connecting to a node to submit a tx or contracts seems to be a step backwards.

JohnAllen on 24 Feb 2018

@JohnAllen Downgrading is two steps backward, in my opinion.

ahester57 on 24 Feb 2018

I'm sure they'll fix this, but not having to mine and run CPUs up (even with minerthreads 1) would be better. Wondering why they made this change!

JohnAllen on 25 Feb 2018

You can't mine on rinkeby, which is a testnet I use often for simplicity. Ropsten is better, but it's more annoying also. I like to start with rinkeby.

ericwooley on 25 Feb 2018

@ahester57 There's a fix for this at truffle-contract 99 that should be released next Monday.

lerer00 on 25 Feb 2018

4.0.7 is out and there's a confirmed success deploying with Geth 1.8 to Rinkeby from Gitter. There's also a confirmed 'having problems' on Ropsten. Feel free to report any developments here or on Gitter. We're also releasing tomorrow so if the current fix doesn't work, we'll have a chance to update it and try again shortly.

cgewecke on 26 Feb 2018

👍3

@hickscorp Closing because we think this is fixed in 4.0.7. Thanks again, and please re-open if there's a problem.

cgewecke on 27 Feb 2018

👍5 ❤1

Small update: This is fixed at Geth as well as of 1.8.2 (released this morning). Geth no longer errors with 'unknown transaction'.

cgewecke on 5 Mar 2018

👍2

Confirmed working with geth 1.8.1 on a non-mining node as well. No more
throwing 'network unknown.'

On Mar 5, 2018 11:54, "c-g-e-w-e-k-e->" notifications@github.com wrote:

Small update: This is fixed at Geth as well as of 1.8.2 (released this
morning). Geth no longer errors with 'unknown transaction'.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/trufflesuite/truffle/issues/721#issuecomment-370505164,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARya1SjB5CJcpH5Fd8i2n43gBLtgAP1sks5tbXvIgaJpZM4RDt8z
.

ahester57 on 5 Mar 2018

🎉1 👍1

Geth 1.8.1. Worked fine till yesterday. Error started appearing consistently for rinkeby and from time to time with ganache. Upgrade to 1.8.2 didn't fixed the issue.