Upgrade 2.1.3 to 2.1.5 failing - no errors



  • Hi,

    I'm somewhat new to pfsense, and i am trying to upgrade from 2.1.3 through the web gui via auto and manual update and the upgrade process seems to work correctly, however after reboot the version is still 2.1.3.  Can anyone give any ideas as to what is going on and how to troubleshoot.

    Thanks



  • You're not out of disk space or something obvious like that?



  • 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.



  • Nothing in the System log?



  • 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



  • 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.


  • LAYER 8 Netgate

    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.



  • @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?



  • @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


  • LAYER 8 Netgate

    @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.



  • 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.



  • 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.


Log in to reply