-
peter22222
hello together. I have a question. I tried to run monerod from cli, and after 99% of syncing (took ages) I got this error message:
-
peter22222
2020-10-14 05:33:14.797 [P2P8] ERROR default src/common/threadpool.cpp:170 Exception in threadpool job: mprotect faile
-
selsta
peter22222: does the error persist after restarting?
-
selsta
also are you using v0.17.0.1?
-
peter22222
selsta yes it does
-
peter22222
yes i use 0.17.0.1
-
peter22222
INFO logging contrib/epee/src/mlog.cpp:273 New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,daemon.rpc:FATAL,global:INFO,verify:FATAL,serialization:FATAL,daemon.rpc.payment:ERROR,stacktrace:INFO,logging:INFO,msgwriter:INF
-
peter22222
I run it as a systemd service
-
peter22222
worked fine till now
-
peter22222
i just run it manually... seem to work now though very slow. thank you
-
selsta
maybe try restarting your system or so
-
selsta
the last percent is slow due to missing checkpoints
-
peter22222
2020-10-14 09:37:20.251 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1593 Synced 2192924/2208216 (99%, 15292 left, 0% of total synced, estimated 3.8 days left)
-
peter22222
3.8 days haha wtf... monero teaches me patience, lol. thanks for the help, selsta :-)
-
selsta
peter22222: is this with HDD or SSD?
-
peter22222
HDD
-
selsta
It should take way less time with SSD.
-
peter22222
selsta yeah I ve been reading about that too.. i ve been running it for a week already...lol
-
selsta
peter22222: update to v0.17.1.0 which will be released today, it contains fresh checkpoints so it should speed things up
-
peter22222
great advice selsta! thank you!
-
selsta
peter22222: hmm with SSD it possible to completely sync up in under 4 hours
-
peter22222
I heard that too.. but unfortunately I dont have an SSD at the moment, so i tried it with HDD...
-
flipchan
Hey, how does monero handle deadnodes? lets say i use my node and it stores the other nodes ip and I start it again and 30% is not working
-
flipchan
how does it handle dead nodes?
-
dEBRUYNE
The peerlist is refreshed on every startup if I recall correctly
-
moneromooo
It just tries others. If all the nodes you know about are not reachable, it won't connect. But it's likely at least one seed node will be available.
-
flipchan
monoremooo: thanks
-
TheCharlatan
binaryFate there is a merge script for the gitian.sigs repo that first checks the sigs and then makes a signed commit.
-
binaryFate
ok I'll use next time, or better I leave that to you but it's much easier for me to check all hashes and sigs if the PRs are merged and not just open
-
binaryFate
I'm releasing binaries now so I just went forward
-
TheCharlatan
no worries, it's easy to use: verify-merge.py --merge --pull_id 79 --version 0.17.1.0 for example. It also checks the hashes and signatures again.
-
pinheadmz
hey friends. curious what framework you use for the GUI ... is it Qt? Electron?
-
asy
pinheadmz: the gui on getmonero.org is Qt
-
pinheadmz
ty
-
binaryFate
v0.17.1.0 is out on getmonero.org
-
hyc
yay for no more tx_meta messages
-
hyc
2020-10-14 15:14:05.906 E failed to find tx meta: <228d6e9a3de532c4711298f633d22632b64df0e3fffedcee10dd49204db840b5> (will only print once)
-
selsta
-
selsta
-
selsta
luigi1111w: please upload them to github and set as latest release
-
TheCharlatan
I'm amazed at the speed these releases have been baked recently, kudos selsta, binaryFate and luigi1111w!
-
selsta
gitian is quite handy for CLI bins :P
-
selsta
.merge+ 6862 6875 6881 6882 6886 6891
-
xmr-pr
Added
-
selsta
^ these have been merged to branch
-
binaryFate
Can anyone confirm the auto-update triggers for 0.17.1?
-
selsta
binaryFate: I think fluffypony has to update DNS
-
fluffypony
yeah busy with it now
-
selsta
oki
-
fluffypony
and it'll take a while to update for everyone
-
luigi1111w
release notes added, will add binaries soon
-
selsta
nice
-
fluffypony
updates.moneropulse.co. 1 IN TXT "monero-gui:install-win-x64:0.17.1.0:be3b1f07ba86a0d46c27f670b27d936baa5c4e7b68f3dc37349b8f91b073dc6a"
-
fluffypony
does that look correct?
-
selsta
yes
-
fluffypony
ok cool
-
fluffypony
ok records all updated
-
fluffypony
plz check and let me know if you spot anything weird
-
moneromooo
2020-10-14 16:41:15.507W No DNSSEC for updates.moneropulse.co
-
moneromooo
Longstanding. The other three do.
-
moneromooo
And none of the seeds.moneroseeds.* do either.
-
selsta
binaryFate: announce email sent twice, was that intended?
-
selsta
auto updater confirmed working
-
binaryFate
lists were down, we thought previous message wasn't sent nor in queue, but it did went out apparently
-
binaryFate
lists are back, and message twice sorry
-
selsta
np
-
fluffypony
moneromooo: .co dropped DNSSEC support
-
fluffypony
moneroseeds I'll have to investigate
-
fluffypony
we have new moneropulse domains to add
-
fluffypony
.fr .de .no .ch
-
fluffypony
need to check DNSSEC on all of them
-
fluffypony
and then we can decommission .co
-
selsta
for seed node operators: reminder to update to v0.17 (ideally v0.17.1.0)
-
moneromooo
None of those have it atm.
-
xmr-pr
dariensc opened issue #6899: XMR wallet GUI not working anymore... Please HELP!!!
-
xmr-pr
-
hyc
a downside of mining on my public node - random attackers, tripping fail2ban, eats enough CPU to impact my hashrate
-
pinheadmz
"sweep unmixable outputs" -> is this required for all UTXOs created before the last hard fork?
-
dEBRUYNE
pinheadmz: No, it is only relevant for certain outputs created before January 2017
-
pinheadmz
dEBRUYNE ah ok thanks, im consolidating a bunch of old wallets
-
pinheadmz
-
dEBRUYNE
No
-
dEBRUYNE
Before RingCT was activated, output values were in the clear
-
dEBRUYNE
In order to be able to create 'rings', outputs were split according to the power of 10
-
dEBRUYNE
So 12.123 XMR would be outputs of 10, 2, 0.1, 0.02, 0.003
-
dEBRUYNE
An 'unmixable' output is essentially an output for which no ring can be created
-
dEBRUYNE
e.g. an output with value 0.0000024123
-
dEBRUYNE
Or some weird value
-
dEBRUYNE
Anyway, not really on-topic for -dev, so let's continue in #monero
-
Alex_LocalMonero
@dEBRUYNE, moneromooo, would it be unreasonable for me to request that in the future whenever you commit RPC API changes into master you add some sort of specified text to the commit message to allow developers to easily pick out the RPC API changes from the rest of the commits?
-
Alex_LocalMonero
Such as "[RPC API CHANGE] Bla bla bla message"
-
moneromooo
Yes, since we often forget to bump the rpc version when it should be bumped.
-
moneromooo
Well, I do anyway. And I added the thing :/
-
binaryFate
btw map is buggy but I think numbers of upgraded/not-upgraded nodes are correct
community.xmr.to/network
-
binaryFate
coverage is not perfect on all nodes, but gives an idea of proportion
-
hyc
seems like if you care about RPC changes, you just have to check the commit logs for the RPC source files
-
moneromooo
I was just typing that.
-
moneromooo
They're supposed to be backward compatible anyway (unless the major version gets bumped).
-
Alex_LocalMonero
Are there any active public testnet nodes running v0.17.1.0 to connect to? Our testnet daemon is having trouble finding peers.
-
dEBRUYNE
What kind of information is leaked to the node if one imports key images btw?
-
moneromooo
Which key images are yours.
-
moneromooo
So your balance.
-
moneromooo
Wait, not balance.
-
moneromooo
That'd only be the case pre-rct.
-
moneromooo
I suppose one could add random values in the main subgroup. And random key images off the chain. But really... use your own dameon.
-
dEBRUYNE
Thanks, merely asking because someone questioned it on Reddit
-
binaryFate
Alex_LocalMonero: public nodes at
community.xmr.to/nodes.html are running 0.17.1 including testnet
-
xiphon
regarding the asshole nodes: at the first glance it looks to me like an attempt to trace monero txes' origin (i.e. link a tx to ip)
-
xiphon
they don't propogate dandelion txes so, mekes it fallback to fluff
-
xiphon
and given that usually there are more than 1 "asshole" node connected, they then can safely link a tx to your ip
-
xiphon
s/so, mekes/, forcing your node to fallback to "fluff"
-
xiphon
given that they report your height
-
xiphon
the worst case scenario is you running fully synced node
-
lza_menace
what a bunch of dicks
-
xiphon
so just looking at the peers' heights you can't distinguish "assholes" from the good ones
-
xiphon
i'm thinking about increasing the default out_peers limit (it is 8 now)
-
xiphon
at least is the easiest thing we can do to significantly reduce their chances
-
xiphon
pfff.. or just force tor and i2p integration. But syncing over tor is forbidden in the code at the moment
-
selsta
Is syncing over Tor required to avoid tracing tx to IP?
-
xiphon
^ nope
-
selsta
I2P / Tor seed nodes are a good start I guess
-
moneromooo
The assholes I'm talking about always claim your height when you connect to them. They also poitn to each other in their peer lists.
-
moneromooo
They date from way before dandelion fwiw.
-
selsta
Snipa: could you merge 6863 6867 to fix our GUI CI? :)
-
Snipa
Sure, gimme a few.
-
Snipa
.merges
-
xmr-pr
6862 6863 6867 6875 6881 6882 6886 6891
-
Snipa
Ooof, okay then. :D
-
selsta
yea they can wait :P 6863 6867 are important
-
Snipa
Done.
-
selsta
nice