Processing response error ,message :already know

[Abhishek-1857]

i am getting this error when i am using my contract function the second time and 1st time its working fine.

/home/user/decentralizedBridge/node_modules/@ethersproject/logger/lib/index.js:233
var error = new Error(message);
^

Error: processing response error (body="{"jsonrpc":"2.0","id":122,"error":{"code":-32000,"message":"already known"}}\n", error={"code":-32000}, requestBody="{"method":"eth_sendRawTransaction","params":["0xf9016b81908502540be400829f1794e280457fdfe83e5e316ecf60c92be747fdfa74f180b901046010a5e70000000000000000000000004f1536fc181c541f3ef766d227373f55d03ce0ba0000000000000000000000004f1536fc181c541f3ef766d227373f55d03ce0ba0000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000413158cecf4b397780a94ad566a7ca897a748b872a4ea91371f8e8817e8744b8936e1416e1bd2d5096f28ef01beefedabaacd84122b6a1576a00d0b3f64e05eff21c0000000000000000000000000000000000000000000000000000000000000081e69f5d2956f6cf6d83cc3fa95ec7589064b4fd4826c579128e8609c32e22df5eb2a063c30079bc7f755de882c1a09a750d0ff1354af6c38a65b856e91fbde2900310"],"id":122,"jsonrpc":"2.0"}", requestMethod="POST", url="https://data-seed-prebsc-1-s1.binance.org:8545", code=SERVER_ERROR, version=web/5.6.0)
at Logger.makeError (/home/user/decentralizedBridge/node_modules/@ethersproject/logger/lib/index.js:233:21)
at Logger.throwError (/home/user/decentralizedBridge/node_modules/@ethersproject/logger/lib/index.js:242:20)
at /home/user/decentralizedBridge/node_modules/@ethersproject/web/lib/index.js:305:32
at step (/home/user/decentralizedBridge/node_modules/@ethersproject/web/lib/index.js:33:23)
at Object.next (/home/user/decentralizedBridge/node_modules/@ethersproject/web/lib/index.js:14:53)
at fulfilled (/home/user/decentralizedBridge/node_modules/@ethersproject/web/lib/index.js:5:58)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
reason: 'processing response error',
code: 'SERVER_ERROR',
body: '{"jsonrpc":"2.0","id":122,"error":{"code":-32000,"message":"already known"}}\n',
error: Error: already known
at getResult (/home/user/decentralizedBridge/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:170:21)
at processJsonFunc (/home/user/decentralizedBridge/node_modules/@ethersproject/web/lib/index.js:348:22)
at /home/user/decentralizedBridge/node_modules/@ethersproject/web/lib/index.js:280:46
at step (/home/user/decentralizedBridge/node_modules/@ethersproject/web/lib/index.js:33:23)
at Object.next (/home/user/decentralizedBridge/node_modules/@ethersproject/web/lib/index.js:14:53)
at fulfilled (/home/user/decentralizedBridge/node_modules/@ethersproject/web/lib/index.js:5:58)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
code: -32000,
data: undefined
},
requestBody: '{"method":"eth_sendRawTransaction","params":["0xf9016b81908502540be400829f1794e280457fdfe83e5e316ecf60c92be747fdfa74f180b901046010a5e70000000000000000000000004f1536fc181c541f3ef766d227373f55d03ce0ba0000000000000000000000004f1536fc181c541f3ef766d227373f55d03ce0ba0000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000413158cecf4b397780a94ad566a7ca897a748b872a4ea91371f8e8817e8744b8936e1416e1bd2d5096f28ef01beefedabaacd84122b6a1576a00d0b3f64e05eff21c0000000000000000000000000000000000000000000000000000000000000081e69f5d2956f6cf6d83cc3fa95ec7589064b4fd4826c579128e8609c32e22df5eb2a063c30079bc7f755de882c1a09a750d0ff1354af6c38a65b856e91fbde2900310"],"id":122,"jsonrpc":"2.0"}',
requestMethod: 'POST',
url: 'https://data-seed-prebsc-1-s1.binance.org:8545',
transaction: {
nonce: 144,
gasPrice: BigNumber { _hex: '0x02540be400', _isBigNumber: true },
gasLimit: BigNumber { _hex: '0x9f17', _isBigNumber: true },
to: '0xe280457fdfE83e5E316EcF60c92BE747FdfA74f1',
value: BigNumber { _hex: '0x00', _isBigNumber: true },
data: '0x6010a5e70000000000000000000000004f1536fc181c541f3ef766d227373f55d03ce0ba0000000000000000000000004f1536fc181c541f3ef766d227373f55d03ce0ba0000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000413158cecf4b397780a94ad566a7ca897a748b872a4ea91371f8e8817e8744b8936e1416e1bd2d5096f28ef01beefedabaacd84122b6a1576a00d0b3f64e05eff21c00000000000000000000000000000000000000000000000000000000000000',
chainId: 97,
v: 230,
r: '0x005d2956f6cf6d83cc3fa95ec7589064b4fd4826c579128e8609c32e22df5eb2',
s: '0x63c30079bc7f755de882c1a09a750d0ff1354af6c38a65b856e91fbde2900310',
from: '0x4F1536FC181C541f3eF766D227373f55d03CE0bA',
hash: '0x2121c53176b22202fe52827033f6cdf1079e9d580fd019e99c8d9949adc81506',
type: null,
confirmations: 0
},
transactionHash: '0x2121c53176b22202fe52827033f6cdf1079e9d580fd019e99c8d9949adc81506'
}

[zemse]

Hey @Abhishek-1857, the rpc error "already known" means that your transaction was previously broadcasted to the network already and the node already has your transaction. If you are intentionally submitting your transaction to multiple nodes, you can ignore this but if this is popping out of no where, it is possible there might be a bug somewhere (e.g. if your other tx parameters are same, then it's possible you are reusing the nonce).

[Abhishek-1857]

NO, for both the transactions the nonce is changing from 150 to 151 then i think its not the nonce issue, im using the same address again and again for the transactions may be this is the issue. Please tell?????

[zemse]

im using the same address again and again for the transactions

Do you mean you have parallel instances of your app that uses same signing address?

[Abhishek-1857]

i use my addresss for calling transfer function of my contract and 2nd time im using again that address and the 2nd time it gives processing response error already known but the transfer happens but with this error..... :'(

[zemse]

Okay it seems the code is being executed twice somehow. So due to the first time the transfer happens, while the second time it will give you this already known error.

[Abhishek-1857]

yeahhh i think so but don't know the reason how its happening