Failed to export TAR file from SCU - "Internal Server Error"
darek-phorest opened this issue · 3 comments
Describe the bug
hi we are seeing an increased number of errors for the last couple of days for the daily closing. The error doesn't say much just "Internal Server Error" Below you will find log from the pods.
{ Status: "-20000", Error: "Internal Server Error", Code: "", RequestId: "ef4ab5e6c5e21ca4530de1c15e13ab1a" }
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Tar file is exported successfully.
Screenshots
If applicable, add screenshots to help explain your problem.
STDOUT/STDERR
Field | Value
-- | --
@ingestionTime | 1627322870051
@log | 863263560856:/eks/fiskaltrust-middleware-prod/containers
@logStream | byodc-5b6dbc6868-xz57q_bring-your-own-datacenter_byodc-c394b9adce79a043cae71849663dce5666a79c73d9978546fd47757c78639a45
@message | {"log":"\u001B[41m\u001B[30mfail\u001B[39m\u001B[22m\u001B[49m: fiskaltrust.Middleware.SCU.DE.Fiskaly.FiskalySCU[0]\n Failed to execute StartExportSessionAsync - Request: {\"ClientId\":null,\"Erase\":true}\n { Status: \"-20000\", Error: \"Internal Server Error\", Code: \"\", RequestId: \"c680ff288e5d7c1bf972bf390f320d1c\" }\n","stream":"stdout","docker":{"container_id":"c394b9adce79a043cae71849663dce5666a79c73d9978546fd47757c78639a45"},"kubernetes":{"container_name":"byodc","namespace_name":"bring-your-own-datacenter","pod_name":"byodc-5b6dbc6868-xz57q","container_image":"ghcr.io/fiskaltrust/byodc-mysql-fiskaly:1.3.16-buster","container_image_id":"docker-pullable://ghcr.io/fiskaltrust/byodc-mysql-fiskaly@sha256:e474c26458ea263e699871ee304a8f2c2d0b229cb0aa9d75333b0d300807489b","pod_id":"1599c220-cbbf-41e4-bd97-f1cc4044d324","host":"ip-192-168-144-20.eu-central-1.compute.internal","labels":{"app":"byodc","pod-template-hash":"5b6dbc6868"},"master_url":"https://10.100.0.1:443/api","namespace_id":"55e764f3-dcc1-456b-a56a-02b4edd83cd7"}}
@timestamp | 1627322863621
docker.container_id | c394b9adce79a043cae71849663dce5666a79c73d9978546fd47757c78639a45
kubernetes.container_image | ghcr.io/fiskaltrust/byodc-mysql-fiskaly:1.3.16-buster
kubernetes.container_image_id | docker-pullable://ghcr.io/fiskaltrust/byodc-mysql-fiskaly@sha256:e474c26458ea263e699871ee304a8f2c2d0b229cb0aa9d75333b0d300807489b
kubernetes.container_name | byodc
kubernetes.host | ip-192-168-144-20.eu-central-1.compute.internal
kubernetes.labels.app | byodc
kubernetes.labels.pod-template-hash | 5b6dbc6868
kubernetes.master_url | https://10.100.0.1:443/api
kubernetes.namespace_id | 55e764f3-dcc1-456b-a56a-02b4edd83cd7
kubernetes.namespace_name | bring-your-own-datacenter
kubernetes.pod_id | 1599c220-cbbf-41e4-bd97-f1cc4044d324
kubernetes.pod_name | byodc-5b6dbc6868-xz57q
log | �[41m�[30mfail�[39m�[22m�[49m: fiskaltrust.Middleware.SCU.DE.Fiskaly.FiskalySCU[0]Failed to execute StartExportSessionAsync - Request: {"ClientId":null,"Erase":true}{ Status: "-20000", Error: "Internal Server Error", Code: "", RequestId: "c680ff288e5d7c1bf972bf390f320d1c" }
stream | stdout
Field | Value
-- | --
@ingestionTime | 1627323876627
@log | 863263560856:/eks/fiskaltrust-middleware-prod/containers
@logStream | byodc-5b6dbc6868-kr7lx_bring-your-own-datacenter_byodc-c188c1c7acb6b09ed2c45ed741fdd3da14b851e14492131d44dcab71f8df0124
@message | {"log":"\u001B[41m\u001B[30mfail\u001B[39m\u001B[22m\u001B[49m: fiskaltrust.Middleware.Localization.QueueDE.SignProcessorDE[0]\n Failed to export TAR file from SCU.\n { Status: \"-20000\", Error: \"Internal Server Error\", Code: \"\", RequestId: \"ef4ab5e6c5e21ca4530de1c15e13ab1a\" }\n","stream":"stdout","docker":{"container_id":"c188c1c7acb6b09ed2c45ed741fdd3da14b851e14492131d44dcab71f8df0124"},"kubernetes":{"container_name":"byodc","namespace_name":"bring-your-own-datacenter","pod_name":"byodc-5b6dbc6868-kr7lx","container_image":"ghcr.io/fiskaltrust/byodc-mysql-fiskaly:1.3.16-buster","container_image_id":"docker-pullable://ghcr.io/fiskaltrust/byodc-mysql-fiskaly@sha256:e474c26458ea263e699871ee304a8f2c2d0b229cb0aa9d75333b0d300807489b","pod_id":"9bb89578-685d-42c0-af29-1e6402aa0c34","host":"ip-192-168-157-187.eu-central-1.compute.internal","labels":{"app":"byodc","pod-template-hash":"5b6dbc6868"},"master_url":"https://10.100.0.1:443/api","namespace_id":"55e764f3-dcc1-456b-a56a-02b4edd83cd7"}}
@timestamp | 1627323876200
docker.container_id | c188c1c7acb6b09ed2c45ed741fdd3da14b851e14492131d44dcab71f8df0124
kubernetes.container_image | ghcr.io/fiskaltrust/byodc-mysql-fiskaly:1.3.16-buster
kubernetes.container_image_id | docker-pullable://ghcr.io/fiskaltrust/byodc-mysql-fiskaly@sha256:e474c26458ea263e699871ee304a8f2c2d0b229cb0aa9d75333b0d300807489b
kubernetes.container_name | byodc
kubernetes.host | ip-192-168-157-187.eu-central-1.compute.internal
kubernetes.labels.app | byodc
kubernetes.labels.pod-template-hash | 5b6dbc6868
kubernetes.master_url | https://10.100.0.1:443/api
kubernetes.namespace_id | 55e764f3-dcc1-456b-a56a-02b4edd83cd7
kubernetes.namespace_name | bring-your-own-datacenter
kubernetes.pod_id | 9bb89578-685d-42c0-af29-1e6402aa0c34
kubernetes.pod_name | byodc-5b6dbc6868-kr7lx
log | �[41m�[30mfail�[39m�[22m�[49m: fiskaltrust.Middleware.Localization.QueueDE.SignProcessorDE[0]Failed to export TAR file from SCU.{ Status: "-20000", Error: "Internal Server Error", Code: "", RequestId: "ef4ab5e6c5e21ca4530de1c15e13ab1a" }
stream | stdout
POSSystem (please complete the following information):
- 46a60bc4-42f6-4a95-b758-77c8da74f203
Cashbox Information (please complete the following information):
- CashboxID
Additional context
Add any other context about the problem here.
Good morning, guys. Could we please get an update on this one?
Good morning, my apologies for the late response. We're working closely with fiskaly currently to resolve these issues you're experiencing, as they seem to be occurring due to many ongoing changes (because of fiskaly's v2 deployment).
We've actually received other requests and noticed that exports from fiskaly can take up to multiple hours currently (instead of few seconds, as before). We've opened a ticket and are trying to clarify this behavior right now. This might also be related to what you mentioned in the last posts of #49.
A workaround until then could be to temporary disable the TAR exports in the affected SCUs by setting the configuration property EnableTarFileExport to false in the SCU configuration (via the Portal). After the Cashboxes restarted next time, the TAR export will be omitted on daily closings. No data will be lost when doing this, as it will just be downloaded after re-enabling the exports.
We will of course get back to you as soon as we have any news.