Closed g4challenge closed 7 years ago
That's very weird, because I am removing and adding back my servers all the time, never had this kind of problem.
I suppose it's related to the way a host has been into a pool and moved back or something like that.
@g4challenge If you could provide a step-by-step recipe to reproduce, it would be a great help :)
Cannot reproduce. @olivierlambert?
Okay, found something: when you modify the IP in the UI, it's modified in our database, but xo-server
will continue to try to connect with the "old" until it's restarted.
@g4challenge can you restart xo-server
and tell me if it solves your issue?
i restarted the appliance, but still the issue is persisting,.... is there any way to clear the cache/database?
Yes it's possible to clear the application database (redis-cli FLUSHALL
), but it would be better for us to be able to reproduce, understand and fix the issue :)
I think it could worth the try to display the list of saved servers via xo-cli
What do you think @julien-f ?
Yeah, sure, @g4challenge, could you check the server list using xo-cli
to see if the old IP is still there?
> npm install -g xo-cli
> xo-cli --register https://xo.company.tld admin@admin.net password
> xo-cli server.getAll
If you want us to take a look at the result without divulging it publicly, you can either add it in HTML comment in your next message (<!-- secret message -->
) or send it to us via email.
@g4challenge any news regarding this?
setting up a new instance solved it, could not find anything special in the cli. Thanks
Context
Expected behavior
Adding a server should work, even if the server has been connected before, deleted and now will be added again.
Current behavior
Message that tells me the server is already existing: