View Revisions: Issue #5054

Summary 0005054: 'contract_terms not found' for transaction which correctly went through
Revision 2017-07-20 09:23 by Christian Grothoff
Description Sometimes, when the backoffice wants to track an order id, the merchant backend returns 404
indicating that the order id is unknown. This is incorrect, because the order id we want to
track is returned by the merchant backend's /history API.

As of commit fc6ee7d, the merchant produces more debugging information when the db is involved.


Those are logs indicating this situation:

Jun 01 16:50:52-716445 taler-merchant-httpd-24124 DEBUG Trying to track h_contract_terms 'CPJB0H5C'
Jun 01 16:50:52-716466 taler-merchant-httpd-24124 DEBUG Finding transaction for h_contract_terms 'CPJB0H5C'
Jun 01 16:50:52-716476 pq-24124 DEBUG Executing prepared SQL statement `find_transaction'
Jun 01 16:50:52-716743 taler-merchant-httpd-24124 DEBUG Could NOT find transaction for h_contract_terms 'CPJB0H5C'
Jun 01 16:50:52-716777 taler-merchant-httpd-24124 WARNING h_contract_terms not found
Revision 2017-06-02 13:58 by Marcello Stanisci
Description
Sometimes, when the backoffice wants to track an order id, the merchant backend returns 404
indicating that the order id is unknown. This is incorrect, because the order id we want to
track is returned by the merchant backend's /history API.

As of commit fc6ee7d, the merchant produces more debugging information when the db is involved.


Those are logs indicating this situation:

Jun 01 16:50:52-716445 taler-merchant-httpd-24124 DEBUG Trying to track h_contract_terms 'CPJB0H5C'
Jun 01 16:50:52-716466 taler-merchant-httpd-24124 DEBUG Finding transaction for h_contract_terms 'CPJB0H5C'
Jun 01 16:50:52-716476 pq-24124 DEBUG Executing prepared SQL statement `find_transaction'
Jun 01 16:50:52-716743 taler-merchant-httpd-24124 DEBUG Could NOT find transaction for h_contract_terms 'CPJB0H5C'
Jun 01 16:50:52-716777 taler-merchant-httpd-24124 WARNING h_contract_terms not found