Forum Replies Created
- AuthorPosts
- 17 June, 2025 at 1:46 pm in reply to: L4XNAT sessions are not removed correctly when backends go down #60052
Hi Stefan, we have a patch that fixes the issue.
Could you please write us to support@relianoid.com so we can facilitate the patch.
Cheers.
13 May, 2025 at 11:57 am in reply to: L4XNAT sessions are not removed correctly when backends go down #59697Hi Stefan!
Thank you for your report, we were able to reproduce the issue. We’ll analyze it thoroughly and we’ll back to you soon with a proper solution.
Cheers.
Hello Uroš,
Exactly, SNI feature for SSL certificates is enabled for Enterprise Edition.
Cheers.
You’re welcome,
Enjoy RELIANOID!Hi!
The maintenance mode and session persistence didn’t change at all.
In your infrastructure, were all the clients always NATed or it is a recent change? Cause if you had the clients load balanced to different backends using persistence by “Source IP” in the case where the clients are NATed then it was a Zevenet bug.
Just to confirm the correct behavior, please change it to “Source IP” and enable the debug at /usr/local/relianoid/config/global.conf , change from:
$debug=”0″;
to
$debug=”9″;
And then, reproduce the maintenance issue.
Finally, please share a fresh support save via email.
Kind Regards.Hi!
Thank you for the support save. It seems related to the persistence configured, as all the clients are Nated to the same IP address.
Please change the session persistence from “Source IP” to “Source Port”.
Looking forward to your feedback,
Cheers.Hi!
Could you please generate a support save (at System > Support Save) and share with us at: support AT relianoid DOT com ?
Thank you!
Hi Francesco, just to confirm that this fix is already included in the last release 7.5.
Cheers.
Hi Francesco, we received the support save.
Some issues detacted in regards:
1. Timeouts from several backends. You could increase the backend timeout for those cases
HTTP/1.1: Connection timed out (45.009 secs)2. All backends from certain farms come down everyday at 7:00am, probably due to a scheduled task.
3. Broken connections to backends due to client timeouts
error read from XXX: Connection timed out
backend YYYY, (…..) error copy server cont: Broken pipeWhen a client timeout is detected, then the proxy closes the backend side. You can try to increase client timeout and see if this palliates the issue.
Cheers.
Hi Willem, we just released a new ISO. Could you try the installation in OpenStack with this new ISO?
Kind Regards.
Hi, please verify you’ve enough disk space first.
Then, execute in console the command:
/usr/local/relianoid/bin/supportsave
Finally, please send it via email.
Cheers.
Hi Willem, the ISO installer doesn’t require additional software to be installed.
Can you share the steps you take to reproduce the issue?
Are you using the latest CE ISO 7.4?Cheers.
- This reply was modified 7 months, 4 weeks ago by
nevola.
Hi,
Could you generate a Support Save file via System > SupportSave and send it to our team at support@relianoid.com ?
Thank you.
Hello.
It seems that the client timeout has been reached.
pound: XXXXX, (7f68b12aa6c0) error read from YYYYY: Connection timed out
And then, the reverse proxy closes the connection with the backend.
pound: XXXXX, service KKKKK, backend ZZZZZ:8280, (7f68b16796c0) error copy server cont: Broken pipe
How many connections are we talking about?
What’s the current value of client and backend timeouts?
Does the log file says about any error in the system?Cheers.
Thank you for the information Willem.
It seems that the CDROM was unmounted (probably from the hypervisor?) and then the packages have not been reachable anymore. The log says:
[…]
Source list entries for this are:
cd cdrom:….
Unmounting CD-ROM….
[…]Are you using the latest CE ISO 7.4?
Can you try the installation without Internet connection?What the logs says about the CD-ROM with the command:
grep -i “CD-ROM” /var/log/syslogCheers.
- This reply was modified 7 months, 4 weeks ago by
- AuthorPosts