PHP Parse error: syntax error, unexpected $end in /usr/local/www/interfaces.php



  • Hello

    I am getting the below error message when trying to view any interface information form the drop down. I tried to submit this via the crash reporter but it errors too… I am not sure it was sent/received properly. See it's error way down...  Any Ideas how I can fix this or work around it?

    I search here: http://redmine.pfsense.org/projects/pfsense/issues  and did not see any mention of this problem..

    ###################BEGIN########################

    Crash report begins.  Anonymous machine information:

    i386
    8.3-RELEASE-p4
    FreeBSD 8.3-RELEASE-p4 #0: Thu Nov 22 05:06:49 EST 2012    root@snapshots-8_3-i386.builders.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_wrap.8.i386

    Crash report details:

    PHP Errors:
    [22-Nov-2012 14:06:38 UTC] PHP Parse error:  syntax error, unexpected $end in /usr/local/www/interfaces.php on line 2808

    #################################################################

    ###################CRASH REPORT ERROR###############################

    Processing… Warning: file_put_contents(/var/crash/crashreport_header.txt): failed to open stream: No such file or directory in /usr/local/www/crash_reporter.php on line 104
    Uploading...
    Upload received OK.

    Continue and delete crash report files from local disk.



  • Fixed, thank you for reporting.



  • I updated to the latest snapshot. Still getting that error. Line 2808 which is empty line by the very end of this file. So, error is somewhere in the "middle". Could you specify how to manually fix it?



  • ITs this one https://github.com/bsdperimeter/pfsense/commit/af13aad69fd8127bc505f36b7debc00aadc9320c.
    Though latest snapshot when mentioned means the next build run after this post which might not be the one you get update notification.



  • @ermal:

    ITs this one https://github.com/bsdperimeter/pfsense/commit/af13aad69fd8127bc505f36b7debc00aadc9320c.
    Though latest snapshot when mentioned means the next build run after this post which might not be the one you get update notification.

    For me at least, loading up that .php file results in the error disappearing when clicking on the WAN interface, but the same error remains for the LAN interface (registered just to post this) (in addition, getting kernel panic, followed by corrupting the entire file system when attempting to enable Intel 4965 PCIe card in AP mode on a fresh install, but that's far less critical at this point)



  • @rmoulynox:

    followed by corrupting the entire file system when attempting to enable Intel 4965 PCIe card in AP mode on a fresh install, but that's far less critical at this point)

    The man page for the FreeBSD iwn driver says it supports the 4965 device but doesn't say AP mode is uspported. (See http://www.freebsd.org/cgi/man.cgi?query=iwn&apropos=0&sektion=0&manpath=FreeBSD+8.3-RELEASE&arch=default&format=html )

    A panic is a poor way of saying "AP mode is probably not supported". But it probably gets more attention than a message on the console or syslog. :)


Locked