Hi!
Sure, we have compiled an article for that, please refer to the link below:
Looking forward to your feedback,
Cheers.
Just to add that next week will be a new release of RELIANOID CE, so probably you could wait until it is released and enjoy of the new features.
Cheers.
Hi!
If your configuration is simple, you could deploy a new instance of RELIANOID CE Load Balancer and then, apply the configuration.
In regards to the SSL certificates, you can copy them without concern to the new instance.
Kind Regards.
Thank you for your report, we’ll take care of it for the next release RELIANOID CE 7.2
Cheers.
Can you send the farm configuration files via support@relianoid.com ?
Thank you.
Did you follow this guide?
Migrating from Zevenet CE to RELIANOID ADC Load Balancer Community Edition
Or which script did you use?
Thank you.
You could edit the farm configuration file of every proxy farm and add the Control directive in the form:
Control “/tmp/FARMNAME_proxy.socket”
Just before the ListenHTTP(S) directive. Then restart the farms and they should create the control socket.
Cheers.
The template for the proxy configuration is under /usr/local/relianoid/share/poundtpl.cfg and should include such directive. How did you created such farms? Did you imported a backup?
Thanks,
In case that it is about a HTTP farm you should have a “pound” process running that should open a control socket defined in the directive “Control” of the farm configuration file “/usr/local/relianoid/config/FARM-NAME_proxy.cfg”. Then, you could execute the ctl command over such socket defined in the farm configuration.
root@noid-ce:~# /usr/local/relianoid/app/pound/sbin/poundctl -c /tmp/<FARM_NAME>_proxy.socket
If the socket is defined but doesn’t exist then that could be the status problem faced. Restarting the farm should regenerate the socket file.
Cheers.
If farmguardian is not detecting down the backends, probably is the reverse proxy. Please check the status of the backends with the command:
root@noid-ce:~# /usr/local/relianoid/app/pound/sbin/poundctl -c /tmp/<FARM_NAME>_proxy.socket
Cheers.
Ciao Stefano,
Please refer to the documentation explaining the color codes for both HTTP and L4 farms.
The “critical” status would mean there are no backends available to deliver the traffic. You could disable temporary the farm guardian advanced checks just to confirm the health scripts are not affecting to the status of the backends.
Hope that helps,
Regards.
Hi Vlad, thank you for the report, this will be included in the upcoming Community Edition 7.2
Kind Regards.
Ciao Stefano, which kind of farms are you using?
The farm status is controlled by a PID file created under /var/run path. You can check the logs in /var/log/syslog searching for some errors.
Also, feel free to generate a support save via System > Support Save and send it via support@relianoid.com
Kind Regards.