@fetzerms I was mistaken: cfg-stdout.log is logrotated, but not removed on boot, and this is useful info. When you are able to reproduce, please share. I believe the corner case I am seeing is distinct but related to what you are seeing. Thanks.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 9 2020
Apr 8 2020
Apr 7 2020
Apr 6 2020
@fetzerms I am able to reproduce this, in a manner that's not completely clean, but which will allow me to investigate further. Feel free to add any other details you run across; thanks.
Note, there is /opt/vyatta/etc/config/vyos-migrate.log (/config/vyos-migrate.log after image installation) that will list failed migration scripts, if any). This is created before /var/log is available, hence the non-canonical location.
Regarding the first question, yes, cfg-stdout.log is cleared on reboot, unfortunately. The commit error logging is currently a mixture of (un-verbose) reporting from the backend, and limited reporting from python; improvements pending. Firstly, if there are migration errors, those need to be investigated; secondly, the error that you initially reported is (generally) related to stale information in the config hierarchy itself, but may be obscuring earlier errors.
Apr 5 2020
In this failure case, there are some expected "failed" lines in /var/log/vyatta/cfg-stdout.log. Although they are not detailed log messages, they may help narrow down the source of the failure, if you could share those.
Apr 4 2020
Apr 3 2020
Apr 2 2020
Mar 31 2020
Mar 30 2020
Mar 29 2020
Mar 27 2020
Thanks, @Viacheslav. We will need to add a migration script for the previous setting; that is simple in this case, since, as you observed, it was a no-op, and can just be dropped. If you are busy, I can add it.
Mar 26 2020
Mar 25 2020
Mar 24 2020
Mar 21 2020
Tested successfully in Crux.
Mar 20 2020
Yes, @jjakob, I run docker as indicated in the vyos-build README, which includes --privileged. I am not that concerned with the docker issue here; rather I want the script to work, and am adding in the necessary ingredients to the script itself. Compare the older prescription:
https://wiki.vyos.net/wiki/Building_images_using_vyos-build_Docker_container#Building_Google_Cloud.2FGCE_image
Mar 19 2020
This should be made consistent with other usage: paths should be lists, not strings. I will make the change, and any other details needed for consistency with model.
Mar 17 2020
Mar 16 2020
Mar 13 2020
Mar 11 2020
@Dmitry The simplest workaround for the moment is to add the following to your load steps:
I've tracked this down to a bug in libboost-filesystem, versions < 1.56, that occurs if the locale is not properly set, as is the case within the Docker environment:
Mar 3 2020
Yes, closing.
The 'showConfig' op is not considered ready for 1.2.5, and specifically json configFormat is not yet backported to crux. Regarding the output in the blog, see the line following the screen shot: "In reality that output is not pretty-printed, though we may add a flag for it. "
Checked on vyos-1.2.5-epa1:
Feb 29 2020
All works as expected; thanks.
This is a result of a missing package vyos-intel-ixgbe_5.6.3-0_amd64.deb in http://dev.packages.vyos.net/repositories/crux/ --- when missing, the build will use an outdated package, leading to incorrect dependencies on the kernel version. On the other hand, if the correct intel module is built as a local package, there is only one resident linux-image, and update-initramfs succeeds as usual. The build/upload mechanism for the intel modules will be fixed soon, and the issue resolved.
Feb 28 2020
Firstly, we need to determine why there are two kernel images.