Avi service engine crash in a GSLB environment with site persistence enabled
search cancel

Avi service engine crash in a GSLB environment with site persistence enabled

book

Article ID: 412782

calendar_today

Updated On:

Products

VMware Avi Load Balancer

Issue/Introduction

If GSLB is configured on the Avi load balancer and site persistence is enabled, it may lead to a service engine crash.

To confirm this is the same issue, please navigate to 'Administration -> Support -> Crash reports' and check for a stacktrace similar to the one below.

[New LWP 3259434]
[New LWP 3259435]
[New LWP 3259436]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `se_dp: worker process 0:                          '.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f458a5f9963 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
[Current thread is 1 (Thread 0x7f4586f5a040 (LWP 3259434))]
#0  0x00007f458a5f9963 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x000056241efe3cd1 in memcpy (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>) at ...
#2  ngx_http_proxy_create_request (r=0x5624278a9de0) at ...
#3  0x000056241efb1c69 in ngx_http_upstream_connect (r=r@entry=0x5624278a9de0, u=u@entry=0x56242c1aaf90) at ...

Cause

The service engine crash occurs due to an uninitialized data structure in a site persistence-enabled GSLB environment.

Resolution

This issue is fixed in Avi version 30.2.3 and later. 

The Bug ID for this issue is AV-251400.

 

Additional Information

Powered by Wolken Software