-
Notifications
You must be signed in to change notification settings - Fork 1
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
部署失败了,帮我看看,哪里有问题呢? #4
Comments
补充“命令行”下的信息:C:\moac_xpress-master>npm run start
{"message":"connected to moac vnode at http://localhost:8545","level":"info"} npm ERR! A complete log of this run can be found in: C:\moac_xpress-master> |
智能合约编译时出错了,估计solc版本问题。可能需要你在工程目录下执行
卸载后再执行
安装后再尝试是否可以正常发链。 或者删除工程目下的node_modules文件夹,重新执行
另外,可以提供下你的操作环境吗?我们在windows10测试没有出现该问题,所以想记录下。 |
嗯,更换了solc版本,已经可以正常发链了。谢谢! |
0 info it worked if it ends with ok
1 verbose cli [ 'C:\nodejs\node.exe',
1 verbose cli 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]
prestart: [email protected]start: [email protected]6 info lifecycle [email protected]
7 verbose lifecycle [email protected]
start: unsafe-perm in lifecycle truestart: PATH: C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\moac_xpress-master\node_modules.bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\apache-ant-1.9.4\bin;C:\android-ndk-r10c;C:\adt-bundle-windows-x86-20131030\sdk\platform-tools;C:\nodejs;C:\jdk1.8.0_161\bin;C:\jdk1.8.0_161\jre\bin;C:\android-sdk\platform-tools;C:\android-sdk\tools;C:\openssh;C:\Program Files\Windows Kits\8.1\Windows Performance Toolkit;C:\Program Files\Microsoft SQL Server\110\Tools\Binn;C:\Users\Administrator\AppData\Roaming\npm;C:\Program Files\Microsoft VS Code\bin8 verbose lifecycle [email protected]
9 verbose lifecycle [email protected]
start: CWD: C:\moac_xpress-masterstart: Args: [ '/d /s /c', 'node ./bin/www' ]10 silly lifecycle [email protected]
11 silly lifecycle [email protected]
start: Returned: code: 1 signal: nullstart: Failed to exec start script12 info lifecycle [email protected]
13 verbose stack Error: [email protected] start:
node ./bin/www
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:326:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess. (C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid [email protected]
15 verbose cwd C:\moac_xpress-master
16 verbose Windows_NT 6.1.7601
17 verbose argv "C:\nodejs\node.exe" "C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "start"
18 verbose node v8.10.0
19 verbose npm v6.10.3
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start:
node ./bin/www
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
The text was updated successfully, but these errors were encountered: