Topic: asterisk after a yum update

[marcelb]

Hello all,

After a (yum update) statement asterisk won’t start anymore.


/etc/init.d/asterisk start


WARNING: /etc/modprobe.conf line 48: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 49: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 50: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 51: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 52: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 53: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 54: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 55: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 56: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 57: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 58: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 59: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 60: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 61: ignoring bad line starting with 'post-install'
FATAL: Module zaptel not found.
Waiting for udev.
Waited too long for udev, - aborting Asterisk  startup.


Sail is running fine, but what to do without a running asterisk?

Regards,
Marcel

[del]

Hi Marcel,

This is something to do with the kernel,

The reason your yum auto update messed up the system is that there is a new kernel in the update. The asterisk zaptel modules are very sensitive to kernel release levels and will ONLY work with the kernel for which they were compiled. We (Selintra Limited) are reluctant to cut a new asterisk rpm for a kernel which is not yet at "production" level (as far as SME Server is concerned). It is several hours of quite painstaking work (even with our rpm generators) so the official line is that we will support SME 7.0 final but NOT anything after that until the SME team announce it as a stable feature/release (we understand the next one will be 7.1 but we don't know what it will contain yet).

This is not actually a SAIL issue, it is an Asterisk/SME Server issue. If you really want to run with the new kernel then there is nothing to stop you compiling your own asterisk image from source if you wish - SAIL will work just fine if you do. You'll need to yum down the development environment but it's not a big job.

Sorry to appear recalcitrant but as we support more and more paying customers we have to stabilize our asterisk releases as best we can and it is somewhat counter productive (to us) to put time in on what are effectively beta test rigs for sme server because we would never install such a system in the field.

The stable asterisk set-up is currently SME 7.0 final, smeserver-asterisk-zappri-MPP-1.2.6-1 and smeserver-asterisk-1.2.10-1 if you are running sail 2.1.13 or higher.

You can see the post here: http://forums.contribs.org/index.php?topic=32854.0

and here: http://forums.contribs.org/index.php?topic=32854.0
I hope this helps. Maybe someone can explain how to reverse the kernel update or if it is possible to use yum and choose selected updates, then the kernel could be excluded.

Regards,
Del

[SARK devs]

Marcel,

you have at least two problems here. (1),  /etc/modprobe.conf is corrupted and (2), you have upgraded to a kernel which doesn't recognise the zaptel modules.

first you need to fix modprobe.conf.  The easiest way is to remove the zappri rpm and re-install it.  rpm -e followed by rpm -Uvh.

To fix the kernel issue there is a new post "Asterisk Zaptel kernel issues"

Kind Regards

Selintra

[marcelb]

Hi Del, Selintra,

Tx for the quick response. I followed the instructions from Jeff in the other part of the forum.


Regards Marcel

[pbearne]

Hi all

I guess I have two options

1 wait untill the updated asterisk for 7.1 is ready

2 down grade the kenel (if I can find up to do this)

Has abody got any ideas?

Paul

[SARK devs]

Hello Paul

No sweat....

Your old  kernel(s) are still there and you can choose which one you want at the linux splash screen by pressing the space bar.  The simplest way to fix/circumvent your prblem is simply to reboot SME and choose the old kernel at start-up.  However if you want to fix your problem then read on....

Firstly, after a yum update, SME/CentOS will attempt to come up with the smp version of the kernel (even if you have a UP system).  This seems to be a small bug in CentOS but it's no big deal to fix.  So....

Firstly  if you have the modprobe.conf problem mentioned in the first post in this thread --->

 WARNING: /etc/modprobe.conf line 48: ignoring bad line starting with 'post-install'  etc etc

AND...

uname -r

shows the kernel as ....-ELsmp then...

Restart SME server and press the space bar at the linux splash screen.   Choose the UP version of the new kernel.  That will fix the modprobe.conf problem.

Next - zaptel will still fail to load after a yum update because the kernel will have changed.  Follow the instructions in the docs manual here...

http://81.149.154.14/docs/cgi-bin/view/Main/DocChapter2510

That will get you back up and running.




Kind Regards

Selintra

[del]

Hi Selintra,

I have followed the steps here:

http://81.149.154.14/docs/cgi-bin/view/Main/DocChapter2510

But I still have to start asterisk manually I am booting to sme7 2.6.9-42.0.2.EL, so I did this:
cp -r /lib/modules/2.6.9-34.EL/extra/ /lib/modules/2.6.9-42.0.2.EL
followed by: depmod But nothing has changed  I still have to start asertisk by doing this: /etc/init.d/asterisk start
It still says: waiting for udev, then asterisk starts and everything works fine, until I have to reboot, which lucky for me isn't very often  Maybe you can tell me what I am missing

Regards,
Del

[chris burnat]

After reboot, go into PCI cards in server-manager and START asterisk.
For good measure, go into Global settings, save and commit.
This done it for me.
Rgds.
chris.

[del]

Hi Chris,

That didn't work either  But at least I now know how start Asterisk without using the console or putty I am not sure what I am doing wrong but it is no big deal, like I said I don't restart that often, normally only after yum update so I can live with it until a new rpm is released to match the latest kernel. I am not clever enough to do them myself so I have learnt to be patient  Only problem for me is I don't like giving up   So I will probably have another go eventually. Thanks for the reply.

Regards,
Del

[SARK devs]

Del,

Check you have asterisk enabled in the SME config...

Code: [Select]

[[root@sam2 ~]# config getprop asterisk status
enabled
[root@sam2 ~]#


If it isn't enabled then do so with

Code: [Select]

[root@sam2 ~]# config setprop asterisk status enabled

Perhaps this

Kind Regards

Selintra

[del]

Hi Selintra,

Did this:

[root@myserver ~]# config getprop asterisk status
and got enable NOT enabled

So I did this:

[root@myserver ~]# config setprop asterisk status enabled then repeated the config getprop asterisk status and got enabled

Rebooted my server to see if Asterisk would restart, but it didn't  So I ran

[root@myserver ~]# config setprop asterisk status and it says it is enabled

So I don't understand what I am doing wrong but none of the workarounds suggested have worked for me. So I just hope you can come up with a new zaptel rpm that plays ball with the latest kernel  Thanks again.

Regards,
Del

[pbearne]

Hi

As a test I am using the free service form sipgate

the sipgate is shown that I am contected but when phone the no i get number not found so I am not sure it conected

and how do you phone out 9+noumber or just dail

using SJphone for now

got the exention talking ok

and how do you set up the dail plan on the routs (blank for all?)

Any throught would help

Paul

[pbearne]

Hi

I have seen mention of the flash controler but what is the URL?

Paul

[del]

Hi Paul,

Try

http://yourdomain/fop

Regards,
Del