Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SIGSERV on arm-based machines #557

Closed
4 tasks done
romankydybets opened this issue Sep 22, 2024 · 3 comments · Fixed by #558
Closed
4 tasks done

SIGSERV on arm-based machines #557

romankydybets opened this issue Sep 22, 2024 · 3 comments · Fixed by #558
Assignees
Labels
scope/backend Related to backend changes status/triage/completed Automatic triage completed type/bug Something isn't working

Comments

@romankydybets
Copy link

romankydybets commented Sep 22, 2024

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running main-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

After image update application didn't run.

Expected behavior

No response

Your installation details

Image used before - 273e64cd1b7096769fad294918017a4db13a1fb4
Helm chart "1.4.2"

Steps to reproduce

Just set image tag to 025c41abdf38f94d65ba22c36df5ba4e7794b598

Screenshots

No response

Logs

Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
default THREAD FACTORY
 _   _ ___    __             _                _          _  __      __ _
| | | |_ _|  / _|___ _ _    /_\  _ __ __ _ __| |_  ___  | |/ /__ _ / _| |_____
| |_| || |  |  _/ _ | '_|  / _ \| '_ / _` / _| ' \/ -_) | ' </ _` |  _| / / _`|
 \___/|___| |_| \___|_|   /_/ \_| .__\__,_\__|_||_\___| |_|\_\__,_|_| |_\_\__,|
                                 |_|

2024-09-22 16:07:28,858 INFO  [main] i.k.u.KafkaUiApplication: Starting KafkaUiApplication using Java 17.0.11 with PID 1 (/api.jar started by kafkaui in /)
2024-09-22 16:07:28,867 DEBUG [main] i.k.u.KafkaUiApplication: Running with Spring Boot v3.1.9, Spring v6.0.17
2024-09-22 16:07:28,869 INFO  [main] i.k.u.KafkaUiApplication: No active profile set, falling back to 1 default profile: "default"
2024-09-22 16:07:32,987 DEBUG [main] i.k.u.s.SerdesInitializer: Configuring serdes for cluster yaml
2024-09-22 16:07:33,752 INFO  [main] o.s.b.a.e.w.EndpointLinksResolver: Exposing 3 endpoint(s) beneath base path '/actuator'
2024-09-22 16:07:33,815 INFO  [main] o.s.b.a.s.r.ReactiveUserDetailsServiceAutoConfiguration:

Using generated security password: 5a1de9fa-58b9-4b54-9917-24bb6672c10d

2024-09-22 16:07:34,134 INFO  [main] i.k.u.c.a.OAuthSecurityConfig: Configuring OAUTH2 authentication.
2024-09-22 16:07:34,736 INFO  [main] o.s.b.w.e.n.NettyWebServer: Netty started on port 8080
2024-09-22 16:07:34,798 INFO  [main] i.k.u.KafkaUiApplication: Started KafkaUiApplication in 7.376 seconds (process running for 8.315)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00000000000226a0, pid=1, tid=34
#
# JRE version: OpenJDK Runtime Environment Zulu17.50+19-CA (17.0.11+9) (build 17.0.11+9-LTS)
# Java VM: OpenJDK 64-Bit Server VM Zulu17.50+19-CA (17.0.11+9-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
# Problematic frame:
# C  [libnetty_tcnative_linux_aarch_6418445906356460903573.so+0x2330c]  init_have_lse_atomics+0xc
#
# Core dump will be written. Default location: //core.1
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid1.log
#
# If you would like to submit a bug report, please visit:
#   http://www.azul.com/support/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

Additional context

No response

@romankydybets romankydybets added status/triage Issues pending maintainers triage type/bug Something isn't working labels Sep 22, 2024
@kapybro kapybro bot added status/triage/manual Manual triage in progress status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Sep 22, 2024
Copy link

Hi romankydybets! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

@Haarolean Haarolean changed the title New image 025c41abdf38f94d65ba22c36df5ba4e7794b598 not running SIGSERV on arm-based machines Sep 23, 2024
@Haarolean
Copy link
Member

@romankydybets are you running on apple silicon specifically or is it some other arm machine?

@Haarolean Haarolean added scope/backend Related to backend changes and removed status/triage/manual Manual triage in progress labels Sep 23, 2024
@Haarolean Haarolean self-assigned this Sep 23, 2024
@Haarolean Haarolean linked a pull request Sep 23, 2024 that will close this issue
13 tasks
@romankydybets
Copy link
Author

@Haarolean sorry for not reply, it's just ARM machine on amazon.
And last commit is working fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope/backend Related to backend changes status/triage/completed Automatic triage completed type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants