Quote from: overtorment2 on May 23, 2018, 10:47:14 AM

Quote from: ketominer on May 23, 2018, 09:17:05 AM

I don't know if it's a consequence of the items above, but I created new payment requests which were paid and arrived in the sub-addresses (I can see them in bitcoin-cli listaddressgroupings) but they are not transferred to the seller account, no trace of them in cashier-btc-out.log

Don't hesitate to ask me for more info

The third question I didn't quite understand.
Probably the payment requests are old enough (>24h) to be ignored by worker.
You can always check out whats wrong with the payment request right in the database.

Thank you for your reply! I'll look into the first two items right now.

About the third one, I have 2 payments of 0.0004 which are received (this morning) :
[/list]

Code:

[
   [
   "XXY",
   0.00040000,
   "XXY"
   ]
  ],
  [
   [
   "XXX",
   0.00040000,
   "XXX"
   ]
  ]

and confirmed (more than 20 confirmations now) but they are not getting transferred to the seller account.

In the database, the paid_on, processed and so on fields are missing. I also don't see those transactions in the worker.js logs.

After looking closer, I found this:

Code:

(node:4415) UnhandledPromiseRejectionWarning: Error: {"result":null,"error":{"code":-4,"message":"Address not found in wallet"},"id":"4faa6833-856e-48b0-afa9-42fe75e8675a"}

   at IncomingMessage. (/home/cashier/Cashier-BTC/node_modules/jayson/lib/client/http.js:74:21)
   at emitNone (events.js:111:20)
   at IncomingMessage.emit (events.js:208:7)
   at endReadableNT (_stream_readable.js:1064:12)
   at _combinedTickCallback (internal/process/next_tick.js:138:11)
   at process._tickCallback (internal/process/next_tick.js:180:9)
(node:4415) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)

I guess I have some address in the database which wasn't created in the bitcoind itself?

EDIT : found the issue, I had some left over data from "npm test" in my database