2.3 update moved me to 32-bit, how?



  • So while I was trying to figure out where all my pretty RRD graphs that showed monthly usage and such went, I kept getting errors.  Updated to 2.3.x and the mystery error went away, but it was replaced with some brief message along the lines of "rrd files from wrong architecture, deleting" (thanks!  I wouldn't want to save and convert years of data…:) ).

    I thought that was a bit odd and then when poking around trying to get apcupsd installed from the FreeBSD repo I noted that it failed because the URL pointed to the amd64 repo.

    Any idea why the 2.3 upgrade shoved me to i386?  This is not a modern box, but it was running amd64 and the one cause I could find googling did not seem to be my issue.  My backup config had this line, which I don't think forces me to a "non-standard" update URL (or is it?):

    
     <firmware><alturl><enable><firmwareurl>https://updates.pfsense.org/_updaters</firmwareurl></enable></alturl></firmware> 
    
    


  • @sporkme:

    Any idea why the 2.3 upgrade shoved me to i386?  This is not a modern box, but it was running amd64 and the one cause I could find googling did not seem to be my issue.  My backup config had this line, which I don't think forces me to a "non-standard" update URL (or is it?):

    That's the standard update URL, but for 32 bit. The 64 bit URL has amd64 in it. You manually set it to that at some point.

    It's no longer possible to intentionally or unintentionally switch architectures in >=2.3, so it won't happen again. But you should reinstall 2.3.1 64 bit and restore your config backup to get back to 64 bit. You can include the RRD data in the backup and it'll restore post-reinstall.


Log in to reply