20900+ entries in 0.043s
mod6: hrm. maybe im misinterpreted the output
mod6: mine was 25 seconds behind or something.
mod6: ok, i had thought that I read somewhere that he said he was gonna let it be until he could examine the fork closer. I never could find it in the log though. Thought maybe I imagined it.
mod6: So I was stuck on block: 363734, then updated time, restarted bitcoind, now seem be be stuck on 363736 for >24 hours.
mod6: asciilifeform: what did you do to bypass this, i thought i read you reconnected with -addnode or did you just /wait/ for a long period?
☟︎ mod6: yeah, im fairly sure that he did.
mod6: I don't see any attempt to reorg... but i'm gonna increase the db locks * 2 and see if that changes anything.
mod6: height=363734 << wedged here for ~2 hours.
mod6: grab those, verify, unpack; beware that you need to drop openssl/bdb/boost in distfiles by hand. and ascii_field's script doesn't want boost.tar.gz, wants boost.tar.bz
mod6: yeah, that auto.sh has problems there.
mod6: you need to use "stator.sh" that comes with the stator tarball
mod6: next, like .cn, selling banned
mod6: trades haulted, no suprise there.
mod6: <+gernika> mod6 I've attempted syncing on OpenBSD again and am now past block 168000 and have reached 185126. It's going very very slowly though. << good to hear though
☟︎ mod6: thestringpuller: if they did, it'd be an altcoin aka; marscoin, uranuscoin etc
mod6: yes, this is fantastic really.
mod6: no idea. i just swapped that stuff out for the fullpath, but gernika reminded me that one can usese readlink -f
mod6: i screwed up i don't have realpath installed.
mod6: phf: do you patches depend on anything besides stator?
mod6: haha, sounds familiar.
mod6: i used to be fairly fluent 10 years ago, now. not so much lol.
mod6 has to ramp up on espanol for c4
mod6: lemme try this out :]
mod6: read your readme... so yeah, months and months ago I was able to build a dynamic bitcoind on openbsd, but that was the exact issue after statically linked: seg fault.
mod6: ok, so I should just use your patches just posted then
mod6: it was from a patch, but not from the email you just sent in...
mod6: phf: i built on 5.6 but I can't seem to get mine to be be statically built :(
mod6: it was last december.
mod6: for those who don't remember, we used to get stuck at block 252`450 before with only 10000 locks set
mod6: i'll have to see when i get there i guess.
mod6: here's something I missed: log.bitcoin-assets.com/?date=04-07-2015#1187292
mod6: alright, as you wish. let me know how it goes.
mod6: i seem to remember asciilifeform switching over to -addnode after he got stuck. but let's see what he says about it. i'll probably hit the same issue myself.
mod6: I'm currently a bit distracted. I'll re-read all of this discussion on my way back and think about it.
mod6: <+ascii_field> mod6: anything that requires the operator to even know that routers exist is inapplicable for pogo << yeah was reading what you guys were saying. basically why I didn't bring it up. too hard for mom & pop.
mod6: <+mircea_popescu> mod6 i think this is related to "askl your isp" << yeah.
mod6: maybe you set your router to respond to this? i dunno. was a passing thought.
mod6: but... if it's behind a NAT< then you can control the default route
mod6: it returns a timestamp
mod6: as dumb as it sounds, i thought about ICMP 13 (dispite it being often fw'd) and checking TS against default route.
mod6: yeah. haven't been able to follow for the last 45 minutes though.
mod6: ( & perhaps a different tool )
mod6: oh was just laughing about that link last night: The loops basically iterate 72 times << 72 i guess. heh
mod6: it checks 71 times!
mod6: i tried to build stator on obsd again, still ended up with some .so's in the output binary.
mod6: should be done in about 24 hours or so?
mod6: Maybe try to make sense of it somehow.
mod6: gernika: it makes sense that you can not dump 168`001. keep it posted at that url for a few days. I wanna see if I can replicate with obsd on my side (as soon as I can get it built statically), or when I free up my aws environment from its current sync process (if that should come first). I can use the aws one to cut out block 168`000 and compare the two.
mod6: <+mircea_popescu> the lulz and the win of our times ;/ << aint this the truth
mod6: i'll try again with obsd again tomorrow.
mod6: gernika: hmm. weird. i might hvae screwed something up in there.
mod6: gernika: it might be helpful to patch in the dump block so we can examine your block(s) 168`000 & 168`001 and see what's going on there.
mod6: mircea_popescu: yeah, we totally were. but it seems this time its a different error and a different txid!
mod6: gernika: yeah, just did `su`...
mod6: mircea_popescu: (this is compiling stator on openbsd)
mod6: cc1plus: out of memory allocating 46376 bytes after a total of 0 bytes << lol
mod6: openbsd requires gmake to be in the stator.sh, not make.
mod6: oh i just solved my own problem. derp.
mod6: did you see the same?
mod6: huh. this is the error we got, different txid and different error, but still, ~weird~: log.bitcoin-assets.com//?date=05-02-2015#1007102
mod6: you are using ssl 1.0.1g with stator right?
mod6: im looking for the exact txid we hit.. it's somewhere in the log im sure.