Last active
January 23, 2019 04:58
-
-
Save vincentntang/2910658e4d7e8a1f0b8fb75b45e63f5c to your computer and use it in GitHub Desktop.
issues with install
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Bears-Team-22 git:(master) npm start | |
| > knowledge@0.0.0 start /Users/vincenttang/www/Bears-Team-22 | |
| > concurrently npm:start:* | |
| [start:server] | |
| [start:server] > knowledge@0.0.0 start:server /Users/vincenttang/www/Bears-Team-22 | |
| [start:server] > cd server && docker-compose up | |
| [start:server] | |
| [start:client] | |
| [start:client] > knowledge@0.0.0 start:client /Users/vincenttang/www/Bears-Team-22 | |
| [start:client] > cd client && npm build && npm start | |
| [start:client] | |
| [start:client] npm WARN build `npm build` called with no arguments. Did you mean to `npm run-script build`? | |
| [start:server] Starting server_mongo_1 ... | |
| [start:client] | |
| [start:client] > knowledge-client@0.0.0 start /Users/vincenttang/www/Bears-Team-22/client | |
| [start:client] > next start | |
| Starting server_mongo_1 ... done | |
| Starting server_server_1 ... | |
| [start:client] Error: Could not find a valid build in the '/Users/vincenttang/www/Bears-Team-22/client/.next' directory! Try building your app with 'next build' before starting the server. | |
| [start:client] at Server.readBuildId (/Users/vincenttang/www/Bears-Team-22/client/node_modules/next/dist/server/next-server.js:753:15) | |
| [start:client] at new Server (/Users/vincenttang/www/Bears-Team-22/client/node_modules/next/dist/server/next-server.js:80:25) | |
| [start:client] at module.exports (/Users/vincenttang/www/Bears-Team-22/client/node_modules/next/dist/server/next.js:6:10) | |
| [start:client] at _callee$ (/Users/vincenttang/www/Bears-Team-22/client/node_modules/next/dist/server/lib/start-server.js:33:37) | |
| [start:client] at tryCatch (/Users/vincenttang/www/Bears-Team-22/client/node_modules/@babel/runtime-corejs2/node_modules/regenerator-runtime/runtime.js:62:40) | |
| [start:client] at Generator.invoke [as _invoke] (/Users/vincenttang/www/Bears-Team-22/client/node_modules/@babel/runtime-corejs2/node_modules/regenerator-runtime/runtime.js:288:22) | |
| [start:client] at Generator.prototype.(anonymous function) [as next] (/Users/vincenttang/www/Bears-Team-22/client/node_modules/@babel/runtime-corejs2/node_modules/regenerator-runtime/runtime.js:114:21) | |
| [start:client] at asyncGeneratorStep (/Users/vincenttang/www/Bears-Team-22/client/node_modules/@babel/runtime-corejs2/helpers/asyncToGenerator.js:5:24) | |
| [start:client] at _next (/Users/vincenttang/www/Bears-Team-22/client/node_modules/@babel/runtime-corejs2/helpers/asyncToGenerator.js:27:9) | |
| [start:client] at /Users/vincenttang/www/Bears-Team-22/client/node_modules/@babel/runtime-corejs2/helpers/asyncToGenerator.js:34:7 | |
| [start:client] npm ERR! code ELIFECYCLE | |
| [start:client] npm ERR! errno 1 | |
| [start:client] npm ERR! knowledge-client@0.0.0 start: `next start` | |
| [start:client] npm ERR! Exit status 1 | |
| npm ERR! | |
| [start:client] npm ERR! Failed at the knowledge-client@0.0.0 start script. | |
| [start:client] npm ERR! This is probably not a problem with npm. There is likely additional logging output above. | |
| [start:client] | |
| [start:client] npm ERR! A complete log of this run can be found in: | |
| [start:client] npm ERR! /Users/vincenttang/.npm/_logs/2019-01-23T04_51_21_172Z-debug.log | |
| [start:client] npm ERR! code ELIFECYCLE | |
| [start:client] npm ERR! errno 1 | |
| [start:client] npm ERR! knowledge@0.0.0 start:client: `cd client && npm build && npm start` | |
| [start:client] npm ERR! Exit status 1 | |
| npm ERR! | |
| [start:client] npm ERR! Failed at the knowledge@0.0.0 start:client script. | |
| npm ERR! This is probably not a problem with npm. There is likely additional logging output above. | |
| [start:client] | |
| [start:client] npm ERR! A complete log of this run can be found in: | |
| [start:client] npm ERR! /Users/vincenttang/.npm/_logs/2019-01-23T04_51_21_190Z-debug.log | |
| Starting server_server_1 ... done | |
| Attaching to server_mongo_1, server_server_1 | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.891+0000 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none' | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.895+0000 I CONTROL [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=f29bc4e961a1 | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.895+0000 I CONTROL [initandlisten] db version v4.0.5 | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.895+0000 I CONTROL [initandlisten] git version: 3739429dd92b92d1b0ab120911a23d50bf03c412 | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.895+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016 | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.895+0000 I CONTROL [initandlisten] allocator: tcmalloc | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.895+0000 I CONTROL [initandlisten] modules: none | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.895+0000 I CONTROL [initandlisten] build environment: | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.895+0000 I CONTROL [initandlisten] distmod: ubuntu1604 | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.895+0000 I CONTROL [initandlisten] distarch: x86_64 | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.895+0000 I CONTROL [initandlisten] target_arch: x86_64 | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.895+0000 I CONTROL [initandlisten] options: { net: { bindIpAll: true } } | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.896+0000 W STORAGE [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty. | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.896+0000 I STORAGE [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.896+0000 W STORAGE [initandlisten] Recovering data from the last clean checkpoint. | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.896+0000 I STORAGE [initandlisten] | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.896+0000 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.896+0000 I STORAGE [initandlisten] ** See http://dochub.mongodb.org/core/prodnotes-filesystem | |
| [start:server] mongo_1 | 2019-01-23T04:51:20.897+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=487M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress), | |
| [start:server] mongo_1 | 2019-01-23T04:51:21.608+0000 I STORAGE [initandlisten] WiredTiger message [1548219081:608064][1:0x7f09855f0a40], txn-recover: Main recovery loop: starting at 1/19968 to 2/256 | |
| [start:server] mongo_1 | 2019-01-23T04:51:21.608+0000 I STORAGE [initandlisten] WiredTiger message [1548219081:608687][1:0x7f09855f0a40], txn-recover: Recovering log 1 through 2 | |
| [start:server] server_1 | | |
| [start:server] server_1 | > knowledge-server@0.0.0 start /server | |
| [start:server] server_1 | > node index.js | |
| [start:server] server_1 | | |
| [start:server] mongo_1 | 2019-01-23T04:51:21.680+0000 I STORAGE [initandlisten] WiredTiger message [1548219081:680918][1:0x7f09855f0a40], txn-recover: Recovering log 2 through 2 | |
| [start:server] mongo_1 | 2019-01-23T04:51:21.726+0000 I STORAGE [initandlisten] WiredTiger message [1548219081:726134][1:0x7f09855f0a40], txn-recover: Set global recovery timestamp: 0 | |
| [start:server] mongo_1 | 2019-01-23T04:51:21.740+0000 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0) | |
| [start:server] mongo_1 | 2019-01-23T04:51:21.773+0000 I CONTROL [initandlisten] | |
| [start:server] mongo_1 | 2019-01-23T04:51:21.773+0000 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database. | |
| [start:server] mongo_1 | 2019-01-23T04:51:21.773+0000 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted. | |
| [start:server] mongo_1 | 2019-01-23T04:51:21.773+0000 I CONTROL [initandlisten] | |
| [start:server] mongo_1 | 2019-01-23T04:51:21.806+0000 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data' | |
| [start:server] mongo_1 | 2019-01-23T04:51:21.808+0000 I NETWORK [initandlisten] waiting for connections on port 27017 | |
| [start:server] mongo_1 | 2019-01-23T04:51:22.026+0000 I FTDC [ftdc] Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost. OK | |
| [start:server] server_1 | /server/node_modules/firebase-admin/lib/auth/credential.js:118 | |
| [start:server] server_1 | throw new error_1.FirebaseAppError(error_1.AppErrorCodes.INVALID_CREDENTIAL, errorMessage); | |
| [start:server] server_1 | ^ | |
| [start:server] server_1 | | |
| [start:server] server_1 | Error: Certificate object must contain a string "private_key" property. | |
| [start:server] server_1 | at FirebaseAppError.FirebaseError [as constructor] (/server/node_modules/firebase-admin/lib/utils/error.js:39:28) | |
| [start:server] server_1 | at FirebaseAppError.PrefixedFirebaseError [as constructor] (/server/node_modules/firebase-admin/lib/utils/error.js:85:28) | |
| [start:server] server_1 | at new FirebaseAppError (/server/node_modules/firebase-admin/lib/utils/error.js:119:28) | |
| [start:server] server_1 | at new Certificate (/server/node_modules/firebase-admin/lib/auth/credential.js:118:19) | |
| [start:server] server_1 | at new CertCredential (/server/node_modules/firebase-admin/lib/auth/credential.js:173:64) | |
| [start:server] server_1 | at Object.cert (/server/node_modules/firebase-admin/lib/firebase-namespace.js:220:58) | |
| [start:server] server_1 | at Object.<anonymous> (/server/index.js:18:31) | |
| [start:server] server_1 | at Module._compile (internal/modules/cjs/loader.js:689:30) | |
| [start:server] server_1 | at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10) | |
| [start:server] server_1 | at Module.load (internal/modules/cjs/loader.js:599:32) | |
| [start:server] server_1 | at tryModuleLoad (internal/modules/cjs/loader.js:538:12) | |
| [start:server] server_1 | at Function.Module._load (internal/modules/cjs/loader.js:530:3) | |
| [start:server] server_1 | at Function.Module.runMain (internal/modules/cjs/loader.js:742:12) | |
| [start:server] server_1 | at startup (internal/bootstrap/node.js:283:19) | |
| [start:server] server_1 | at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3) | |
| [start:server] server_1 | npm ERR! code ELIFECYCLE | |
| [start:server] server_1 | npm ERR! errno 1 | |
| [start:server] server_1 | npm ERR! knowledge-server@0.0.0 start: `node index.js` | |
| [start:server] server_1 | npm ERR! Exit status 1 | |
| [start:server] server_1 | npm ERR! | |
| [start:server] server_1 | npm ERR! Failed at the knowledge-server@0.0.0 start script. | |
| [start:server] server_1 | npm ERR! This is probably not a problem with npm. There is likely additional logging output above. | |
| [start:server] server_1 | | |
| [start:server] server_1 | npm ERR! A complete log of this run can be found in: | |
| [start:server] server_1 | npm ERR! /root/.npm/_logs/2019-01-23T04_51_24_744Z-debug.log | |
| [start:server] server_server_1 exited with code 1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment