Sshdcond - call to undefined function



  • Starting with a new, preinstalled, 2.2 build, with very little done to it beyond basic configuration, I installed the SSHDCond package (1.0.5) from the packages menu.  _The SSHDCond package appeared to install without error, and GUI presented correctly, but changes were not saved to the sshd_config file and a crash report was generated.

    Crash report begins.  Anonymous machine information:
    i386
    10.1-RELEASE-p9
    FreeBSD 10.1-RELEASE-p9 #0 57b23e7(releng/10.1)-dirty: Mon Apr 13 20:37:21 CDT 2015    root@pfs22-i386-builder:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_wrap.10.i386
    Crash report details:
    PHP Errors:
    [10-Oct-2015 10:58:28 Etc/UTC] PHP Fatal error:  Call to undefined function sshdcond_custom_php_write_config() in /usr/local/www/pkg_edit.php(173) : eval()'d code on line 1

    This looks to me like a genuine "bug" rather than operator error, but I lack the knowledge to diagnose any further.

    On a subsequent reboot, the GUI stalled at "Packages are being reinstalled in the background".  After leaving well alone for over an hour, I rebooted again and this time it didn't stall but I got the above error message repeated in the console transcript, and no SSH Conditions entry in the services menu.

    Is this even the right place to raise the matter?  I pressed the submit button on the crash report to send it in, but that appears to be a fire-and-forget facility.

    Suggestions?

    Thanks.

    PS: It all works perfectly on an earlier 2.1.5 system._


  • Banned

    The function is defined just fine… You are missing the inc file. Clear the package lock (Diagnostics - Backup/Restore) and try again.



  • Thank you, but no "Clear Package Lock" button is offered.  From the documentation this is presumably because the "Packages are Reinstalling" screen was not being displayed at the time.

    However, this may all have become moot as the system has now become (or I have rendered it) so confused that it will not boot at all.  Just 2 or 3 lines of gibberish characters on the serial console - and then nothing.

    Time, I fear, to take the lid off and blow a clean image onto the CF card.


  • Banned

    Uhm… The serial console defaults to 115200 with 2.2.x. In general, I'd suggest to read the changelogs @ the wiki.



  • The documentation eventually led me to the bit about ALIX boards defaulting to 38400 BAUD.
    With my terminal set accordingly, I got a series of boot messages along the lines of:

    FreeBSD/x86 boot
    Default: 0:ad(0,a)/boot/kernel/kernel
    boot: PC Engines ALIX.2 v0.99m
    640 KB Base Memory
    261120 KB Extended Memory

    01F0 Master 044A CF Card
    Phys C/H/S 7745/16/63 Log C/H/S 968/128/63

    1  pfSense
    2  pfSense

    F6 PXE
    Boot:  1
    No /boot/loader

    FreeBSD/x86 boot
    Default: 0:ad(0,a)/boot/kernel/kernel
    boot:
    No /boot/kernel/kernel

    FreeBSD/x86 boot
    Default: 0:ad(0,a)/boot/kernel/kernel
    boot: No /boot/kernel/kernel

    FreeBSD/x86 boot
    Default: 0:ad(0,a)/boot/kernel/kernel
    boot: 2No 2

    FreeBSD/x86 boot
    Default: 0:ad(0,a)2
    boot: No 2

    FreeBSD/x86 boot
    Default: 0:ad(0,a)2
    boot: No 2

    FreeBSD/x86 boot
    Default: 0:ad(0,a)2
    boot: No 2

    Which I loosely translated as "Well and Truly Dead - Give up now!".

    So I flashed a fresh image to the card and started over.
    But that's a whole new story for the Installations and Upgrades section…


Log in to reply