Are you using vrf? Maybe it's an issue and router can't resolve dns for ntp servers

@Viacheslav
I will check it today or tomorrow. But I believe I know the culprit, the new firewall rules didn't allow my VyOS instance to contact the CoreDNS (set to host mode) container that is hosted as a container in VyOS. I was unable to ping 127.0.0.1 as well as all of my VyOS's IP addresses.

Don't have this issue
@dcplaya Could you re-check in the newest rolling image?

PR https://github.com/vyos/vyos-1x/pull/2205

Close it if this issue is solved.

Should be executed there, for future debugs https://github.com/vyos/vyatta-wanloadbalance/blob/c7708bc6ef689f5744272a15a601a56a03890afa/src/lbdecision.cc#L429

Just waiting for upstream updates

PR https://github.com/vyos/vyos-1x/pull/2204

PR https://github.com/vyos/vyos-1x/pull/2202

There definitely should be a second, i.e., max value 3600 seconds.

PR for 1.3.4 https://github.com/vyos/vyos-build/pull/393

I observed the trace from 1.4-rolling-202306180309 as I was trying to slowly increment up. This was the path I took to get there

grub was very buggy for me in a USB console. I did finally manage to get vyos-config-debug to boot.

Might be related:

I would like to stage this in a VM if I do try the above as physical access to the router is tough. Does anyone know where I can find a ISO for 1.4-rolling-202212310809. It seems the old s3 endpoint doesn't resolve https://s3.vyos.io/rolling/current/vyos-1.4-rolling-202212310809-amd64.iso

PR 1.3.4 https://github.com/vyos/vyos-1x/pull/2200

Adding vyos-config-debug to the boot cmdline should allow you to log in and will provide some information in /tmp/boot-config-trace. Cf.:
https://docs.vyos.io/en/latest/contributing/debugging.html

I upgraded from 1.4-rolling-202307060317 to 1.4-rolling-202309040919 and the issue mention in this post was resolved. The configuration was migrated. However nothing worked in regards to the firewall, and I am not familiar enough with the new syntax so I cannot, nor do I have time to troubleshoot it right now.

@syncer At first glance, the generated config is correct for VyOS 1.3-stable-202308240442

set protocols igmp interface eth0 join 239.1.2.3 source '192.0.2.1'
set protocols igmp interface eth1 join 239.1.2.3
set protocols igmp interface eth2

Unless there is something wrong with the firewall ruleset in VyOS any malfunctions in the FTP helper itself will mainly be fixed upstream at the Linux kernel or in this particular case the netfilter team:

My config file is https://gist.github.com/anthr76/4b091d952bcd69b1ac8d4c7d08aaaac6

PR: https://github.com/vyos/vyos-1x/pull/2199

PR: https://github.com/vyos/vyos-1x/pull/2199

Disabling all validators for both vyatta-cfg and vyatta-op bring the boot time down to approx 73 seconds.

Modifying node.def (comment out "syntax:expression:") recursively in the paths of:

Moving along in the blamegame I will after a tip try to disable the various validators being runned.

Any updates to this?

That relates would seem reasonable. I'm seeing a similar explosion in commit lag but I have zero static routes. I did change to zone-based firewall and added about 6 vlans. Lines of my config went from ~500 to ~3000. Commit times increased almost linearly.

Can be related: https://vyos.dev/T2431

Continued debugging by also modifying /usr/libexec/vyos/services/vyos-configd by adding:

Attempted some debugging on this issue.

According to https://man7.org/linux/man-pages/man7/capabilities.7.html this capability can load, unload AND delete kernel modules.

https://github.com/vyos/vyos-1x/pull/2197

@Viacheslav, can you backport this to 1.3

PR https://github.com/vyos/vyos-1x/pull/2196