Hi there.
I am facing the following issue with the distributed launched YETI (Version 1.12) services which are not detected on all-in-one host solution.
For your reference: I have WEB, CDR, SIP-1 and SIP-2 on different hosts (in total 4 hosts).
SEMS nodes (2 nodes) on dedicated hosts and there is an issue with autostarting. Manual start after machine full loading (service sems start) starts SIP node successfully and all hosts work well together.
I saw similar topics earlier with recomndation to add After=postgresql.service in to /lib/systemd/system/sems.service
In my version it is present by default after install (After=postgresql.service redis-server.service network-online.target)
Please advise what I need to do or what I did wrong (seems all done according to the manual).
It looks like “systemctl enable sems” solve the problem
Just clarify why on single-host instalation it enabled by default and not on a distributed one.
I think you have to ask person who installed it. Because sems package installation scripts have no idea is it “distributed installation” or not.
Thanks for the reply @dmitry.s
System installed by me and as I remember everything was done the same
Anythere, issue resolved now. Will take note for future