freenode #monero

11 Mar 2020

[XMR] Be excellent to each other and welcoming to newcomers || getmonero.org || Dev: #monero-dev || Pool related: #monero-pools || Price chat: #monero-markets || OTC: #monero-otc || People can & do log this channel || DON'T USE Changelly, Freewallet or Minergate: reddit.com/r/monero/wiki/avoid

• 07:37
  spoke0_
  Is it possible that an rpc call to rescan_spent will delete the destination field of all past outgoing transaction?
• 07:43
  selsta
  IIRC yes
• 07:47
  spoke0_
  Is it also possible that this happens during importing keyimages/outputs?
• 10:09
  snackoverflow
  is monero a bitcoin fork?
• 10:10
  aqua42
  no
• 10:15
  tryphe
  monero, it's got what plants crave!
• 10:26
  aqua42
  ring signatures?
• 10:27
  asymptotically
  privacy! plants don't like to grow while you're watching
• 10:45
  aqua42
  🌵👀
• 11:38
  asymptotically
  is there a way to start a new private testnet/stagenet from the latest fork or block version?
• 12:19
  moneromooo
  spoke0_: no
• 14:17
  newyearday
  hello
• 17:30
  eddyH
  anyone managed to recover from a coredump when running monerod. managed to get 50% blockchain download yesterday, today it just core dumps.
• 17:30
  selsta
  you most likely have to sync from scratch
• 17:31
  eddyH
  start over again ?
• 17:31
  selsta
  core dump usually means that your computer crashed / didn’t shut down properly
• 17:31
  moneromooo
  Yeah, that db is annoying, it's fast as it saves the "links" data directly, but it means segfaults and bus errors when it's bad :/
• 17:31
  moneromooo
  It's supposed to never corrupt, but in practice it can't avoid it.
• 17:31
  eddyH
  so shall i start over and run in safe mode ?
• 17:32
  moneromooo
  Could be a bug in monero too though.
• 17:32
  eddyH
  i raised it on github, but log file says nothing, where is core dump nowadays
• 17:33
  moneromooo
  You can try running once with --db-salvage, might help.
• 17:33
  eddyH
  tried that :)
• 17:33
  eddyH
  no luck
• 17:33
  moneromooo
  Then nothing left but re-download.
• 17:34
  eddyH
  ok
• 17:35
  moneromooo
  If you're on crashy/windows, I guess you can exit from time to time and backup the partly synced db, then restart from that next time you run into this :)
• 17:37
  eddyH
  im on ubuntu. i noticed when i control D the terminal it seemed to hang.
• 17:37
  eddyH
  no smooth closedown
• 17:38
  selsta
  does ctrl + c work?
• 17:39
  eddyH
  same with that as well, hangs
• 17:39
  moneromooo
  An all thread stack trace would be helpful if that happens again.
• 17:40
  eddyH
  ok, see if i can get one of those.
• 17:41
  moneromooo
  (thread apply all bt full)
• 18:06
  Adriel
  If I am running in rpc mode, how do I see the hash rate of all my workers?
• 18:06
  Adriel
  in monerod
• 18:08
  Adriel
  is there any documentation that explains how the rpc daemon mode works besides the api documentation? I searched but could not find anything.
• 18:09
  nioc
  Adriel: there is also #monero-pools for a possible answer
• 18:10
  nioc
  Much off topic and trolling along with knowledge :)
• 18:10
  Adriel
  ?
• 18:10
  Adriel
  what is off topic and trolling?
• 18:15
  lza_menace
  Adriel: he means your question might be better suited in #monero-pools channel but that they go off topic a lot and occasionally troll
• 18:15
  Adriel
  ohhh ok
• 18:16
  Adriel
  they said it cant be done
• 18:16
  Adriel
  monerod just doesnt do it
• 18:17
  lza_menace
  yeah, it depends on the mining software you're using ,really
• 18:17
  lza_menace
  i'll carry the convo in the other channel
• 18:20
  fuwa
  Adriel: web.getmonero.org/resources/develop…uides/daemon-rpc.html#mining_status
• 18:23
  Adriel
  yea that just shows the status of the internal miner
• 18:23
  Adriel
  not any rpc clients that are mining through the daemon
• 18:23
  fuwa
  daemon couldn't possibly know that
• 18:24
  Adriel
  yea the workaround that sounds best is to use a proxy and have that connect to the daemon
• 18:24
  Adriel
  then I can get full stats at the proxy
• 18:24
  fuwa
  right
• 18:24
  Adriel
  anyway I think I have enough to go on now, thanks very much for the recommendation for the other channel :)
• 18:25
  nioc
  meow
• 20:02
  azy2
  monerod: W Failed to commit a transaction to the db: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid, E Exception in cleanup_handle_incoming_blocks: Failed to commit a transaction to the db: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
• 20:03
  moneromooo
  OS crash or power loss ?
• 20:07
  azy2
  i put it to sleep/hibernate regularly
• 20:12
  moneromooo
  I think that should be fine (unless buggy).
• 20:13
  selsta
  azy2: self compiled or release binaries?
• 20:13
  azy2
  release
• 20:14
  moneromooo
  Or it could be that odd bug with some error message scribbling over the db.
• 20:14
  marmulak
  I always compile
• 20:14
  selsta
  I think you can send the DB to hyc (if he has time)
• 20:14
  moneromooo
  And with what version of libunbound ?
• 20:15
  moneromooo
  Not that I know which one is suspected anyway :P
• 20:15
  azy2
  how would i find that out?
• 20:16
  selsta
  release binaries should have ok unbound
• 20:16
  fuwa
  yeah
• 20:16
  selsta
  though no idea if unbound even is / was the problem
• 21:00
  xmrpow
  Hey, guys might it be possible that monerod cant run stable on 2gb ram without the swap activated?
• 21:01
  xmrpow
  Im running my monerod on 4gb ram machine that is always in sync for some days but then it suddenly stops
• 21:01
  xmrpow
  With memory allocation failed
• 21:01
  xmrpow
  Should be a ram problem,right?
• 21:14
  hyc
  given that the corruption we saw consisted of libunbound debug msgs that normally go to stderr, it's quite certain that the offending data came from libunbound
• 21:14
  hyc
  whether it was libunbound or something else that messed up stderr, dunno
• 21:15
  selsta
  updating unbound to the latest release would probably be a good idea
• 21:15
  selsta
  they had an audit and fixed a lot of bugs
• 21:15
  hyc
  yeah, I guess we ought to do that before v0.15.1
• 21:17
  selsta
  yep