Kernel notifier crashloopback

2023-10-17 07:55:31,879 [main] INFO [o.s.c.c.c.ConfigServicePropertySourceLocator].getRemoteEnvironment.206 : Fetching config fr om server at : http://config-server.config-server/config
2023-10-17 07:55:32,672 [main] WARN [o.s.c.c.c.ConfigServicePropertySourceLocator].locate.141 : Could not locate PropertySource: label not found
2023-10-17 07:55:32,675 [main] INFO [o.s.b.SpringApplication].logStartupProfileInfo.663 : The following profiles are active: def ault
2023-10-17 07:55:32,687 [main] INFO [o.s.c.s.AbstractApplicationContext].prepareRefresh.590 : Refreshing org.springframework.boo t.web.servlet.context.AnnotationConfigServletWebServerApplicationContext@368247b9: startup date [Tue Oct 17 07:55:32 UTC 2023]; parent: org.springframework.context.annotation.AnnotationConfigApplicationContext@21507a04
2023-10-17 07:55:32,967 [main] WARN [o.s.c.s.AbstractApplicationContext].refresh.558 : Exception encountered during context init ialization - cancelling refresh attempt: org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configu ration class [io.mosip.kernel.emailnotification.NotificationBootApplication]; nested exception is java.lang.IllegalArgumentExcep tion: Could not resolve placeholder ‘mosip.auth.adapter.impl.basepackage’ in value “${mosip.auth.adapter.impl.basepackage}”
2023-10-17 07:55:32,971 [main] ERROR [o.s.b.SpringApplication].reportFailure.842 : Application run failed
org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configuration class [io.mosip.kernel.emailnotifi cation.NotificationBootApplication]; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder ‘mosi p.auth.adapter.impl.basepackage’ in value “${mosip.auth.adapter.impl.basepackage}”
at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:184)
at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClas sPostProcessor.java:316)
at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(Configuratio nClassPostProcessor.java:233)
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(Post ProcessorRegistrationDelegate.java:273)
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRe gistrationDelegate.java:93)
at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationCon text.java:694)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:532)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationCo ntext.java:140)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:759)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:395)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:327)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1255)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1243)
at io.mosip.kernel.emailnotification.NotificationBootApplication.main(NotificationBootApplication.java:29)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
at org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:593)
Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder ‘mosip.auth.adapter.impl.basepackage’ in value “${m osip.auth.adapter.impl.basepackage}”
at org.springframework.util.PropertyPlaceholderHelper.parseStringValue(PropertyPlaceholderHelper.java:172)
at org.springframework.util.PropertyPlaceholderHelper.replacePlaceholders(PropertyPlaceholderHelper.java:124)
at org.springframework.core.env.AbstractPropertyResolver.doResolvePlaceholders(AbstractPropertyResolver.java:237)
at org.springframework.core.env.AbstractPropertyResolver.resolveRequiredPlaceholders(AbstractPropertyResolver.java:211)
at org.springframework.core.env.AbstractEnvironment.resolveRequiredPlaceholders(AbstractEnvironment.java:567)
at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.resolveBasePackage(ClassPathScanni ngCandidateComponentProvider.java:481)
at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.scanCandidateComponents(ClassPathS canningCandidateComponentProvider.java:420)
at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathS canningCandidateComponentProvider.java:316)
at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:275)
at org.springframework.context.annotation.ComponentScanAnnotationParser.parse(ComponentScanAnnotationParser.java:132)
at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser. java:288)
at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.ja va:245)
at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:202)
at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:170)
… 21 common frames omitted

Dear @paredescedric3 , As per above screen shot, Error triggered in ${mosip.auth.adapter.impl.basepackage} property missing.

Please check application-default.properties file whether below property available or not. incase not available please add it

mosip.auth.adapter.impl.basepackage=io.mosip.kernel.auth.defaultadapter

and also artifactory pod should up and run

Where can we edit the application default.properties?

Hello @thamarai_kannan How can we access the application default properties,

application default.properties present in mosip-config repository. i hope you have clone the mosip-config repository to your local github for mosip config-server deployment

Thanks for the reply @thamarai_kannan

does this suffice that?


Or do we need to clone first the mosip-config repo, then we run ./install.sh?

as checked on the the git, it is already added

Hello @thamarai_kannan

and also artifcatory is running,

hi @paredescedric3 , as per the screen shot, you are using mosip-config from mosip organization. its better to clone the mosip-config to your local organization and modify the application-default.properties then use same in you config-server

once clone done check the below property in application-default,properties
mosip.auth.adapter.impl.basepackage=io.mosip.kernel.auth.defaultadapter

Hello @thamarai_kannan
How to point the repository to our cloned config-server, it seems that it is still using the git ones

Are you using Environment V2 or V3 ?

Hi @thamarai_kannan Im currently using V3

Hello @thamarai_kannan

Updates sir?

In V3, you have to Update the Github Url & User id in

Namespace : Config-server
configmaps : config-server-env-vars
Fields to Update : SPRING_CLOUD_CONFIG_SERVER_GIT_URI & SPRING_CLOUD_CONFIG_SERVER_GIT_USERNAME

and for Github branch details in
Namespace : multiple Namespace
Configmaps : config-server-share
Fields to update : spring_config_label_env

for Github secrets
Namespace : config-server
Secret : config-server
Fields: github-token

Thank you so much @thamarai_kannan
it now works, I really appreciate your feedback

Hi @paredescedric3

I hope we were able to solve your issue and for further queries, you can raise another ticket here on our community channel.

Best Regards,
Team MOSIP