"there are pending operations on that name"

[m4rkiz]

i tried to register my first .bit domain, after couple tries (see below) it all seemed ok, namecoins are gone from my wallet but there is no sign of it in http://explorer.dot-bit.org

any attempt to name_update or name_firstupdate returns

Code: Select all

error: {"code":-1,"message":"there are pending operations on that name"}

i tried to register another, different one and it all went ok

so i checked what i have with name_list but it returns only second domain

next thing i did is set up namecoin daemon on another machine, transferred some funds there and tried to start again with first name, but that returns same error (no namecoins were lost\charged on second attempt though)

can lack

Code: Select all

d/

before domain name in first try cause that? [/color]

couldn't find anything about that error except: http://forum.bitcoin.org/index.php?topi ... #msg141347
but there is no solution too

[m4rkiz]

i did

Code: Select all

deletetransaction

for all related things with 0 confirmations that i found in

Code: Select all

listtransactions "" 1000

tried to register again and i have it working ok now

[khal]

ok, good to know that some tx where blocking.

[m4rkiz]

that actually happened for me more than once already, there must be some glitch in windows client that prevent some transaction from gaining confirmations, because i had same problems with couple more domains, and they all working fine now after i repeated those steps

[phelix]

I had the same issue. It seemed to be an unrelated tx...

script that helped me out:

http://blockchained.com/stuff/nmccleanzero2.zip

it deletes all 0 confirmation tx

You have to edit params.py_dist to params.py and edit it with the rpc username/pw from your conf file.

use at your own risk. be careful, if you have any proper but unconfirmed transactions.

edit: also back up before using it!!!

[georgem]

I am still getting this error from time to time.

Even with the newest wallet 0.3.72
on win 7 64bit.

Is it still recommended to erase the tx using deletetransaction?

[cassini]

Is it still recommended to erase the tx using deletetransaction?

I got this error on two different occasions:
a) I did a name operation and shut the namecoin client down after a few minutes. The name operation never made it to the blockchain, but the client somehow remembered it and blocked all future operations on that name.
b) I issued a name_update just a little too late. There were still "expires_in: 4 blocks", but the miners didn't accept any name operations for the next 5 blocks.


In both cases a deletetransaction helped. After that, the name is ripe to begin afresh.

[georgem]

Is it still recommended to erase the tx using deletetransaction?

I got this error on two different occasions:
a) I did a name operation and shut the namecoin client down after a few minutes. The name operation never made it to the blockchain, but the client somehow remembered it and blocked all future operations on that name.
b) I issued a name_update just a little too late. There were still "expires_in: 4 blocks", but the miners didn't accept any name operations for the next 5 blocks.


In both cases a deletetransaction helped. After that, the name is ripe to begin afresh.

Your case a) is the reason it happened to me, atleast I suppose so.