Hi Ayesh, This error comes when you don't have synapse artifacts in the deployment/server location. As you are using host path for mounting, make sure host mount paths are empty or use the server folder files. There is a chance that mounts get exchanged as it dynamically pics the mounts when you redeploy the deployment.
One solution is to delete the content in the host mounts when you are redeploying the entire deployment. As we are using host path, we need to restrict the deployment (ex: wso2apim-manager-worker) to a known host. Otherwise, when the pod respins for some reason, it would lose the data already had when spins up in another host node. These limitations have been tackled in NFS based mounting [2]. [2] - https://github.com/wso2/kubernetes-apim/releases/tag/v2.1.0-2 Thank you! On Thu, Sep 28, 2017 at 12:19 PM, Ayeshmantha Perera < [email protected]> wrote: > Hi all, > > As mentioned in the kubernetes artifacts deployment documentation [1] we > have built the base image and deployed k8 artifacts with the pattern 1. > Although artifacts got deployed without an error at deployment time, and > the analytics dashboard is accessible via : https://wso2apim-analytics/ > carbon the API manager is not working as expected. > When going through the logs in wso2-apim-worker and > wso2-api-manager-worker pods, we can see below error: > > [2017-09-28 06:21:53,224] FATAL - ServiceBusInitializer Couldn't > initialize the ESB... > org.apache.synapse.SynapseException: The synapse.xml location > ././repository/deployment/server/synapse-configs/default doesn't exist > at org.apache.synapse.SynapseControllerFactory.handleFatal( > SynapseControllerFactory.java:121) > at org.apache.synapse.SynapseControllerFactory.validatePath( > SynapseControllerFactory.java:113) > at org.apache.synapse.SynapseControllerFactory.validate( > SynapseControllerFactory.java:88) > at org.apache.synapse.SynapseControllerFactory.createSynapseController( > SynapseControllerFactory.java:44) > at org.apache.synapse.ServerManager.init(ServerManager.java:103) > at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB( > ServiceBusInitializer.java:451) > at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate( > ServiceBusInitializer.java:196) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.internal.ds.model.ServiceComponent. > activate(ServiceComponent.java:260) > at org.eclipse.equinox.internal.ds.model.ServiceComponentProp. > activate(ServiceComponentProp.java:146) > at org.eclipse.equinox.internal.ds.model.ServiceComponentProp. > build(ServiceComponentProp.java:345) > at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent( > InstanceProcess.java:620) > at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents( > InstanceProcess.java:197) > at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343) > > We also ran the apim-kubernetes:2.1.0 docker image in the deployed VM > instance, and it starts up without above error, so we think this is > something related to the kubernetes artifacts. > > Appreciate if someone can help us to resolve this deployment issue. > > Regards, > Ayeshmantha > > [1] https://github.com/wso2/kubernetes-apim/tree/v2.1.0-1 > -- *Pubudu Gunatilaka* Committer and PMC Member - Apache Stratos Senior Software Engineer WSO2, Inc.: http://wso2.com mobile : +94774078049 <%2B94772207163>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
