Skip to main content

Hello,

I’m actually running an instance of FME Server deployed using Safe Software’s Helm chart.

The core component image version is 2024.1, and the HTTP readiness probe path is the following:

/fmeapiv4/healthcheck/readiness
 
The result of a get request is the following:
{
"status": "notReady",
"message": "One or more essential processes are unavailable.",
"components": t
{
"component": "notifier",
"status": "up"
},
{
"component": "connections",
"status": "up"
},
{
"component": "queue",
"status": "up"
},
{
"component": "resources",
"status": "up"
},
{
"component": "core",
"status": "up"
},
{
"component": "cleanup",
"status": "up"
},
{
"component": "configuration",
"status": "up"
},
{
"component": "relayer",
"status": "up"
},
{
"component": "scheduler",
"status": "up"
}
],
"initializationTasks": k
{
"task": "installDefaultContent",
"status": "failure"
}
]
}

The problem seems to be with initialization tasks.

Do you have a pointer to where to look in order to fix this ?

Thanks

Hello

What deployment type are you using to install FME? Also if using Kubernetes can you run describe on the core container and post what information you see there? in the meantime, It could also be helpful to restart the services 


Reply