- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jan 30 2025
Jan 29 2025
Thanks for confirming
Jan 28 2025
Tested as working in: 1.5-rolling-202501280006
it seems I can look into the full workflow logs, but the root cause remains unclear to me.
- Raised https://github.com/vyos/vyos.vyos/pull/379
- Completed integration tests for 1.3- but 1.4+ fails - need to workaround unsupported commands in tests setup (e..g 'config-trap' and look into module code as new stanzas are not handled correctly (e.g. log vs log 'enable')
- Unit tests are failing after the parser regex change - need to fix them too
The problem seems to be solved with https://github.com/vyos/vyos-1x/pull/4318 (T7089).
The error no longer occurs in a custom image...
From my experience having systemd manage the watchdog has been very stable.
I would not recommend using using watchdogd to manage the hardware watchdog, it is ancient and doesn't integrate well with systemd.
If anyone can find reproducing conditions for this task, feel free to reopen.
Since the problem was resolved by Proxmox, we will skip this one task.
If the issue was related to ISC DHCP, then Kea changes everything there. If not, its scope and reproducing conditions will need to be clarified so that we can reproduce it and prove that it's fixed. If new information appears, feel free to reopen the task.
Jan 27 2025
Probably related bug https://vyos.dev/T7089
https://github.com/vyos/vyos-1x/pull/4318
Changing sleep to 5 sec fixes the issue
This issue appears to persist. I have been trying to run QAT with 8970 cards, and I am also running into this issue. Ultimately I have two separate instances of VyOS which exhibit the same lockup issue (separate hardware and locations). The frequency of the locks ups is far more frequent than what lucasec mentioned. Anywhere in the 12 hour range after a reboot the system crashes.
Is it reproducible in 1.4 or later? 1.3 will EOL very soon, so if it's unique to 1.3, we may mark this wontfix.