16
19.1 Legacy Series / Re: VM of OPNsense on Hyper-V Win Svr 2019 Std - Fails
« on: March 02, 2019, 10:00:47 am »
19.1.2 released, I didn't see any changes in this regard in the changelog. However I tried to (after taking snapshots) my test-environment from 18.x to 19.1.2. However, as far as the logs go, I see it first tries to 19.1:
***GOT REQUEST TO UPGRADE: maj***
Fetching packages-19.1-OpenSSL-amd64.tar: ...............................pgrep: Cannot open pidfile `/tmp/opnsense-fetch.pid.oUd52D': No such file or directory
done
Fetching base-19.1-amd64.txz: ........ done
Fetching kernel-19.1-amd64.txz: .... done
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Extracting packages-19.1-OpenSSL-amd64.tar... done
Extracting base-19.1-amd64.txz... done
Installing kernel-19.1-amd64.txz... done
Please reboot.
***REBOOT***
19.1.2 update was available in the updates-list though. Would this mean we will have a hard time updating these affected machines to a 19.x version that has this issue fixed later on, as it'll always first update to this non-working version? So maybe offtopic here, but how do we update to a 19.1.x version in this case, skipping the faulty 19.1 release?
***GOT REQUEST TO UPGRADE: maj***
Fetching packages-19.1-OpenSSL-amd64.tar: ...............................pgrep: Cannot open pidfile `/tmp/opnsense-fetch.pid.oUd52D': No such file or directory
done
Fetching base-19.1-amd64.txz: ........ done
Fetching kernel-19.1-amd64.txz: .... done
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Extracting packages-19.1-OpenSSL-amd64.tar... done
Extracting base-19.1-amd64.txz... done
Installing kernel-19.1-amd64.txz... done
Please reboot.
***REBOOT***
19.1.2 update was available in the updates-list though. Would this mean we will have a hard time updating these affected machines to a 19.x version that has this issue fixed later on, as it'll always first update to this non-working version? So maybe offtopic here, but how do we update to a 19.1.x version in this case, skipping the faulty 19.1 release?