Truffle cannot migration with the latest Geth 1.8
See original GitHub issue- 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
package1.7.3-stable
. - you can observe the crash using the
geth-unstable
package1.8.0-unstable
.
Steps to Reproduce
Create the most simplistic project with only the Migration.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 with4.0.1
. - Ethereum client: See issue ticket.
- node version:
8.9.1
- npm version:
5.6.0
Issue Analytics
- State:
- Created 6 years ago
- Reactions:18
- Comments:53 (9 by maintainers)
Top Results From Across the Web
go ethereum - Truffle migrate fails with geth - Ethereum Stack ...
When I run "truffle migrate" I wait for few seconds than the geth node fall down and I got this truffle error :...
Read more >ConsenSys/truffle - Gitter
I just started getting this error when I run truffle test -- X has not been deployed to detected network (network/artifact mismatch) ....
Read more >Newest 'go-ethereum' Questions - Page 7 - Stack Overflow
I tried to migrate the contract Migrations by using Truffle migrate, it got hang and show ... Can't install older version 1.8.27 of...
Read more >Downloads | Go Ethereum
You can download the latest 64-bit stable release of Geth for our primary platforms ... If you're looking to install Geth and/or associated...
Read more >Crazy Problems You'll See During Truffle Migrations - Medium
This seems entirely caused by a mismatch between truffle and geth. Ethereum devs tend to make sweeping and breaking changes willy nilly and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Having the exact same issue also on geth 1.8.0-unstable. Was rectified by using geth 1.7.3.
@hickscorp Closing because we think this is fixed in
4.0.7
. Thanks again, and please re-open if there’s a problem.