OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 18.1 Legacy Series »
  • [OBSOLETE] How to test the development version
« previous next »
  • Print
Pages: 1 [2] 3 4 ... 6

Author Topic: [OBSOLETE] How to test the development version  (Read 128020 times)

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 17707
  • Karma: 1618
    • View Profile
Re: How to test the development version
« Reply #15 on: November 07, 2016, 06:54:11 am »
"make package-keywords" was a workaround for a particular quirk when building packages that really needed the /usr/ports tree, or very few parts of it. Another workaround has been put into place meanwhile, and the step became unnecessary. I've updated the documentation.

I'm not entirely sure how stuck on "make package-keywords" warrants a reinstall. Each step should tell you what's wrong or what command needs to be run to fix it. If there is a particular error from a working command, the output should be posted in order to fix the things that don't do that yet.

17.1 is alpha, as is 2.4. But case in point GPT/UEFI was shipped in July 2016 along with 16.7. ;)


Thanks,
Franco
Logged

Solaris17

  • Full Member
  • ***
  • Posts: 118
  • Karma: 17
    • View Profile
Re: How to test the development version
« Reply #16 on: November 15, 2016, 04:23:20 am »
Finally took the plunge and did the upgrade.

Only issues iv ran into thus far are now I cant SSH and UPnP is broken.

Those 2 services

miniupnpd
sshd

refuse to start. Even after reboots. Changing the gui has no effect.

I also wasnt able to run the commands to allow updates by isntalling GIT, because I cant SSH into the unit. I will need to wait until I can console in.
« Last Edit: November 15, 2016, 04:29:51 am by Solaris17 »
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 17707
  • Karma: 1618
    • View Profile
Re: How to test the development version
« Reply #17 on: November 15, 2016, 05:04:57 pm »
It sounds like the underlying packages haven't been properly reinstalled similar to what we had here:

https://forum.opnsense.org/index.php?topic=3909.0

We're looking into it.

In the meantime, which command sequence did you use to install? Which version was active before changing to 17.1.a?


Thanks,
Franco
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 17707
  • Karma: 1618
    • View Profile
Re: How to test the development version
« Reply #18 on: November 15, 2016, 10:39:12 pm »
Was this a LibreSSL install prior to upgrade?
Logged

Solaris17

  • Full Member
  • ***
  • Posts: 118
  • Karma: 17
    • View Profile
Re: How to test the development version
« Reply #19 on: November 16, 2016, 01:38:56 am »
Hey Franco, Sorry its taken so long to respond.

I was running the alpha 17.x on BSD 10.3. I dont remember exact versioning. sorry.

It was an openSSL build. Though funny you should mention I could have sworn I had libreSSL installed at one point and I have not formatted.

I used the update command sequence in the OP of this thread.

You wouldnt have any idea how to maybe get this patched up would you? Any way I might be able to just pkg install the missing dependencies? I will format if needed but if there is a chance I can pull up the plane ill do it.

Thanks a bunch let me know if I can be of any assistance Franco!
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 17707
  • Karma: 1618
    • View Profile
Re: How to test the development version
« Reply #20 on: November 16, 2016, 07:31:45 am »
It should be fairly easy given internet+dns works:

# opnsense-update -sn "17.1\/latest"
# opnsense-update -fp

It should reinstall all packages, if not please let me know the error encountered.

After successful run, reboot from the GUI and services should be back up afterwards.


Cheers,
Franco
Logged

Solaris17

  • Full Member
  • ***
  • Posts: 118
  • Karma: 17
    • View Profile
Re: How to test the development version
« Reply #21 on: November 16, 2016, 07:37:20 pm »
Hey thanks for taking the time out of your day to give me the commands. I dont know the repos well enough to be able to guess. Im at work ATM but till give it a try tonight.
Logged

tillsense

  • Sr. Member
  • ****
  • Posts: 325
  • Karma: 49
    • View Profile
Re: How to test the development version
« Reply #22 on: November 16, 2016, 07:41:52 pm »
that's really interesting - a new install the repo is 16.7 after this is 17.1 but DOWNGRADED from 17.1.a_673 -> 17.1.a_539

Code: [Select]
*** test.loca: OPNsense 17.1.a_673 (amd64/OpenSSL) ***

 LAN (re0)       -> v4: 192.168.1.1/24
 WAN (pppoe0)    -> v4/PPPoE: *.*.*.*

 0) Logout                             7) Ping host
 1) Assign Interfaces                  8) Shell
 2) Set interface(s) IP address        9) pfTop
 3) Reset the root password           10) Filter Logs
 4) Reset to factory defaults         11) Restart web interface
 5) Power off system                  12) Upgrade from console
 6) Reboot system                     13) Restore a configuration

Enter an option: 8       

root@test:~ # cat /usr/local/etc/pkg/repos/origin.conf
OPNsense: {
  fingerprints: "/usr/local/etc/pkg/fingerprints/OPNsense",
  url: "pkg+http://pkg.opnsense.org/${ABI}/16.7/latest",
  signature_type: "fingerprints",
  mirror_type: "srv",
  priority: 11,
  enabled: yes
}
root@test:~ # opnsense-update -sn "17.1\/latest"
root@test:~ # opnsense-update -fp
Updating OPNsense repository catalogue...
Fetching meta.txz: 100%    1 KiB   1.5kB/s    00:01   
Fetching packagesite.txz: 100%   94 KiB  95.8kB/s    00:01   
Processing entries: 100%
OPNsense repository update completed. 307 packages processed.
Updating OPNsense repository catalogue...
OPNsense repository is up-to-date.
All repositories are up-to-date.
Updating database digests format: 100%
Checking for upgrades (121 candidates): 100%
Processing candidates (121 candidates): 100%
The following 121 package(s) will be affected (of 0 checked):

Installed packages to be DOWNGRADED:
opnsense-devel: 17.1.a_673 -> 17.1.a_539

Installed packages to be REINSTALLED:
pkg-1.9.1
zip-3.0_1
wol-0.7.1_2
unbound-1.5.10
syslogd-10.3
suricata-3.1.2
sudo-1.8.18
strongswan-5.5.0
sshlockout_pf-0.0.2_2

---------------------------------------------------------------------------------snip

/var/cache/pkg/beep-1.0_1-b2d78e37a3.txz
/var/cache/pkg/bind910-9.10.4P3.txz
/var/cache/pkg/beep-1.0_1.txz
/var/cache/pkg/apinger-0.7-38946bab0c.txz
/var/cache/pkg/apinger-0.7.txz
/var/cache/pkg/GeoIP-1.6.9-3fe84bba19.txz
/var/cache/pkg/GeoIP-1.6.9.txz
The cleanup will free 76 MiB
Deleting files: 100%
All done
root@test:~ #                                                                               
*** FINAL System shutdown message from root@test.loca ***             

System going down IMMEDIATELY                                                 

                                                                               
Connection to 192.168.1.1 closed by remote host.
Connection to 192.168.1.1 closed.
root@test:~$ ssh root@192.168.1.1
Password for root@test.loca:
Last login: Wed Nov 16 17:49:50 2016 from 192.168.1.101
FreeBSD 11.0-RELEASE-p2 (SMP) #0 850e1e9(master): Fri Oct 28 17:09:55 CEST 2016

----------------------------------------------
| Hello, this is OPNsense 16.7!              |       @@@@@@@@@@@@@@@
|                                            |      @@@@         @@@@
| Website: https://opnsense.org/        |       @@@\\\   ///@@@
| Handbook: https://docs.opnsense.org/   |     ))))))))   ((((((((
| Forums: https://forums.opnsense.org/ |       @@@///   \\\@@@
| Lists: https://lists.opnsense.org/  |      @@@@         @@@@
| Code: https://github.com/opnsense  |       @@@@@@@@@@@@@@@
----------------------------------------------

 0) Logout                             7) Ping host
 1) Assign Interfaces                  8) Shell
 2) Set interface(s) IP address        9) pfTop
 3) Reset the root password           10) Filter Logs
 4) Reset to factory defaults         11) Restart web interface
 5) Power off system                  12) Upgrade from console
 6) Reboot system                     13) Restore a configuration

Enter an option: 8

root@test:~ # cat /usr/local/etc/pkg/repos/origin.conf
OPNsense: {
  fingerprints: "/usr/local/etc/pkg/fingerprints/OPNsense",
  url: "pkg+http://pkg.opnsense.org/${ABI}/17.1/latest",
  signature_type: "fingerprints",
  mirror_type: "srv",
  priority: 11,
  enabled: yes
}
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 17707
  • Karma: 1618
    • View Profile
Re: How to test the development version
« Reply #23 on: November 16, 2016, 08:10:51 pm »
Hi Till,

That's normal as the 17.1.a upgrade installs an older snapshot--it hasn't received an update in a few weeks. But anyway, it looked like it works as expected there.


Cheers,
Franco
Logged

Solaris17

  • Full Member
  • ***
  • Posts: 118
  • Karma: 17
    • View Profile
Re: How to test the development version
« Reply #24 on: November 17, 2016, 02:57:51 am »
ran the updates via console and everything is fine now on the following.

OPNsense 17.1.a_539-amd64
FreeBSD 11.0-RELEASE-p2
OpenSSL 1.0.2j 26 Sep 2016
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 17707
  • Karma: 1618
    • View Profile
Re: How to test the development version
« Reply #25 on: November 24, 2016, 12:36:10 pm »
Neat, pkg 1.9.x has a bug that prevents installation of packages because it tries to drop privileges and thus can't read the directory owned by root.

EDIT: OTOH, I'm relieved that the upgrades do work and we can explain the missing packages transition reported recently.
« Last Edit: November 24, 2016, 12:40:16 pm by franco »
Logged

Solaris17

  • Full Member
  • ***
  • Posts: 118
  • Karma: 17
    • View Profile
Re: How to test the development version
« Reply #26 on: November 24, 2016, 04:45:36 pm »
Quote from: franco on November 24, 2016, 12:36:10 pm
Neat, pkg 1.9.x has a bug that prevents installation of packages because it tries to drop privileges and thus can't read the directory owned by root.

EDIT: OTOH, I'm relieved that the upgrades do work and we can explain the missing packages transition reported recently.

Wow thats odd. Does BSD know about this yet?
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 17707
  • Karma: 1618
    • View Profile
Re: How to test the development version
« Reply #27 on: November 24, 2016, 05:08:28 pm »
Considering that the fix was backported 13 days ago, a week after pkg 1.9.3 came out and the commit message reads "Stop dropping privileges when fetching as it causes more issues than it solves", they know about it but 1.9.4 isn't out so the impact in FreeBSD itself is likely low.

https://github.com/freebsd/pkg/commit/504cff94

Various project use pkg in different ways, report bugs upstream, have different side-effects from changes. I'm just glad that wasn't injected into a production environment as it only affects upgrading to 17.1-ALPHA at this point.

Packages are rebuilt, I'm fixing the upgrade instructions now.


Cheers,
Franco
« Last Edit: November 24, 2016, 05:10:29 pm by franco »
Logged

Solaris17

  • Full Member
  • ***
  • Posts: 118
  • Karma: 17
    • View Profile
Re: How to test the development version
« Reply #28 on: November 24, 2016, 05:12:04 pm »
On that topic Were the commands at the end of the OP supposed to bring people upto the GIT version? Because the base install only currently goes upto 539. After the mishap with upgrading those commands don't really work, stating that the directory already exists etc. I would remove it to attempt it again but i'm uncertain what was touched in the process originally.
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 17707
  • Karma: 1618
    • View Profile
Re: How to test the development version
« Reply #29 on: November 24, 2016, 05:17:47 pm »
17.1.a_539 is still recent, mostly because each build requires changes that are done out of tree to avoid breaking 16.7 progress. The exercise is testing 11.0 and the upgrades more than the GUI code in this case.

I'm not sure if the installation can be unbroken easily. Which command is failing for you particularly?
Logged

  • Print
Pages: 1 [2] 3 4 ... 6
« previous next »
  • OPNsense Forum »
  • Archive »
  • 18.1 Legacy Series »
  • [OBSOLETE] How to test the development version
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2