Date: Mon, 10 Apr 2017 10:00:22 -0600 From: Alan Somers <asomers@freebsd.org> To: freebsd-ports@freebsd.org Subject: 410.pkg-audit with pkg_jails="*" corrupts jails' pkg databases Message-ID: <CAOtMX2gR7P=f6WU4dkepv9J81_aOw=HO6_NZJCEY47wekf_LRQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I have a jailer running 11.0-RELEASE-p8 with 8 jails running either 11.0-RELEASE-p8 or 10.3-RELEASE-p12. On my jailer, I have 410.pkg-audit enabled and pkg_jails="*" is set in /etc/periodic.conf. Up until now, that's worked fine. But apparently at some point I upgraded pkg on the jailer but not in all of its jails. On the jails that got left behind, pkg is busted. All commands fail with an error like this: $ pkg audit -F vulnxml file up-to-date pkg: warning: database version 34 is newer than libpkg(3) version 33, but still compatible pkg: sqlite error while executing INSERT OR ROLLBACK INTO pkg_search(id, name, origin) VALUES (?1, ?2 || '-' || ?3, ?4); in file pkgdb.c:1544: no such table: pkg_search Presumably, copying the new pkg binary into the jails will fix this problem. But if my analysis is correct, then this is a serious problem with 410.pkg-audit. Until it gets fixed, everyone should leave pkg_jails="" in /etc/periodic.conf. -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2gR7P=f6WU4dkepv9J81_aOw=HO6_NZJCEY47wekf_LRQ>