[Bug] Unable to register Log4j shutdown hook

[qianghong000]

Search before asking

• I had searched in the issues and found no similar issues.

Apache SkyWalking Component

OAP server (apache/skywalking)

What happened

The OAP service restarts frequently many times before it returns to the normal state
The OAP service logs are as follows：
2024-11-29 07:30:29,578 Thread-1 WARN Unable to register Log4j shutdown hook because JVM is shutting down. Using SimpleLogger

What you expected to happen

The OAP service can be in the READY status without restarting

How to reproduce

Deploy via the https://github.com/apache/skywalking-helm/tree/master link

Anything else

No response

Are you willing to submit a pull request to fix on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

This is just a warning, it would not affect the booting.

[qianghong000]

The restart event is：Container oap failed liveness probe, will be restarted

I tried to modify the health check time via the：--set oap.livenessProbe.initialDelaySeconds=60 --set oap.livenessProbe.periodSeconds=60command argument, but it was useless

[wu-sheng]

You could change the log level of OAP to DEBUG, and see what is happening.

[qianghong000]

I modified the values.yaml configuration and couldn't change it to the DEBUG log level。

oap:
  name: oap
  image:
    tag: null
  storageType: elasticsearch
  ports:
    grpc: 11800
    rest: 12800
  replicas: 2
  nodeSelector:
    role: apm
  config:
    log4j2.xml: |
     <Configuration status="DEBUG">
       <!-- ... -->
     </Configuration>

[qianghong000]

After about 6-8 restarts, the status becomes stable

[qianghong000]

2024-11-29 08:11:37,539 org.apache.skywalking.oap.server.library.server.grpc.GRPCServer 133 [main] INFO [] - Bind handler CLRMetricReportServiceHandler into gRPC server 0.0.0.0:11800
2024-11-29 08:11:37,542 org.apache.skywalking.oap.server.library.server.grpc.GRPCServer 133 [main] INFO [] - Bind handler CLRMetricReportServiceHandlerCompat into gRPC server 0.0.0.0:11800
2024-11-29 08:11:37,548 org.apache.skywalking.oap.server.library.module.BootstrapFlow 43 [main] INFO [] - start the provider default in receiver-otel module.
2024-11-29 08:11:42,364 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric aws_gateway_service_4xx is already defined, so skip the metric creation.
2024-11-29 08:11:42,422 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric aws_gateway_service_5xx is already defined, so skip the metric creation.
2024-11-29 08:11:43,420 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric aws_gateway_endpoint_4xx is already defined, so skip the metric creation.
2024-11-29 08:11:43,471 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric aws_gateway_endpoint_5xx is already defined, so skip the metric creation.
2024-11-29 08:11:48,506 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_cpu_total_percentage is already defined, so skip the metric creation.
2024-11-29 08:11:48,543 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_cpu_average_used is already defined, so skip the metric creation.
2024-11-29 08:11:48,557 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_cpu_load1 is already defined, so skip the metric creation.
2024-11-29 08:11:48,570 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_cpu_load5 is already defined, so skip the metric creation.
2024-11-29 08:11:48,584 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_cpu_load15 is already defined, so skip the metric creation.
2024-11-29 08:11:48,597 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_memory_total is already defined, so skip the metric creation.
2024-11-29 08:11:48,610 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_memory_available is already defined, so skip the metric creation.
2024-11-29 08:11:48,635 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_memory_used is already defined, so skip the metric creation.
2024-11-29 08:11:48,692 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_memory_swap_free is already defined, so skip the metric creation.
2024-11-29 08:11:48,725 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_memory_swap_total is already defined, so skip the metric creation.
2024-11-29 08:11:48,755 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_memory_swap_percentage is already defined, so skip the metric creation.
2024-11-29 08:11:48,778 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_filesystem_percentage is already defined, so skip the metric creation.
2024-11-29 08:11:48,794 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_disk_read is already defined, so skip the metric creation.
2024-11-29 08:11:48,809 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_disk_written is already defined, so skip the metric creation.
2024-11-29 08:11:48,828 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_network_receive is already defined, so skip the metric creation.
2024-11-29 08:11:48,843 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_network_transmit is already defined, so skip the metric creation.
2024-11-29 08:11:48,858 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_tcp_curr_estab is already defined, so skip the metric creation.
2024-11-29 08:11:48,873 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_tcp_tw is already defined, so skip the metric creation.
2024-11-29 08:11:48,887 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_tcp_alloc is already defined, so skip the metric creation.
2024-11-29 08:11:48,945 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_vm_udp_inuse is already defined, so skip the metric creation.
2024-11-29 08:11:49,906 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_apisix_endpoint_http_status is already defined, so skip the metric creation.
2024-11-29 08:11:49,924 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_apisix_endpoint_bandwidth is already defined, so skip the metric creation.
2024-11-29 08:11:49,941 org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem 202 [main] INFO [] - Metric meter_apisix_endpoint_http_latency is already defined, so skip the metric creation.
2024-11-29 08:12:11,539 Thread-1 WARN Unable to register Log4j shutdown hook because JVM is shutting down. Using SimpleLogger

[qianghong000]

I didn't find the variable name for the log4j2.xml log level

[qianghong000]

I should know the reason because I installed the latest version in the way above。

But I installed the release version in the way recommended below, and the network was abnormal

Error: INSTALLATION FAILED: failed to do request: Head "https://registry-1.docker.io/v2/apache/skywalking-helm/manifests/4.7.0": dial tcp 45.114.11.238:443: connect: connection timed out

[wu-sheng]

If you are in China mainland, you need to deal with that common issue.

[qianghong000]

helm pull oci://registry-1.docker.io/apache/skywalking-helm
I switched to the U.S. network and still can't download. Please have the address of the helm private repository in China

[qianghong000]

I want to install the latest stable version and don't want to use the development version of the master branch