Have you tried specifying /config/config.boot instead?

Problem seems to be coming from there being no queue set on the interface, setting a queue manually resolves the issue till the device is restarted

man strace(1) indicates that it opens several system files until it gets a match for any known distro.

Another way is to check in /etc/os-release, but that is also a changeable file.... Wondering where lsb_release reads it from ( no pc atm, so cannot check)

VyOS ships a serial port interface in the default configuration upon installation.

Yes it is a virtual environment, that was a simple fix. Removed the serial entry. I don't recall adding it, is it added by default or maybe erroneously detected?

May it be you are running on a virtualized environment and have not added a serial port to your VM?

run sh ip route

ddclient version 3.8.2 is currently include with VyOS which is 2 versions behind. Latest is 3.9.0 which has the required fixes.

Good ol' Occam says no. We already have a general mechanism for that, and I think as we rewrite code, we may want to get rid of the description fields that predate that mechanism.

Looks like this might be upstream and has been corrected there.

In T1003#26043, @oliko wrote:

Same problem, but at the bare metal server with VyOS 1.2-rc7 from repo.

Same problem, but at the bare metal server with VyOS 1.2-rc7 from repo.

@LiquidLight there is a Dockerfile, too to build VyOS

Issue file con be overwritten. lsb_release -d would be a better way, as it gives you Description: Debian GNU/Linux 8.11 (jessie)

Thanks for your reply.

Do you also create the iso yourself or dowload it?
In 1.2 we will be using cloud-init and the ec2 init script was removed.

Looks like this was always a bug. In the old Perl implementation the if clause was the same:
https://github.com/vyos/vyatta-cfg-system/blob/9b469f3c5734c086fc30b097405ea46ec2cee725/scripts/dynamic-dns/vyatta-dynamic-dns.pl#L223-L230

Ah, I see the problem. You can't have both ip and ipv6 in the same route-map match rule.

I have confirmed this does not happen in 1.1.8. Here is a sample working config in 1.1.8:

https://github.com/vyos/vyos-1x/commit/c798e0821c4acbf7ff89e6d2aeb2807cd07f4152
Should be fixed in the next rolling.

bug verified, thanks for reporting.

https://github.com/vyos/vyos-1x/commit/e1abd4f61f31d9ce7c54fe790a30d973aae53ab2

My test env has been running for 50 minutes without the prefix-lists engaging so I'd say this is another issue. Furthermore I think the issue you are describing has been fixed in the upcoming rc6 (T944).

Vyos has had a similar issue for quite some time with BGP route maps. route maps and filters do not work initially on first boot or when the box is being taken down. the BGP sessions are up w/out filters for several minutes and usually trip prefix number filters on peers. Is this the same issue? i.e. are you sure the prefix list isn't engaged after several minutes?