pfSense-upgrade -n (Dry run)
-
Is it safe to run this command on a productive machine, just to check how it would go, WITHOUT making actually any changes to the running system?
Reading all the failed upgrades and package updates lately, makes me a little nervous.
Thanks.
-
Is it advisable and safe to use "pfSense-upgrade -n" before major upgrades ?
What will it achieve ?
Thx
-
That's the dry-run option. It goes through the motions of upgrading your system without actually making any changes. It's a good way to see if you're missing anything or if something is out of place.
-
That will still upgrade
pfSense-upgrade
itself, which is safe (and good -- you want bug fixes that come with new versions of `pfSense-upgrade). Otherwise it will just output what it wants to do and then exit, which is safe. -
@jimp said in pfSense-upgrade -n (Dry run):
That will still upgrade
pfSense-upgrade
itself, which is safe (and good -- you want bug fixes that come with new versions of `pfSense-upgrade). Otherwise it will just output what it wants to do and then exit, which is safe.OK thank you !
Can you pls take a look at my output https://pastebin.com/Pzn2Lbwe ?
Does it mean my upgrade will go smoothly ?
-
@chudak said in pfSense-upgrade -n (Dry run):
Can you pls take a look at my output https://pastebin.com/Pzn2Lbwe ?
Does it mean my upgrade will go smoothly ?
Looks fine to me.
-
Thanks for the clarification jimp!
https://pastebin.com/UnjAEpcS
There should be no major issues here, right?
Thanks again.
/edit
After running pfSense-upgrade -n, the Package Manager is offering me now many updates, better not to update them, before upgrade pfSense to 2.4.4?
-
Exact.
As found elsewhere on the forum, most packages will include PHP 7.2.
And that will break the GUI and other PHP related tasks. -
When I run 'pfSense-upgrade -n' I see some left overs from packages that were removed, for example:
"Updating dnsthingy repository catalogue...
dnsthingy repository is up to date."Is there a way to clean up left overs ?
Thx
-
That depends on what you did to add it in there. It could just be an extra file in
/usr/local/etc/pkg/repos/
.Since we don't know how you added that, we can't tell you how to fix it. Reverse whatever steps you took to get it there.
-
Thx
Seem there was an extra file, and removing it worked[2.4.3-RELEASE][admin@pfSense]/root: cat /usr/local/etc/pkg/repos/dnsthingy.conf
dnsthingy:{url: "https://downloads.dnsthingy.com/pkg/test/${ABI}",enabled: yes}