OPNsense Forum
Archive => 19.7 Legacy Series => Topic started by: bobbis on January 31, 2020, 03:58:02 pm
-
on opnsense nano amd64, upgrading from 19.7.9_1 to 19.7.10_1 throws out a error from Netflow Migration failed:
Upgrade Log:
*** opnsense.foobar: OPNsense 19.7.9_1 (amd64/OpenSSL) ***
0) Logout 7) Ping host
1) Assign interfaces 8) Shell
2) Set interface IP address 9) pfTop
3) Reset the root password 10) Firewall log
4) Reset to factory defaults 11) Reload all services
5) Power off system 12) Update from console
6) Reboot system 13) Restore a backup
Enter an option: 12
Fetching change log information, please wait... done
This will automatically fetch all available updates, apply them,
and reboot if necessary.
Proceed with this action? [y/N]: y
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (37 candidates): .......... done
Processing candidates (37 candidates): .... done
The following 13 package(s) will be affected (of 0 checked):
Installed packages to be UPGRADED:
strongswan: 5.8.2 -> 5.8.2_1
py37-urllib3: 1.25.6,1 -> 1.25.7,1
py37-six: 1.12.0 -> 1.13.0
py37-setuptools: 41.4.0_1 -> 44.0.0
opnsense: 19.7.9_1 -> 19.7.10_1
liblz4: 1.9.2,1 -> 1.9.2_1,1
isc-dhcp44-server: 4.4.1_4 -> 4.4.2
isc-dhcp44-relay: 4.4.1 -> 4.4.2
e2fsprogs-libuuid: 1.45.4 -> 1.45.5
cyrus-sasl: 2.1.27 -> 2.1.27_1
curl: 7.67.0 -> 7.68.0
ca_root_nss: 3.48 -> 3.49.1
Installed packages to be REINSTALLED:
wpa_supplicant-2.9 (options changed)
Number of packages to be upgraded: 12
Number of packages to be reinstalled: 1
10 MiB to be downloaded.
[1/13] Fetching wpa_supplicant-2.9.txz: .......... done
[2/13] Fetching strongswan-5.8.2_1.txz: .......... done
[3/13] Fetching py37-urllib3-1.25.7,1.txz: .......... done
[4/13] Fetching py37-six-1.13.0.txz: ... done
[5/13] Fetching py37-setuptools-44.0.0.txz: .......... done
[6/13] Fetching opnsense-19.7.10_1.txz: .......... done
[7/13] Fetching liblz4-1.9.2_1,1.txz: .......... done
[8/13] Fetching isc-dhcp44-server-4.4.2.txz: .......... done
[9/13] Fetching isc-dhcp44-relay-4.4.2.txz: .......... done
[10/13] Fetching e2fsprogs-libuuid-1.45.5.txz: ..... done
[11/13] Fetching cyrus-sasl-2.1.27_1.txz: .......... done
[12/13] Fetching curl-7.68.0.txz: .......... done
[13/13] Fetching ca_root_nss-3.49.1.txz: .......... done
Checking integrity... done (0 conflicting)
[1/13] Upgrading py37-setuptools from 41.4.0_1 to 44.0.0...
[1/13] Extracting py37-setuptools-44.0.0: .......... done
[2/13] Upgrading py37-six from 1.12.0 to 1.13.0...
[2/13] Extracting py37-six-1.13.0: .......... done
[3/13] Upgrading cyrus-sasl from 2.1.27 to 2.1.27_1...
*** Added group `cyrus' (id 60)
*** Added user `cyrus' (id 60)
[3/13] Extracting cyrus-sasl-2.1.27_1: .......... done
[4/13] Upgrading ca_root_nss from 3.48 to 3.49.1...
[4/13] Extracting ca_root_nss-3.49.1: ...... done
[5/13] Upgrading py37-urllib3 from 1.25.6,1 to 1.25.7,1...
[5/13] Extracting py37-urllib3-1.25.7,1: .......... done
[6/13] Upgrading liblz4 from 1.9.2,1 to 1.9.2_1,1...
[6/13] Extracting liblz4-1.9.2_1,1: .......... done
[7/13] Upgrading e2fsprogs-libuuid from 1.45.4 to 1.45.5...
[7/13] Extracting e2fsprogs-libuuid-1.45.5: .......... done
[8/13] Upgrading curl from 7.67.0 to 7.68.0...
[8/13] Extracting curl-7.68.0: .......... done
[9/13] Reinstalling wpa_supplicant-2.9...
[9/13] Extracting wpa_supplicant-2.9: ....... done
[10/13] Upgrading strongswan from 5.8.2 to 5.8.2_1...
[10/13] Extracting strongswan-5.8.2_1: .......... done
[11/13] Upgrading isc-dhcp44-server from 4.4.1_4 to 4.4.2...
===> Creating groups.
Using existing group 'dhcpd'.
===> Creating users
Using existing user 'dhcpd'.
[11/13] Extracting isc-dhcp44-server-4.4.2: .......... done
[12/13] Upgrading isc-dhcp44-relay from 4.4.1 to 4.4.2...
[12/13] Extracting isc-dhcp44-relay-4.4.2: ....... done
[13/13] Upgrading opnsense from 19.7.9_1 to 19.7.10_1...
[13/13] Extracting opnsense-19.7.10_1: .......... done
Stopping configd...done
Resetting root shell
Updating /etc/shells
Unhooking from /etc/rc
Unhooking from /etc/rc.shutdown
Updating /etc/shells
Registering root shell
Hooking into /etc/rc
Hooking into /etc/rc.shutdown
Starting configd.
Keep version OPNsense\Backup\NextcloudSettings (1.0.0)
Keep version OPNsense\CaptivePortal\CaptivePortal (1.0.0)
Keep version OPNsense\Cron\Cron (1.0.1)
*** OPNsense\Diagnostics\Netflow Migration failed, check log for details
Keep version OPNsense\Firewall\Alias (1.0.0)
Keep version OPNsense\IDS\IDS (1.0.3)
Keep version OPNsense\Monit\Monit (1.0.8)
Keep version OPNsense\OpenVPN\Export (0.0.1)
Keep version OPNsense\Proxy\Proxy (1.0.3)
Keep version OPNsense\Routes\Route (1.0.0)
Keep version OPNsense\Syslog\Syslog (1.0.0)
Keep version OPNsense\TrafficShaper\TrafficShaper (1.0.3)
Keep version OPNsense\IPsec\IPsec (0.0.0)
Keep version OPNsense\Dnscryptproxy\Forward (0.1.0)
Keep version OPNsense\Dnscryptproxy\General (0.1.0)
Keep version OPNsense\Dnscryptproxy\Whitelist (0.1.0)
Keep version OPNsense\Dnscryptproxy\Server (1.0.0)
Keep version OPNsense\Dnscryptproxy\Dnsbl (1.0.0)
Keep version OPNsense\Dnscryptproxy\Cloak (0.1.0)
Writing firmware setting...done.
Writing trust files...done.
Configuring login behaviour...done.
Configuring system logging...done.
=====
Message from py37-urllib3-1.25.7,1:
--
Since version 1.25 HTTPS connections are now verified by default which is done
via "cert_reqs = 'CERT_REQUIRED'". While certificate verification can be
disabled via "cert_reqs = 'CERT_NONE'", it's highly recommended to leave it on.
Various consumers of net/py-urllib3 already have implemented routines that
either explicitly enable or disable HTTPS certificate verification (e.g. via
configuration settings, CLI arguments, etc.).
Yet it may happen that there are still some consumers which don't explicitly
enable/disable certificate verification for HTTPS connections which could then
lead to errors (as is often the case with self-signed certificates).
In case of an error one should try first to temporarily disable certificate
verification of the problematic urllib3 consumer to see if that approach will
remedy the issue.
=====
Message from opnsense-19.7.10_1:
--
Roar!
Checking integrity... done (0 conflicting)
Nothing to do.
The following package files will be deleted:
/var/cache/pkg/wpa_supplicant-2.9-df45bfa07f.txz
/var/cache/pkg/py37-urllib3-1.25.7,1.txz
/var/cache/pkg/wpa_supplicant-2.9.txz
/var/cache/pkg/strongswan-5.8.2_1-85827980a9.txz
/var/cache/pkg/strongswan-5.8.2_1.txz
/var/cache/pkg/py37-urllib3-1.25.7,1-b5c3cc22c4.txz
/var/cache/pkg/py37-six-1.13.0-494f3dbe6d.txz
/var/cache/pkg/py37-six-1.13.0.txz
/var/cache/pkg/py37-setuptools-44.0.0-bc59683dd1.txz
/var/cache/pkg/opnsense-19.7.10_1-12739fe312.txz
/var/cache/pkg/py37-setuptools-44.0.0.txz
/var/cache/pkg/liblz4-1.9.2_1,1-9215a70718.txz
/var/cache/pkg/opnsense-19.7.10_1.txz
/var/cache/pkg/isc-dhcp44-server-4.4.2.txz
/var/cache/pkg/liblz4-1.9.2_1,1.txz
/var/cache/pkg/isc-dhcp44-server-4.4.2-96caf7608e.txz
/var/cache/pkg/isc-dhcp44-relay-4.4.2-a822c3e3de.txz
/var/cache/pkg/e2fsprogs-libuuid-1.45.5.txz
/var/cache/pkg/isc-dhcp44-relay-4.4.2.txz
/var/cache/pkg/e2fsprogs-libuuid-1.45.5-1835b57ba0.txz
/var/cache/pkg/cyrus-sasl-2.1.27_1-cc555fccc9.txz
/var/cache/pkg/curl-7.68.0-a1e70e5ab7.txz
/var/cache/pkg/cyrus-sasl-2.1.27_1.txz
/var/cache/pkg/curl-7.68.0.txz
/var/cache/pkg/ca_root_nss-3.49.1-556f4ad733.txz
/var/cache/pkg/ca_root_nss-3.49.1.txz
The cleanup will free 10 MiB
Deleting files: .......... done
All done
Starting web GUI...done.
Generating RRD graphs...done.
*** opnsense.foobar: OPNsense 19.7.10_1 (amd64/OpenSSL) ***
0) Logout 7) Ping host
1) Assign interfaces 8) Shell
2) Set interface IP address 9) pfTop
3) Reset the root password 10) Firewall log
4) Reset to factory defaults 11) Reload all services
5) Power off system 12) Update from console
6) Reboot system 13) Restore a backup
Enter an option:
-
We made the validation stricter some time ago for NetFlow settings. You probably don't use NetFlow so that is not to worry, but if you want to see this gone go to Reporting: NetFlow and save the settings, adjust for validation errors until save is ok.
Cheers,
Franco