pfSense-upgrade 0.94 -> 0.95
-
Hi,
after updating the pfSense-upgrade script (0.94 -> 0.95) in the cli when invoking pos. 13 (Update from console) the script never finish - had to use CTRL^C to abort.
Please take a look on that.Thank you,
fireodo -
@fireodo said in pfSense-upgrade 0.94 -> 0.95:
Please take a look on that.
Saw the same thing as I hit option 13 also.
But I was warned ^^I had another SSH instance with 'htop' open to see what happened :
Ok, were good for the joke : it's a "wire-guard bug" ;))
Your Ctrl-C worked fine
-
Hi!
Me too, from cli (option 13).
Had to use ctrl c. With ps and ssh shell I saw a sed process doing something with wireguard config, did not write it up what exactly.
pfSense-Plus 21.02-p1
Rerun and same result.
-
Thinking loud ....
Saw on reddit , that some users mentioned they got something like this on an update (might not be via cli)
Error: Please remove any Wireguard configurationCould WG configs be the reason it's spinning ?
Should they be removed before cli update ?/Bingo
-
@bingo600 I don't think that it's to do with WireGuard. I've a couple of lab devices affected by this issue today, one on pfS+ 21.02.2RC and one on 2.5.1RC. Both had been running RCs built after WG removal on 20th March and the configs had been wiped of any references to WG.
-
Never used wireguard on this device, so I really don't know.
Can anyone provide additional info please?
-
@dread I would just wait it out and see what happens with the next RC builds.
-
Hopefully this will be fixed soon with the next stable patch release.
(pfSense Plus 21.02-RELEASE-p2 / pfSense 2.5.x with FreeBSD-SA-21:07.openssl patch, just wondering..).
Thanks
-
@dread said in pfSense-upgrade 0.94 -> 0.95:
Hopefully this will be fixed soon with the next stable patch release.
It is fixed since this morning 0.95 -> 0.96
Regards,
fireodo -
@fireodo said in pfSense-upgrade 0.94 -> 0.95:
It is fixed since this morning 0.95 -> 0.96
Solved. Thanks!!