hello

something changed on monero from last commits and there are no connections

can anyone understand something from this

all this are my nodes

Try to exit monerod, remove p2pstate.bin, and restart monerod.

Try exiting even. Can't grammar.

i always do rm -rf .bitmonero

nothing change

my peerlist cant connect between?

Try adding: --exclusive-node 88.198.163.90

If this works, then exit, and restart without it again.

(that's a node I know is running right now)

nope

same

What monerod version ?

latest

compile by me

clone --recursive

I assume that means master ?

yes

maybe this monero-project/monero 7354ffb

add some issue

Well, you can try reverting it I guess.

i dont to say the truth i'm guessing

just before everything was working

It worked for me, but you never know :)

It touches the bit that broke, so worth a try.

u mean that u revert that and nodes are working better??

I am asking you that.

to test ok i'll do it

Oh. I meant the patch worked for me. I could connect and all just fine.

But it might be buggy under some conditions.

u dont have other info if that is buggy just u are guessing ok?

I am gauging the probability of your guess. It sounds like a fair guess to me.

how to revert? im not github guru

git revert 7354ffb8a7ccdfab0c7be186423634ac571ba1cb

When you want to go back to the original state: git reset --hard HEAD^

(assuming you made no manual changes)

i add another patch that is on pulls

Then you're not using master, are you.

If you have many patches, I guess you can bisect:

git bisect start; git bisect bad; git bisect good XXXX

Replace XXXX with the last hash you know was working

i added this

nothing else

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.

Then git will zero down to the bad commit.

And when done, git bisect reset

after excutable will run without problems git bisect reset?

start/reset/good/bad check revisions out. After reset, you'll be back on the rev you were on when you started bisecting.

Ideally, all binaries you build from what git checks out will run.

If one does not, or you can't test whether that prticular binary works or not, then: git bisect skip

do u believe that this can help monero-project/monero #7873

Not too likely.

It'd just crash, typically.

(without the patch)

hello

how to revert without logging on github

why github must logg whatever

monero need some decentralize git

you don't need github

git revert 7354ffb8a7ccdfab0c7be186423634ac571ba1cb

*** Please tell me who you are.

Run

git config --global user.email "you⊙ec"

git config --global user.name "Your Name

this isn't github

that's just git wants to know an author

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.

i know that git is a program

Maybe I should fix it. But something tells me if it hasn't been fixed yet, ut's because it's wanted that way...

there is not smth like patch?

patch -p1 < patch

What are you asking ? If you're getting conflicts, you get to fix them I'm afraid :)

If you're not a hacker, then... you can't.

In which case, go the biscet route.

.merge+ 3572

Added

hi

how to avoid connecting to yourself

back again

after some gdb cjecks i found this monero-project/monero #1377

is possible after so many years

what is the issue again?

this is logged from gdb

../sysdeps/unix/sysv/linux/x86_64/clone.S: No such file or directory

i have my nodes but ther connection problems

there are

does it get fixed by downgrading to v0.17.2.0?

not

desperated i did the hacker as moneromoo said and found that

../sysdeps/unix/sysv/linux/x86_64/clone.S: No such file or directory

it doesn't seem related

it is because daemon crash often

and i found segfault source

post full backtrace

ok

and how long until this is triggered?

from 2-10 sec

on some pc this dont happen

the most strange is this

i put it on 6 and is doing this on 4

on the 2 daemon work without crashing

is it custom compiled?

did you copy paste the blockchain file?

yes all folder

i remove p2pbin not lmdb

and still the same

try the following: use the version from getmonero.org

and then delete the lmdb folder on one of the nodes where you have issues with crashing

and then check if you still have issues

i did this

i use monero binary but same

the most strange is why is running ok on 2 and not in other 4 pcs

there is no known crash like you have posted

at least not reported by anyone else

maybe u need more info from gdb?

do thread apply all bt

ok

`thread apply all bt`

ok

immediately after run?

no need of "where" ,"list"

no once it crashes

ok nothing else?

quit after

once it crashes enter `thread apply all bt` and then post the output like before

ok

ok come back tomorrow again will ask someone else

ok thank you

.merge+ 3683

Added

.merges