Skip to content
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

bugfix yes #373

Open
MgMgAye opened this issue Jun 24, 2019 · 2 comments
Open

bugfix yes #373

MgMgAye opened this issue Jun 24, 2019 · 2 comments

Comments

@MgMgAye
Copy link

MgMgAye commented Jun 24, 2019

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.

    1. You can find it by input grep -i "NodeServer.DataDir" gvite.log on your terminal. eg. the terminal output:
    t=2019-02-27T15:17:41+0800 lvl=info msg=NodeServer.DataDir:/root/.gvite/testdata module=gvite/node_manager
    1. The log directory is /root/.gvite/testdata/runlog. Every startup will create a directory named by Date. eg.
    2019-03-19T13-20  2019-03-21T22-52  2019-03-22T10-36 
    1. Go into the latest directory, fileList maybe like following:
    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.

    1. You can grep the keyword in logfile, eg. "download" is about sync file download. grep -i "download" vite.log will show:
    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
    1. Tail the error/vite.error.log.

    2. Paste the log info get by previous step4 and step5 into this issue.

@MgMgAye
Copy link
Author

MgMgAye commented Jun 24, 2019

bugfix
Yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@MgMgAye and others