Logs for #trilema-mod6

Go to: #trilema #pizarro #trilema-mod6 #chainstate #eulora

This is the log of #trilema-mod6 : Contained within are the daily on-goings of The Bitcoin Foundation's (http://thebitcoin.foundation) Reference Implementation (trb) development. Do not, under any circumstances, use any code/vpatch/logic/configurations/ideas or otherwise found in this forum. In fact, you should NOT read this at all. Failure to heed these warnings may result in death or dismemberment! ALL ANNOUNCEMENTS, BUSINESS, AND/OR QUESTIONS INVOLVING THE BITCOIN FOUNDATION AND/OR THE BITCOIN REFERENCE IMPLEMENTATION (TRB) WILL TAKE PLACE IN #TRILEMA: YOU HAVE BEEN WARNED.

2018-3-31 | 2018-5-1

mod6: hola!
mod6: there are some messages from earlier today, wanted to re-invite you per usual so you had a heads up
mod6: Hi guys
mod6: So on the 1st, I went ahead and grabbed another core from the running trb process that was having some trouble again.
mod6: I did a disasssembly of the first two calls in the backtrace -- looks like it was in lseek :
mod6: http://p.bvulpes.com/pastes/nIQt2/?raw=true
mod6: any thoughts? more I could do here?
mod6: (more to examine, etc?)
mod6: fwiw, the node has been running fine since the 1st; i restarted the node and I got it caught back up. and has stayed caught up since.
asciilifeform: mod6: plox describe in a bit of detail the most recent 'some trouble'
mod6: same thing as last time.
mod6: fell behind about ~blocks, getting the same stuff in the logs as before.
mod6: iirc, was about the 18th of march.
asciilifeform: i still suspect failing iron
mod6: i was thinking that perhaps being stuck in some sort of lseek call might be realted to the bad disk theory that we were going with before.
mod6: (aparently 0x8 syscall is `lseek')
mod6: wb
diana_coman: thanks! still catching up with the logs here too
diana_coman: apparently the flipside of a short break is a full day spent reading logs
mod6: np, take your time :]
mod6: takes a while to re-immerse.

2018-3-31 | 2018-5-1