-
Notifications
You must be signed in to change notification settings - Fork 91
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
gvite can not start properly #493
Comments
t=2020-07-29T01:32:30.194+0800 lvl=warn msg="block exists in BCPool. hash:[f8c7168363f75a731a76aaeb33e9bfdc1799912dd4ba1ed670d5ea10a8f8c64c], height:[319474]." module=pool account=accountChainPool-vite_48895412bb0959e6a2ae48dcb5e6e7b5695a6bc3c4c3f5bf34 |
Latest snapshot block height is 36476498 runtime stack: goroutine 1 [running]: goroutine 5 [syscall, 3 minutes]: goroutine 10 [chan receive, 4 minutes]: goroutine 12 [select]: goroutine 13 [select, 4 minutes]: goroutine 14 [select]: goroutine 15 [select, 4 minutes]: goroutine 16 [select, 4 minutes]: goroutine 33 [select]: goroutine 34 [select, 3 minutes]: goroutine 35 [select]: goroutine 36 [select, 3 minutes]: goroutine 37 [select, 4 minutes]: goroutine 38 [select]: goroutine 39 [select]: goroutine 40 [select]: goroutine 41 [select]: goroutine 42 [select, 4 minutes]: goroutine 43 [select]: goroutine 44 [select, 4 minutes]: goroutine 45 [select]: goroutine 46 [select, 4 minutes]: goroutine 47 [select, 4 minutes]: goroutine 48 [select]: goroutine 18 [select]: goroutine 19 [select, 4 minutes]: goroutine 20 [select]: goroutine 21 [select, 4 minutes]: goroutine 22 [select, 4 minutes]: goroutine 52 [semacquire, 3 minutes]: |
Syncing will consume more ram than usual. When your node was killed and restarted it should start sync immediately, so it's in "sync mode" rather than "synced", that explains why it reports OOM more easily. 2 GB ram is insufficient to run a full node at present. Install 4 GB for your node or create SWAP as an alternative. |
Please make sure you have search your question in our forum.
Describe the bug briefly
gvite can not start properly
Information
after I kill the previous gvite to do some ops for my os, when restart the gvite, it can not start properly, and OS report OOM. It is normal before kill, and gvite process is OK in my another same hardware os server。So there maybe some logic not process properly in gvite start, mainly cause the process using too much memory
OS
[root@VM_0_7_centos gvite-v2.9.0-linux]# uname -r
3.10.0-1062.9.1.el7.x86_64
[root@VM_0_7_centos gvite-v2.9.0-linux]# cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)
Hardware (CPU info and Memory size)
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 79
Model name: Intel(R) Xeon(R) CPU E5-26xx v4
Stepping: 1
CPU MHz: 2394.454
BogoMIPS: 4788.90
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
NUMA node0 CPU(s): 0
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl eagerfpu pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch bmi1 avx2 bmi2 rdseed adx xsaveopt
[root@VM_0_7_centos gvite-v2.9.0-linux]# free
total used free shared buff/cache available
Mem: 1882192 524988 730196 504 627008 1199168
Swap: 0 0 0
gvite version
[root@VM_0_7_centos gvite-v2.9.0-linux]# ./gvite --version
this vite node`s git GO version is b0ae1db
gvite version v2.9.0
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.
[root@VM_0_7_centos gvite-v2.9.0-linux]# tail -n 100 gvite.log
this vite node`s git GO version is b0ae1db
t=2020-07-28T23:27:43.006+0800 lvl=info msg="runtime num" module=gvite/main max=2
t=2020-07-28T23:27:43.006+0800 lvl=info msg="DefaultNodeconfig: { /root/.gvite /root/.gvite 0 [] false 0.0.0.0 8483 8484 vite-node 3 true 60 5 2 10 [] [] [] any [] [] [] [] cross false 0 false false false gvite.ipc 48132 [] 31420 [] [] [] true true info false false false false false }" module=gvite/node_manager
t=2020-07-28T23:27:43.006+0800 lvl=info msg="Will use the default config node_config.json" module=gvite/node_manager
t=2020-07-28T23:27:43.006+0800 lvl=info msg="After load config file: { /root/.gvite /root/.gvite 0 [] 0xc00003077c false 0.0.0.0 8483 8484 newcent_001 1 true 10 5 2 5 [] [https://bootnodes.vite.net/bootmainnet.json] [] any [] [] [] [] cross false 0 true true false gvite.ipc 0.0.0.0 48132 [] 0.0.0.0 41420 [] [] [ledger public_onroad net contract pledge register vote mintage consensusGroup tx debug sbpstats dashboard] true true dbug false false false false false wss://stats.vite.net vite_24d6313a1ee1bcd8e979565a39a9c6f4decc8a1be01a5debee }" module=gvite/node_manager
t=2020-07-28T23:27:43.006+0800 lvl=info msg="After mapping cmd input: { /root/.gvite /root/.gvite 0 [] 0xc00003077c false 0.0.0.0 8483 8484 newcent_001 1 true 10 5 2 5 [] [https://bootnodes.vite.net/bootmainnet.json] [] any [] [] [] [] cross false 0 true true false gvite.ipc 0.0.0.0 48132 [] 0.0.0.0 41420 [] [] [ledger public_onroad net contract pledge register vote mintage consensusGroup tx debug sbpstats dashboard] true true dbug false false false false false wss://stats.vite.net vite_24d6313a1ee1bcd8e979565a39a9c6f4decc8a1be01a5debee 0xc0003e93f0 0xc0003e9400 0xc0003e9410 0xc0003e9420}" module=gvite/node_manager
t=2020-07-28T23:27:43.006+0800 lvl=info msg="Last override config: {main /root/.gvite/maindata /root/.gvite/maindata/wallet 0 [] 0xc00003077c false 0.0.0.0 8483 8484 newcent_001 1 true 10 5 2 5 [] [https://bootnodes.vite.net/bootmainnet.json] [] any [] [] [] [] cross false 0 true true false gvite.ipc 0.0.0.0 48132 [] 0.0.0.0 41420 [] [] [ledger public_onroad net contract pledge register vote mintage consensusGroup tx debug sbpstats dashboard] true true dbug false false false false false wss://stats.vite.net vite_24d6313a1ee1bcd8e979565a39a9c6f4decc8a1be01a5debee 0xc0003e93f0 0xc0003e9400 0xc0003e9410 0xc0003e9420}" module=gvite/node_manager
t=2020-07-28T23:27:43.006+0800 lvl=info msg=NodeServer.DataDir:/root/.gvite/maindata module=gvite/node_manager
t=2020-07-28T23:27:43.006+0800 lvl=info msg=NodeServer.KeyStoreDir:/root/.gvite/maindata/wallet module=gvite/node_manager
Node prepared successfully!!!
Node started successfully!!!
Vite RPC service started successfully!
no more log info output
strace message:
clock_gettime(CLOCK_MONOTONIC, {1342, 256468338}) = 0
clock_gettime(CLOCK_MONOTONIC, {1342, 256494631}) = 0
futex(0x1cb4020, FUTEX_WAIT_PRIVATE, 0, {0, 9911020}) = -1 ETIMEDOUT (Connection timed out)
clock_gettime(CLOCK_MONOTONIC, {1342, 266592360}) = 0
futex(0x1cb00d0, FUTEX_WAKE_PRIVATE, 1) = 1
clock_gettime(CLOCK_MONOTONIC, {1342, 266723297}) = 0
futex(0xc0001fcf40, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xc000052f40, FUTEX_WAKE_PRIVATE, 1) = 1
clock_gettime(CLOCK_MONOTONIC, {1342, 266869776}) = 0
clock_gettime(CLOCK_MONOTONIC, {1342, 266894495}) = 0
futex(0x1cb4020, FUTEX_WAIT_PRIVATE, 0, {0, 9916757}) = -1 ETIMEDOUT (Connection timed out)
clock_gettime(CLOCK_MONOTONIC, {1342, 277174761}) = 0
futex(0x1cb00d0, FUTEX_WAKE_PRIVATE, 1) = 1
clock_gettime(CLOCK_MONOTONIC, {1342, 277311144}) = 0
futex(0xc0001fcf40, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xc000052f40, FUTEX_WAKE_PRIVATE, 1) = 1
clock_gettime(CLOCK_MONOTONIC, {1342, 277483774}) = 0
futex(0x1cb4020, FUTEX_WAIT_PRIVATE, 0, {0, 255358245}) = 0
clock_gettime(CLOCK_MONOTONIC, {1342, 287600295}) = 0
clock_gettime(CLOCK_MONOTONIC, {1342, 287746114}) = 0
futex(0x1cb4020, FUTEX_WAIT_PRIVATE, 0, {0, 9905231}) = -1 ETIMEDOUT (Connection timed out)
clock_gettime(CLOCK_MONOTONIC, {1342, 297836297}) = 0
futex(0x1cb00d0, FUTEX_WAKE_PRIVATE, 1) = 1
clock_gettime(CLOCK_MONOTONIC, {1342, 298033465}) = 0
futex(0xc0001fcf40, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xc000052f40, FUTEX_WAKE_PRIVATE, 1) = 1
clock_gettime(CLOCK_MONOTONIC, {1342, 298203509}) = 0
futex(0x1cb4020, FUTEX_WAIT_PRIVATE, 0, {0, 234635924}) = 0
futex(0x1cb00d0, FUTEX_WAKE_PRIVATE, 1) = 1
clock_gettime(CLOCK_MONOTONIC, {1342, 318508297}) = 0
clock_gettime(CLOCK_MONOTONIC, {1342, 318684763}) = 0
futex(0x1cb4020, FUTEX_WAIT_PRIVATE, 0, {0, 9826970}) = -1 ETIMEDOUT (Connection timed out)
clock_gettime(CLOCK_MONOTONIC, {1342, 328664161}) = 0
futex(0x1cb00d0, FUTEX_WAKE_PRIVATE, 1) = 1
clock_gettime(CLOCK_MONOTONIC, {1342, 328721322}) = 0
futex(0xc0001fcf40, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xc000052f40, FUTEX_WAKE_PRIVATE, 1) = 1
clock_gettime(CLOCK_MONOTONIC, {1342, 328817591}) = 0
The text was updated successfully, but these errors were encountered: