Page MenuHomeVyOS Platform

lldpcli: unknown command from argument 1: `#`
Closed, ResolvedPublicBUG

Description

After system startup I get

cpo@AC1:~$ show log tail
Mar 23 08:24:36 AC1 lldpcli[2670]: unknown command from argument 1: `#`
Mar 23 08:24:36 AC1 lldpcli[2670]: unknown command from argument 1: `#`

LLDP configuration is:

cpo@AC1:~$ show configuration commands | grep lldp
set service lldp interface eth0 'disable'
set service lldp management-address '172.16.254.100'
set service lldp snmp 'enable'

Details

Difficulty level
Unknown (require assessment)
Version
999.201803162053
Why the issue appeared?
Implementation mistake
Is it a breaking change?
Perfectly compatible
Issue type
Bug (incorrect behavior)

Event Timeline

c-po renamed this task from lldpcli: unknown command from argument 1: `#' to lldpcli: unknown command from argument 1: `#`.Mar 23 2018, 7:26 AM
c-po created this task.
syncer triaged this task as Normal priority.Apr 7 2018, 11:09 AM

Scrolling back in show log I see some additional lines:

Apr 25 12:29:48 CR2 lldpcli[3000]: cannot find configuration file/directory /etc/lldpd.conf
Apr 25 12:29:48 CR2 lldpcli[3000]: unknown command from argument 1: `#`
Apr 25 12:29:48 CR2 lldpcli[3000]: unknown command from argument 1: `#`
Apr 25 12:29:48 CR2 lldpcli[3000]: an error occurred while executing last command
Apr 25 12:29:48 CR2 lldpcli[3000]: unknown command from argument 1: `#`
Apr 25 12:29:48 CR2 lldpcli[3000]: unknown command from argument 1: `#`
Apr 25 12:29:48 CR2 lldpcli[3000]: an error occurred while executing last command
Apr 25 12:29:48 CR2 lldpcli[3000]: lldpd should resume operations

I see the same lines still in log on VyOS-1.2.0-rolling+201805220337 as @c-po .
In filesystem there is no directory '/etc/lldpd.conf' but there is a '/etc/lldpd.d' and a file '/etc/init.d/lldpd.conf'

Happens too when started by hand, where 172.16.254.35 is the management address

sudo /usr/sbin/lldpd -m 172.16.254.35 -d -x  -M4 -S "VyOS unknown" -P VyOS -I *,!eth0
2018-09-01T20:10:16 [WARN/lldpctl] unknown command from argument 1: `#`
2018-09-01T20:10:16 [WARN/lldpctl] unknown command from argument 1: `#`

Even happens without any argument:

cpo@LR1# sudo /usr/sbin/lldpd -d
2018-09-01T20:12:53 [WARN/lldpctl] unknown command from argument 1: `#`
2018-09-01T20:12:53 [WARN/lldpctl] unknown command from argument 1: `#`

is that still an issue in the latest rolling image?

Version: VyOS 1.2.0-rolling+201905170337

sudo /usr/sbin/lldpd -d
2019-05-17T20:36:48 [INFO/privsep] /etc/localtime copied to chroot
2019-05-17T20:36:48 [INFO/main] protocol LLDP enabled
2019-05-17T20:36:48 [INFO/main] protocol CDPv1 disabled
2019-05-17T20:36:48 [INFO/main] protocol CDPv2 disabled
2019-05-17T20:36:48 [INFO/main] protocol SONMP disabled
2019-05-17T20:36:48 [INFO/main] protocol EDP disabled
2019-05-17T20:36:48 [INFO/main] protocol FDP disabled
2019-05-17T20:36:48 [INFO/event] libevent 2.0.21-stable initialized with epoll method
2019-05-17T20:36:48 [INFO/lldpctl] lldpd should resume operations

I can't see 'unknown command' lines in log anymore, on VyOS 1.2.0-rolling"201905180337.

Thanks for testing it, I'll close the bug ticket then.

dmbaturin changed Why the issue appeared? from Will be filled on close to Implementation mistake.Sep 3 2021, 7:35 AM
dmbaturin set Is it a breaking change? to Perfectly compatible.
dmbaturin set Issue type to Bug (incorrect behavior).