wood-j

same issue @2021

Scree shots of zk, port `32001` is the nodeport service i created to output the port `2181` of pod `serving-zookeeper-0`. Before restart:  After restart: 

@owlet42 Hi owlet, we have set `persistence: true` in our cluster.yml and cluster_serving.yml of `fate-9999` and `fate-10000`, but `false` of `exchange`, is that the issue? After I set the `persistence:...

Hi @JingChen23, here is the cluster.yaml content of exchange cluster. ```yaml name: fate-exchange namespace: fate-exchange chartName: fate-exchange chartVersion: v1.8.0 partyId: 1 #

By the way, I tried to deploy a similar cluster with docker-compose from this [doc](https://github.com/FederatedAI/KubeFATE/blob/master/docker-deploy/README.md) Added persistent volume to zookeeper for serving: ```yaml serving-zookeeper: image: "bitnami/zookeeper:3.7.0" ports: - "2181:2181" -...

@JingChen23 > Oops, I wanted to say cluster_serving.yml but somehow I let yot to show the exchange.yaml. > > Could you please also show cluster_serving.yml? So that we can try...

Hi @JingChen23 @owlet42 Guys, glad to tell you that this has been solved. The direct cause is the persistent issue of serving server container(pod), the following path is not included...

I had the same result info but not all the same When i scroll up all the output, I got some lines like: ``` Loading "jinja.coffee" tasks...ERROR >> Error: Grunt...

Same log but different cause, basiclly the eggroll sub process error: My cluster is run with: - k3s - self built image on arm64v8 - base on code release `1.8.0`...

Great job, Thanks While it's not avaliable at 2020/11, I just use your commit as a monkey patch so solve my problem. Thanks aloooooooooooooooot! By the way, I found that...