Page MenuHomeVyOS Platform

LLDP: "show lldp neighbors detail" returns warnings when service is not configured
Closed, ResolvedPublicBUG

Description

If you didn't configure LLDP and try to show neighbors detail, this will result in an error.

sever@vyos-1.3-roll:~$ show lldp neighbors detail 
2020-04-18T13:05:42 [WARN/control] unable to connect to socket /var/run/lldpd.socket: No such file or directory
2020-04-18T13:05:42 [WARN/lldpctl] not able to get the list of interfaces. Unable to connect to lldpd daemon
-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------

Details

Difficulty level
Easy (less than an hour)
Version
VyOS 1.3-rolling-202004180117
Why the issue appeared?
Design mistake
Is it a breaking change?
Perfectly compatible
Issue type
Bug (incorrect behavior)

Event Timeline

As workaround

vyos@r1-roll:~$ /usr/sbin/lldpctl -f plain 2> /dev/null 
-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------

The problem exists when LLDP is not configured but one wants to run the detail command. Running "show lldp neighbors" is not possible when LLDP is not running - so should the the detail command.

vyos@vyos:~$ show lldp neighbors 
Service LLDP is not configured
vyos@vyos:~$ show lldp neighbors detail 
2020-08-03T14:44:45 [WARN/control] unable to connect to socket /var/run/lldpd.socket: No such file or directory
2020-08-03T14:44:45 [WARN/lldpctl] not able to get the list of interfaces. Unable to connect to lldpd daemon
-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
vyos@vyos:~$
c-po renamed this task from LLDP op-mode error to LLDP: "show lldp neighbors detail" returns warnings when service is not configured.Aug 3 2020, 2:45 PM
c-po changed the task status from Open to In progress.
c-po claimed this task.
c-po triaged this task as Low priority.
c-po changed Difficulty level from Unknown (require assessment) to Easy (less than an hour).
c-po changed Why the issue appeared? from Will be filled on close to Design mistake.
c-po changed Is it a breaking change? from Unspecified (possibly destroys the router) to Perfectly compatible.
erkin set Issue type to Bug (incorrect behavior).Aug 30 2021, 6:49 AM
erkin removed a subscriber: Active contributors.