TB website error in admin mode after update

All seem to be working,
But when I pull the system status page I get about 3+ mbytes of the error text shown above. My updates were performed the same way, "yum update". I am assuming we still don't have a solution, do we have a hint at the root cause?

Wade B

I am wondering how easy it would be (and how/if risky it would be) to backout the updates to the last known good state. Thanks for the feeback Greg, that is very helpful.

Wade B

and I did basically the same thing as did lleopold19
fwrite(): 69 is not a valid stream resource in /var/www/html/framework/modules/trixbox/libraries/AGI_AsteriskManager.php

However, lleopold19 has fwrite():66 i have fwrite(): 69

Any ideas???

I wonder how hard it would be to add a module that can reverse any updates that break the system. I guess it would have to back up the current settings and configurations before the update and have them available in case the update fails or is buggy. It could be part of trixbox 3.0

I installed from this ISO months ago:
trixbox-2.6.0.7-i386.iso

I updated doing the following:
yum update --exclude=tbm-pbxconfig --exclude=trixbox

as per the example above.

However, I am getting the same errors. I am cursed to have upgraded. I should know better, but keeping boxes patched up, from a security perspective, is typically good policy.

Why the hell isn't there more testing to prevent these sort of things? In any case now I'm going to go ahead and upgrade trixbox and tbm-pbxconfig since that IS NOT the problem.

Hm....

I'm not a php wizard, I much prefer perl, ruby, and python (I hate php actually); however, this is interesting:

Running the commandline php interpreter against the library file yields the following warning:

[sip.nsihosting.net libraries]# php AGI_AsteriskManager.php
PHP Warning: PHP Startup: memcache: Unable to initialize module
Module compiled with module API=20050922, debug=0, thread-safety=0
PHP compiled with module API=20060613, debug=0, thread-safety=0
These options need to match
in Unknown on line 0

The code, near line 150, in AGI_AsteriskManager.php where my errors start (before they loop forever until stopped) is:

function send_request($action, $parameters=array())
{
$req = "Action: $action\r\n";
foreach($parameters as $var=>$val)
$req .= "$var: $val\r\n";
$req .= "\r\n";
fwrite($this->socket, $req);
return $this->wait_response();
}

From the above, fwrite() attempts to write to object 'socket' that and send it $req. However,
I don't believe that 'socket' has been instantiated. It remains NULL and therefore the next function wait_response() ends up looping forever since the variable $allow_timeout=false is set.

The reason that the object socket is not NULL (instantiated) is because the trixbox code required memcached (somewhere in an include, or require, or whatever the hell php uses to include libraries in code) and the module mod_mem_cache.so is compiled with API=20050922 and php is compiled with API=20060613. As per the following log entry in /var/log/httpd/error_log:

---o---
PHP Warning: PHP Startup: memcache: Unable to initialize module
Module compiled with module API=20050922, debug=0, thread-safety=0
PHP compiled with module API=20060613, debug=0, thread-safety=0
These options need to match
in Unknown on line 0
hudlite-server: unrecognized service
hudlite-server: unrecognized service
[Sun Aug 31 00:46:04 2008] [error] [client 10.x.x.37] Sun, 31 Aug 2008 00:46:04 -0400 - Failed to login., referer: http://sip.int/maint/
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 13 0 13 0 0 67 0 --:--:-- --:--:-- --:--:-- 0
---o---

So, what I think needs to happen is that an updated memcache module needs to be installed to match the php version. However, there may be a bunch of other examples like this and other php modules need to be fixed/upgraded as well.

Somebody PLEASE send this upstream to the appropriate Trixbox PHP coders so they can fix this mess in their yum repo. I don't want to have to spend the time compiling modules unless I have to....

Well, after installing hud-lite with:
install-hudlite command

The only thing left in the /var/log/httpd/error_log file now is:

---o---
[Sun Aug 31 02:06:58 2008] [error] [client 10.x.x.37] Sun, 31 Aug 2008 02:06:58 -0400 - Failed to login., referer: http://sip.int/maint/
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 13 0 13 0 0 87 0 --:--:-- --:--:-- --:--:-- 0
--

So, I'm back to square one with no other theories.

I've applied the above workaround to prevent the inevitable browser crash. I also have had this problem strike since yesterday when I used the Packages page to select all available updates and install them. Pain in the backside, but at least Trixbox is still working - it could have been a lot worse.

Hoping Fonality find a solution for this soon!

Should I be installing FreePBX on this system, since at the moment this is 'as it stands' off of the TrixboxCE install disk with the exception of the updates...?

>Well I excluded tbm-pbxconfig and mine is also bust ... so it is Trixbox.

Actually, I don't believe its either. When I first upgraded I excluded both modules and still encountered the bug.

This is definitly a bug. I don't think the variables are setup properly in some of the new updates. I also think this may be an issue with the asmanager password and not the mysql password. Most of us change them in amportal.conf at the same time and I found there are numerous other places that need to be updated for the new updates to work. Here's how I solved it.

grep amp111 -R /etc/*
Change everyfile that has amp111 to what ever you use for ampmanager pass.
grep amp111 -R /var/www/*
Change everyfile that has amp111 to what ever you use for ampmanager pass.
amportal restart

PS:I excluded trixbox and tbm-pbxconfig from the yum updates and still got the error. This happend after I updated all the modules and then changed ampmanager password, asteriskuser mysql password.

bradolive, you got it! I just changed the amp111 to the password I was using, and everything is working now. Thanks a bunch! Hopefully they fix this bug in their next update.

Thanks for the quick response to this one, all, saved me arse again!

The only error that I know of after doing a update from 2.6.1 to 2.6.1.10 is php-pecl-memcache on the Centos updates is reported as a newer version. The version numbers actually match to the custom version we compiled for this build. So this updates this rpm and will throw errors when httpd is restarted. Simple remove php-pecl-memcache

rpm -e --nodeps php-pecl-memcache

Then install the version from our repo.

yum install php-pecl-memcache --disablerepo=updates --disablerepo=base --disablerepo=extras

If you look in /var/log/httpd/error_log you might see.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
^M 0 12 0 12 0 0 28 0 --:--:-- --:--:-- --:--:-- 28^M 0
12 0 12 0 0 28 0 --:--:-- --:--:-- --:--:-- 0

Which is nothing to worry about.

Thank you,
Engineer Tim

No, I have never changed the default passwords during my upgrade/install tests.

Thank you,
Engineer Tim

Tim,
Wouldn't it make sense to change passwords when testing?
I know alot of us change the default passwords for security purposes (And it's annoying to see the message on the pbxsettings page) Just a thought.....

Any word on these packages being fixed yet in the repos? Kerry?

that sounds like a great idea cstar707!

Thanks for the post I had the same issue and thanks to you I fixed it, but also I had a db error connect when I tried hitting the pbx settings. to fix it all I did was to Log into phpMyAdmin, and select Privileges from the main page. From there, select the user you want to edit, and click the edit icon next to their name.

asteriskuser where it says password put your actual password used. and hit go. for more information look at this page.

http://www.freepbx.org/support/documentation/faq/changing-the-mys...

rrichiez

If you are using mysql authentication you have to comment out these lines in /etc/trixbox/httpdconf/trixbox.conf

#commented out because using mysql auth MJM
#
#AuthType Basic
#AuthName "Restricted Area"
#AuthUserFile /usr/local/apache/passwd/wwwpasswd
#Require user wwwadmin maint
#

Your fixed worked for me!! I changed all the files to the updated password that we use and everything is back to normal. Had to reset mysql password to our password as well.

Thank you!

Paul
AndersonPC.com
FtOCC Admin

This fixed the status page,
My operator panel still will not show any queue or call detail and flashes green/red with a page reload every few seconds. Is this related or something else entirely? Thanks.

Wade Blackwell

Do not change the passwords in /var/www/html/admin/functions.inc.php. These are the variables System Satus uses to see if you are using the default passwords. If you make them the same as your ampmanager password and asteriskuser password you will get the notice that you are using the default passwords on the pbx settings main page. If you changed them chnage them back to amp111 and amp109. On the other hand if you insist on using default passwords you can get rid of the notices by changing the passwords in /var/www/html/admin/functions.inc.php to something besides amp111 and amp109

Did you change any passwords besides amp109 and amp111 anywhere?

Hey Guys,

Ok I just hit this problem as well following my standard procedure for changing passwords on a new 2.6.1 server after yum updates I was installing. Backed the password changes back to the defaults and problem was gone. Now this got me pondering....

What is the difference between the amp109 password and the amp111 password??

I usually change the default password of the mysql user "asteriskuser" which is amp109 and then go and change the following based on old instructions I found on this forum a while ago:

* The ARI_ADMIN_PASSWORD in /var/www/html/recordings/includes/main.conf.php
* /etc/amportal.conf - changing AMPMGRPASS & AMPDBPASS
* /etc/asterisk/cdr_mysql.conf - changing PASSWORD
* /etc/asterisk/manager.conf - changing SECRET

Now the defaults on all those changes are a mix of amp109, amp111 and ari_password. Now considering I only changed the asteriskuser password which was amp109 how do those other ones work in the default configuration? Up until today I have never had a problem changing passwords by following my method, but it is a little confusing.....

Any help in explaining the different passwords would be great!!

Thanks,
Luke.

Have you even read the whole forum? The "fix" was posted about 12 posts up

Just my 2 cents and how I fixed this issue on a system that is PRE 2.6.2.10

Someone correct me on this, but on a system that is 2.6.1 the directory /var/www/html/framework/modules/trixbox... doesn't exist. I'm assuming that, as I have both a 2.6.1 server and a 2.6.1.10 server, when you upgrade it adds these directories and adds these files to the .../trixbox/libraries directories:

AGI_AsteriskManager.php
Notifications.php
TrixpbxDevice.php
TrixpbxExtension.php
Trixpbx.php
TrixpbxUser.php
Trix.php

In order to resolve the issue for the endpoint_cisco.php connect error: "Warning: fopen(/tftpboot/*.cnf.xml) [function.fopen]: failed to open stream: No such file or directory in /var/www/html/maint/modules/endpointcfg/endpoint_cisco.php on line 165"

On the 2.6.1 system, I edited the file: /var/www/html/maint/modules/home/includes/asteriskInfo_functions.php using VI and added these lines as they didn't exist:

Locate:
function buildAsteriskInfo(){
global $XPath;
global $text;

Then add:
include "/var/www/html/framework/modules/trixbox/libraries/AGI_AsteriskManager.php";

$ami = new AGI_AsteriskManager();
$ami->connect("127.0.0.1:5038", 'admin' , 'insert_your_password_here');

On the 2.6.1 system, I had to add the /var/www/html/framework/modules/trixbox/libraries/ directory and then copy the AGI_AsteriskManager.php over from my 2.6.1.10 server.

Now both the front System Status page works as well as the Endpoint manager for Cisco phones.

To conclude, it's very important to distinguish what version of Trixbox you're running as 2.6.1 does not apparently have the same file structure as 2.6.1.10

I hope this helps.

I changed the "amp111" in the asteriskInfo_functions.php file (line 164) and everything started to work fine, at "System status" page.

Great job ;)

I’ve been through the forum and reset the password ever and reset file permissions after I did all that it still wasn’t working.
I edited /etc/asterisk/manager.conf and changed the bindaddr, it was set to the IP address of the server after changing it back to 0.0.0.0 it was working/

:)

Hello all,
you can imagine I'v read all of this thread before posting.
I'm also a vistim of these bugs.
I did all of the password changes back in order for every thing to work.
I can't seem to get the "PBX Settings" to work.
I'v done almost anything I can think of.

can anyone help with this ?

Zion.