Hi, Please check the controller services in the NiFi UI to get the details as to why those controller services are not valid. If I had to guess, I'd say that this is an unexpected side-effect of the JIRA [1] even though those changes should not cause such effects. The likely solution is to manually disable the problematic controller service(s), fix the corresponding configuration issues, and re-enable the controller services.
Would love to know what the problems are though... We may have to fix something. [1] https://issues.apache.org/jira/browse/NIFI-14109 Thanks, Pierre Le mer. 24 sept. 2025 à 19:09, [email protected] <[email protected]> a écrit : > > Dear community, > > Since updating from NiFi 2.4 to NiFi 2.6, I have been getting the > following errors: > > ERROR > Could not start > StandardControllerServiceNode[service=MapCacheServer[id=fa3ffa43-0193-1000-1b02-4a4de9da8762], > name=MapCacheServer, active=true] due to > java.util.concurrent.ExecutionException: > java.lang.IllegalStateException: Cannot enable > StandardControllerServiceNode[service=MapCacheServer[id=fa3ffa43-0193-1000-1b02-4a4de9da8762], > name=MapCacheServer, active=true] because it is not valid > > ERROR > Could not start > StandardControllerServiceNode[service=SSLContextService[id=b3942123-018b-1000-3507-9ecf751f5bbc], > name=StandardRestrictedSSLContextService, active=true] due to > java.util.concurrent.ExecutionException: > java.lang.IllegalStateException: Cannot enable > StandardControllerServiceNode[service=SSLContextService[id=b3942123-018b-1000-3507-9ecf751f5bbc], > name=StandardRestrictedSSLContextService, active=true] because it is not > valid > > I am using Ubuntu 22.04 and Java 21.0.8 (OpenJDK). > > Is this a known issue? > > Did I forget something when upgrading? > Was there a name change to any class in Java that requires flow.json.gz > to be adjusted? > Am I overlooking something else? > > Does anyone have any advice or ideas? > > Regards, > Kay-Uwe >
