https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162017-03-14T21:22:59ZpfSense bugtrackerpfSense - Bug #7345: nanobsd upgrades still fail bacause of lacking resolv.confhttps://redmine.pfsense.org/issues/7345?journal_id=321772017-03-14T21:22:59ZBrett Keller
<ul></ul><p>I also ran into this issue, which broke my ability to update my NanoBSD 2.3.2_1 box to 2.3.3_1. The box in question runs neither unbound nor dnsmasq, as we have a separate DNS server on the LAN, so the fallback DNS calls to localhost mentioned in bug <a class="issue tracker-1 status-3 priority-5 priority-high4 closed" title="Bug: nanobsd upgrades may fail from lacking resolv.conf (Resolved)" href="https://redmine.pfsense.org/issues/6557">#6557</a> were failing after very long timeouts:</p>
<code><pre>
>>> Mounting second partition to run upgrade... done.
>>> Copying resolv.conf to upgrade partition... done.
>>> Downloading upgrade packages...
Updating pfSense-core repository catalogue...
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
Unable to update repository pfSense
All repositories are up-to-date.
pkg: Repository pfSense-core cannot be opened. 'pkg update' required
pkg: Repository pfSense cannot be opened. 'pkg update' required
Checking for upgrades (0 candidates): . done
Processing candidates (0 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
>>> Upgrading pfSense kernel...
pkg: Repository pfSense-core cannot be opened. 'pkg update' required
pkg: Repository pfSense cannot be opened. 'pkg update' required
pkg: No packages available to upgrade matching 'pfSense-kernel-pfSense' have been found in the repositories
>>> Locking package pfSense-kernel-pfSense... done.
Failed
</pre></code>
<p>Thanks to Andrew Hotlab for identifying the root cause! This is the right fix, but I had to tweak your patch slightly because your call to <code>_exec()</code> was missing an argument for <code>_msg</code>, and <code>_exec()</code> makes the assumption that the second argument will <em>always</em> be the log message, no matter what.</p>
<p>I tested my tweaked version of your patch on the box I had that was suffering from this issue, and the update was able to complete successfully. I've submitted <a href="https://github.com/pfsense/FreeBSD-ports/pull/332" class="external">pull request #332</a> on GitHub, so hopefully this should get merged and fixed shortly.</p> pfSense - Bug #7345: nanobsd upgrades still fail bacause of lacking resolv.confhttps://redmine.pfsense.org/issues/7345?journal_id=321822017-03-15T06:05:10ZAndrew Hotlab
<ul></ul><p>Great, thank you very much Brett!</p> pfSense - Bug #7345: nanobsd upgrades still fail bacause of lacking resolv.confhttps://redmine.pfsense.org/issues/7345?journal_id=323882017-03-29T07:06:13ZRenato Botelhorenato@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Renato Botelho</i></li><li><strong>Target version</strong> changed from <i>Future</i> to <i>2.3.4</i></li></ul> pfSense - Bug #7345: nanobsd upgrades still fail bacause of lacking resolv.confhttps://redmine.pfsense.org/issues/7345?journal_id=323892017-03-29T07:06:34ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>PR has been merged, thanks!</p> pfSense - Bug #7345: nanobsd upgrades still fail bacause of lacking resolv.confhttps://redmine.pfsense.org/issues/7345?journal_id=326712017-05-03T08:06:30ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Fixed in 2.3.3-p1</p>