Upgrade 2.0 RC3 (amd64) now i386?

[ldtech]

Same problem…

[Nachtfalke]

I am tryinh with update from URL from conseole:
http://pfsense.bol2riz.com/updates/

[databeestje]

oops, will take that up.

[Nachtfalke]

Hmmm…updating over the cosole is really slow...

Fetching MD5...
looking up pfsense.bol2riz.com
connecting to pfsense.bol2riz.com:80
requesting http://pfsense.bol2riz.com/updates/pfSense-Full-Update-2.0-RELEASE-amd64.tgz.md5
remote size / mtime: 83 / 1316225269
/root/firmware.tgz.md5                        100% of   83  B  794 kBps
URL MD5: 15ad7e8672ea057c4a3e3834606751d3

Downloaded file MD5: 15ad7e8672ea057c4a3e3834606751d3

MD5 checksum matches.

One moment please...

Broadcast Message from admin@pfsense1.hpa
        (no tty) at 14:12 CEST...

Firmware upgrade in progress...

...

Perhaps better wait till the update URL gets fixed

[jimp]

Yeah that needs a separate url for updates. I just added one to the manifest. Go to firmware settings and make sure you choose the amd64 location from the drop-down.

[Clouseau]

Update url down?

http://updates.pfsense.org/_updaters

=> 404 - Not Found

[Nachtfalke]

@Clouseau:

Update url down?

http://updates.pfsense.org/_updaters

=> 404 - Not Found

Go to System -> Firmware -> Updater Settings -> Default Auto Update URLs
Select i386 or amd64
Both are working now.

[tester_02]

same issue.   tried manual update with file manually downloaded from the mirrors, but it's not doing anything (firefox just waits and waits after the upload button is clicked).

[tester_02]

ok.  I now see the amd64/32 showing up.  How do we convert from back to 64 bit?  Manual update not working, auto says on latest version.

[jimp]

going from 32->64 requires a manual reboot at the end of the upgrade because of the architecture change. Otherwise the upgrade path is the same.

Going the other way works because you can run 32-bit binaries on amd64 but not the other way 'round.

[tester_02]

Manual upgrade never did anything for me.  just waited and waited and nothing.  Even tried exploder and nothing..
Went to console and told it to do update from auto and it went and got the 64 bit from the new updater setting..
Update is going, assuming when it's done all will be back to normal….

Lesson learned... Should have done a backup before the upgrade, and could have reverted back and tried again with the proper update url.

[Nachtfalke]

I have no remote access to my first box using webGUI or SSH anymore.
Traffic is passing, OpenVPN server is running and I can connect.

I updates from
http://pfsense.bol2riz.com/updates/pfSense-Full-Update-2.0-RELEASE-amd64.tgz
using the console.

Do I have any chance to get remote access to the box again ?
Is there an update running in the background ?!

Thanks for feedback.

[databeestje]

If you upgrade a i386 to a amd64 you will lose remote access and you need to reboot the machine manually.

As Jim mentioned above.

[Swordforthelord]

@Nachtfalke:

@Clouseau:

Update url down?

http://updates.pfsense.org/_updaters

=> 404 - Not Found

Go to System -> Firmware -> Updater Settings -> Default Auto Update URLs
Select i386 or amd64
Both are working now.

This works for me on a PC based platform but I have a 2g nanobsd box and a 4g nanobsd box and both can no longer check for updates after following these steps.

[dzeanah]

It could be worse.

I wasn't paying much attention and uploaded the x64 version to my Netgate m1n1wall.  Looks like I'll have to reimage the CF card when I get the time.

:-[

[slu]

Go to "System" -> "Firmware" -> "Updater Settings" -> "Default Auto Update URLs" -> "pfSense Stable Release Updates (amd64)" and Pfsense will use "Firmware Auto Update URL" –> "http://updates.pfsense.org/_updaters/amd64".

http://updates.pfsense.org/_updaters/amd64
-> 404 - Not Found

What is correct now?  ???

[jimp]

@Swordforthelord:

This works for me on a PC based platform but I have a 2g nanobsd box and a 4g nanobsd box and both can no longer check for updates after following these steps.

Should be OK now.

[Swordforthelord]

@jimp:

@Swordforthelord:

This works for me on a PC based platform but I have a 2g nanobsd box and a 4g nanobsd box and both can no longer check for updates after following these steps.

Should be OK now.

Thanks, it is.

[Clouseau]

2.0-RELEASE (i386)
built on Tue Sep 13 18:02:53 EDT 2011 

Works fine now - Alix got the release !

[jimp]

It always had it, just not the automatic way. :-)