Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    64bit version now seems to be 32bit and Monitoring Grphs cannot display

    Installation and Upgrades
    3
    5
    1535
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      andy_enuff last edited by

      Hi

      Thanks for a great product! One quick question…. I recently upgraded from version 2.2 to version 2.3 and the RRD data that seemed to be displaying fine before seems not to display now in the monitoring section of 2.3. I receive the message "Error: This RRD was created on another architecture".  I wasn't aware that I had changed from 64bit to 32bit, but it would appear that my installation IS now 32bit as far a i can tell... If all my old graphs are now "the wrong architecture I must have been on 64bit?

      "2.3.1-RELEASE (i386) "  is 32bit right?  I am not going mad?

      What is my next step to get this all back working again?

      Backup config, reinstall 64bit and try again?  How did I end up back at 32bit when is simply used the auto upgrade?

      Thanks,

      Swampy

      1 Reply Last reply Reply Quote 0
      • C
        caseystone last edited by

        Same just happened to me. I was on 2.2.something recent and updated to 2.3.1 using the built-in update mechansim. I stop by "monitoring" / rrd graphs and I see "Error: This RRD was created on another architecture".

        I also would like an answer, and would like to retain my old rrd data.

        I installed my system from the 2.2.6 amd64 iso and installed as a full system (not embedded). My pfsense runs as a KVM virtual machine.

        Running version now is:

        2.3.1-RELEASE (i386)
        built on Tue May 17 18:46:37 CDT 2016
        FreeBSD 10.3-RELEASE-p3

        Thanks.

        1 Reply Last reply Reply Quote 0
        • A
          andy_enuff last edited by

          Have just upgraded 20 2.3.1_1 and still have the same issue. (wasn't expecting a magical change back mind you!)

          Would be good to understand what happened here.

          1 Reply Last reply Reply Quote 0
          • J
            JorgeOliveira last edited by

            https://doc.pfsense.org/index.php/Upgrade_Guide

            Avoiding Unintended Architecture Change

            In 2.2.x and earlier versions, the firmware update URL could be hard-coded to a user-specified value. If this is done on a 32 bit system, and that configuration later restored to a 64 bit system, the next upgrade of the restored system will switch it to 32 bit. When using auto-update, first browse to System>Firmware, Updater Settings tab. If the "Use an unofficial server for firmware upgrades" box is checked, un-check it, and click Save. Then your system will remain on its current architecture.

            My views have absolutely no warranty express or implied. Always do your own research.

            1 Reply Last reply Reply Quote 0
            • C
              caseystone last edited by

              Thanks JorgeOliveira for that link – I had seen it, after the fact of course!

              When I installed 2.2.6 AMD64 from iso I then brought in my full config backup file. I think it's unlikely I would have 'hard coded' any particular update path into my settings, I probably had it set to just install stable updates.

              I think that is a pretty odd situation to end up in ... running any auto-update on a 64 bit system and ending up with a 32 bit system and I think there should have been some means of preventing that or at least warning about it.

              In any case, I backed up my config file again, did a clean install of 2.3.1 from the amd64 full install iso, reloaded my config file, and my system is working again.

              Sadly, it seems my RRD data was lost. It is working again, creating new data, but I can't go back to see old data. Does anyone know how that works? I was looking in /var/db/rrd/ and my files are not too small, like:

              -rw-r--r--   1 nobody  wheel   144K May 30 18:19 WAN_DHCP-quality.rrd
-rw-r--r--   1 nobody  wheel   384K May 30 18:19 ipsec-packets.rrd
-rw-r--r--   1 nobody  wheel   384K May 30 18:19 ipsec-traffic.rrd
-rw-r--r--   1 nobody  wheel   384K May 30 18:19 lan-packets.rrd
-rw-r--r--   1 nobody  wheel   288K May 30 18:19 lan-queuedrops.rrd
-rw-r--r--   1 nobody  wheel   288K May 30 18:19 lan-queues.rrd
-rw-r--r--   1 nobody  wheel   384K May 30 18:19 lan-traffic.rrd
-rw-r--r--   1 nobody  wheel   384K May 30 18:19 ovpns1-packets.rrd
-rw-r--r--   1 nobody  wheel   384K May 30 18:19 ovpns1-traffic.rrd
-rw-r--r--   1 nobody  wheel    49K May 30 18:19 ovpns1-vpnusers.rrd
-rw-r--r--   1 nobody  wheel   575K May 30 18:19 system-mbuf.rrd
-rw-r--r--   1 nobody  wheel   718K May 30 18:19 system-memory.rrd
-rw-r--r--   1 nobody  wheel   240K May 30 18:19 system-processor.rrd
-rw-r--r--   1 nobody  wheel   240K May 30 18:19 system-states.rrd
-rw-r--r--   1 root    wheel   8.7K May 30 18:13 updaterrd.sh
-rw-r--r--   1 nobody  wheel   384K May 30 18:19 wan-packets.rrd
-rw-r--r--   1 nobody  wheel   240K May 30 18:19 wan-queuedrops.rrd
-rw-r--r--   1 nobody  wheel   240K May 30 18:19 wan-queues.rrd
-rw-r--r--   1 nobody  wheel   384K May 30 18:19 wan-traffic.rrd

              Is that the size of 'blank' rrd data? Was the data 'poisoned' by running the 32 bit OS briefly? I'm not sure I ever did a backup that contained the full RRD data, my XML backups are usually 150k or so.

              Thanks.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post