Page MenuHomeVyOS Platform

VPP doesn't log to /var/log/vpp.log
Closed, InvalidPublicBUG

Description

Log contains only process start entries:

vyos@VyOS-for-Smoke-Tests:~$ cat /var/log/vpp.log
2025/09/05 10:21:02:848: ***** Start: PID 3669 *****
2025/09/05 10:40:12:137: ***** Start: PID 3676 *****
2025/09/05 10:40:49:747: ***** Start: PID 4093 *****
2025/09/05 10:55:52:572: ***** Start: PID 5097 *****

Google cloud vm: e2-standard-8 (8 vCPUs, 32 GB Memory)

Version:          VyOS 2025.09.01-0023-rolling
Release train:    current
Release flavor:   generic

Built by:         autobuild@vyos.net
Built on:         Mon 01 Sep 2025 00:23 UTC
Build UUID:       a729cf79-bf12-4b5f-8d10-261158e4c5f0
Build commit ID:  242c1a587acac6

Architecture:     x86_64
Boot via:         installed image
System type:      KVM guest
Secure Boot:      disabled

Hardware vendor:  Google
Hardware model:   Google Compute Engine
Hardware S/N:     GoogleCloud-AAD02DEFDD2556E2E95D7FB7D9562375
Hardware UUID:    aad02def-dd25-56e2-e95d-7fb7d9562375

Steps to reproduce:

set vpp settings interface eth1 driver 'dpdk'
commit
set vpp settings logging default-log-level debug
commit

Details

Version
vyos-2025.09.01-0023-rolling-generic-amd64
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Bug (incorrect behavior)

Related Objects

StatusSubtypeAssignedTask
OpenBUGNone
InvalidBUGNone

Event Timeline

Do you see logs while doing sudo journalctl -f ?
We do not handle/process the /var/log/vpp.log at least by our scripts/configs.

Do you see logs while doing sudo journalctl -f ?
We do not handle/process the /var/log/vpp.log at least by our scripts/configs.

Yes, journalctl contains vpp log entries.
/var/log/vpp.log is referred in the docs - https://docs.vyos.io/en/latest/vpp/configuration/dataplane/logging.html

Viacheslav triaged this task as Normal priority.Sep 6 2025, 9:07 AM

Those are additional daemon logs, like commands executed in the VPP

vyos@r14:~$ tail -f /var/lo
local/ lock/  log/   
vyos@r14:~$ tail -f /var/log/vpp.log 

2025/09/19 14:46:43:116[0]: quit
2025/09/19 12:34:58:229: ***** Start: PID 2069 *****
2025/09/19 12:35:13:804[0]: create pppoe map dp eth1 cp tap4097

2025/09/19 12:35:13:804[0]: quit
2025/09/19 15:40:17:059: ***** Start: PID 2069 *****
2025/09/19 15:40:32:715[0]: create pppoe map dp eth1 cp tap4097

2025/09/19 15:40:32:716[0]: quit
2025/09/19 17:33:37:122[0]: 2025/09/19 17:33:37:309[0]: 2025/09/19 17:33:37:473[0]: 2025/09/19 17:33:40:247[0]: show int
2025/09/19 17:33:44:939[0]: 2025/09/19 17:33:45:097[0]: 2025/09/19 17:33:45:275[0]: 2025/09/19 17:33:48:998[0]: show memory 
2025/09/19 17:33:52:710[0]: 2025/09/19 17:33:57:798[0]: 2025/09/19 17:33:59:812[0]: show memory main-heap