I have been attempting to upgrade from 2.11 to 12.x and am stumped with this error. I was able to access the 12.x module admin and download/update the modules. However, I now get this error:
Thanks. I blew away all the existing stuff from my /usr/local/apache24/data/freepbx directory and started over. I am doing this on FreeBSD BTW, 10.1. However, I am now running into a problem with freepbx_engine during the install or when I attempt to fix stuff with amportal. I see:
PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/20121212-zts/http.so’ - Cannot open “/usr/local/lib/php/20121212-zts/http.so” in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/20121212-zts/memcache.so’ - Cannot open “/usr/local/lib/php/20121212-zts/memcache.so” in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/20121212-zts/soap.so’ - /usr/local/lib/php/20121212-zts/soap.so: Undefined symbol “ps_globals_id” in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/20121212-zts/wddx.so’ - /usr/local/lib/php/20121212-zts/wddx.so: Undefined symbol “ps_globals_id” in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/20121212-zts/memcached.so’ - /usr/local/lib/php/20121212-zts/memcached.so: Undefined symbol “ps_globals_id” in Unknown on line 0
/usr/local/asterisk/bin/freepbx_engine: line 98: Warning:: command not found
**** WARNING: ERROR IN CONFIGURATION ****
astrundir in ‘/etc/asterisk’ is set to but the directory
does not exists. Attempting to create it with: 'mkdir -p ’
usage: mkdir [-pv] [-m mode] directory_name …
**** ERROR: COULD NOT CREATE ****
Attempt to execute 'mkdir -p ’ failed with an exit code of 64
You must create this directory and the try again.
That line is:
$gen_path/gen_amp_conf.php
And the whole thing dies even though I can run that script (which really lives at /usr/local/asterisk/bin/gen_amp_conf.php):
Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/20121212-zts/http.so’ - Cannot open “/usr/local/lib/php/20121212-zts/http.so” in Unknown on line 0
Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/20121212-zts/memcache.so’ - Cannot open “/usr/local/lib/php/20121212-zts/memcache.so” in Unknown on line 0
Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/20121212-zts/soap.so’ - /usr/local/lib/php/20121212-zts/soap.so: Undefined symbol “ps_globals_id” in Unknown on line 0
Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/20121212-zts/wddx.so’ - /usr/local/lib/php/20121212-zts/wddx.so: Undefined symbol “ps_globals_id” in Unknown on line 0
Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/20121212-zts/memcached.so’ - /usr/local/lib/php/20121212-zts/memcached.so: Undefined symbol “ps_globals_id” in Unknown on line 0
export AS_DISPLAY_FRIENDLY_NAME=1
export AS_DISPLAY_HIDDEN_SETTINGS=0
export AS_DISPLAY_READONLY_SETTINGS=1
export AS_OVERRIDE_READONLY=1
export HTTPENABLESTATIC=1
export HTTPENABLED=1
…
…
…
That script expects parameters to be EXPORTED to bash so that it can read them. If there is any garbage out it won’t work. You’ve got a ton of garbage from your system (completely un freepbx related) that you should fix. I am really baffled that PHP Startup messages have not even grabbed your attention, they are really really bad.
OK, I have FreePBX 12.x up and running (sort of) on FreeBSD 10.1 with asterisk 1.8.x. What I have done so far is…
portupgrade -r -f php55
Which completely rebuilds all php55 modules recursively. Then clean out all the stuff under /usr/local/www/apache24/data/freepbx and then run install_amp. After that I struggled through sprintf_ errors in the GPG scripts by cli upgrading framework and core. I had to upgrade all the “broken” modules using the cli since the module admin gui is a complete fail. Now, most of the gui functions except for the apply config button which fails because of errors like these:
PHP Strict Standards: Non-static method DB::isManip() should not be called statically, assuming $this from incompatible context in /usr/local/share/pear/DB/common.php on line 2200
PHP Strict Standards: Non-static method DB::isError() should not be called statically in /usr/local/www/apache24/data/freepbx/admin/libraries/sql.functions.php on line 24
PHP Strict Standards: Non-static method DB::isManip() should not be called statically, assuming $this from incompatible context in /usr/local/share/pear/DB/common.php on line 2200
PHP Strict Standards: Non-static method DB::isError() should not be called statically in /usr/local/www/apache24/data/freepbx/admin/libraries/sql.functions.php on line 24
I assume there should be coding changes to depricate reliance on DB in php at some point? In any event - I can manually from retreive_conf from the cli and it updates the conf files. So, it’s limping along.
Something else I had to do is symlink /usr/local/bin/gpg to /usr/bin/gpg to get updates to work…
Those are not errors. They won’t prevent apply changes. There’s more you aren’t showing us. Would be nice to know the sprintf errors as well instead of being left in the dark
The sprintf errors are the ones documented in the bug forums. I am going to guess that it is a known thing. Other than that, I had to manually update everything to get things working. The retrieve_conf error I get is “error = 20” in case you are wondering. Other than that - you are missing nothing. Perhaps a new tarball download is in order. 12.0.3 does not work. Period. Not out of the box anyway…
Ian
P.S If there is better documented error reporting info I will happily report my woes…
Oh right 12.0.3 is very old. We are at 23 now. Most people just checkout from our source these days. I will update the tarball links. No need to report bugs on things that were already fixed.
FreeBSD is not supported. But I guess you know that.
So, in the end I would consider this “solved” as it turned out that I removed wget some time ago on the server (I forget exactly why). A simple reinstall of wget and all seems well. So far…
