So at litecoin newest source, after I set all values as mine, first run ./xxxcoind , nothing happen, it seems stop, so I opened debug.log file, it says
2018-02-21 11:44:37 ERROR: AcceptBlock: high-hash, proof of work
failed (code 16)
2018-02-21 11:44:37 Reindexing finished
2018-02-21 11:44:37 Failed to open mempool file from disk. Continuing
anyway.
2018-02-21 11:48:22 Potential stale tip detected, will try using extra
outbound peer (last tip update: 180 seconds ago)
2018-02-21 11:51:22 Potential stale tip detected, will try using extra
outbound peer (last tip update: 360 seconds ago)
So I searched about [Potential stale....] some says add [ -connect=0 ], so I did, then again past same error appears...
2018-02-21 12:47:18 ERROR: ReadBlockFromDisk: Errors in block header
at CBlockDiskPos(nFile=0, nPos=8)
2018-02-21 12:47:18 *** Failed to read block
2018-02-21 12:47:18 Error: Error: A fatal internal error occurred, see
debug.log for details
Why and how to resolve... ?
This seems same error before I set GenesisHash and merkleroot as mine.
Very frustrating to see again this error..
Thanks.
you can change genesis params in src/chainparam.cpp adjust nonce value (like +1, +2 ..) until match beneath target
Related
My last context/error I see in my valgrind output file is...
==3030== 1075 errors in context 61 of 540:
==3030== Syscall param ioctl(SIOCETHTOOL,ir) points to uninitialised byte(s)
==3030== at 0x7525248: ioctl (syscall-template.S:84)
==3030== by 0x686A2A7: ??? (in /lib/libpal.so)
==3030== Address 0x96cf958 is on thread 16's stack
==3030== Uninitialised value was created by a stack allocation
==3030== at 0x686A20C: ??? (in /lib/libpal.so)
...but I don't see error contexts 62 - 540. My first thought was maybe in closing the program, valgrind crashed, but after this context it printed the ERROR SUMMARY
ERROR SUMMARY: 9733 errors from 540 contexts (suppressed: 0 from 0)
I don't think it's because we came across a frame without debug info because I can see this exact same issue get hit the first time at the very beginning of my output file. Or maybe the printing of error contexts specifically, is halted when a stacktrace has missing debug info?
Any ideas? Need an additional command line argument for valgrind? I know in helgrind it'll quit after seeing 1000000 errors(something like that) but it explicitly tells you what it's doing.
So for my version of valgrind I also executed helgrind and saw all contexts(647) as expected. I think the problem above is simply a result of valgrind coming across a frame with no debug symbols and saying, "If there's no debug info, I'm moving on"
All of my logs I'm producing end with this same libpal frame at various context numbers 100-something, 200-something, etc.
For a few days now, after using gofmt ("gofmt -w test.go"), I have received an error message with which I cannot do anything:
Error: size of test.go changed during reading (from 18786 to 18742 bytes)
This message appears, although I did not change the program code, but only added a comment. What am I doing wrong?
I have 14 scheduled queries that run hourly from Google Sheets but they fail half of the time. I don't understand the error status though as the queries do run successfully half of the time. The error reads:
Error status: Invalid value Error while reading table: tester-253410.test1.Table_View_2_Agent_Targets, error message: Failed to read the spreadsheet. Errors: Deadline=118.888051456s; JobID: tester-253410:5e59a150-0000-2421-b469-001a1144591c
Is there anything that I can try?
I am suddenly receiving this error message when compiling my app:
elm make src/App.elm --output ../assets/javascripts/elm/App.js
elm: not enough bytes
CallStack (from HasCallStack):
error, called at libraries/binary/src/Data/Binary.hs:212:21 in binary-0.8.5.1:Data.Binary
make: *** [App.js] Error 1
Compiler bug?
Edit: The workaround is to delete elm-stuff. Then it will compile once, and have the same bug on the next attempt.
Pig exists with exit code 7 after printing these 3 lines:
2014-07-16 21:57:37,271 [main] INFO org.apache.pig.Main - Apache Pig version 0.11.0-cdh4.6.0 (rexported) compiled Feb 26 2014, 03:01:22
2014-07-16 21:57:37,272 [main] INFO org.apache.pig.Main - Logging error messages to: ..../pig_1405562257268.log
2014-07-16 21:57:37,627 [main] INFO org.apache.pig.impl.util.Utils - Default bootup file /home/sam/.pigbootup not found
what does this mean?
The INFO messages are normal
The only unusual bit is the exit code (7, see above)
The pig_*.log file does not exist
Is this documented somewhere?
EDIT: the problem was eliminated when I removed the semicolon from the end of the %declare line.
go figure...
You may take a look at the return codes in the source code.
The book Programming Pig also contains a list of their meaning in chapter two.
I copy them here for reference:
0 Success
1 Retriable failure
2 Failure
3 Partial failure - Used with multiquery; see “Nonlinear Data Flows”
4 Illegal arguments passed to Pig
5 IOException thrown - Would usually be thrown by a UDF
6 PigException thrown - Usually means a Python UDF raised an exception
7 ParseException thrown (can happen after parsing if variable substitution
is being done)
8 Throwable thrown (an unexpected exception)