You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @Junaidbt,
Would like to know which version of fabric you are running. Please pull the latest images of explorer & explorer-db and try to bring up the explorer application. If the issue still exists, please free to further post here.
Thanks.
Running based on source code, has anyone ever encountered a lifecycle lifecycle problem?
>[email protected] start /node-data/code/fabric-explorer
>export NODE_ENV=production && run-s build app-start
>[email protected] build /node-data/code/fabric-explorer
> tsc
>[email protected] app-start /node-data/code/fabric-explorer
> ./start.sh
**************************************************************************************************************** Hyperledger Explorer **********************************************************************************************************************
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR![email protected] app-start: `./start.sh`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] app-start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2024-04-15T11_28_55_414Z-debug.log
ERROR: "app-start" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR![email protected] start: `export NODE_ENV=production && run-s build app-start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2024-04-15T11_28_55_443Z-debug.log
What happened?
Facing issue after docker-compose -up -d explorer unable to start
2023-04-15 23:17:55 > [email protected] app-start /opt/explorer
2023-04-15 23:17:55 > ./start.sh
2023-04-15 23:17:55
2023-04-15 23:17:56 start.sh: applet not found
2023-04-15 23:17:56 npm ERR! code ELIFECYCLE
2023-04-15 23:17:56 npm ERR! syscall spawn
2023-04-15 23:17:56 npm ERR! file sh
2023-04-15 23:17:56 npm ERR! errno ENOENT
2023-04-15 23:17:56 npm ERR! [email protected] app-start:
./start.sh
2023-04-15 23:17:56 npm ERR! spawn ENOENT
2023-04-15 23:17:56 npm ERR!
2023-04-15 23:17:56 npm ERR! Failed at the [email protected] app-start script.
2023-04-15 23:17:56 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2023-04-15 23:17:56
2023-04-15 23:17:56 npm ERR! A complete log of this run can be found in:
2023-04-15 23:17:56 npm ERR! /root/.npm/_logs/2023-04-15T19_17_56_018Z-debug.log
Log File:
info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'app-start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'preapp-start', 'app-start', 'postapp-start' ]
5 info lifecycle [email protected]
preapp-start: [email protected]app-start: [email protected]6 info lifecycle [email protected]
7 verbose lifecycle [email protected]
app-start: unsafe-perm in lifecycle trueapp-start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/opt/explorer/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin8 verbose lifecycle [email protected]
9 verbose lifecycle [email protected]
app-start: CWD: /opt/explorerapp-start: Args: [ '-c', './start.sh' ]10 silly lifecycle [email protected]
11 info lifecycle [email protected]~app-start: Failed to exec app-start script
12 verbose stack Error: [email protected] app-start:
./start.sh
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack
What did you expect to happen?
it working fine on ubuntu , can you please help is this error due to Mac m2?
How can we reproduce it (as minimally and precisely as possible)?
run hyperledger explorer on mac m2 machine using first option deplotment
Anything else we need to know?
No response
OS version
On mac os M2 Machine:
info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'app-start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'preapp-start', 'app-start', 'postapp-start' ]
5 info lifecycle [email protected]
preapp-start: [email protected]app-start: [email protected]6 info lifecycle [email protected]
7 verbose lifecycle [email protected]
app-start: unsafe-perm in lifecycle trueapp-start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/opt/explorer/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin8 verbose lifecycle [email protected]
9 verbose lifecycle [email protected]
app-start: CWD: /opt/explorerapp-start: Args: [ '-c', './start.sh' ]10 silly lifecycle [email protected]
11 info lifecycle [email protected]~app-start: Failed to exec app-start script
12 verbose stack Error: [email protected] app-start:
./start.sh
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack
The text was updated successfully, but these errors were encountered: