Warning! This service has been deregistered and no longer exists in the catalog

Consul
1

Hey,
i have an issue with service registered on consul .
I am creating 2 instances of same job and they are scheduling on two different client nodes . Because i want to run them in High Availability.
i have added a single service in nomad job configuration file. The job is deployed successfully and service i also created .
But the service is conficting, it is getting registered and deregistered frequently, sometimes point to client node 1 and sometimes to client node 2.
I don’t understand why this happening .
[Note : If i stop the one node and then run the job , then it works fine]

Please suggest me how i can resolve this issue.

1 Like
2

I think that the issue is related to missconfiguration. The nomad client should point to CONSUL_CLIENT_HOST:CONSUL_CLIENT_PORT.

E.g

consul {
    # The address to the Consul agent.
    address = "127.0.0.1:8500"
    token = ".xxxx"
   ....
}
3

Is there anyone to solve this problem? I have been looking for this problem for several days, but it has not been solved.
Is a periodic online, about 10 to 10 seconds off the line, and then online.
go round and begin again

2 Likes
4

Have you figured out how to resolve that?