We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please make sure you have search your question in our forum.
Describe the bug briefly
Information
Some necessary information can help use handle your issue quickly.
OS
Hardware (CPU info and Memory size)
gvite version
peer` number, can get from this API
Startup log, is in file gvite.log, usually in the same directory which gvite belongs.
gvite.log
Command grep -i "error" gvite.log can find the startup error. If the output is not null, then paste it into this issue.
grep -i "error" gvite.log
Runtime log, runtime log directory will be printed into gvite.log when gvite start.
grep -i "NodeServer.DataDir" gvite.log
t=2019-02-27T15:17:41+0800 lvl=info msg=NodeServer.DataDir:/root/.gvite/testdata module=gvite/node_manager
/root/.gvite/testdata/runlog
2019-03-19T13-20 2019-03-21T22-52 2019-03-22T10-36
error vite-2019-03-22T10-57-22.797.log.gz vite-2019-03-22T11-25-25.901.log.gz vite.log
Some log files are compressed, decompress them by gzip -d *.log.gz.
gzip -d *.log.gz
grep -i "download" vite.log
t=2019-03-22T11:25:31+0800 lvl=info msg="download <file subgraph_2581201_2584800> from 108.61.170.32:8484 elapse 7.846745653s" module=net/fileClient t=2019-03-22T11:25:38+0800 lvl=info msg="begin download <file subgraph_2584801_2588400> from 108.61.170.32:8484" module=net/fileClient t=2019-03-22T11:25:47+0800 lvl=info msg="download <file subgraph_2584801_2588400> from 108.61.170.32:8484 elapse 8.800968866s" module=net/fileClient t=2019-03-22T11:25:51+0800 lvl=info msg="begin download <file subgraph_2588401_2592000> from 108.61.170.32:8484" module=net/fileClient t=2019-03-22T11:26:02+0800 lvl=info msg="download <file subgraph_2588401_2592000> from 108.61.170.32:8484 elapse 11.184523779s" module=net/fileClient t=2019-03-22T11:26:05+0800 lvl=info msg="begin download <file subgraph_2592001_2595600> from 108.61.170.32:8484" module=net/fileClient t=2019-03-22T11:26:11+0800 lvl=info msg="download <file subgraph_2592001_2595600> from 108.61.170.32:8484 elapse 6.579606422s" module=net/fileClient
Tail the error/vite.error.log.
error/vite.error.log
Paste the log info get by previous step4 and step5 into this issue.
The text was updated successfully, but these errors were encountered:
bugfix Yes
Sorry, something went wrong.
No branches or pull requests
Please make sure you have search your question in our forum.
Describe the bug briefly
Information
Some necessary information can help use handle your issue quickly.
OS
Hardware (CPU info and Memory size)
gvite version
peer` number, can get from this API
Startup log, is in file
gvite.log
, usually in the same directory which gvite belongs.Command
grep -i "error" gvite.log
can find the startup error. If the output is not null, then paste it into this issue.Runtime log, runtime log directory will be printed into gvite.log when gvite start.
grep -i "NodeServer.DataDir" gvite.log
on your terminal. eg. the terminal output:/root/.gvite/testdata/runlog
. Every startup will create a directory named by Date. eg.Some log files are compressed, decompress them by
gzip -d *.log.gz
.grep -i "download" vite.log
will show:Tail the
error/vite.error.log
.Paste the log info get by previous step4 and step5 into this issue.
The text was updated successfully, but these errors were encountered: