I am ready to push out the updated Distro 4.211.64-7 ISOs but would like to get a few people to test them before I put them on the download site.
You can review the wiki for release notes here.
Below are links for the different versions I need help testing.
Ok I know the 32bit is having a problem. Asterisk is core dumping. 64bit seems to work fine.
I’m on a FreePBX Distro 4.211.64-6 64 bit system and I’m going to update now via /usr/sbin/sysadmin_update_system command (I prefer the CLI despite the SysAdmin Pro module is installed).
I’ll report back ASAP. Hope to not break my system (never happened before).
Here a cat of /var/log/messages take from another shell (the one used to make the update seems stuck and I will wait its release):
Sep 18 17:30:34 freepbx yum[20783]: Updated: asterisk11-core-11.5.1-11_centos6.x86_64
Sep 18 17:30:34 freepbx yum[20783]: Updated: asterisk11-addons-core-11.5.1-11_centos6.x86_64
Sep 18 17:30:34 freepbx yum[20783]: Updated: asterisk11-addons-mysql-11.5.1-11_centos6.x86_64
Sep 18 17:30:34 freepbx yum[20783]: Updated: asterisk11-addons-bluetooth-11.5.1-11_centos6.x86_64
Sep 18 17:30:34 freepbx yum[20783]: Updated: asterisk11-voicemail-11.5.1-11_centos6.x86_64
Sep 18 17:30:34 freepbx yum[20783]: Updated: asterisk11-addons-ooh323-11.5.1-11_centos6.x86_64
Sep 18 17:30:34 freepbx yum[20783]: Updated: asterisk11-doc-11.5.1-11_centos6.x86_64
Sep 18 17:30:35 freepbx yum[20783]: Updated: asterisk11-dahdi-11.5.1-11_centos6.x86_64
Sep 18 17:30:35 freepbx yum[20783]: Updated: asterisk11-11.5.1-11_centos6.x86_64
Sep 18 17:30:35 freepbx yum[20783]: Updated: asterisk11-flite-11.5.1-11.x86_64
Sep 18 17:30:35 freepbx yum[20783]: Updated: asterisk11-addons-11.5.1-11_centos6.x86_64
Sep 18 17:30:35 freepbx yum[20783]: Updated: asterisk11-odbc-11.5.1-11_centos6.x86_64
Sep 18 17:30:35 freepbx yum[20783]: Updated: asterisk11-curl-11.5.1-11_centos6.x86_64
Sep 18 17:30:35 freepbx yum[20783]: Updated: asterisk11-flite-debuginfo-11.5.1-11.x86_64
Sep 18 17:30:36 freepbx kernel: vzaphfc: card 0: chan B1 closed as ZTHFC1/0/1.
Sep 18 17:30:36 freepbx kernel: vzaphfc: card 0: chan B2 closed as ZTHFC1/0/2.
Sep 18 17:30:36 freepbx kernel: vzaphfc: card 0: chan D closed as ZTHFC1/0/3.
Sep 18 17:30:38 freepbx kernel: vzaphfc: card 0: chan B1 opened as ZTHFC1/0/1.
Sep 18 17:30:38 freepbx kernel: vzaphfc: card 0: chan B2 opened as ZTHFC1/0/2.
Sep 18 17:30:38 freepbx kernel: vzaphfc: card 0: chan D opened as ZTHFC1/0/3.
I have to admit that the update command above didn’t release the shell, it’s stuck here:
[root@freepbx tmp]# /usr/sbin/sysadmin_update_system
Array
(
[status] => ok
[data] => Array
(
[4.211.64-7] => Array
(
[url] => http://upgrades.freepbxdistro.org/stable/4.211.64/upgrade-4.211.64-7.sh
[changelog] =>
)
)
)
running http://upgrades.freepbxdistro.org/stable/4.211.64/upgrade-4.211.64-7.sh
mkdir: cannot create directory `/etc/schmooze’: File exists
/bin/grep: /tftpboot/version: No such file or directory
/bin/grep: /tftpboot/version: No such file or directory
Maybe is it normal?
Usually I performed the update with the other method (wget+chmod+exectuting the shell script).
Is it OK?
OK, the shell was released and this is the whole set of messages about the sysadmin_update_system command:
[root@freepbx tmp]# /usr/sbin/sysadmin_update_system
Array
(
[status] => ok
[data] => Array
(
[4.211.64-7] => Array
(
[url] => http://upgrades.freepbxdistro.org/stable/4.211.64/upgrade-4.211.64-7.sh
[changelog] =>
)
)
)
running http://upgrades.freepbxdistro.org/stable/4.211.64/upgrade-4.211.64-7.sh
mkdir: cannot create directory `/etc/schmooze’: File exists
/bin/grep: /tftpboot/version: No such file or directory
/bin/grep: /tftpboot/version: No such file or directory
kmod-dahdi-linux-2.6.1-29_centos6.2.6.32_279.11.1.el6.x86_64.x86_64 was supposed to be removed but is not!
kmod-dahdi-linux-2.7.0-43_centos6.2.6.32_358.0.1.el6.x86_64.x86_64 was supposed to be removed but is not!
Davide.
And this is the cat of /var/log/pbx/upgrade/
[root@freepbx upgrade]# cat 4.211.64-7
Wed Sep 18 17:28:31 CEST 2013 This appears to be a FreePBX Distro system as it has a Distro Version of 4.211.64-6
VARIABLES SET FOR UPGRADE
asterisk=Asterisk 11.4.0 built by root @ jenkins-el6-64.schmoozecom.net on a x86_64 running Linux on 2013-06-02 15:27:41 UTC
kernel=Linux freepbx.shirt.internal 2.6.32-358.0.1.el6.x86_64 #1 SMP Wed Feb 27 06:06:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
version=4.211.64-6
host=freepbx.shirt.internal
upgradeversion=4.211.64-7
virtual=0
Wed Sep 18 17:28:31 CEST 2013 Your FreePBX Distro System is being upgraded to 4.211.64-7. Please standby…
Wed Sep 18 17:28:31 CEST 2013 STAGE 1 STARTING - GUI Modules
Wed Sep 18 17:28:33 CEST 2013 Upgrade All FreePBX GUI Modules
Wed Sep 18 17:28:56 CEST 2013 STAGE 1 COMPLETED - GUI Modules - Moving to Stage 2
Wed Sep 18 17:28:56 CEST 2013 STAGE 2 STARTING - RPM’s
Wed Sep 18 17:28:56 CEST 2013 Replace repos with only FreePBX Distro since some people have added other repos which can break updates
Wed Sep 18 17:28:57 CEST 2013 Update Asterisk RPMs
Wed Sep 18 17:30:36 CEST 2013 Updating all remaining RPMS now to Centos 6.4
Wed Sep 18 17:45:44 CEST 2013 STAGE 2 COMPLETED - Misc Items - Moving to Stage 4
Wed Sep 18 17:45:44 CEST 2013 STAGE 3 STARTING - Misc Items
Wed Sep 18 17:45:44 CEST 2013 Allow overrides in apache for FreePBX
Wed Sep 18 17:45:44 CEST 2013 STAGE 3 COMPLETED - Misc Items - Moving to Stage 4
Wed Sep 18 17:45:44 CEST 2013 STAGE 4 STARTING - Clean Up
Wed Sep 18 17:45:44 CEST 2013 updatedb for locate command
Wed Sep 18 17:45:47 CEST 2013 Restart incron to be safe
Wed Sep 18 17:45:47 CEST 2013 STAGE 4 COMPLETED - Clean Up - Moving to Stage 5
Wed Sep 18 17:45:47 CEST 2013 STAGE 5 STARTING - Final Verifications
Wed Sep 18 17:45:47 CEST 2013 STAGE 5 COMPLETED - Final Verifications - Moving to Stage 6
Wed Sep 18 17:45:47 CEST 2013 UPGRADE 100% COMPLETED
So far no issues.
Asterisk is now 11.5.1.
I just noticed that now /boot is approaching 78% in my installation (first time) and so is marked Yellow (2 kernels other than the running one are retained). Eventually I’ll check how to dismiss the oldest.
That error you got is nothing to worry about. Its just saying since the old kernel is still their its going to keep the DAHDI kmod for it.
Also fixed the 32bit issue. Rolling new RPMS now
Hello Tony, so far so good (next time I’ll back to the classical CLI update’s method: personally I like to see what’s happening real time while the update process is running).
Davide.
Free some space in the very little /boot (<100MB!) by performing a:
package-cleanup --oldkernels --count=2
and modifying (Kernels retention) the /etc/yum.conf parameter:
installonly_limit=2
In my case FreePBX Distro had 3 Kernels.
Now the /boot turned back to be in use for 54% which is a quite safe value (or, at least, it’s now “Green” once again on FreePBX System Statistics).
P.S. yum-utils package needs to be installed first (FreePBX Distro hasn’t it).
We just updated to this version… Now all of our asterisk queue commands are missing. How do we fix this (or how do we roll back to 4.211.64-6)?
Hi, if it’s not working as expected I suggest you to file a proper Ticket request supplying to developers all the logs/evidences/details of what you discovered and let developers go deep.
Is the update log ok?
Have you done a reboot just to be in the right position to start examining Asterisk/FreePBX logs (I mean with new Kernel up and running)?
Their is no roll back option. But what do you mean queue commands dont work. Need alot more info.
I have rebooted fully… Running the latest kernel and asterisk…
We noticed our queues not working this morning when we got into the office.
when a user attempts to log into a queue this warning is thrown:
[2013-09-19 09:15:43] WARNING[28672][C-0000002a]: app_exec.c:268 execif_exec: Could not find application! (AddQueueMember)
and the extension is hung up on.
Connected to Asterisk 11.5.1 currently running on add19 (pid = 5586)
add19CLI> queue show
No such command ‘queue show’ (type ‘core show help queue show’ for other possible commands)
add19CLI> show queue
No such command ‘show queue’ (type ‘core show help show queue’ for other possible commands)
add19CLI>
! acl ael agi aoc cc cdr cel channel cli
confbridge config core dahdi data database devstate dialplan dnsmgr event
fax features file group http iax2 indication keys local logger
manager meetme mfcr2 mgcp minivm mixmonitor module moh no odbc
parkedcalls phoneprov presencestate pri realtime rtcp rtp say sip sla
ss7 stun timing transcoder udptl ulimit voicemail wat
add19CLI>
What log files should I attach?
I will gladly file a proper ticket, since I have never done that before, which logs/files/evidences do you suggest I add? I would imagine that creating the ticket right the first time is key, hence why I started here.
What version of Asterisk are you using?
Asterisk 11.5.1
I believe that was part of the upgrade.
Please open a bug report at http://issues.freepbx.org/browse/FPBXDISTRO and provide commands using and version of asterisk.
Yes its part of the upgrade but you could be using Asterisk 1.8, 10 or 11 as at install time you can pick which is why I needed to know. Anyways open that bug report and we will take a look today.
kernel
Linux add19 2.6.32-358.14.1.el6.x86_64 #1 SMP Tue Jul 16 23:51:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux