search cancel

RESTMon Instance not completing boot process

book

Article ID: 252969

calendar_today

Updated On:

Products

DX Operational Intelligence

Issue/Introduction

Issue:

Trying to deploy the RESTMon image caapm/dx-restmon:2.2 on an EKS Node in AWS. After the helm install command, the container hangs on the Spring Boot Initialization:

[http-nio-8080-exec-2] INFO  [/restmon/api]:173 - Initializing Spring DispatcherServlet 'dispatcherServlet'

 

Troubleshooting:

For troubleshooting I tried switching to debug. Here are the entries I changed in the values.yaml

#Health specific logger

logging.level.com.ca.ce.restmon.app.health=debug

#DataCollector URL And Response Logger

logging.level.UrlResponseLogger=on

 

What Happened:

After I scale down/up it goes into a CrashLoopBackOff state. I also tried blowing away the namespace and attaching the K8s label to a different Node in the cluster then rebuilding Here’s the problem in the kubectl pod log:

Reason: failed to convert java.lang.String to org.springframework.boot.logging.LogLevel (caused by java.lang.IllegalArgumentException: No enum constant org.springframework.boot.logging.LogLevel.on)

Once I switch the UrlResponseLogger back to “off” it makes it back to the original error:

[http-nio-8080-exec-2] INFO  [/restmon/api]:173 - Initializing Spring DispatcherServlet 'dispatcherServlet'

Environment

Release : 21.3

Resolution

Running a curl put statement on the appd.json got data flowing

Additional Information

logging.level.UrlResponseLogger=debug (the value of "on" is not supported value)