Upgraded to 2.4.2_1 But still shows 2.4.2

pr4499

Anyone?

detox

I am having a similar issue. I did an upgrade from 2.3 via service console

dashboard states:
2.4.2-RELEASE (amd64)
built on Tue Dec 12 13:45:26 CST 2017
FreeBSD 11.1-RELEASE-p6

Widget Netgate services and support continues to spin stating "Retrieving support information"

I also tried pfSense-upgrade -d, and it stalls at " Updating repositories metadata.

Now, I think I broke it by deleting some *.conf file on the initial upgrade as the installed recommended removing it. I do not remember what it was.

So on the assumption I 'bricked' it, how can I reimage it? It was purchased from Netgate ( Netgate SG-4860)
Netgate device ID: 67f61d3cb8fa0b145112

Found reference in manual to got netgate portal (I have gold membership) to DL the image. I cannot find a link for downloading an image.

The pfSense site has a select for Netgate ADI under architecture, but I don't know if this is it or not.

Thanks for any help!

Thanks

detox

Success!

After quite a bit of Googling, I was able to find the solution.

I now have a fully functional SG-4860 again!

Once I was able to put the pieces together, the process was simple and painless.

pr4499

Does anyone have a solution for when it won't update either from the Web gui or the command line?

Gil

Save your config, then reinstall 2.4.2-1 from scratch, then upload old config

pr4499

This is a good solution, except its difficult to do remotely.

Any other ideas?

Gertjan

@pr4499:

This is a good solution, except its difficult to do remotely.

Any other ideas?

Ship a prepared unit to the site, and have the installed one shipped back ?

pr4499

Again, this would require the end user to know what to do with it.

Does anyone know the actual cause of this issue? And a command to fix it?

peter_richardson

different version numbers, same issue. Anyone got an idea about this one?

Today's output from the command "pfSense-upgrade -d" is:

>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pkg-static: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
pkg-static: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/meta.txz: Network is unreachable
repository pfSense-core has no meta file, using default settings
pkg-static: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/packagesite.txz: Network is unreachable
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
pkg-static: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4/meta.txz: Network is unreachable
repository pfSense has no meta file, using default settings
pkg-static: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4/packagesite.txz: Network is unreachable
Unable to update repository pfSense
Error updating repositories!

output from "pkg info -x pfsense" is:

pfSense-2.4.4
pfSense-Status_Monitoring-1.7.6
pfSense-base-2.4.4
pfSense-default-config-2.4.4
pfSense-kernel-pfSense-2.4.4
pfSense-pkg-ntopng-0.8.13_3
pfSense-rc-2.4.4
pfSense-repo-2.4.4
pfSense-upgrade-0.59
php72-pfSense-module-0.64_6

It appears it can't get out to the internet:

PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host

Which is strange because the connection is definitely up. We have a gateway group with 2 WAN connections. One is down, the other is up at the moment.

peter_richardson

anyone?

Rico

Same issue maybe?
https://forum.netgate.com/topic/138788/no-default-route-after-reboot-using-gateway-groups

-Rico