JSReport container deployed in Azure terminating after start completed (was working fine)
-
HI,
Our company has deployed JSReport 3.7.1 as a Web App in Azure. This has been done long time ago (before me joining the company) so I am not familiar with the details of how this was done. But it has been running without problems for several years.
We used the free version for a long time because we had less than 5 templates. Recently we added more templates and had to purchase a license.
We have 2 instances running - one production and one development.
On the production instance I set the environment variable "licenseKey" with a value of the key we purchased and everything has been fine since.
But on the development version I set 2 variables - "licenseKey" & "license_development", the second with a value "true".
For a while things were working OK.
Then I needed to restart that instance and since then it just stopped working. Seems like the container is terminating right after the start completes.
Here is the log file (sanitized of potentially sensitive info):2024-08-30T07:50:08.3433473Z Container start method called. 2024-08-30T07:50:08.3716913Z Establishing network. 2024-08-30T07:50:08.4116379Z Pulling image: appsvc/kudulite:bullseye_xxxxx.2.tuxprod. 2024-08-30T07:50:11.2395698Z Container is starting. 2024-08-30T07:50:11.2396626Z Establishing user namespace if not established already. 2024-08-30T07:50:11.2397032Z Establishing network if not established already. 2024-08-30T07:50:11.2397398Z Mounting volumes. 2024-08-30T07:50:11.2575913Z Nested mountpoint 2024-08-30T07:50:11.2969536Z Nested mountpoint volatile/logs 2024-08-30T07:50:11.3069608Z Nested mountpoint 2024-08-30T07:50:11.3737112Z Nested mountpoint 2024-08-30T07:50:11.4434581Z Nested mountpoint 2024-08-30T07:50:11.4729696Z Creating container. 2024-08-30T07:50:11.4887675Z Creating pipes for streaming container io. 2024-08-30T07:50:11.4896121Z Creating stdout named pipe at /podr/container/pipe... 2024-08-30T07:50:11.4916482Z Successfully created stdout named pipe at: /podr/container/pipe... 2024-08-30T07:50:11.4923301Z Opening named pipe /podr/container/pipe... for reading in non-blocking mode. 2024-08-30T07:50:11.4985931Z Successfully opened named pipe: /podr/container/pipe... 2024-08-30T07:50:11.4990180Z Successfully removed non-blocking flag from /podr/container/pipe... 2024-08-30T07:50:11.4996105Z Creating stderr named pipe at /podr/container/pipe... 2024-08-30T07:50:11.5001919Z Successfully created stderr named pipe at: /podr/container/pipe... 2024-08-30T07:50:11.5005763Z Opening named pipe /podr/container/pipe... for reading in non-blocking mode. 2024-08-30T07:50:11.5009557Z Successfully opened named pipe: /podr/container/pipe... 2024-08-30T07:50:11.5013324Z Successfully removed non-blocking flag from /podr/container/pipe... 2024-08-30T07:50:11.5081193Z Creating container with image: appsvc/kudulite:bullseye_XXX.2.tuxprod from registry: mcr.microsoft.com and fully qualified image name: mcr.microsoft.com/appsvc/kudulite:bullseye_XXX.2.tuxprod 2024-08-30T07:50:13.6333579Z Starting container: xxxxxx-jsreport-app1_kudu_xxxxx. 2024-08-30T07:50:13.9076342Z Starting watchers and probes. 2024-08-30T07:50:13.9154763Z Starting metrics collection. 2024-08-30T07:50:13.9175611Z Container is running. 2024-08-30T07:50:13.9938233Z Container start method finished after 5649 ms. 2024-08-30T07:50:45.4248059Z Container is terminating. Grace period: 0 seconds. 2024-08-30T07:50:45.4617662Z Stop and delete container. Retry count = 0 2024-08-30T07:50:45.4709063Z Stopping container: xxxxxx-jsreport-app1_kudu_xxxxx. 2024-08-30T07:50:45.6911918Z Deleting container: xxxxxx-jsreport-app1_kudu_xxxxx. Retry count = 0 2024-08-30T07:50:46.1235109Z Container spec TerminationMessagePolicy path 2024-08-30T07:50:46.1314138Z Container is terminated. Total time elapsed: 705 ms.Is there something I can do to fix the problem?
If not - are there instructions on how to redeploy the latest version again?
-
These are the azure system logs which aren't useful to me. Please share the app logs (stdout/stderr) from the app container.
This can be enabled somewhere in the azure portal...