Daniel Berlin

Solved in my case by lowering the `net.keepalive_idle_timeout` (in my case to 30 sec). I assume that fluent-bit assumed the connections to be alive, while the server side had already...

My bad... 30 sec was the original timeout - I lowered it to 10 sec. Anyway I'm still not sure whether the error and `net.keepalive_idle_timeout` are related or not...

Found the problem: the storage account has sku_type Standard_LRS, which does not support immutability. Anyhow, I think this constellation should be caught by the SDK... AzureWhatEverError('Your account does not support...

I found this doc and to me it sounded, like the storage account mus be a Premium one... https://learn.microsoft.com/en-us/azure/storage/blobs/immutable-storage-overview#supported-account-configurations

You're right - I created a second storage account that is (as much as possible) identical to my primary one, but has "Standard" performance instead of Premium. Still works.

So at the moment I'm not able to reproduce the problem - unfortunately, as it was 100% reproducible at first. From my side we can close this issue.

Agreed - dividing it by the number of cores makes sense... but not dividing it by 100 and putting a percent sign behind it - at least imho.

Looks good

Same for me: ``` Character set conversion not possible for one or more characters. Source data from the first non-convertible byte: "C4 27 2E 0A 20 20 20 20 20...

For ZRFC_STATRECS_SUMMARY, the problem seems to be this line: ` WHEN '§'. gs_result-tasktype = 'lrrfc'. "(417) paragraph sign` It triggers an exception in ABAPGIT, line 28.076, METHOD CONVERT