Lots of updates coming today

Ohhh....Ahhhh!

All available through yum update or package manager?

The PBX Config updates are already available, just go into the PBX Config and go to module admin. Other updates will be yum/package manager later, and the new ISO will be ready to test out soon as well.

ISO 2.6.1.9 (Dev) is now available and is working around the sourceforge mirrors. Note the much reduced images size!! The link on the download page should work fine.
-Kerry

with the now reduced package size, maybe more NIC drivers can be added for more compatibility.

Thats an issue of the kernel and we are looking at moving to CentOS 5.2 to add more hardware support.

We've tried "yum update" and we can't see the new packages, are they in trixboxbeta or some other repo which is disabled by default?

Is there anything in this update that could potentially break anything?
I think I've just about finished setting 2.6.1 up to replace our current 2.3.x system and it'd be easier for me if I knew of anything that *might* break before I did it.
Thanks

Just picked a random module to update from pbx module manager and got this error

Please wait while module actions are performed
Downloading daynight 0 of 10485 (0%)Error(s) downloading daynight:

    * Error opening http://update.trixbox.org/modules/release/2.4/daynight-2.4.0.3.tgz for reading


Return

I've tried 3 times with 3 different modules.
My internet is working fine etc, etc.

Is it just me or are others having problems?

edit:I manually downloaded each module to update, then uploaded them and it worked fine. Quite irritating that I had to download and upload 14 separate things though. (I'm not even thinking about enabling the new ones yet.)

Also when I try yum update I get 3 items. 'Y' gets me:

Trying other mirror.
http://mirrors.nl.kernel.org/centos/5.2/updates/i386/RPMS/libxml2-2.6.26-2.1.2.4.i386.rpm: [Errno 14] HTTP Error 403: Forbidden: header 'Content-Type' value denied

:repeated multiple times (diff url obv) but same error.

I see only Asterisk CLI as an update.

We ran out of time last night. We got the new PBX Config modules pushed and the first test of the new ISO. Today will be some additional things such as Asterisk 1.4.21-2.

Hi Kerry

I Just make a new installation from the ISO 2.6.1 and there is no more Backup & Restore module (module admin). I installed ALL the modules and does a ''Check for module update'' many times and nothing...

Now how should I do for Restore the data of my 2.4 Server?

trixbox-2.6.1.1, *-1.14.20, zaptel-1.4.10.1-2, Digium-TDM04B, Aastra & Polycom phones

hi there big brother kerry, why did you delete my critics and feedback of your new broke upgrade?
i said clearly and with no disrispect at all in my post .....the "quality work" and upgrades broke my entire test system that was functioning well since 2.6.1 in june
Thanx again for freedom of speech, My company and all my affiliates wiill not use trix or any derivative work anymore and we will stop any new instalations and sales of trixbox pro with our ftocc partner Net sec solutions from colombia.
All my friends forums and blogs will be forwarded with this notice....
voipnovatos.es sinologic.net asteriskcolombia.com and many more...thanx again
Ing. Fernando M. Villares Terán
Intelix Communications

Fernando,

I wish Kerry wouldn't have deleted your comments either because your scenario was a perfect example of what not to do. As you know, Fonality forked FreePBX and created their own, but you decided to install the 2.5 beta on your production server anyway. Then your run of weekly yum updates messed up the interface, and of course now you are mad. First off, you installed beta non supported software on working server. Do you not have a test server, virtual machine, etc? Why do you run yum updates once a week on server that is working fine? Also, you don't test the updates on a test server before applying them? Lastly, where are you backups? Do you not make any backups before installing updates or upgrading the server? I think you should feel largely responsible for this failure instead of blaming Kerry or Fonality for this blunder. For what its worth, I logged into a client's server this morning (not during business hours), made a full Acronis image backup, then ran the freepbx (or whatever they call it now) updates followed by the yum updates, rebooted everything works without a problem. If there were blog or forum of admins that did not do their job well, you would be on it. I sincerely mean "no disrespect", just hope that you learn from your mistakes.

-Eddie

I thought the same thing yesterday when I read "my weekly yum ugrade"... WHAT??
I upgrade 2 or 3 times a year and I though I was pushing it!

of tbm-pbxconfig, or if you have installed the 2.5 Release Candidate (as I have) then you can still get all the upgrades, and they all seem to work fine (at least so far - we use our office machine as a test bed to really stress updates, and so far so good!) do the following:

(from the cli:)

yum update --exclude=tbm-pbxconfig --exclude=trixbox

tbm-pbxconfig is the forked FreePBX, and trixbox is a dependency on it - like I said I have applied all updates (except these) and am running 2.5 RC2.2 and it is working great, and yum update with these exclusions says I have all available updates.

Greg

I have to agree, weekly updates? Why? This is really one place where the saying "if it ain't broke, don't fix it" really applies. Not to mention the administration to just look after updates like that......wow.

My comments were also deleted! I have trixbox running at home and is very critical to me. I do not have the luxury of having a test environment either. The reason I ran yum update was for security related updates. The point is that the update broke lot of things which it should not! What I do not understand is that instead of accepting the fault you are putting the blame on the person running yum update. Fernando, I (I am sure many others like us) trusted the owners of the product/process to do a good job at what is called testing and Q/A before putting it out!

I sure learned a lesson and hope many others did too ..... :-)

Weekly or even DAILY updates on our test-bed machines is our standard - we are constantly pounding on our test-bed machines (our office system, a test platform, and a VM image) so we know what the updates do and if they break anything - either immediately, or over time. Most nights I check for updates out of habit - and unless I have a specific reason not to, I apply them to the test machines.

Customer machines on the other hand are left alone except for three conditions:

1) We are onsite or remote to do planned maintenance of some type or
2) We are having a problem that an update specifically fixes or
3) Corporate policy stipulates that security and bug fixes have to be applied (we have 5 customers like this now)

Because we have already rolled out any update or patch that we would apply to a customer machine on our own equipment and have it in production, we are never suprised by a patch or update.

Way too many people have only their production box, and they are constantly experimenting on it, sometimes with very unhappy results - this is just bad practice, and is NOT best practice by any measure.

However, not applying patches and updates, especially when they are security related is not only a disservice to your customers, it is a disservice to the whole world because you are (possibly) allowing your computers to become part of a bot-net, either for spam, malware, or worse - these machines don't operate in isolation - anything that's on the 'Net has the potential to start being a menace to everyone else.

Server creation and maintenance is not a one-time task - putting a trixbox (or any other Asterisk-Based distro) into production is an ongoing commitment - ALL servers have bugs, ALL servers need updates and ALL servers need maintenance - if you are not up to the challenge, you should consider a old-style Digital infrastructure for your phones - that equipment does not require near as much upkeep.

Greg

Hi folks again and thanx for not to delete my "flame", im no troll but im really concerned about security in xnix environment,
1st of all my broke server is a test bed wich i use in real production in my house with a sip e1 like line , 2nd of all i do not install freepbx 2.5...simple yum upgrade....and that yum upgrade broke ALL!!!!!!!!!!!!!!!!!!!!!!!! and of course yeah i will upgrade all the standard packages all the times that i want to do........quality and standard software do no break with a gcc upgrade or open ssh, zaptel drivers yes will be broke with a kernel upgrade but for that reason you put exclude=kernel*...so before speak please ask!!!!!!!
If a near 1 million downlaoded times product not open but free, with excluded beta files repository simple making a 1 line upgrade breaks all simply has 1 result
FAIL, fail to achieve consistency, fail to achieve quality and the fail of the Q/A team
In my company a mistake of this magnitude that can potencially break thousands of systems would end in one phrase "someone wil be fired today".
I use and worship some of trixbox facilities in my dcap certifications all over lat am, but with this type of actions by owners of the blog i will not use it again probably
Best regards
Ing. Fernando M. Villares Terán
Intelix Communications

I say that if you don't have a test box don't even try the beta releases until they become part of the stable packages. That's why they are beta. There is no need to break a working system just because you want to try some "nice and new" features which might have some bugs anyways. Just wait until they are fully stable.
I would also wait longer to get new updates and make sure they are bullet proof before updating any of my systems.
Just some thoughts.

Getting metadata mismatch errors when ref the repository, not even getting index!

Hey there again some of the responses to my first critics and feedback for this "destroyer" upgrade of fonality makes me wonder if some pleople knows how to read....
i ve been reading some comments like: you dont have to upgrade if it is a beta....
THIS upgrade that brokes everything... IT WAS NOT PUBLISHED AS A BETA....it was published via trixbox stable repository so it was a meyor FLAW of the Q/A team by the developers of trixbox packages, not a mistake made by me or other folks that execute yum upgrade as a regular basis....
Please people be objective...this is the 4th of 5th major mistake made this year, along with the registry.pl "trojan", the IMHO not necessary freepbx fork, the supppoded flame made in other forums by a second again supposed Mr. Garrison identity, the permanent censorship of totally objetive and real critics by admins, etc, etc....
One final thought, if you want to receive less critics, listen to the good and bad news equally, you dont have to censor any messages except the ones that disrispect some rules of nettiquette and you have to WRITE q/a PROCESSES that evidently dont have or are useless in CE version.
Best regards to all
Ing. Fernando M. Villares Terán
Intelix Communications

Hi All,
I was about to send a similar email (Ing. Fernando M. Villares Terán) that these upgrades are in stable repository and not in development or beta! Now that many of us have a broken system I am wondering how long will it take to come up with the fix.

Two days and counting ......

Cheers!

Sohail.

Well, this pretty much borked my test system. Here's what I see off of the top of my head:

1. Hamachi fails to start:
[asterisk.jason.linux httpd]# hamachi start
31 20:39:33.223 [ 0] [12386] tap: connect() failed 2 (No such file or directory)

2. New system status page is wrong:

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

These are definitely in the production repository.
[yum.repos.d]# cat trixboxdevel.repo
[trixboxdev]
name=trixbox development area - not meant for production
baseurl=http://yum.trixbox.org/centos/$releasever/devel/RPMS/
gpgcheck=0
enabled=0
[yum.repos.d]# cat trixboxbeta.repo
[trixboxbeta]
name=trixbox BETA RPM Repository for CentOS and RHEL
baseurl=http://yum.trixbox.org/centos/$releasever/beta/RPMS/
gpgcheck=0
enabled=0

HI again, what happens that anybody has left the building???
No news, no patches, no responses....not even an apology to all the testers that crash their systems...whta is happeing here? Need some help, contact me in private if you need some...
I´m an ITIL/CISA certified engineer and ISO 9001:2000 auditor
Ing. Fernando M. Villares Terán
Intelix Communications

Sorry, I have no idea that any comments where deleted. I have not been here deleting anything unless I email the person and tell them why I delete something. Usually because of a end user agreement violation.

The best place to post problems is in the bug tracker, that is reviewed every single day by the entire development team, we do not read through pages of comments or forum posts to find where problems are. I have done numerous upgrades this week with no problem and there are none reported in the bug tracker.

Slow down and be kind. Even though there were technical issues, please keep in mind that some of the version are still beta.

The pace of life in modern society is too quick that pressure of life, over time, can affect our emotion frequently. We need to examine from within first before we blame the outside world.

trixbox is an open source community driven project. Everybody uses the project for free and helps out the community. If you have a problem with trixbox writing a forum post or comment about how much you hate free software and it's developers/comminty will not help you. Please post a DETAILED bug report so the community can help you with your problem.

hate free software???? yeap right from fonality LOL...
please, accept some critics in the good way, this incident was a mejor flaw, so use Q/A and do a better job period
Ing. Fernando M. Villares Terán
Intelix Communications

well the error has been detected and corrected, i will explain it briefly
1st one error on memcached module compile that not matched php version
2nd. another attempt to remove customization capabilities (password changes)...if you have change admin passwords or asterisk db passwords of the system, the entire system breaks apart. That´s because instead of a single variable repository like amportal.conf in free pbx, the genius here uses 7 different config files loaded with all the passwords on it instead of hashes or secure passing of variables....
look in the forums and the answer is there...
thanx again to make this kind "free software" like you said... more insecure and buggy every day...
And of course i hope that some of your new capital injection of this "weak", oh sorry, week, goes to ce instead of trix pro that is as expensive as some nortel solutions that i IMHO prefer....
oh, yeah I remember i´m the free and open source hater not you...
Best regards
Ing. Fernando M. Villares Terán
Intelix Communications

I noticed that update.trixbox.org only has one line of code? I tried updating but this is the error I got:

Warning: Cannot connect to online repository (update.trixbox.org). Online modules are not available.

Fernando

Please provide a way for me to contact you. I would like to speak to you about our system.

Rick

I did a clean install of 2.6 and changed the PW's per this link. http://sureteq.com/asterisk/trixbox_CE_v2.6_security.htm and this link http://www.trixbox.org/forums/trixbox-forums/help/unable-access-g... I then installed the modules and all was fine. I then did a yum update and here is what I get when I log in to the GUI.

Warning: fwrite(): 65 is not a valid stream resource in /var/www/html/framework/modules/trixbox/libraries/AGI_AsteriskManager.php on line 150

Warning: feof(): 65 is not a valid stream resource in /var/www/html/framework/modules/trixbox/libraries/AGI_AsteriskManager.php on line 171

Warning: fgets(): 65 is not a valid stream resource in /var/www/html/framework/modules/trixbox/libraries/AGI_AsteriskManager.php on line 173

Warning: feof(): 65 is not a valid stream resource in /var/www/html/framework/modules/trixbox/libraries/AGI_AsteriskManager.php on line 171

Warning: fgets(): 65 is not a valid stream resource in /var/www/html/framework/modules/trixbox/libraries/AGI_AsteriskManager.php on line 173

Warning: feof(): 65 is not a valid stream resource in /var/www/html/framework/modules/trixbox/libraries/AGI_AsteriskManager.php on line 171

What is causing this and how to I correct it? It seems that an update should not make these type of changes.

Any help would be very much appreciated.

Rick
rick@pivical.com
Pivical Communications
www.pivical.com

I went back through and reset PW's The catch is when I try to reset mysqladmin asterisk user.
mysqladmin -u asteriskuser -p password new_password_here.
I get this. Can't turn off logging; error: 'Access denied; you need SUPER privilege for this operation' What is the SUPER privilege? I am SSHed in as root. This is the only PW it will not let me change since I ran the yum update. Seems fishy to me. I did change all of the PW's before running the update. Am I to leave the default mysql and asterisk PW alone and have a security issue? I don't get it.

I just read this issues, and I'm just start comming in panic, I don't know what are you doing guys, but (Fernanado) I have 3 Trixbox boxes, in production, when update the FreePBX 2.5 beta version, also updated yum, so I am running the 3 server without problem, it is somethig else what are you are doing. My 3 server updated wel at any time, unitl today 9/14/08
Kerry, are your sure you updater it is safe?
SIPTELLNET
VOIP Provider

I just finish updated my 3 servers FreePBX, after that I just ran yum -y update, my 3 servers are up and running well, I have nothing to say, but my 3 servers are 2.6.1 ver,, freepbx 2.5 with 100 users, DELL servers, chipset Intel etc, and are in production all the time.
Let me know any hide trick to break this server. I have proven many IP-PBX with 15 years of experience
Kerry. please tell us if everything is going well, so we will don't run to another IP-PBX, like 3cx, or Asterisk now.
I have my 3 boxes integrated with Cisco CM 4.3, and everything is smooth

SIPTELLNET
VOIP PROVIDER

I even reloaded and changed the PW's as follows as well as leaving the passwords alne and doing the yum update. Either way it messes up the GUI as you will see once you log in. There are many posts about this issue but none that explain how to fix or avoid it and still update?

Change default passwords:
Let's change our passwords. We need to do this at the Linux CLI.
Update maint password by typing ‘passwd-maint’ at the command line. Enter the password twice.
Update Web meetme password by typing 'passwd-meetme' at the command line. Enter the password twice.
FreePBX admin pass:
To change the FreePBX manager pass, you need to edit two separate files and put in the new password.
nano /etc/asterisk/manager.conf
Find 'secret = amp11' under the [admin] section. Change 'amp11' to your new desired password. CTRL+X followed by 'Y' to save and exit.
Now, we need to edit the /etc/amportal.conf to use our new password.
nano /etc/amportal.conf
Find the line that says 'AMPMGRPASS=amp11' and change the 'amp11' to the new password you just set. CTRL+X followed by 'Y' to save and exit.
amportal restart
*** NOTE: I have found out the hard way that FreePBX does not like having an exclamation point (!) in the admin password. There may be other special characters that it doesn't like also.
MySQL passwords:
Update the MySQL asteriskuser password by doing the following at the Linux CLI:
mysqladmin -u asteriskuser -p password new_password_here
Replacing 'new_password_here' with your desired password. When you hit 'Enter' you'll be prompted for a password...enter in the default password of 'amp109.'
Now, we need to edit the /etc/amportal.conf to use our new password.
nano /etc/amportal.conf
ind the line that says 'AMPDBPASS=amp109' and change the 'amp109' to the new password you just set. CTRL+X followed by 'Y' to save and exit.
***NOTE: In the amportal.conf, there are TWO places to change the amp109 password...near the top of the file, and at the very end. The one at the top is commented out, so changing that one doesn't really do anything...but to be consistent, make sure you change the password in both places.
You will also need to update the password in the /etc/asterisk/cdr_mysql.conf file for call detail records (cdr).
nano /etc/asterisk/cdr_mysql.conf
Find the line that says 'password=amp109' and change the 'amp109' to the new password you just set. CTRL+X followed by 'Y' to save and exit.
service mysqld restart
amportal restart
*** NOTE: I have found out the hard way that FreePBX/MySQL does not like having an exclamation point (!) in the password. There may be other special characters that it doesn't like also. It is also a good idea to change the default mysql root user password. To change the default mysql root password, do the following:
mysqladmin -u root -p password new_password_here
Replacing 'new_password_here' with your desired password. When you hit 'Enter' you'll be prompted for a password...enter in the default mysql root user password of 'passw0rd' (with a zero)
You will also need to update the password in the /etc/asterisk/cbmysql.conf file for meetme settings.
nano /etc/asterisk/cbmysql.conf
Find the line that says 'password=passw0rd' and change the 'passw0rd' to the new password you just set. CTRL+X followed by 'Y' to save and exit.
service mysqld restart
amportal restart
nano /var/www/html/include/ccsframework/Common.php
amportal restart

Thank you pivicalrick for the very detailed step by step guide to changing these passwords! :-)