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

SIGSEGV when using S3Client in Docker based on adoptopenjdk/openjdk8:jdk8u212-b03-alpine-slim #3189

Closed
rzhang90 opened this issue May 13, 2022 · 7 comments
Labels
bug This issue is a bug. dependencies This issue is a problem in a dependency. transfer-manager

Comments

@rzhang90
Copy link

Describe the bug

When the following code is running

S3Client.builder()
            .region(Region.of(s3Region))
            .credentialsProvider(awsCredentialsProvider)
            .build();

The following exception occurs:
software.amazon.awssdk.crt.CrtRuntimeException: S3Client.aws_s3_client_new: creating aws_s3_client failed (aws_last_error: AWS_IO_TLS_CTX_ERROR(1033), Failed to create tls context) UNKNOWN(-1)

Expected Behavior

The initialization of S3Client should work.

Current Behavior

The initialization of S3Client works well locally on my MacOS 12.3.1, but when I build a docker image based on adoptopenjdk/openjdk8:jdk8u212-b03-alpine-slim and run the container, it fails.

The whole error is:

#

# A fatal error has been detected by the Java Runtime Environment:

#

#  SIGSEGV (0xb) at pc=0x00007f851b746260, pid=1, tid=0x00007f8506ffd700

#

# JRE version: OpenJDK Runtime Environment (8.0_212-b03) (build 1.8.0_212-b03)

# Java VM: OpenJDK 64-Bit Server VM (25.212-b03 mixed mode linux-amd64 compressed oops)

# Problematic frame:

# C  [AWSCRT_16524652677012128309476830629660libaws-crt-jni.so+0xc0260]

#

# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

#

# An error report file with more information is saved as:

# //hs_err_pid1.log

2022-05-13 18:07:47.821  WARN 1 --- [           main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - ... nested exception is software.amazon.awssdk.crt.CrtRuntimeException: S3Client.aws_s3_client_new: creating aws_s3_client failed (aws_last_error: AWS_IO_TLS_CTX_ERROR(1033), Failed to create tls context) UNKNOWN(-1)

Reproduction Steps

The Dockerfile is like:

FROM adoptopenjdk/openjdk8:jdk8u212-b03-alpine-slim

# Install mono for alpine
RUN echo "http://dl-4.alpinelinux.org/alpine/edge/testing" >> /etc/apk/repositories && apk update && apk add mono
RUN apk add openssh

COPY target/server*.jar /app/server.jar
CMD ["java", "-Xmx18g",  "-jar", "/app/server.jar"]
EXPOSE 8080

The s3 sdk is:

<dependency>
  <groupId>software.amazon.awssdk</groupId>
  <artifactId>s3-transfer-manager</artifactId>
  <version>2.17.16-PREVIEW</version>
</dependency>

Possible Solution

No response

Additional Information/Context

No response

AWS Java SDK version used

2.17.16

JDK version used

8

Operating System and version

MacOS 12.3.1

@rzhang90 rzhang90 added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels May 13, 2022
@zoewangg zoewangg added dependencies This issue is a problem in a dependency. transfer-manager and removed needs-triage This issue or PR still needs to be triaged. labels May 13, 2022
@zoewangg
Copy link
Contributor

Hi @rzhang90, thanks for reaching out. S3 Transfer Manager depends on the AWS Common Runtime (CRT) libraries, and Alpine Linux is not supported yet in CRT, see similar issue: #2868. But looks like the error message is a bit different this time, can you enable CRT logs and share the stacktrace? Please make sure to redact any sensitive information.

You can enable logs by adding the following statement before you create the transfer manager

// logging to a file
Log.initLoggingToFile(Log.LogLevel.Trace, "log.txt")

// logging to the console
Log.initLoggingToStdout(Log.LogLevel.Trace);

@rzhang90
Copy link
Author

@zoewangg Hi Zoe, Thank you so much for your quick response. Here is the stracktrace:

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713e72c0: Initializing edge-triggered epoll

[DEBUG] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713e72c0: Eventfd not available, falling back to pipe for cross-thread notification.

[TRACE] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713e72c0: pipe descriptors read 35, write 36.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713e72c0: Starting event-loop thread.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713e9900: Initializing edge-triggered epoll

[DEBUG] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713e9900: Eventfd not available, falling back to pipe for cross-thread notification.

[TRACE] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713e9900: pipe descriptors read 38, write 39.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713e9900: Starting event-loop thread.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713ea450: Initializing edge-triggered epoll

[DEBUG] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713ea450: Eventfd not available, falling back to pipe for cross-thread notification.

[TRACE] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713ea450: pipe descriptors read 41, write 42.

[INFO] [2022-05-13T19:22:44Z] [00007fb1c6dfd700] [event-loop] - id=0x7fb2713e72c0: main loop started

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c6dfd700] [event-loop] - id=0x7fb2713e72c0: subscribing to events on fd 35

[INFO] [2022-05-13T19:22:44Z] [00007fb1c6dfd700] [event-loop] - id=0x7fb2713e72c0: default timeout 100000, and max events to process per tick 100

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713ea450: Starting event-loop thread.

[INFO] [2022-05-13T19:22:44Z] [00007fb1c65fc700] [event-loop] - id=0x7fb2713e9900: main loop started

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c65fc700] [event-loop] - id=0x7fb2713e9900: subscribing to events on fd 38

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713eafa0: Initializing edge-triggered epoll

[INFO] [2022-05-13T19:22:44Z] [00007fb1c65fc700] [event-loop] - id=0x7fb2713e9900: default timeout 100000, and max events to process per tick 100

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c65fc700] [event-loop] - id=0x7fb2713e9900: waiting for a maximum of 100000 ms

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c6dfd700] [event-loop] - id=0x7fb2713e72c0: waiting for a maximum of 100000 ms

[INFO] [2022-05-13T19:22:44Z] [00007fb1c5dfb700] [event-loop] - id=0x7fb2713ea450: main loop started

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c5dfb700] [event-loop] - id=0x7fb2713ea450: subscribing to events on fd 41

[INFO] [2022-05-13T19:22:44Z] [00007fb1c5dfb700] [event-loop] - id=0x7fb2713ea450: default timeout 100000, and max events to process per tick 100

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c5dfb700] [event-loop] - id=0x7fb2713ea450: waiting for a maximum of 100000 ms

[DEBUG] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713eafa0: Eventfd not available, falling back to pipe for cross-thread notification.

[TRACE] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713eafa0: pipe descriptors read 44, write 45.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713eafa0: Starting event-loop thread.

[INFO] [2022-05-13T19:22:44Z] [00007fb1c55fa700] [event-loop] - id=0x7fb2713eafa0: main loop started

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c55fa700] [event-loop] - id=0x7fb2713eafa0: subscribing to events on fd 44

[INFO] [2022-05-13T19:22:44Z] [00007fb1c55fa700] [event-loop] - id=0x7fb2713eafa0: default timeout 100000, and max events to process per tick 100

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c55fa700] [event-loop] - id=0x7fb2713eafa0: waiting for a maximum of 100000 ms

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [dns] - id=0x7fb2713eaff0: Initializing default host resolver with 8 max host entries.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [channel-bootstrap] - id=0x7fb2713ecd70: Initializing client bootstrap with event-loop group 0x7fb2713e74a0

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa330: Initializing edge-triggered epoll

[DEBUG] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa330: Eventfd not available, falling back to pipe for cross-thread notification.

[TRACE] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa330: pipe descriptors read 48, write 49.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa330: Starting event-loop thread.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa380: Initializing edge-triggered epoll

[DEBUG] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa380: Eventfd not available, falling back to pipe for cross-thread notification.

[TRACE] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa380: pipe descriptors read 51, write 52.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa380: Starting event-loop thread.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa3d0: Initializing edge-triggered epoll

[DEBUG] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa3d0: Eventfd not available, falling back to pipe for cross-thread notification.

[INFO] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: main loop started

[TRACE] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa3d0: pipe descriptors read 54, write 55.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: subscribing to events on fd 48

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa3d0: Starting event-loop thread.

[INFO] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: default timeout 100000, and max events to process per tick 100

[INFO] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: main loop started

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa420: Initializing edge-triggered epoll

[DEBUG] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa420: Eventfd not available, falling back to pipe for cross-thread notification.

[TRACE] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa420: pipe descriptors read 57, write 58.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [event-loop] - id=0x7fb2713fa420: Starting event-loop thread.

[INFO] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: main loop started

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: subscribing to events on fd 54

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: subscribing to events on fd 51

[INFO] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: default timeout 100000, and max events to process per tick 100

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: waiting for a maximum of 100000 ms

[INFO] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: default timeout 100000, and max events to process per tick 100

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: waiting for a maximum of 100000 ms

[INFO] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: main loop started

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: subscribing to events on fd 57

[INFO] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: default timeout 100000, and max events to process per tick 100

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: waiting for a maximum of 100000 ms

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: waiting for a maximum of 100000 ms

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [tls-handler] - ctx: cannot enable ocsp stapling: OCSP stapling was requested, but is not supported

[ERROR] [2022-05-13T19:22:44Z] [00007fb277db9700] [tls-handler] - ctx: configuration error Error initializing trust store (Error encountered in /codebuild/output/src472507778/src/aws-crt-java/crt/s2n/tls/s2n_x509_validator.c line 118)

[ERROR] [2022-05-13T19:22:44Z] [00007fb277db9700] [tls-handler] - Failed to set ca_path: (null) and ca_file (null)


[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [thread] - id=0x7fb277db2a70: cpu affinity of cpu_id 0 was specified, attempting to honor the value.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb277db9700] [channel-bootstrap] - id=0x7fb2713ecd70: releasing bootstrap reference

[INFO] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa420: Destroying event_loop

[INFO] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa420: Stopping event-loop thread.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa420: Scheduling task 0x7fb2713fdcd8 cross-thread for timestamp 0

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa420: Waking up event-loop thread

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: wake up with 1 events to process.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: activity on fd 57, invoking handler.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: notified of cross-thread tasks to schedule

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: processing cross-thread tasks

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: task 0x7fb2713fdcd8 pulled to event-loop, scheduling now.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [task-scheduler] - id=0x7fb2713fdcd8: Scheduling epoll_event_loop_stop task for immediate execution

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: running scheduled tasks.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [task-scheduler] - id=0x7fb2713fdcd8: Running epoll_event_loop_stop task with <Running> status

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: no more scheduled tasks using default timeout.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: exiting main loop

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: un-subscribing from events on fd 57

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [event-loop] - id=0x7fb2713fa420: scheduling task 0x7fb1bc002150 in-thread for timestamp 0

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b2ffd700] [task-scheduler] - id=0x7fb1bc002150: Scheduling epoll_event_loop_unsubscribe_cleanup task for immediate execution

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [task-scheduler] - id=0x7fb1bc002150: Running epoll_event_loop_unsubscribe_cleanup task with <Canceled> status

[INFO] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa3d0: Destroying event_loop

[INFO] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa3d0: Stopping event-loop thread.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa3d0: Scheduling task 0x7fb2713fd2c8 cross-thread for timestamp 0

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa3d0: Waking up event-loop thread

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: wake up with 1 events to process.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: activity on fd 54, invoking handler.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: notified of cross-thread tasks to schedule

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: processing cross-thread tasks

2022-05-13 19:22:44.952  WARN 1 --- [           main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: ... Constructor threw exception; nested exception is software.amazon.awssdk.crt.CrtRuntimeException: S3Client.aws_s3_client_new: creating aws_s3_client failed (aws_last_error: AWS_IO_TLS_CTX_ERROR(1033), Failed to create tls context) UNKNOWN(-1)

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: task 0x7fb2713fd2c8 pulled to event-loop, scheduling now.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [task-scheduler] - id=0x7fb2713fd2c8: Scheduling epoll_event_loop_stop task for immediate execution

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: running scheduled tasks.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [task-scheduler] - id=0x7fb2713fd2c8: Running epoll_event_loop_stop task with <Running> status

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: no more scheduled tasks using default timeout.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: exiting main loop

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: un-subscribing from events on fd 54

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [event-loop] - id=0x7fb2713fa3d0: scheduling task 0x7fb1b4001550 in-thread for timestamp 0

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b37fe700] [task-scheduler] - id=0x7fb1b4001550: Scheduling epoll_event_loop_unsubscribe_cleanup task for immediate execution

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [task-scheduler] - id=0x7fb1b4001550: Running epoll_event_loop_unsubscribe_cleanup task with <Canceled> status

[INFO] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa380: Destroying event_loop

[INFO] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa380: Stopping event-loop thread.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa380: Scheduling task 0x7fb2713f9758 cross-thread for timestamp 0

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa380: Waking up event-loop thread

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: wake up with 1 events to process.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: activity on fd 51, invoking handler.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: notified of cross-thread tasks to schedule

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: processing cross-thread tasks

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: task 0x7fb2713f9758 pulled to event-loop, scheduling now.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [task-scheduler] - id=0x7fb2713f9758: Scheduling epoll_event_loop_stop task for immediate execution

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: running scheduled tasks.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [task-scheduler] - id=0x7fb2713f9758: Running epoll_event_loop_stop task with <Running> status

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: no more scheduled tasks using default timeout.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: exiting main loop

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: un-subscribing from events on fd 51

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [event-loop] - id=0x7fb2713fa380: scheduling task 0x7fb1b8001250 in-thread for timestamp 0

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b3fff700] [task-scheduler] - id=0x7fb1b8001250: Scheduling epoll_event_loop_unsubscribe_cleanup task for immediate execution

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [task-scheduler] - id=0x7fb1b8001250: Running epoll_event_loop_unsubscribe_cleanup task with <Canceled> status

[INFO] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa330: Destroying event_loop

[INFO] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa330: Stopping event-loop thread.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa330: Scheduling task 0x7fb2713fa918 cross-thread for timestamp 0

[TRACE] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [event-loop] - id=0x7fb2713fa330: Waking up event-loop thread

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: wake up with 1 events to process.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: activity on fd 48, invoking handler.

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: notified of cross-thread tasks to schedule

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: processing cross-thread tasks

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: task 0x7fb2713fa918 pulled to event-loop, scheduling now.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [task-scheduler] - id=0x7fb2713fa918: Scheduling epoll_event_loop_stop task for immediate execution

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: running scheduled tasks.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [task-scheduler] - id=0x7fb2713fa918: Running epoll_event_loop_stop task with <Running> status

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: no more scheduled tasks using default timeout.

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: exiting main loop

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: un-subscribing from events on fd 48

[TRACE] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [event-loop] - id=0x7fb2713fa330: scheduling task 0x7fb1ac001370 in-thread for timestamp 0

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1c4df9700] [task-scheduler] - id=0x7fb1ac001370: Scheduling epoll_event_loop_unsubscribe_cleanup task for immediate execution

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [task-scheduler] - id=0x7fb1ac001370: Running epoll_event_loop_unsubscribe_cleanup task with <Canceled> status

[DEBUG] [2022-05-13T19:22:44Z] [00007fb1b27fc700] [S3Client] - id=0x7fb27161f2a0 Client body streaming ELG shutdown.

#

# A fatal error has been detected by the Java Runtime Environment:

#

#  SIGSEGV (0xb) at pc=0x00007fb1ec15f260, pid=1, tid=0x00007fb1b27fc700

#

# JRE version: OpenJDK Runtime Environment (8.0_212-b03) (build 1.8.0_212-b03)

# Java VM: OpenJDK 64-Bit Server VM (25.212-b03 mixed mode linux-amd64 compressed oops)

# Problematic frame:

# C  [AWSCRT_16524697646286961603906954472286libaws-crt-jni.so+0xc0260]

#

# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

#

# An error report file with more information is saved as:

# //hs_err_pid1.log

2022-05-13 19:22:44.963  INFO 1 --- [           main] o.apache.catalina.core.StandardService   : Stopping service [Tomcat]

#

# If you would like to submit a bug report, please visit:

#   http://bugreport.java.com/bugreport/crash.jsp

#


[error occurred during error reporting , id 0xb]

@rzhang90
Copy link
Author

Hi @zoewangg , could you please give me some possible alternatives or a white list of supported linux versions? Thank you.

@zoewangg
Copy link
Contributor

Apologies for the delayed response. Below are the relevant error logs. I will reach out to CRT team to investigate further.

[INFO] [2022-05-13T19:22:44Z] [00007fb277db9700] [tls-handler] - ctx: cannot enable ocsp stapling: OCSP stapling was requested, but is not supported

[ERROR] [2022-05-13T19:22:44Z] [00007fb277db9700] [tls-handler] - ctx: configuration error Error initializing trust store (Error encountered in /codebuild/output/src472507778/src/aws-crt-java/crt/s2n/tls/s2n_x509_validator.c line 118)

[ERROR] [2022-05-13T19:22:44Z] [00007fb277db9700] [tls-handler] - Failed to set ca_path: (null) and ca_file (null)

Non alpine Linux should be supported. You can also try with building CRT yourself on that platform. Can you also try with the latest version? (2.17.192 as of today)

@rzhang90
Copy link
Author

@zoewangg Thank you. I changed my base image from alpine to debian and it works.

@zoewangg
Copy link
Contributor

Good to hear! We will close this issue and track alpine support in #2868

@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

aws-sdk-java-automation added a commit that referenced this issue Aug 21, 2024
…fc37bd9d9

Pull request: release <- staging/572d51bc-2184-4b09-b010-1cffc37bd9d9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. dependencies This issue is a problem in a dependency. transfer-manager
Projects
None yet
Development

No branches or pull requests

2 participants