Cluster problem
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Bonjour, lors de la mise en place d'un backup sur un controller omada avec le mode cluster. le node backup pert la connexion et impossible d'afficher la page interface ensuite .<
dans le log j'ai :
h.f(): Can not connect remote mongoDb, set self primary.
pouvez vous m'aider
________________
Hello, when setting up a backup on an omada controller with cluster mode. the backup node loses the connection and cannot display the interface page afterwards . <
in the log I Dve:
h.f(): Can not connect remote mongoDb, set self primary.
Thank
Hi @Yann77 ‘’
What's the status of the backup node on the following page? Please share a screenshot:
If it's disconnected, please ping the IP address and let us know the result.
BTW, you may also refer to the troubleshoot suggestion in the following FAQ: check the differences of the nodes system time.
How to Configure Distributed Cluster Mode on Linux Controller
Bonjour vincent,
Nous n'avons pas du tout la meme interface. enfin presque.
J'ulilise le 'noeud a chaud', avec cette traduction horrible au passage.
A la fin sur mon noeud principal je me retrouve avec "not connected" a mon souvenir, et le second ne redemarre jamais avec le mesage dans le log sité plus haut,et obbliger de réinstaller.
J'ai pas essayer la partie Mixed car il me demmande plusieurs noeud ; sauf que j'en est que deux.
PS : Je pensse sincerement a quitter Omada et partir sur Unifi car les bug a repetition, mise a jour flinger , traduction foirreuse, bug jamais résolut cela devient amateur de la part de TP Link pour du matos pro; sans compter un routeur qui a crammer au bout d'un an ...
-------
Hello Vincent,
We don't have the same interface at all. Well, almost.
I'm using the 'hot node', with that horrible translation by the way.
In the end, on my main node, I get "not connected" as I remember, and the second one never restarts with the message in the log mentioned above, and I have to reinstall.
I haven't tried the Mixed part because it asks me for several nodes; except I only have two.
PS: I'm sincerely thinking of leaving Omada and switching to Unifi because of the recurring bugs, the sluggish updates, the shoddy translation, the bugs never resolved; it's becoming amateurish for TP Link to use for professional equipment; not to mention a router that died after a year...
______
Je vient de re re re commencer la manip ,
Pour la partie modification SSH cela n'est pas faisable sur synology et même apres recherche je n'est pas trouver le fichier.
Apres reboot des deux , le principal est bien la , le second ne redemarre jamais correctement.
Le vous joint les derniers logs en piece joint
Hello,
got the same issue while testing out Omada Cluster Backup.
After setup like described my secondary node cannot connect to the MongoDB on the first primary node.
Firewall is open, even for testing i disabled it completly.
I think it may be related to the mongodb setting, which listens only on localhost (127.0.0.1) per default, or will the cluster-config overwrite this setting on primary node?
Attached you will find server.log and mongodb.log from secondary node:
