ArcBlock/community

magrook

@magrook

and

/usr/local/bin/forge

I followed the docs for each, I'm not sure why I have two separate packages

I'm guessing I need to remove and reinstall everything?

polunzh

@polunzh

@magrook Sorry to bring you trouble.
Does your dApp created base on react-starter blocklet? If so, can you please run with the command, and check its output?

npm run start:server

This command will just start the server.

magrook

@magrook

forge@craig-backbone:/opt/ABTChainNode$ npm run start:server
npm ERR! path /opt/ABTChainNode/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/opt/ABTChainNode/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/forge/.npm/_logs/2019-10-16T02_07_38_497Z-debug.log

And yes, it was a react-starter based dapp

magrook

@magrook

Also @polunzh, It's really no trouble :) I understand what it's like when you are supporting an early version of a platform!

wangshijun

@wangshijun

Yeah, there are apparently two on my machine, under different users which is probably not helping me:

@magrook Maybe it's better to install just one-copy of forge-cli, try to remove one to see if it helps fix the issue.

forge@craig-backbone:/opt/ABTChainNode$ npm run start:server
npm ERR! path /opt/ABTChainNode/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/opt/ABTChainNode/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /home/forge/.npm/_logs/2019-10-16T02_07_38_497Z-debug.log

About this error, where is your app located, the npm run start:server command should be run in your dapp root directory.

magrook

@magrook

@wangshijun sounds good re: cleanup. Not sure how I managed to get two of the same package installed in different places but I can walk through the docs again, probably helpful to do now that I've been through it once.

re: npm run start:server - here's the output following execution from the dapp directory:

forge-react-starter v0.38.3 ready on http://192.168.1.73:3030
/home/craig/demochain-dapp/node_modules/mongodb/lib/operations/mongo_client_ops.js:474
throw err;
^

MongoNetworkError: failed to connect to server [127.0.0.1:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]
at Pool.<anonymous> (/home/craig/demochain-dapp/node_modules/mongodb-core/lib/topologies/server.js:564:11)
at Pool.emit (events.js:193:13)
at Connection.<anonymous> (/home/craig/demochain-dapp/node_modules/mongodb-core/lib/connection/pool.js:317:12)
at Object.onceWrapper (events.js:281:20)
at Connection.emit (events.js:193:13)
at Socket.<anonymous> (/home/craig/demochain-dapp/node_modules/mongodb-core/lib/connection/connection.js:246:50)
at Object.onceWrapper (events.js:281:20)
at Socket.emit (events.js:193:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at processTicksAndRejections (internal/process/task_queues.js:81:17)

I'm installing mongo now though I had thought the original installation of the forge packages had done so - I'm guessing the document storage engine for the forge dashboard and chain data is sqlite or something?

wangshijun

@wangshijun

@magrook The above error message shows that your mongodb server is not running, so the dapp cannot connect to it

Perhaps it should be better if we check the runtime requirements before start the dapp.

@polunzh

polunzh

@polunzh

Perhaps it should be better if we check the runtime requirements before start the dapp.

@magrook We'll do something to make the fatal error more friendly.

magrook

@magrook

npm run start:server
npm ERR! path /home/craig/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/home/craig/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/craig/.npm/_logs/2019-10-18T01_16_24_943Z-debug.log
npm run start:server
npm ERR! path /home/craig/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/home/craig/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/craig/.npm/_logs/2019-10-18T01_16_24_943Z-debug.log
craig@craig-backbone:~$ which forge
/home/craig/.npm-packages/bin/forge
craig@craig-backbone:~$ forge start
⚠ There are no chains, please create it by run forge chain:create
forge chain:create
✖ Forge releases not found.

You can either run forge install to get the latest forge release.
Or start node with custom forge release folder:

forge start --release-dir ~/Downloads/forge/
FORGE_RELEASE_DIR=~/Downloads/forge/ forge start

Hi guys, just wanted to ask if this is a known issue with release .14 - I updated my .bashrc so both the forge user and my user are pointed at the same source, then was about to start on a custom dapp PoC to get a better sense on blocklets etc., but after saying yes to the upgrade I cannot seem to get anything to run. I'll re-install probably this evening or tomorrow AM, but I thought this info might be helpful. I'm about to upload the log file too in case you need it

(And please, just let me know if you would rather I file straight into github - I just want to avoid creating annoying duplicate issues for the team)

polunzh

@polunzh

@magrook What do you mean "updated my .bashrc"?

Don't worry about duplicated issue, if it is, we will deal with it, thanks.

magrook

@magrook

@polunzh when I upgraded via npm, it looks like a separate forge was installed in my local dir, /home/craig/.npm-packages/bin/forge

the original was a symlink generated in /usr/local/bin/ forge -> ../share/.config/yarn/global/node_modules/.bin/forge

so my user on debian was using the first forge, the forge user was using that second one, the symlink I pasted in

what I did was change the forge .bashrc config to match my user account to override and ensure I was using the same source package for both users

(^ where forge is the user account on my box)

magrook

@magrook

heya everyone, I have an odd problem happening here

craig@craig-backbone:~$ forge start --dry-run
⚠ There are no chains, please create it by run forge chain:create
craig@craig-backbone:~$ forge chain:create
✖ Forge releases not found.

You can either run forge install to get the latest forge release.
Or start node with custom forge release folder:

forge start --release-dir ~/Downloads/forge/
FORGE_RELEASE_DIR=~/Downloads/forge/ forge start

craig@craig-backbone:~$ forge --version
0.39.15

I've sorted out the version discrepancy and there is only one forge instance being referenced by both users

However, I cannot create a chain due to the error above. I will review github to see if there's any additional info there

Additionally, forge install latest rolls me back to 0.39.2 -> even after I manually updated the release.yml file to point at .15

magrook

@magrook

This one is already in github issues, but I'm currently kind of unable to progress, I will continue to familiarize with underlying source code to see if I can find anything further

magrook

@magrook

It looks to me as though something has been missed in ~/.forge_cli/release

when I installed .15 via npm

npm install -g @arcblock/forge-cli --unsafe-perm

^ that's in my own home directory

However, in the forge user home directory, there is information which allows me to start creating a chain

so removing the .forge-cli and .forge-chains directories, then running forge start does not write the information regarding the release data that I do see under the forge user's home directory:

forge start
✔ initialized tmp dir for forge-cli: /home/craig/.forge_cli/tmp
✔ initialized bin dir for forge-cli: /home/craig/.forge_cli/bin
✔ initialized cache dir for forge-cli: /home/craig/.forge_cli/cache
✔ initialized logs dir for forge-cli: /home/craig/.forge_cli/logs
✔ initialized release dir for forge-cli: /home/craig/.forge_cli/release
✔ Checking new version...
⚠ There are no chains, please create it by run forge chain:create
craig@craig-backbone:~$ cd /home/craig/.forge_cli/release
craig@craig-backbone:~/.forge_cli/release$ ls -al
total 8
drwxr-xr-x 2 craig craig 4096 Oct 18 15:40 .
drwxr-xr-x 7 craig craig 4096 Oct 18 15:40 ..

magrook

@magrook

so yeah, even though both users report using 0.39.15 via forge --version, and they are both referencing the exact path for the npm installed packages, if I try to forge install latest or forge install v0.39.15 I get a version not found error, forge ls:remote is also showing me that the list provided from the remote is capped at 0.39.2

At this point I'm kind of unable to do more experimentation because I cannot create chains on 0.39.15 - which I expect is due to the release folder being empty for my user when I try to do so

I'll look around at the install and init code and see if I can track it down

wangshijun

@wangshijun

@magrook let's schedule a zoom call to fix your setup?

magrook

@magrook

What slots do you have open today?

I'm pretty sure the issue is missing release folders for my specific user but a zoom session would probably be very helpful to make sure a) I didn't do something silly by accident, and b) get a better overall sense of the download and installation process in the source code so I can resolve my own issues (and maybe even help you guys with pull requests in the process)

magrook

@magrook

@wangshijun (sorry, forgot to @ you in my last msg)

magrook

@magrook

@wangshijun I may have fixed it, looks like the release folder and version for forge install is 0.39.2, but forge --version gives me 0.39.15

so I'm guessing it may be an inconsequential discrepancy between the available local versions and the version that is actually in use (which was installed via npm)

Where communities thrive

People

Repo info

Activity