Topic: SAIL and SME 7.1 problems

[del]

Hi All,

Has anyone had any problems with SAIL/Asterisk since upgrading to SME 7.1? I did the updates tonight and had the same old problem with it not starting due to the new kernel  but I usually get round it by starting asterisk manually (is there any solutions to this problem yet?) but when I tried with this /etc/init.d/asterisk start I got this message:

FATAL: Module zaptel not found.
Waiting for udev.
Waited too long for udev, - aborting Asterisk  startup.

I then rebooted and chose the old 2.6.9.34.EL kernel at the splash screen and it took 3 attempts to get asterisk to start  Can anyone point me in the right direction to finally get asterisk to start when I boot up  Thanks in advance.

Regards,
Del

[SARK devs]

Hi Del

If it isn't finding zaptel it means that the kernel has changed.  What do you get when you type

uname -r

Once you know the kernel release you can follow the section in the docs re Yum Updates....

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

This should get you on your way.

We'll put up a 7.1 rpm release shortly but in the meantime, you can fiddle it with the above.

Kind Regards

Selintra

[del]

Hi Selintra,

After the updates it was running kernel 2.6.9-42.0.3.EL so I did this:

[mybox]# cp -r /lib/modules/2.6.9-34.EL/extra/ /lib/modules/2.6.9-42.EL

It gave some error about directory not existing, so I did this:

[mybox]# cp -r /lib/modules/2.6.9-34.EL/extra/ /lib/modules/2.6.9-42.0.3.EL
[mybox]# depmod

but asterisk would not start and in all honesty I have never been able to get any of the fixes to work for me but I have always been able to start asterisk from the command line before this update so I figured I'd wait until some new rpms came out  I am now running kernel 2.6.9-34EL and the following rpms:

smeserver-asterisk-1.2.10-1.i686.rpm
smeserver-asterisk-zappri-MPP-1.2.6-1.i686.rpm
selintra-sail-2.1.14-339.noarch.rpm
smeserver-asterisk-sounds-1.2.2-2.noarch.rpm

Do I need to upgrade to selintra-sail-2.1.14-347.noarch.rpm? Is smeserver-asterisk-sounds-1.2.2-2.noarch.rpm needed? I see that it is not in the download link from your docs site anymore. Thanks for looking.

Regards,
Del

[hervep]

Hi all,

I don't have any problem using Sail 2.1.14-358 in combination with
SME 7.1 ( Kernel 2.6.9-42.0.3ELsmp ). Harware used is X100P 'clone'.
FYI : SME 7.1 is 'server only' installed from 7.1 ISO + yum updates.

Del ...  Just an idea : what about your tftp server ? I remember I had once a startup problem during installation ( just before TFTP install ).
Is your TFTP server still running after the upgrade ?

Kind regards,

Hervé

[del]

Hi hervep,

I believe I saw tftp server start because I watched the boot sequence. Is there a command to check it, I don't want to risk restarting in case I can't get asterisk up and running. I am not using any PCI cards just SPA-2000 and voip trunks. I would upgrade sail but I don't believe this is a problem with that rpm but a problem with smeserver-asterisk or zappri rpms and I already have the ones in the download area installed. Thanks for your suggestions though.

Regards,
Del

[Tib]

del

Make sure your system has not started in SMP mode ... my test machine did that from first boot.

Single PCU mode:

Code: [Select]


cp -r /lib/modules/2.6.9-34.EL/extra/ /lib/modules/2.6.9-42.0.3.EL
depmod



If you have dual processors then run:

Code: [Select]


cp -r /lib/modules/2.6.9-34.ELsmp/extra/ /lib/modules/2.6.9-42.0.3.ELsmp
depmod


Regards,

Tib

[Tib]

Also all I had to do is click on commit in Global settings to kick things back into gear.

My home machine is working no probs as well since that.


del

All my files on the test unit are the same as yours and are working no probs.

smeserver-asterisk-1.2.10-1.i686.rpm
smeserver-asterisk-zappri-MPP-1.2.6-1.i686.rpm
selintra-sail-2.1.14-339.noarch.rpm
smeserver-asterisk-sounds-1.2.2-2.noarch.rpm

Also make sure you use the right code for your setup and only use

depmod

with the correct code.

eg: if you do

Code: [Select]


cp -r /lib/modules/2.6.9-34.EL/extra/ /lib/modules/2.6.9-42.0.3.EL
depmod

and then

Code: [Select]


cp -r /lib/modules/2.6.9-34.ELsmp/extra/ /lib/modules/2.6.9-42.0.3.ELsmp
depmod

then I noticed that only the SMP mode is enabled because you used the SMP code last ... so if you want EL mode only use the EL code.

If I'm wrong please let me know.

Regards,

Tib

[del]

Hi Tib,

Thanks for the info, I am running in EL mode and currently it is using 2.6.9-34.EL kernel So to clear up a few things in my head do I do this:

cp -r /lib/modules/2.6.9-34.EL/extra/ /lib/modules/2.6.9-42.0.3.EL
depmod

now with 2.6.9-34.EL kernel running and then reboot or do I have to reboot into the 2.6.9-42.0.3.EL kernel and then do it? This may sound dumb (probably because I am dumb) but depmod is a seperate command that is run after doing cp -r /lib/modules/2.6.9-34.EL/extra/ /lib/modules/2.6.9-42.0.3.EL  I am sorry for being a bit slow here but I seem to have tried everything and still I have no luck with asterisk starting on boot  I am now in the process of reinstalling my test server and will put the same contribs as my main server and test it a bit before I risk loosing my communications center (or centre) I will report back ASAP

Regards,
Del

[Tib]

del

I did the command while in the new kernel ... then went to the server manager and under Global Settings I clicked on commit.

after that I tried a re-boot and all started no probs.

Regards,

Tib

[hervep]

Hi hervep,

I believe I saw tftp server start because I watched the boot sequence. Is there a command to check it, I don't want to risk restarting in case I can't get asterisk up and running. I am not using any PCI cards just SPA-2000 and voip trunks. I would upgrade sail but I don't believe this is a problem with that rpm but a problem with smeserver-asterisk or zappri rpms and I already have the ones in the download area installed. Thanks for your suggestions though.

Regards,
Del

Hi Del,

To check if tftp is running,

Code: [Select]

# service tftp status
should report something like :

Code: [Select]

in.tftpd (pid 4442) is running...

another way to do it :

Code: [Select]

# ps -ef|grep tftp
should report something like :

Code: [Select]

root      4442     1  0 Jan07 ?        00:00:00 /usr/sbin/in.tftpd -l -v -v -p -s /tftpboot

... just for your info

Kind regards,

Hervé

[del]

Hi All,

Ok today I did everything according to the replies here on my test server and asterisk didn't start after a reboot but it did start by clicking save on the asterisk extensions menu (where said something like " Asterisk has not started, if it does not start after saving something then there is something wrong") So I did the same on my real server and it was the same result, this time I started the PBX under the PCI Cards section and it started OK so at least I can get it to start easy enough now. I must have something else causing me a problem. I will try a straight forward shut down and restart over the weekend

Regards,
Del