Jannis
commented
4 years ago Node logs (excerpt):
[Nest] 1 - 02/27/2020, 6:59:57 PM [LockService] Failed to execute callback while lock is held: IO_SEND_AND_WAIT timed out after 90s waiting for counterparty reply in propose +238ms
Error: IO_SEND_AND_WAIT timed out after 90s waiting for counterparty reply in propose
at eval (webpack:///./node_modules/@connext/cf-core/dist/src/node.js?:107:23)
at async ProtocolRunner.runProtocol (webpack:///./node_modules/@connext/cf-core/dist/src/machine/protocol-runner.js?:80:33)
at async ProposeInstallController.executeMethodImplementation (webpack:///./node_modules/@connext/cf-core/dist/src/methods/app-instance/propose-install/controller.js?:52:9)
[Nest] 1 - 02/27/2020, 6:59:57 PM [LockService] Releasing lock for 0xC7c4175D538A7300f2cAc20AA613257C4F072Ab3 with secret b91e4102da31410fc2e71b7e8dfe0617
[Nest] 1 - 02/27/2020, 6:59:57 PM [LockService] Failed to release the lock due to expired ttl: LockError: Unable to fully release the lock on resource "0xC7c4175D538A7300f2cAc20AA613257C4F072Ab3".;
[Nest] 1 - 02/27/2020, 6:59:57 PM [LockService] No return value found from task with lockName: 0xC7c4175D538A7300f2cAc20AA613257C4F072Ab3, and failed to release due to expired ttl: Unable to fully release the lock on resource "0xC7c4175D538A7300f2cAc20AA613257C4F072Ab3". +1ms
LockError: Unable to fully release the lock on resource "0xC7c4175D538A7300f2cAc20AA613257C4F072Ab3".
at loop (/root/node_modules/redlock/redlock.js:265:18)
at tryCatcher (/root/node_modules/standard-as-callback/built/utils.js:11:23)
at /root/node_modules/standard-as-callback/built/index.js:19:49
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
debug: [NatsMessagingService] Publishing _INBOX.U56JYA7BUUUQI5FCZ9HQYL.U56JYA7BUUUQI5FCZ9HQTP: {"err":"LockError: Unable to fully release the lock on resource \"0xC7c4175D538A7300f2cAc20AA613257C4F072Ab3\".","message":"Error during processor function: "}
[Nest] 1 - 02/27/2020, 6:59:57 PM [MessagingProvider] Error processing message transfer.resolve-linked.xpub6EVQvyzRp3zNKiQwSNdc7yLCqoqXqAM9jYv724yGmLfDbUn3AAqPaunpxg1cJQgTbm3TCBVVLfvh4gkkAu6tA9uYUkWPJ2JWnPiU2RnBw7v: Unable to fully release the lock on resource "0xC7c4175D538A7300f2cAc20AA613257C4F072Ab3". +5ms
LockError: Unable to fully release the lock on resource "0xC7c4175D538A7300f2cAc20AA613257C4F072Ab3".
at loop (/root/node_modules/redlock/redlock.js:265:18)
at tryCatcher (/root/node_modules/standard-as-callback/built/utils.js:11:23)
at /root/node_modules/standard-as-callback/built/index.js:19:49
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
Describe the bug
I have the following system set up (all using Connext 4.2.0):
RECEIVE_TRANSFER_FINISHED_EVENT)meta.sendercarrying the xpub of the sender), these clients wait for 1s and then transfer the same amount back to the senderAfter a few payments back and forth, client C logged this:
It still continued to receive payments from A and was able to send payments back to A. But it no longer received anything from B.
After a restart, client C logged the following when trying to run
connext.connect(). Additional restarts don't help, it keeps logging the same (except with a differentreceovered 0x...address every time):After the timeout, client C manages to continue, but when it then tries to deposit something into the state channel, that times out as well:
Your Environment