Topic: SAIL/Asterisk and SME Kernel

[del]

Hi All,

Asterisk still doesn't start when I boot or reboot my server. Is this still a problem with the latest zaptel rpm or am I doing something wrong  I can still start it by clicking on save/commit in the general tab through server-manager though, so it still does work 
I am running the following rpms:
selintra-sail-2.1.14-507.noarch.rpm
smeserver-asterisk-1.2.10-10.i686.rpm
smeserver-asterisk-zappri-MPP-1.2.13-1.i686.rpm
and kernel 2.6.9-55.0.2.EL

Regards,
Del

[SARK devs]

Hi Del

do this at the console....

config show asterisk

If the status is showing as disabled then do this...

config setprop asterisk status enabled

That'll do it.

Best

S

[del]

Hi Selintra,

I issued the commands as you suggested and it says:

[root@sme-server ~]# config show asterisk
asterisk=service
    UDPPorts=4569,5060,10000:20000
    status=enabled

So I don't understand what's going on Do I need to probe for PCI cards in server-manager? Even though I don't have any? I read on another asterisk forum something about loading zt dummy (or something similar) is it possible that this is anything to do with it?
Regards,
Del

[SARK devs]

Hello Del,

What do you get when you do...

db selintra show ztdummy

Best

S

[del]

Hi Selintra,
Result of the command:

[root@sme-server ~]# db selintra show ztdummy
ztdummy=loadmod
    status=YES
    zzeor=EOR

Hope this sheds some light on things. I have not yet done the latest updates to SME so I will try and find time today and see if it restarts. Thanks for your help.

Regards,
Del

[del]

I had to reboot my server today and Asterisk did not start until I clicked on commit in the Globals panel  So I guess I must be doing something wrong  Any ideas?

Del

[SARK devs]

Check your messages log to see why asterisk didn't start

Post it back here if it stil isn't clear what the problem is.

Kind REgards

S

[del]

Hi Selintra,

How do I view the log Thanks

Del

[chris burnat]

First look into /var/log/messages it may provide a clue.
Next:
/var/log/asterisk/messages
and possibly:
/var/log/asterisk/event_log

You can access all of these logs from the "view log" in server manager.  However, unless you run the latest version of Sail, you may find that your  /asterisk/messages is very big, because it did not rotate. 

To avoid waiting for ever trying to open a large log file, do:

Code: [Select]

tail -100 /var/log/asterisk/messages
This should do it.
chris

[sonoracomm]

If your SME Server was recently updated, it may have a new kernel version.  Make sure you reboot to run the latest kernel.  At the console, verify the kernel version:

Code: [Select]

uname -r
Verify the necessary kernel modules are in the right place:

Code: [Select]

ll /lib/modules/`uname -r`/extra
If they are not there, copy the kernel modules from an older kernel to the new location and activate them.  You may need to adjust the 'from' and 'to' locations:

Code: [Select]

cp -r /lib/modules/2.6.9-42.0.10.ELsmp/extra /lib/modules/2.6.9-55.0.9.ELsmp/
depmod
Make sure Asterisk will start up automatically upon a reboot.  This may specifically be needed after an Asterisk upgrade.  Check for the existence of the runlevel 7 link.

Code: [Select]

ll /etc/rc.d/rc7.d/S93asterisk
and if it's not there:

Code: [Select]

ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S93asterisk
Finally, reboot to test:

Code: [Select]

signal-event reboot
After it boots back up, check that Asterisk is running:

Code: [Select]

ps ax|grep ast
Hope that helps,

G