Vyos 1.4-rolling - Flow Accounting - Netflow Issue

General questions
1

Hi,
I have configured flow accounting for my LAN interface however it crashes with an error. Here is the interface and flow-accounting config.

ethernet eth1 {
address 192.168.1.250/24
description LAN
hw-id 52:54:00:95:51:c2
}

flow-accounting {
buffer-size 32
enable-egress
interface eth1
netflow {
engine-id 100
sampling-rate 1
server 192.168.1.204 {
port 2055
}
timeout {
expiry-interval 30
flow-generic 3600
icmp 300
max-active-life 604800
tcp-fin 300
tcp-generic 3600
tcp-rst 120
udp 300
}
version 9
}
}

uacctd service crashes with following error in /var/log/messages

Sep 24 13:05:59 vyos kernel: [ 2673.793589] uacctd[6206]: segfault at 6 ip 00007f5d9caa077e sp 00007ffcafba3a68 error 4 in libc-2.31.so[7f5d9ca1e000+14b000]
Sep 24 13:05:59 vyos kernel: [ 2673.793606] Code: 4c 8d 0c 16 4c 39 cf 0f 82 63 01 00 00 48 89 d1 f3 a4 c3 80 fa 08 73 12 80 fa 04 73 1e 80 fa 01 77 26 72 05 0f b6 0e 88 0f c3 <48> 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48 89 37 c3 8b 4c 16 fc 8b
Sep 24 13:05:59 vyos systemd[1]: uacctd.service: Main process exited, code=killed, status=11/SEGV
Sep 24 13:05:59 vyos systemd[1]: uacctd.service: Failed with result ‘signal’.

Any thoughts what is causing this? This configuration works fine with ver 1.3.

Thanks.

1 Like
2

I think it must be a problem in 1.4 rolling that hasn’t been ironed out. I’m testing with a custom build of the latest 1.4 and the problem is still there.

I’ve tested using a Xen VM (in XCP-NG 8.2) with 1.4-rolling-202110020217 and I’ve also tested on my i7-8700K natively (to see how vyos performs on a faster box) with the same result.

All I have to do is set flow-accounting on an interface and it will crash within a few seconds. I’ll try to check again if there’s an existing bug, but I’m definitely interested to see what it looks like with flow accounting on!

3

Oops! Forgot to post the error output from uacctd:

[  127.532340] uacctd[3878]: segfault at 6 ip 00007f2f4803777e sp 00007ffcf7d6f838 error 4 in libc-2.31.so[7f2f47fb5000+14b000]
[  127.532365] Code: 4c 8d 0c 16 4c 39 cf 0f 82 63 01 00 00 48 89 d1 f3 a4 c3 80 fa 08 73 12 80 fa 04 73 1e 80 fa 01 77 26 72 05 0f b6 0e 88 0f c3 <48> 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48 89 37 c3 8b 4c 16 fc 8b

I just saw that someone has already started a thread on Github about this issue. I will try to follow up there if I can get some useful debug.