Update issue (resolved)



  • Latest update blew me up…   pfSense-Full-Update-1.2.1-RC1-20080823-0318.tgz
    call to undefined function xml parser create() ect/inc/xmlparse.inc on line 153



  • The latest known to be working build is 20080820-2342



  • @nocer:

    The latest known to be working build is 20080820-2342

    Does this still hold, or has the php issue been sorted?

    ryts



  • Loaderd the pfSense-Full-Update-1.2.1-RC1-20080825-0218 build. Works for me here !  :D



  • @DeCex:

    Loaderd the pfSense-Full-Update-1.2.1-RC1-20080825-0218 build. Works for me here !  :D

    tnx for being the guinea pig  ;D

    ryts



  • tnx for being the guinea pig  ;D
    ryts

    Is a dirty job, someone gotto do it  ;D



  • yup, the latest works again. go get'em and your done.



  • I upgraded to pfSense-Full-Update-1.2.1-RC1-20080825-0741 and it sent my server into a reboot cycle.  I'm back at pfSense-Full-Update-1.2.1-RC1-20080820-2342 installed with a fresh ISO.  I did not get a specific error at least written down but it sure did not like the upgrade.  It is the first time that a pfsense version has continually rebooted my system.  Oh well.



  • I seem oK on 0741.

    At least on what I think is 0741 ???. I am a bit dim and find the versions difficult to follow:

    0741 reflects so in the name on http://snapshots.pfsense.org/FreeBSD7/RELENG_1_2/ and is the build time but the file time on the server reads 04:30'ish (time to copy and time difference??) yet the version file on snapshots (and thus what reflects in the auto-update display) reads  08:11 EDT. However, when installed the web interface system display presents  07:40:58 EDT which is 0741!!!

    So, I think I am OK on 0741 but it could be wormhole version 0811 …

    Goodnight all.... ;)

    ryts



  • If I'd like to update 1.2.1-beta-mumble to the latest code….would the following work?

    Backup the current config to my laptop.
    Download the latest snap and burn onto CD
    Boot with new CD and install to hard disk
    On reboot after install restore config from laptop

    Currently running:

    1.2.1-TESTING-SNAPSHOT
    built on Sat Jul 19 07:13:48 EDT 2008

    Cheers,



  • @familyguy:

    If I'd like to update 1.2.1-beta-mumble to the latest code….

    Why not use the inbuilt update method?

    System: Firmware: Settings <– Select from the drop down box 1.2.1-snapshots
    then
    System: Firmware: Auto Upgrade <-- Invoke Auto Update

    Backup your configuration first just in case of breakage.



  • My latest attempt to update ended with the rebooting issue again.  In trying to update to pfSense-Full-Update-1.2.1-RC1-20080825-2326 on reboot I get:

    Incorrect Block Count I = 884507 (80 should be 0)
    correct? yes

    There are several of these with different number.  I'm guessing this is some kind of chkdsk?  It then proceeds to:
    Phase 5 cklg cyl group. . .

    I then got a "Fatal Trap 12," and was unable to write anything more about the issue.  It will continue to reboot over and over.

    thanks,
    Jim



  • hmmmm…I'm not sure here but I loaded up pfSense-Full-Update-1.2.1-RC1-20080825-2326 just fine. Oh, it was the box with pfSense-Full-Update-1.2.1-RC1-20080825-0218 loaded and running fine.

    The messages you've seen were, as you may aware, from fsck which means that shutdown/reboot/halt the box without sync'ing the hdd buffer, or sudden power loss, or disconnect the power cable, or the hdd really damaged. Have you tried fresh ISO, newfs/slice once again?

    Finally, "Fatal Trap 12" is too common while booting the kernel so can't say anything without debug enabled. Googling it might be a help.



  • ^ That same release has busted me right up. No browsing is working.



  • anyone can confirm if the pfSense-Full-Update-1.2.1-RC1-20080825-2326 is REALLY working?

    Thanks!



  • @danzel:

    anyone can confirm if the pfSense-Full-Update-1.2.1-RC1-20080825-2326 is REALLY working?

    Thanks!

    There is a problem with  -2326 regarding the md5 and sha1 checkfiles on http://snapshots.pfsense.org/FreeBSD7/RELENG_1_2/. The updaters directory is on -0741.

    I would shy away from it as there seem to be build issues.

    ryts



  • @danzel:

    anyone can confirm if the pfSense-Full-Update-1.2.1-RC1-20080825-2326 is REALLY working?

    Thanks!

    Uptime 2 days, 00:52

    ![2008-08-28 16-51-04.jpg](/public/imported_attachments/1/2008-08-28 16-51-04.jpg)
    ![2008-08-28 16-51-04.jpg_thumb](/public/imported_attachments/1/2008-08-28 16-51-04.jpg_thumb)



  • But the builder is still stuck. Waiting for someone to unwedge it.



  • Yes it was at least for me. Already moved to the latest so that I won't be able to proof it tho. Is that really an issue while new snapshots are ready every two hours? Why don't you keep uploading 'till you find working snap?  I think that is what snapshot for, and is only an RC, anything would happen in every minute :D



  • Just did an fresh install on CF (first 1.2 from cd then straight away upgraded to the latest snapshot 1.2.1-RC1-20080829-1254) and it seems there are some packages missing.

    I noticed earlier (when first upgrading to this beta) that phpsysinfo was gone but now also dashboard is gone. Is there any way to get these back or are those going to automaticly show up at some point on the packages list?

    So basicly, is this "missing packages" thing an bug or an feature and how to fix it?



  • Please see:

    http://forum.pfsense.org/index.php/topic,10601.0.html

    concerning dashboard.



  • I was finally able to move past the snapshot done on the 20th.  I believe it had something to do with selecting, on one of my installs, how the hard drive was partitioned.  This last time I did not select the option to partition and now I am able to upgrade without issue.



  • @dro:

    @familyguy:

    If I'd like to update 1.2.1-beta-mumble to the latest code….

    Why not use the inbuilt update method?

    System: Firmware: Settings <– Select from the drop down box 1.2.1-snapshots
    then
    System: Firmware: Auto Upgrade <-- Invoke Auto Update

    Backup your configuration first just in case of breakage.

    When I try this, it downloads the update and then hangs after the download is complete.

    Cheers,


Locked