[EC-CUBE] EC-CUBE4.0.4 新規インストール
[レンタルサーバ] sakuraサーバー
[OS] FreeBSD 11.2-RELEASE-p14 amd64
[PHP] PHP Version 7.4.29
[WEBサーバ] Apache/2.4.53

[現象]在庫がある商品なのに、カートにいれて確認まで進み、最後の注文で在庫なしの購入エラーとなってしまう現象が発生します。

その商品を商品登録で開き、そのまま登録すると購入できるようになります。

キャッシュをクリアしたり、PHPのmemory_limitも3072Mまで増やしてみましたが発生します。

関係あるかどうかわからないのですが、ログをみるとhandleError:532 が多く発生しています。

ご教示の程よろしくお願いいたします。

以下、購入エラー近辺のログです。

[2022-05-30 15:58:51] app.INFO [N/A] [189f651] [6] [Eccube\Log\Logger:log:68] - PROCESS END ["shopping_error"] [GET, /shopping/error, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:51] front.INFO [b3783c00] [189f651] [6] [Eccube\Log\Logger:log:66] - LOGIC END ["shopping_error"] [GET, /shopping/error, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:51] php.INFO [b3783c00] [189f651] [6] [Symfony\Component\Debug\ErrorHandler:handleError:532] - User Deprecated: Calling Doctrine\ORM\EntityManager::flush() with any arguments to flush specific entities is deprecated and will not be supported in Doctrine ORM 3.0. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Calling Doctrine\\ORM\\EntityManager::flush() with any arguments to flush specific entities is deprecated and will not be supported in Doctrine ORM 3.0. at /home/xxxxxx/www/vendor/doctrine/orm/lib/Doctrine/ORM/EntityManager.php:362)"} [GET, /shopping/error, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:51] php.INFO [b3783c00] [189f651] [6] [Symfony\Component\Debug\ErrorHandler:handleError:532] - User Deprecated: Calling Doctrine\ORM\EntityManager::flush() with any arguments to flush specific entities is deprecated and will not be supported in Doctrine ORM 3.0. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Calling Doctrine\\ORM\\EntityManager::flush() with any arguments to flush specific entities is deprecated and will not be supported in Doctrine ORM 3.0. at /home/xxxxxx/www/vendor/doctrine/orm/lib/Doctrine/ORM/EntityManager.php:362)"} [GET, /shopping/error, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:51] php.INFO [b3783c00] [189f651] [6] [Symfony\Component\Debug\ErrorHandler:handleError:532] - User Deprecated: Calling Doctrine\ORM\EntityManager::flush() with any arguments to flush specific entities is deprecated and will not be supported in Doctrine ORM 3.0. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Calling Doctrine\\ORM\\EntityManager::flush() with any arguments to flush specific entities is deprecated and will not be supported in Doctrine ORM 3.0. at /home/xxxxxx/www/vendor/doctrine/orm/lib/Doctrine/ORM/EntityManager.php:362)"} [GET, /shopping/error, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:51] php.INFO [b3783c00] [189f651] [6] [Symfony\Component\Debug\ErrorHandler:handleError:532] - User Deprecated: Calling Doctrine\ORM\EntityManager::flush() with any arguments to flush specific entities is deprecated and will not be supported in Doctrine ORM 3.0. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Calling Doctrine\\ORM\\EntityManager::flush() with any arguments to flush specific entities is deprecated and will not be supported in Doctrine ORM 3.0. at /home/xxxxxx/www/vendor/doctrine/orm/lib/Doctrine/ORM/EntityManager.php:362)"} [GET, /shopping/error, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.INFO [b3783c00] [189f651] [6] [Eccube\Log\Logger:log:66] - LOGIC START ["shopping_error"] [GET, /shopping/error, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.INFO [b3783c00] [189f651] [6] [Eccube\Log\Logger:log:66] - PROCESS START ["shopping_error"] [GET, /shopping/error, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.INFO [N/A] [189f651] [N/A] [Eccube\Log\Logger:log:66] - INIT [] [GET, /shopping/error, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] app.DEBUG [N/A] [f2422fd] [6] [Eccube\Log\Logger:log:68] - Commit executed. [] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] app.INFO [N/A] [f2422fd] [6] [Eccube\Log\Logger:log:68] - PROCESS END ["shopping_checkout"] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.INFO [b3783c00] [f2422fd] [6] [Eccube\Log\Logger:log:66] - LOGIC END ["shopping_checkout"] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.ERROR [b3783c00] [f2422fd] [6] [Eccube\Log\Logger:log:66] - [注文処理] 購入エラーが発生しました. ["「商品XXX」の在庫が足りません。"] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.INFO [b3783c00] [f2422fd] [6] [Eccube\Log\Logger:log:66] - [注文処理] PaymentMethod::applyを実行します. [] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.INFO [b3783c00] [f2422fd] [6] [Eccube\Log\Logger:log:66] - [注文処理] PaymentMethodを取得します. ["Eccube\\Service\\Payment\\Method\\Cash"] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.INFO [b3783c00] [f2422fd] [6] [Eccube\Log\Logger:log:66] - [注文処理] 集計処理を開始します. [584] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.INFO [b3783c00] [f2422fd] [6] [Eccube\Log\Logger:log:66] - [注文処理] 注文処理を開始します. [584] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.INFO [b3783c00] [f2422fd] [6] [Eccube\Log\Logger:log:66] - LOGIC START ["shopping_checkout"] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.DEBUG [b3783c00] [f2422fd] [6] [Eccube\Log\Logger:log:66] - Begin Transaction. [] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.INFO [b3783c00] [f2422fd] [6] [Eccube\Log\Logger:log:66] - fallback to PC layout [] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]
[2022-05-30 15:58:50] front.INFO [b3783c00] [f2422fd] [6] [Eccube\Log\Logger:log:66] - PROCESS START ["shopping_checkout"] [POST, /shopping/checkout, xxx.xxx.105.38, https://xxx.xxxxx.jp/shopping/confirm, Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko]

dtb_product_class.stock
dtb_product_stock.stock
これら2箇所の在庫数に不一致があったりしませんか？

不一致なら、ぱっと見在庫があるのに(dtb_product_class.stock=1)
実際買おうとする時にない(dtb_product_stock.stock=0)のでエラーになっちゃうかも。

管理画面で再登録するとこれらが揃うので買えちゃう。

ちなみにログの"User Deprecated"の行は無視でいいと思います。
非推奨で近い将来使えなくなるぞというやつで、この事象には関係ないかと。

返信ありがとうございます。確認しました。

カスタマイズで作成したCSV読み込みでの在庫数更新処理で不一致の状態になっていたようです。CSVで在庫を更新した商品で発生していました。

この部分を改修いたします。ありがとうございました。