Hi All,
I have had trouble with upgrading to the latest Stable Asterisk, and I am now running an unhappy linux box and would appreciate help!
When I commenced the process, I was running Centos 64 Release 5.7 (Final) and Asterisk 1.8.9.3, and FreePBX 2.10.1.1
My CentOS machine was built via the distro downloaded from FreePBX.
My kernel version was: 2.6.18-274.3.1.el5
My issue was that I was affected by an asterisk bug in 1.8.9.3, resolved in 1.8.14 where a *2 transferred call would be dropped if the callee refused the call and hung up (when the call should have returned to the initial party who attempted the transfer).
So, in order to update, I followed the instructions and used the scripts here:
I ran them, one at a time in order, from 1.889.210.57-2.
(I even ran them, first, in a test machine I had. It all went fine on the test machine. It did NOT go fine on the production machine!)
The problem arose during the upgrade in 1.812.210.58-1.sh This script, among other things, updates the underlying system from CentOS release 5.7 to Centos release 5.8 and upgrades the kernel to
2.6.18-308.4.1.el5-x86_64
This is where it all started to go wrong. The script downloaded 260M of updates, and finished without indicating an error, however it did not call for a reboot (as happened on my test machine when I ran the same script)
I rebooted anyway, and checked my Linux version, and was still at 5.7.
I tried an update manually:
Yum clean all
Yum update glibc* yum* rpm* python*
(this worked)
Yum update
I downloaded 260M of updates, and then had a dependency failure.
I then upgraded just the kernel
Yum update kernel-devel
This appeared to succeed, however when I rebooted using 2.6.18-308.4.1.el5 kernel, my system has no modules loading – no internet connection, no WanRouter, certainly no asterisk!
I have checked, and I have :
/usr/src/kernels/2.6.18-308.4.1.el5-x86_64/
I have
/lib/modules/2.6.18-274.3.1.el5/
But I DO NOT HAVE
/lib/modules/2.6.18-308.4.1.el5/
The new kernel is present and tries to load on boot:
Jul 29 13:49:44 PABX kernel: Linux version 2.6.18-308.4.1.el5 ([email protected]) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)) #1 SMP Tue Apr 17 17:08:00 EDT 2012
However, this is an error appearing on startup:
Jul 29 04:48:01 PABX modprobe: FATAL: Could not load /lib/modules/2.6.18-308.4.1.el5/modules.dep: No such file or directory
I think that the underlying problem may be to do with dahdi and modules for my Sangoma A101 WanRouter card. (This card was not present in my test system, which successfully upgraded).
I am using the Wanpipe release 3.5.27 which is the latest stable release.
This appears in the logs from the attempted upgrade:
Jul 28 11:43:19 PABX kernel:
Jul 28 11:43:19 PABX kernel: wanpipe: WANPIPE Modules Unloaded.
Jul 28 11:43:19 PABX kernel: usbcore: deregistering driver sdlausb
Jul 28 11:43:19 PABX kernel: usbcore: deregistering driver xpp_usb
Jul 28 11:43:19 PABX kernel: dahdi: Telephony Interface Unloaded
Jul 28 11:43:45 PABX yum: Installed: kmod-dahdi-linux-2.6.0-2_centos5.2.6.18_274.3.1.el5.x86_64
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid KERNEL operation
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid rule '/etc/udev/rules.d/50-udev.rules:1’
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid KERNEL operation
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid rule '/etc/udev/rules.d/50-udev.rules:1’
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid KERNEL operation
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid rule '/etc/udev/rules.d/50-udev.rules:1’
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid KERNEL operation
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid rule '/etc/udev/rules.d/50-udev.rules:1’
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid KERNEL operation
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid rule '/etc/udev/rules.d/50-udev.rules:1’
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid KERNEL operation
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid rule '/etc/udev/rules.d/50-udev.rules:1’
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid KERNEL operation
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid rule '/etc/udev/rules.d/50-udev.rules:1’
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid KERNEL operation
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid rule '/etc/udev/rules.d/50-udev.rules:1’
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid KERNEL operation
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid rule '/etc/udev/rules.d/50-udev.rules:1’
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid KERNEL operation
Jul 28 11:43:53 PABX udevd[606]: add_to_rules: invalid rule ‘/etc/udev/rules.d/50-udev.rules:1’
The only way I can get my system to function correctly is to use the GRUB menu to boot into my earlier kernel - 2.6.18-274.3.1.el5.
Using this kernel, I get full system functions, however on reboot it attempts to load the new kernel, which fails.
I am not sure how to proceed from here?
My present system status:
CentOS release 5.7 (Final)
LSB Version: :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch
uname -r
2.6.18-274.3.1.el5
Any help would be appreciated.