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

    Upgrade 2.1.3 to 2.1.5 failing - no errors

    Problems Installing or Upgrading pfSense Software
    5
    12
    2.4k
    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.
    • T
      tlachau
      last edited by

      gui shows 16% usage.

      the upgrade seems to go successful, but after reboot still shows 2.1.3 and then states it is reinstalling packages like normal.  I've updated 4 others with no problems, it is just this one with the problem.

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        Nothing in the System log?

        1 Reply Last reply Reply Quote 0
        • T
          tlachau
          last edited by

          THe logs clear from the upgrade, but this is there.

          ov 28 11:43:41 syslogd: kernel boot file is /boot/kernel/kernel
          Nov 28 11:43:41 syslogd: exiting on signal 15
          Nov 28 11:43:41 php: rc.bootup: Creating rrd update script
          Nov 28 11:43:41 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/ipsec-packets.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 4 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
          Nov 28 11:43:41 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/ipsec-traffic.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 4 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
          Nov 28 11:43:41 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/opt3-packets.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 4 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
          Nov 28 11:43:41 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/opt3-traffic.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 4 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
          Nov 28 11:43:41 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/opt1-packets.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 4 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
          Nov 28 11:43:41 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/opt1-traffic.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 4 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
          Nov 28 11:43:41 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/lan-packets.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 4 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
          Nov 28 11:43:41 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/lan-traffic.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 4 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
          Nov 28 11:43:41 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/wan-packets.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 4 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
          Nov 28 11:43:41 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/wan-traffic.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 4 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
          Nov 28 11:43:30 check_reload_status: Updating all dyndns
          Nov 28 11:43:29 php: rc.bootup: ROUTING: setting default route to 64.33.182.65
          Nov 28 11:43:25 syslogd: sendto: Network is unreachable
          Nov 28 11:43:25 kernel: em1: link state changed to UP
          Nov 28 11:43:25 check_reload_status: Linkup starting em1
          Nov 28 11:43:24 kernel: em2: link state changed to UP

          1 Reply Last reply Reply Quote 0
          • KOMK
            KOM
            last edited by

            Do you have a bunch of packages installed?  Perhaps as an idea, you might try removing all your installed packages and then try the upgrade.  This may be a severe option if you have several packages installed and configured.  Before I tried anything drastic, I would make sure that I have a fresh backup file via Diagnostics - Backup/Restore, and preferably a bare-metal image that you could restore in a snap if necessary.  Or you could try performing a backup and then do a fresh install of 2.1.5, then restore from your backup file.

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              Are you sure you're installing 32-bit over 32-bit or 64-bit over 64-bit?  I think installing 64 over 32 chokes on RRD data.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

              1 Reply Last reply Reply Quote 0
              • T
                tlachau
                last edited by

                @Derelict:

                Are you sure you're installing 32-bit over 32-bit or 64-bit over 64-bit?  I think installing 64 over 32 chokes on RRD data.

                i would think the autoinstaller would catch that, right?

                1 Reply Last reply Reply Quote 0
                • T
                  tlachau
                  last edited by

                  @KOM:

                  Do you have a bunch of packages installed?  Perhaps as an idea, you might try removing all your installed packages and then try the upgrade.  This may be a severe option if you have several packages installed and configured.  Before I tried anything drastic, I would make sure that I have a fresh backup file via Diagnostics - Backup/Restore, and preferably a bare-metal image that you could restore in a snap if necessary.  Or you could try performing a backup and then do a fresh install of 2.1.5, then restore from your backup file.

                  the only package is NRPE

                  1 Reply Last reply Reply Quote 0
                  • DerelictD
                    Derelict LAYER 8 Netgate
                    last edited by

                    @tlachau:

                    @Derelict:

                    Are you sure you're installing 32-bit over 32-bit or 64-bit over 64-bit?  I think installing 64 over 32 chokes on RRD data.

                    i would think the autoinstaller would catch that, right?

                    Going from 32 to 64 I think there are issues with that.  I would take a backup without RRD data, install fresh, and restore the backup.

                    Chattanooga, Tennessee, USA
                    A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                    DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                    Do Not Chat For Help! NO_WAN_EGRESS(TM)

                    1 Reply Last reply Reply Quote 0
                    • K
                      kejianshi
                      last edited by

                      I'm afraid to go from 32 to 64 bit on an upgrade.  Unless there is some major config issues, I'd probably wipe and do a clean install. 
                      I hate unexpected side effects in a device that my internet depends on.

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

                        Those RRD logs are symptomatic of a system that ran out of RAM at boot time. Only circumstances where I can recall seeing that are systems with 256 MB or less RAM, running nano (so a chunk of the RAM is taken by rw filesystems), and more packages or other services than should be run with minimal RAM.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.