Issue or ambiguity in logging

[ghost]

lisk_user@develop-desktop:~/lisk-main$ bash lisk.sh logs
info 2016-05-25 16:36:07 Modules ready and launched 
NOTICE:  relation "mem_accounts" already exists, skipping
NOTICE:  relation "mem_round" already exists, skipping
NOTICE:  relation "mem_accounts2delegates" already exists, skipping
NOTICE:  relation "mem_accounts2u_delegates" already exists, skipping
NOTICE:  relation "mem_accounts2multisignatures" already exists, skipping
NOTICE:  relation "mem_accounts2u_multisignatures" already exists, skipping
info 2016-05-25 16:36:07 Blocks 6066 
warn 2016-05-25 16:36:07 Detected missed blocks in mem_accounts 
warn 2016-05-25 16:36:07 Recreating memory tables 
log 2016-05-25 16:36:10 GET /api/loader/status from 10.0.0.2 
log 2016-05-25 16:36:10 GET /api/loader/status from 10.0.0.2 
NOTICE:  relation "mem_accounts" already exists, skipping
NOTICE:  relation "mem_round" already exists, skipping
NOTICE:  relation "mem_accounts2delegates" already exists, skipping
NOTICE:  relation "mem_accounts2u_delegates" already exists, skipping
NOTICE:  relation "mem_accounts2multisignatures" already exists, skipping
NOTICE:  relation "mem_accounts2u_multisignatures" already exists, skipping
info 2016-05-25 16:36:17 Current 0 

From what i understand
Current = 0 mean last blocked in local blockchain snapshot ?
If this is correct, then value appears to be invalid. Since it should be equal to 6066
info 2016-05-25 16:36:07 Blocks 6066

[Isabello]

It's rebuilding memory tables from the table data. If it fails you will
need to rebuild
On May 25, 2016 11:55, "karek314" [email protected] wrote:

lisk_user@develop-desktop:~/lisk-main$ bash lisk.sh logs
info 2016-05-25 16:36:07 Modules ready and launched
NOTICE: relation "mem_accounts" already exists, skipping
NOTICE: relation "mem_round" already exists, skipping
NOTICE: relation "mem_accounts2delegates" already exists, skipping
NOTICE: relation "mem_accounts2u_delegates" already exists, skipping
NOTICE: relation "mem_accounts2multisignatures" already exists, skipping
NOTICE: relation "mem_accounts2u_multisignatures" already exists, skipping
info 2016-05-25 16:36:07 Blocks 6066
warn 2016-05-25 16:36:07 Detected missed blocks in mem_accounts
warn 2016-05-25 16:36:07 Recreating memory tables
log 2016-05-25 16:36:10 GET /api/loader/status from 10.0.0.2
log 2016-05-25 16:36:10 GET /api/loader/status from 10.0.0.2
NOTICE: relation "mem_accounts" already exists, skipping
NOTICE: relation "mem_round" already exists, skipping
NOTICE: relation "mem_accounts2delegates" already exists, skipping
NOTICE: relation "mem_accounts2u_delegates" already exists, skipping
NOTICE: relation "mem_accounts2multisignatures" already exists, skipping
NOTICE: relation "mem_accounts2u_multisignatures" already exists, skipping
info 2016-05-25 16:36:17 Current 0

From what i understand
Current = 0 mean last blocked in local blockchain snapshot ?
If this is correct, then value appears to be invalid. Since it should be
equal to 6066
info 2016-05-25 16:36:07 Blocks 6066

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#155

[ghost]

So it is current block of rebuild into memory? I think it should have improved description.

[fix]

the info that it is rebuilding is lacking i agree. Here bascially the app will log every 5000 blocks (Current 0, Current 5000, etc...)