Closed mohammedyaqub closed 2 years ago
seems like an OOM issue. Please check that VPP heap size is reasonably enough as well as OS memory fits it.
Thank you for the response,
my apologize for late although increasing the size of main heap size the problem still appears to be the same.
#0 mspace_malloc (msp=0x0, bytes=1116) at /home/ubuntu/upg-vpp/vpp/src/vppinfra/dlmalloc.c:4375
ms = 0x0
#1 0x00007ffff7f26951 in mspace_get_aligned (msp=0x0, n_user_data_bytes=0, align=16, align_offset=<optimized out>)
at /home/ubuntu/upg-vpp/vpp/src/vppinfra/dlmalloc.c:4256
ms = 0x0
rv = <optimized out>
wwp = <optimized out>
searchp = <optimized out>
#2 0x00007ffff7f7ceb7 in clib_mem_alloc_aligned_at_offset (size=1096, align=8, align_offset=0,
os_out_of_memory_on_failure=1) at /home/ubuntu/upg-vpp/vpp/src/vppinfra/mem.h:142
cpu = 27
heap = 0x7fffffffc910
p = <optimized out>
#3 vec_resize_allocate_memory (v=<optimized out>, length_increment=64, data_bytes=1096, header_bytes=<optimized out>,
data_align=8, numa_id=255) at /home/ubuntu/upg-vpp/vpp/src/vppinfra/vec.c:67
vh = <optimized out>
oldheap = 0xa
old = <optimized out>
old_alloc_bytes = <optimized out>
new_alloc_bytes = <optimized out>
new = <optimized out>
#4 0x00007ffff7f3e856 in _vec_resize_inline (v=0x0, length_increment=64, data_bytes=1024, header_bytes=64,
data_align=8, numa_id=255) at /home/ubuntu/upg-vpp/vpp/src/vppinfra/vec.h:170
new_data_bytes = <optimized out>
aligned_header_bytes = 72
vh = <optimized out>
oldheap = <optimized out>
p = <optimized out>
_x = <optimized out>
_y = <optimized out>
--Type <RET> for more, q to quit, c to continue without paging--
#5 _hash_create (elts=64, h_user=<optimized out>) at /home/ubuntu/upg-vpp/vpp/src/vppinfra/hash.c:750
_V = <optimized out>
log2_pair_size = 1
v = <optimized out>
h = <optimized out>
_x = <optimized out>
_y = <optimized out>
_V = <optimized out>
_x = <optimized out>
_y = <optimized out>
#6 _hash_set3 (v=0x0, key=93824993157914, value=0x0, old_value=0x0) at /home/ubuntu/upg-vpp/vpp/src/vppinfra/hash.c:848
_h = {elts = 0, flags = 0, log2_pair_size = <synthetic pointer>, key_sum = <synthetic pointer>,
key_equal = <synthetic pointer>, user = <synthetic pointer>, format_pair = <synthetic pointer>,
format_pair_arg = <synthetic pointer>, is_user = 0x38}
h = <optimized out>
#7 0x00005555555a11ae in upf_init (vm=0x55555566e600 <vlib_m>) at /home/ubuntu/upg-vpp/upf/upf.c:316
_f = 0x55555563631a <upf_proxy_main_init>
_error = 0x0
sm = 0x55555566ed80 <upf_main>
error = <optimized out>
#8 0x00005555555a2918 in main (argc=33, argv=0x5555556874f0) at /home/ubuntu/upg-vpp/upf/upf.c:590
i = 32
vm = 0x55555566e600 <vlib_m>
main_heap_size = 2147483648
sizep = <optimized out>
size = <optimized out>
main_core = 1
main_heap = <optimized out>
e = <optimized out>
- I tried to print the *vm there everything appeared to be `NULL ` below is the output.
(gdb) p *vm
$1 = {cacheline0 = 0x55555566e600
- looks like the way i tried calling `upf_init()` was not correct please check #271
Kindly suggest to overcome this issue.
Regards,
Yaqub.
Please check out how does VPP perform it's startup. UPG is a plugin and it's init stage following after VPP internal modules startup and other plugins.
Hi,
We are trying to run travelping/upg-vpp UPF executable binary but facing segmentation fault.
Environment details.
Tried debugging through GDB below is the output.
The back trace output shows.
Kindly help @ivan4th.
Thanks.