log☇︎
620 entries in 0.671s
asciilifeform: ;;later tell mircea_popescu dulap: 'reboot system boot 2.6.32-431.el6.x Tue Sep 1 03:05 - 10:05 (07:00)' << phuctor is dead in the water until this stops.
assbot: Logged on 01-09-2015 01:00:40; asciilifeform: mircea_popescu: dulap ~still~ trailing by 35 blx
asciilifeform: mircea_popescu: dulap ~still~ trailing by 35 blx ☟︎
ascii_field: dulap!
asciilifeform: ;;later tell mircea_popescu (corrected) dulap still behind; i had a thought that the very possibility of this problem is an atrocious idiocy - why should an infrastructural node (so0opernoude!!!) rely on the whims of wild animals to learn latest blocks? we need the 'nobles'-never-disconnect table. ☟︎
asciilifeform: ;;later tell mircea_popescu dulap still behind; i had a thought that the very possibility of this problem is an atrocious idiocy - why should an infrastructural node (so0opernoude!!!) rely on the whims wild animals to lean latest blocks? we need the 'nobles'-never-disconnect table.
asciilifeform: in other nyooz, dulap now behind by 'only' 32 blocks.
assbot: Logged on 29-08-2015 02:48:54; mircea_popescu: dulap may be the latest piece of software in actual use that doesn't actually benefit from periodic rebooting
asciilifeform: ;;later tell mircea_popescu dulap is a quad-core machine. current 'werker' (phuctor) uses strictly a single core, at the maximum. but what is happening appears to be bus cycle starvation (shared cores share a cache; and at any rate all processes share a single ram bus)
assbot: Logged on 29-08-2015 19:48:13; asciilifeform: ;;later tell mircea_popescu potentially interesting observation: dulap has been ~50 blocks behind semi-permanently since reboot. in as far as i can tell, it is not mainly from 'blackholing' but due to cpu starvation! on account of phuctor re-grinding the product...!
assbot: Logged on 29-08-2015 02:22:08; asciilifeform: mircea_popescu et al: dulap rebooted today for no reason known to me.
asciilifeform: ;;later tell mircea_popescu potentially interesting observation: dulap has been ~50 blocks behind semi-permanently since reboot. in as far as i can tell, it is not mainly from 'blackholing' but due to cpu starvation! on account of phuctor re-grinding the product...! ☟︎
asciilifeform: in other nyooz, dulap is still ~50 blox behind
phf: asciilifeform: i thought dulap hosting was stateside. shame, tummy people are excellent at what they do
phf: <asciilifeform> mircea_popescu et al: dulap rebooted today for no reason known to me. << if you start evaluating new hosting solutions, try these guys http://www.tummy.com. uptime on my box 529 days
mircea_popescu: dulap may be the latest piece of software in actual use that doesn't actually benefit from periodic rebooting ☟︎
mircea_popescu: dulap may be the latest piece of software in actual use that yeah
asciilifeform: dulap has had three in almost as many months.
asciilifeform: mircea_popescu et al: dulap rebooted today for no reason known to me. ☟︎
mircea_popescu: anyway, the whole as is down, being worked on, dulap should be back later.
asciilifeform: ;;later tell mircea_popescu dulap is down - whole machine.
asciilifeform: ~~97~~ connections on dulap
asciilifeform: in other nyooz, 72 connections on dulap
cazalla: asciilifeform, are these AcceptToMemoryPool() : ConnectInputs failed errors a problem? also is it normal behaviour to gain so many new connections from other ips? i thought i'd only be syncing from dulap http://dpaste.com/3KHQH2A.txt
asciilifeform: 56/59/27 (dulap/zulag/incitatus), all 3 fully synced
asciilifeform: in other nyooz, 56 connections each on dulap and zulag.
asciilifeform: dulap is getting reactor rods swapped
ben_vulpes: slurping dregs from dulap
ben_vulpes: aha, dulap.b-a.link
ben_vulpes: hm i can't find the dulap dns record in search.bitcoin-assets.com
assbot: Logged on 01-08-2015 05:27:46; asciilifeform: 'dulap' and 'zoolag' now running 80000.
asciilifeform: aaand dulap is back in business. for now...
asciilifeform trying to restart node on dulap, bitcoin won't even eat SIGTERM
asciilifeform: in other nyooz, dulap ~STILL~ blackholed
asciilifeform: dulap ~still~ blackholes
asciilifeform: dulap ~still~ in black hole.
asciilifeform: confirmed, neither zoolag nor incitatus is presently connected to dulap
asciilifeform: think of it this way: zoolag and incitatus were plugged into dulap with -addnode. but this was not enough
asciilifeform: dulap ~STILL~ wedged
asciilifeform: (in unrelated newz, dulap is getting blackholed again)
assbot: Logged on 23-07-2015 14:58:22; kakobrekla: dulap.b-a.link, incitatus.b-a.link, zoolag.b-a.link is set
asciilifeform: 50 connections, presently (dulap - 40; incitatus - 32)
asciilifeform: like dulap
asciilifeform: dulap appears to have fallen into an nsa silent hole again...
asciilifeform: 'dulap' and 'zoolag' synced still.
asciilifeform: dulap synced
asciilifeform: dulap unwedged.
asciilifeform: dulap is in nsa hell
asciilifeform: 'dulap' and 'zoolag' now running 80000. ☟︎
assbot: Logged on 31-07-2015 15:01:30; mircea_popescu: <gribble> Sent 57 minutes ago: <asciilifeform> dulap desperately needs to not be the only industrial-sized therealbitcoin node. phuctor is severely i/o starved << so help hanbot get it going.
mircea_popescu: <gribble> Sent 57 minutes ago: <asciilifeform> dulap desperately needs to not be the only industrial-sized therealbitcoin node. phuctor is severely i/o starved << so help hanbot get it going. ☟︎
assbot: dpaste: 1MEA7DD: therealbitcoin on dulap since 7/5 ... ( http://bit.ly/1LUNeLx )
asciilifeform: ;;later tell mircea_popescu dulap desperately needs to not be the only industrial-sized therealbitcoin node. phuctor is severely i/o starved.
asciilifeform: dulap!
mod6: ok restarting & connecting to dulap and incitatus
mod6: <+ascii_field> http://btc.yt/lxr/satoshi/source/src/net.cpp#1263 << Ah! so just -connect=dulap -connect=other
ascii_field: dulap is 100% up to date chainwise
mod6: yeah dulap
ascii_field: mod6: -addnode from dulap ?
mod6: and it sync'd against your dulap with -verifyall all the way up to 365454, then wedged for ~36 hours or so. but this evening, restarted it and continued sync'ing just fine.
asciilifeform: dulap, yes.
mod6: i thought that was the dulap?
assbot: Logged on 23-07-2015 14:58:22; kakobrekla: dulap.b-a.link, incitatus.b-a.link, zoolag.b-a.link is set
kakobrekla: dulap.b-a.link, incitatus.b-a.link, zoolag.b-a.link is set ☟︎☟︎
asciilifeform: dulap has 71 peers which is a new record.
asciilifeform: mod6: dulap (s.nsa flagship node) unwedged on july 10 when i fixed its clock. 'zoolag' was never wedged in its whole life thus far.
asciilifeform: http://log.bitcoin-assets.com/?date=21-07-2015#1208260 << 1631edac873633135b9eb9b8214d6d2b30d708d00ec4dd1db6a9bf09f384551b (on 'dulap' AND 'zoolag') ☝︎
assbot: Logged on 05-07-2015 14:50:21; asciilifeform: ;;later tell mircea_popescu node on dulap is still wedged. and apparently this is not a terribly good place for a node, phuctor gets i/o-starved and dies
mircea_popescu: dulap
asciilifeform: in other nyooz, 363954 on dulap
asciilifeform: ;;later tell mircea_popescu node on dulap appears to have unwedged. by itself. or perhaps somebody fed it
asciilifeform: ;;later tell mircea_popescu node on dulap is still wedged. and apparently this is not a terribly good place for a node, phuctor gets i/o-starved and dies ☟︎
asciilifeform: ;;later tell mircea_popescu public node on dulap.
ascii_modem: gonna plug in the one on dulap when i get home
asciilifeform: ;;later tell mircea_popescu i built stator on dulap just now. unchanged from public recipe other than the 'realpath' thing (mentioned earlier.) same process ought to work on your other centos boxes. it will run as a public node as soon as i shove a blockchain in there.
asciilifeform: http://log.bitcoin-assets.com/?date=04-07-2015#1186165 << my idea is to bring up node on dulap as soon as syncs ☝︎
asciilifeform: pc keyboard, esp. the piece of shit most folks use, is a veritable 'dulap' for hands, yes
mircea_popescu: made your own dulap have you
assbot: 40 results for 'dulap' : http://s.b-a.link/?q=dulap
asciilifeform: !s dulap
mircea_popescu: asciilifeform to answer earlier q : i think for thius purpose (running on dulap etc) static glibc is exactly right.
assbot: Logged on 28-06-2015 02:30:30; asciilifeform: if mircea_popescu asks, this turd will be deployed to dulap (s.nsa box)
asciilifeform: if mircea_popescu asks, this turd will be deployed to dulap (s.nsa box) ☟︎
assbot: Logged on 06-05-2015 22:20:53; ascii_field: ;;later tell mircea_popescu ERROR: certificate common name “keys.mattrude.com” doesn’t match requested host name “keyserver.mattrude.com” << when fetching fresh sks from dulap
mircea_popescu: usually it's resolved with "if you ever do this again im going to beat you with a wet dulap"
asciilifeform: http://log.bitcoin-assets.com/?date=02-06-2015#1151226 << looks like a dude 'enjoying' a homemade dulap !? ☝︎
asciilifeform: forget for two weeks and it's the dulap !
asciilifeform: s cock in dulap.
asciilifeform: ;;later tell mircea_popescu i've developed a heuristic. see litmus.py on dulap.
asciilifeform: mircea_popescu: at this point i must note that i have no idea if i'm connected to shakespeare or another man by the same name, when i talk to dulap
mircea_popescu: asciilifeform o btw dulap's back, magically.
asciilifeform: ;;later tell mircea_popescu dulap down ?
asciilifeform: ;;later tell mircea_popescu keys are batch-converting on dulap. after they're done, will be pumped in locally.
asciilifeform: http://dpaste.com/1X7FSYP << on dulap
asciilifeform: not dulap and (not mybox)
asciilifeform loading locally, will push to dulap - but this is retarded and ought to be addressed
asciilifeform: but not what we get on dulap.
asciilifeform: but would go substantially faster if done from dulap local
ascii_field: ;;later tell mircea_popescu ERROR: certificate common name “keys.mattrude.com” doesn’t match requested host name “keyserver.mattrude.com” << when fetching fresh sks from dulap ☟︎
gribble: http://www.urbandictionary.com/define.php?term=dulap | pronounced: "doo-lap" -noun 1. the soft area of skin between the chin and neck. " Man, I got her dulap so good today at lunch!" by JourneeLee March 14, 2007.