Hi,
All was working fine before I have upgraded from php 5.1.6 to php 5.2.11 because one of my application required php 5.2 or greater. Now when i login as admin to freepbx webgui(http://serverIP/admin/config.php) it is showing the blank page, No error messages. If i access FOP or ARI they are working fine. Below is my server info and httpd error logs. Please help
Server Info
AsteriskNOW-1.7.1-i386
which comes with Centos 5.5, Asterisk 1.6 and freepbx 2.7.0(I have upgraded it to 2.8.0)
Httpd error_logs
[Sun Oct 03 04:02:26 2010] [notice] Digest: generating secret for digest authentication …
[Sun Oct 03 04:02:26 2010] [notice] Digest: done
[Sun Oct 03 04:02:26 2010] [notice] Apache/2.2.3 (CentOS) configured – resuming normal operations
[Sun Oct 03 13:04:19 2010] [error] [client 77.132.193.92] File does not exist: /var/www/html/favicon.ico
[Sun Oct 03 13:04:38 2010] [error] [client 77.132.193.92] PHP Warning: dl() [function.dl]: Temporary module name should contain only filename in /var/www/html/admin/modules/digiumaddoninstaller/libdregister/digium_register.php on line 72, referer: http://serverIP/
rm -rf /var/www/html/admin/modules/digiumaddoninstaller
mysql -u<MYSQL USER NAME> -Dasterisk -p<MYSQL PASSWORD> -e"delete from modules where modulename = 'digiumaddoninstaller'"
Thanks Moshe,
I ran this command and get the following output. Still not able to see Freepbx administration webgui. Am i missing something here.
[root@abc ~]#amportal a ma disable digiumaddoninstaller
output:
PHP Warning: dl(): Temporary module name should contain only filename in /var/www/html/admin/modules/digiumaddoninstaller/libdregister/digium_register.php on line 72
try this on the command line: amportal a ma disable digiumaddoninstaller. This will disable Digium’s add-on installer module, which seems to be the culprit here.
Your welcome! Hard to tell what it’ll affect with Digium’s stuff, you would need to ask them that (probably nothing!), but it should have no bearing on FreePBX. Good to know that FreePBX work with php 5.2! (not that there is any reason that it shouldn’t). You may also want to report the issue to Digium.