Error after stack change to cflinuxfs4 - glibc

[vbalko-claimate]

Hello,

Today I discovered in whats new, that new linux stack for cloud foundry is being implemented and therefore we should upgrade stack of all of our apps deployed to cloud foundry.

I headed to our DEV subaccount and tried to upgrade stack manually, but I app crashed upon upgrade with error, that glibc and glibxx are not found

Did you encounter such issue too?

24 Mar 2023, 09:17:13 (GMT+01:00)STDOUT[CELL/0]Cell ad049dc3-8675-4cff-8eef-86833cd21113 successfully destroyed container for instance 550f6eaa-0593-4769-65da-fb2d24

Mar 2023, 09:17:11 (GMT+01:00)STDOUT[PROXY/0]Exit status 13724

Mar 2023, 09:17:11 (GMT+01:00)STDOUT[API/84]"550f6eaa-0593-4769-65da-fb2d", "index"=>0, "cell_id"=>"ad049dc3-8675-4cff-8eef-86833cd21113", "reason"=>"CRASHED", "exit_description"=>"APP/PROC/WEB: Exited with status 1", "crash_count"=>3, "crash_timestamp"=>1679645831645076725, "version"=>"76d3c8d4-ce62-4d00-9ca8-22156b36800d"}" class="sapMText sapUiSelectable sapMTextNoWrap sapMTextMaxWidth sapMFlexItem" style="-webkit-tap-highlight-color: rgba(0, 0, 0, 0); text-size-adjust: none; position: relative; display: inline-block; box-sizing: border-box; overflow-wrap: normal; cursor: text; font-size: 0.875rem; font-family: "72", "72full", Arial, Helvetica, sans-serif; overflow: hidden; text-overflow: ellipsis; max-width: 100%; vertical-align: middle;">App instance exited with guid 9939c97d-d8db-465c-94d0-1124ed6f14b1 payload: {"instance"=>"550f6eaa-0593-4769-65da-fb2d", "index"=>0, "cell_id"=>"ad049dc3-8675-4cff-8eef-86833cd21113", "reason"=>"CRASHED", "exit_description"=>"APP/PROC/WEB: Exited with status 1", "crash_count"=>3, "crash_timestamp"=>1679645831645076725, "version"=>"76d3c8d4-ce62-4d00-9ca8-22156b36800d"}

24 Mar 2023, 09:17:11 (GMT+01:00)STDOUT[API/84]Process has crashed with type: "web"24 Mar 2023, 09:17:11 (GMT+01:00)STDOUT[CELL/0]Cell ad049dc3-8675-4cff-8eef-86833cd21113 stopping instance 550f6eaa-0593-4769-65da-fb2d24

Mar 2023, 09:17:11 (GMT+01:00)STDOUT[CELL/0]Cell ad049dc3-8675-4cff-8eef-86833cd21113 destroying container for instance 550f6eaa-0593-4769-65da-fb2d

24 Mar 2023, 09:17:05 (GMT+01:00)STDOUT[APP/PROC/WEB/0]Exit status 124 Mar 2023, 09:17:05 (GMT+01:00)STDERR[APP/PROC/WEB/0]node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by node)

24 Mar 2023, 09:17:05 (GMT+01:00)STDERR[APP/PROC/WEB/0]node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by node)

24 Mar 2023, 09:17:05 (GMT+01:00)STDERR[APP/PROC/WEB/0]node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by node)

24 Mar 2023, 09:17:05 (GMT+01:00)STDERR[APP/PROC/WEB/0]node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)

24 Mar 2023, 09:17:05 (GMT+01:00)STDERR[APP/PROC/WEB/0]node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by node)

24 Mar 2023, 09:17:05 (GMT+01:00)STDERR[APP/PROC/WEB/0]node: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by node)

24 Mar 2023, 09:17:05 (GMT+01:00)STDERR[APP/PROC/WEB/0]node: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by node)

24 Mar 2023, 09:17:05 (GMT+01:00)STDERR[APP/PROC/WEB/0]node: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by node)

24 Mar 2023, 09:17:05 (GMT+01:00)STDOUT[CELL/0]Downloaded droplet (42.9M)

[vbalko-claimate]

Nobody encounters this problem? I guess, that very soon everybody will have to solve this problem. Or is it just me, having something wrongly set?

[martin-kl]

I do run into the same problem when updating the stack of an existing solution via the UI.

However, I did succeed in changing the stack some time ago by setting the stack manually in my mta.yaml and redeploying the application. I did not try that since the change of the default stack but that could work for you as well.