Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 14:22
    dvdplm synchronize #11312
  • 14:22

    dvdplm on chore

    Be precise about version requir… (compare)

  • 14:20
    dvdplm edited #11312
  • 14:16
    dvdplm labeled #11312
  • 14:16
    dvdplm unlabeled #11312
  • 14:16
    dvdplm review_requested #11312
  • 14:16
    dvdplm ready_for_review #11312
  • 14:15
    dvdplm synchronize #11312
  • 14:15

    dvdplm on chore

    Override all of parity-common f… (compare)

  • 13:55
    dvdplm synchronize #11312
  • 13:55

    dvdplm on chore

    Fix atomicity violation in netw… Enable EIP-2384 for ice age har… [secretstore] migrate to versio… and 5 more (compare)

  • 10:36
    dvdplm commented #11335
  • 10:36
    dvdplm opened #11339
  • 10:35
    soc1c commented #11337
  • 10:34
    dvdplm commented #11337
  • 10:23
    dvdplm commented #11338
  • 09:53
    soc1c synchronize #11338
  • 09:53

    soc1c on s1-classic-aztlan

    ethcore/res: update bootnodes f… (compare)

  • 09:45
    soc1c commented #11337
  • 09:44
    soc1c commented #11338
joshua-mir
@joshua-mir
but ultimately that would be slower than a warp sync
Nick Savers
@nicksavers
@imxeno it depends how many blocks you want to go back. Usually you can reset up to 64 blocks. parity db reset 30 for example
AFAIK it depends on your pruning level. If you have an archive node, you should be able to reset all the way back to block 1. Although I wonder how long that would take.
Piotr Adamczyk
@imxeno
@joshua-mir so essentially it's like regular sync just without downloading all the blocks from the network and instead "syncing" them from local disk?
Nick Savers
@nicksavers
Isn't there an export / import when you don't verify the block history? It's your own backup, so why process the blocks?
joshua-mir
@joshua-mir
@imxeno yep exactly; @nicksavers you still need to calculate/process state, and you can't export state at an arbitrary block
but you can just move your db manually, parity assumes it's /chains/[chain]/db folder is verified
Nick Savers
@nicksavers
@joshua-mir Do you have a Docker image that builds Parity from source? I'm currently using the README only, but am still having trouble with the lto = true setting
joshua-mir
@joshua-mir
https://github.com/paritytech/parity-ethereum/tree/master/scripts/docker one of the dockerfiles here. I've had the best experience with the alpine image - the hub image is what we build for dockerhub
Nick Savers
@nicksavers
Perfect, thanks
Joaquin Diaz
@joadr
Hello, my node is failing to die SIGTERM... it is not dying... more than 5 minutes have passed science I tried to stop it with "kill -15 23286"
Last time this happened, I killed it with "kill -9 23286" and database got corrupted
Any idea how can I stop it without corrupting the database?
joshua-mir
@joshua-mir
@joadr to be safe, I'd go offline if possible, and then wait another minute or two before killing it.
Joaquin Diaz
@joadr
I will try that... hope it doesn't corrupt, it's and archive node and takes years to sync :/
Joaquin Diaz
@joadr
not dying :(
Genysys
@Genysys
can you check the logs to see if its still mining?
@joadr
Joaquin Diaz
@joadr
I don't use if for mining
Genysys
@Genysys
sorry producing blocks
like any log output
*processing blocks
i would make a couple of back up and sigkill it
Joaquin Diaz
@joadr
I'm tailing the logs and doesn't seem to be syncing... the last lines are from a while ago
Also... I suspect this happened because the data drive got full, I increased it and I saw with the RPC that it wasn't getting new blocks.. so I'm trying to restart it
Genysys
@Genysys
ah
its defintely corrypts when the data drive gets full
Joaquin Diaz
@joadr
at least last 100 lines are
eth_accounts is deprecated and will be removed in future versions: Account management is being phased out see #9997 for alternatives.
Genysys
@Genysys
its happend to me before
run df
Joaquin Diaz
@joadr
yup, I already increased disk size and now I have like 100GB of available space
Genysys
@Genysys
or journalctl -r
it sounds like its constanly restarting
are you running it in a daemon?
or systemctl?
joshua-mir
@joshua-mir
no, he'd be getting that message if he was calling RPCs in eth_accounts
so I wouldn't worry about the logs
Joaquin Diaz
@joadr
I actually get those logs and don't use eth_accounts
will sigkill and see what happens... for starting it again should I just remove the lock file?
joshua-mir
@joshua-mir
(unless you didn't know you were calling those RPCs, in which case going offline might help 😅)
Joaquin Diaz
@joadr
ufff! it's syncing
my heart stopped for a while hahahah
Thanks guys
:)!
Last time we didn't have a node for days until quiknode allowed me to use one of theirs
also, I still get this log:
eth_accounts is deprecated and will be removed in future versions: Account management is being phased out see #9997 for alternatives.
and we don't use that anywhere, do you know why do I get this log? or how can I track which IP or which endpoint is logging that?
joshua-mir
@joshua-mir
-l rpc=debug?
lzhou1110
@lzhou1110
Hi, I was trying to filter transactions to a specific address today using parity_pendingTransactions api. I passed the parameters stated exactly as the example shown on https://wiki.parity.io/JSONRPC-parity-module#parity_pendingtransactions, but it seems it still returns all pending transactions.
Just wondering if anyone knows what is happening :)