11:02:06 <tauntaum> hello
11:03:01 <tauntaum> something changed on monero from last commits and there are no connections
11:03:03 <tauntaum> http://paste.debian.net/1210039/
11:03:22 <tauntaum> can anyone understand something from this
11:07:08 <tauntaum> all this are my nodes
11:11:21 <moneromooo> Try to exit monerod, remove p2pstate.bin, and restart monerod.
11:11:39 <moneromooo> Try exiting even. Can't grammar.
11:14:24 <tauntaum> i always do rm -rf .bitmonero
11:14:35 <tauntaum> nothing change
11:18:10 <tauntaum> my peerlist cant connect between?
11:20:47 <moneromooo> Try adding: --exclusive-node 88.198.163.90
11:20:59 <moneromooo> If this works, then exit, and restart without it again.
11:21:09 <moneromooo> (that's a node I know is running right now)
11:26:33 <tauntaum> nope
11:26:36 <tauntaum> same
11:27:44 <moneromooo> What monerod version ?
11:29:51 <tauntaum> latest
11:29:56 <tauntaum> compile by me
11:30:04 <tauntaum> clone --recursive
11:30:27 <moneromooo> I assume that means master ?
11:30:42 <tauntaum> yes
11:30:49 <tauntaum> maybe this https://github.com/monero-project/monero/commit/7354ffb8a7ccdfab0c7be186423634ac571ba1cb
11:30:58 <tauntaum> add some issue
11:31:34 <moneromooo> Well, you can try reverting it I guess.
11:32:05 <tauntaum> i dont to say the truth i'm guessing
11:32:13 <tauntaum> just before everything was working
11:32:22 <moneromooo> It worked for me, but you never know :)
11:32:31 <moneromooo> It touches the bit that broke, so worth a try.
11:33:12 <tauntaum> u mean that u revert that and nodes are working better??
11:33:45 <moneromooo> I am asking you that.
11:33:57 <tauntaum> to test ok i'll do it
11:34:07 <moneromooo> Oh. I meant the patch worked for me. I could connect and all just fine.
11:34:20 <moneromooo> But it might be buggy under some conditions.
11:35:09 <tauntaum> u dont have other info if that is buggy just u are guessing ok?
11:36:16 <moneromooo> I am gauging the probability of your guess. It sounds like a fair guess to me.
11:37:22 <tauntaum> how to revert? im not github guru
11:38:03 <moneromooo> git revert 7354ffb8a7ccdfab0c7be186423634ac571ba1cb
11:38:23 <moneromooo> When you want to go back to the original state: git reset --hard HEAD^
11:38:29 <moneromooo> (assuming you made no manual changes)
11:39:01 <tauntaum> i add another patch that is on pulls
11:39:26 <moneromooo> Then you're not using master, are you.
11:39:38 <moneromooo> If you have many patches, I guess you can bisect:
11:39:52 <moneromooo> git bisect start; git bisect bad; git bisect good XXXX
11:40:02 <tauntaum> https://github.com/monero-project/monero/pull/7774
11:40:03 <moneromooo> Replace XXXX with the last hash you know was working
11:40:05 <tauntaum> i added this
11:40:16 <tauntaum> nothing else
11:40:40 <moneromooo> Then git will check verisons out, just build and test, and every time, enter either "git bisect good" or "git bisect bad" depending on whether it works or not.
11:40:49 <moneromooo> Then git will zero down to the bad commit.
11:42:30 <moneromooo> And when done, git bisect reset
11:52:20 <tauntaum> after excutable will run without problems git bisect reset?
11:53:00 <moneromooo> start/reset/good/bad check revisions out. After reset, you'll be back on the rev you were on when you started bisecting.
11:53:20 <moneromooo> Ideally, all binaries you build from what git checks out will run. 
11:53:42 <moneromooo> If one does not, or you can't test whether that prticular binary works or not, then: git bisect skip
11:58:18 <tauntaum> do u believe that this can help https://github.com/monero-project/monero/pull/7873
12:00:50 <moneromooo> Not too likely.
12:01:07 <moneromooo> It'd just crash, typically.
12:01:12 <moneromooo> (without the patch)
17:20:47 <tauntaum> hello
17:20:56 <tauntaum> how to revert without logging on github
17:21:10 <tauntaum> why github must logg whatever
17:21:29 <tauntaum> monero need some decentralize git
17:21:34 <selsta> you don't need github
17:21:58 <tauntaum> git revert 7354ffb8a7ccdfab0c7be186423634ac571ba1cb
17:21:59 <tauntaum> *** Please tell me who you are.
17:21:59 <tauntaum> Run
17:22:00 <tauntaum>   git config --global user.email "you⊙ec"
17:22:00 <tauntaum>   git config --global user.name "Your Name
17:22:59 <selsta> this isn't github
17:23:05 <selsta> that's just git wants to know an author
17:23:59 <moneromooo> git is a program. github is a website that people who use git can use. Those are two different things. That said, this prompt is damn annoying to me too.
17:24:37 <tauntaum> i know that git is a program
17:24:39 <moneromooo> Maybe I should fix it. But something tells me if it hasn't been fixed yet, ut's because it's wanted that way...
17:25:27 <tauntaum> there is not smth like patch?
17:25:56 <tauntaum> patch -p1 < patch
17:26:43 <moneromooo> What are you asking ? If you're getting conflicts, you get to fix them I'm afraid :)
17:27:09 <moneromooo> If you're not a hacker, then... you can't.
17:27:25 <moneromooo> In which case, go the biscet route.
18:07:33 <selsta> .merge+ 3572
18:07:33 <xmr-pr> Added
19:55:36 <panua44> hi
19:59:19 <panua44> how to avoid connecting to yourself
20:17:27 <tauntaum> back again
20:17:48 <tauntaum> after some gdb cjecks i found this https://github.com/monero-project/monero/issues/1377
20:18:00 <tauntaum> is possible after so many years
20:19:08 <selsta> what is the issue again?
20:19:37 <tauntaum> this is logged from gdb
20:19:49 <tauntaum> ../sysdeps/unix/sysv/linux/x86_64/clone.S: No such file or directory
20:20:41 <tauntaum> i have my nodes but ther connection problems
20:20:52 <tauntaum> there are
20:20:54 <selsta> does it get fixed by downgrading to v0.17.2.0?
20:21:02 <tauntaum> not
20:21:26 <tauntaum> desperated i did the hacker as moneromoo said and found that 
20:21:28 <tauntaum> ../sysdeps/unix/sysv/linux/x86_64/clone.S: No such file or directory
20:21:47 <selsta> it doesn't seem related
20:22:11 <tauntaum> it is because daemon crash often
20:22:30 <tauntaum> and i found segfault source
20:22:49 <selsta> post full backtrace
20:23:09 <tauntaum> ok
20:30:07 <tauntaum> http://paste.debian.net/1210150/
20:31:31 <selsta> and how long until this is triggered?
20:32:07 <tauntaum> from 2-10 sec
20:32:21 <tauntaum> on some pc this dont happen
20:32:29 <tauntaum> the most strange is this
20:32:47 <tauntaum> i put it on 6 and is doing this on 4
20:33:03 <tauntaum> on the 2 daemon work without crashing
20:33:57 <selsta> is it custom compiled?
20:34:05 <selsta> did you copy paste the blockchain file?
20:34:15 <tauntaum> yes all folder
20:34:29 <tauntaum> i remove p2pbin not lmdb
20:34:38 <tauntaum> and still the same
20:35:33 <selsta> try the following: use the version from getmonero.org
20:35:46 <selsta> and then delete the lmdb folder on one of the nodes where you have issues with crashing
20:35:54 <selsta> and then check if you still have issues
20:36:11 <tauntaum> i did this
20:36:26 <tauntaum> i use monero binary but same
20:36:56 <tauntaum> the most strange is why is running ok on 2 and not in other 4 pcs
20:37:13 <selsta> there is no known crash like you have posted
20:37:18 <selsta> at least not reported by anyone else
20:37:51 <tauntaum> maybe u need more info from gdb?
20:38:04 <selsta> do thread apply all bt
20:38:17 <tauntaum> ok
20:38:25 <selsta> `thread apply all bt`
20:39:13 <tauntaum> ok
20:39:54 <tauntaum> immediately after run?
20:40:04 <tauntaum> no need of "where" ,"list"
20:40:14 <selsta> no once it crashes
20:40:59 <tauntaum> ok nothing else?
20:41:02 <tauntaum> quit after
20:42:04 <selsta> once it crashes enter `thread apply all bt` and then post the output like before
20:42:16 <tauntaum> ok
20:45:20 <tauntaum> http://paste.debian.net/1210153/
20:47:27 <selsta> ok come back tomorrow again will ask someone else
20:48:40 <tauntaum> ok thank you
23:02:14 <selsta> .merge+ 3683
23:02:14 <xmr-pr> Added
23:25:48 <selsta> .merges
23:25:48 -xmr-pr- 3096 3282 3452 3471 3472 3473 3477 3481 3572 3679 3683