similar to: Use safe_asterisk manually, you get colors in CLI. Crontab it, you don't.

Hi all, I have installed some Asterisk machine, all with the same problem. My typical configuration is: - Asterisk 1.2.14 (or 1.4.0beta3) - CentOS 4.4 server. The problem is this: When I start Asterisk with the default init script (/etc/init.d/asterisk start) distributed with the source, and kill (or kill -9) Asterisk-pid, then safe_asterisk doesn't correctly work (it dies and not restart

Recently safe_asterisk is failing to pick up ASTSBINDIR. I've never had this problem before and even when I move to back versions I have the issue. I did upgrade safe_asterisk and the init.d scripts a version or so ago but even when I try older ones I still have the problem. When I hard code the location things seem to work. The problem that occurs is: cat:

Hello, I've found a couple of previous posts on this subject, but with no posted resolution... I'm attempting to run * as a non-root user (asterisk), following the guidelines on the wiki: http://voip-info.org/tiki-index.php?page=Asterisk%20non-root I can run * as my new user with "/usr/sbin/asterisk -vvvvc" without problem. However, I'm unable to run * using

Hello my friends, I'm very worry about a problem i'm having...my asterisk got freez some times, every 5 or 6 days with NO trace in /var/log/asterisk/messages What i want to know is if safe_asterisk has something to be with this? This is what i have on my server: [root at mypbx ~]# ps -A | grep asterisk 9118 ? 00:01:30 asterisk [root at dreampbx ~]# ps aux | grep asterisk root

Hi Please help me understand about the below issue ? [root at asterisk1 ~]# /etc/init.d/asterisk restart Stopping safe_asterisk: [ OK ] Shutting down asterisk: [ OK ] Starting asterisk: /usr/sbin/safe_asterisk: line 86: ulimit: open files: cannot modify limit: Operation not permitted

Hi Please help me understand about the below issue ? [root at asterisk1 ~]# /etc/init.d/asterisk restart Stopping safe_asterisk: [ OK ] Shutting down asterisk: [ OK ] Starting asterisk: /usr/sbin/safe_asterisk: line 86: ulimit: open files: cannot modify limit: Operation not permitted

I have no problems lauching asterisk from the command line . . . asterisk -vvvvc However, I'm trying to autostart on boot up, so I'm trying safe_asterisk When I do this, I get: Asterisk ended with exit status 127. Asterisk died with code 127. Aborting. I've looked through the script but can't find what the problem is. I'm running on RedHat Fedora. Thanks for your help.

I was looking at the shell in /usr/sbin and the following statement does not seem right: while :; (read colon + semi colon). In C that would be 2xsemi-colon. is this correct in a bash shell? I am having problems with safe_asterisk. when it dies, it is not being brought up again. It works very well for stop/start/startus but does not bring up asterisk when it fails. -------------- next part

About two weeks ago there was a thread about asterisk suddenly dying - I posted a response that the same happens to my asterisk about once a month, sometimes more. Someone suggested using 'safe_asterisk' (and get hold of a core dump) which sounds like a good idea, but one thing I can't figure is how to get "module reload app_queue" executed automatically at startup?

Hi All, I'm running * 1.6.0.28 on Debian Lenny. The init'd script starts the asterisk daemon not the safe_asterisk daemon so when asterisk is running and I ssh tot he server then 'asterisk -vr' to attach to the asterisk console there are no colors. If I use the safe_asterisk script to start asterisk, the colors are fine when I attach through SSH. I found this in the init

Hi, I configured Asterisk to run as "asterisk" user, but I see that a user can anyway get a root sheet using !command in CLI. I understood that it's something related to safe_asterisk and TTY console, but modifying the script safe_asterisk I wasn't able to disable this root access. Can someone help me? Thanks. -------------- next part -------------- An HTML attachment was

I've been experiencing some crashes in Asterisk in the past few weeks. I haven't been able to find out why as gdb shows it's in a different function every time. But, in the meantime, I've been using safe_asterisk hoping that it would simply restart Asterisk by itself. It doesn't seem to do that. Whenever Asterisk crashed, the list of processes doesn't show asterisk or

Here is how I start asterisk: [root@asterisk asterisk]# /usr/sbin/safe_asterisk 2>&1 >/dev/null & safe_asterisk returns immediatly saying "Done" but asterisk still starts. Why doesn't safe_asterisk stay running? Thanks, Matthew

Here's a strange one - when I run safe_asterisk on either of these distros, words that are colored blue or violet (but not red) turn up in Russian (and some other languages, I think). If I run asterisk with the same arguments (-vvvg -c) as safe_asterisk does, from the console, it's OK. If I run it in a Putty window it's OK. If I run asterisk -r from another console or from

Hi - I just got an A200 card with 1 FXO and 1 FXS module. Sadly, I can't make it work- currently, asterisk will not startup because of a bad module. Below are some log files/config files. If anyone has any suggestions, I'd appreciate it. I used Trixbox 2.0 and followed instructions on (http:// sangoma.editme.com/wanpipe-linux-asterisk-atHome) - no problems running through or

Hi, I'm running asterisk 1.2.0 on a debian rel 2.6.13 and when I start it with safe asterisk I got instantly more then 10 processes. Until now I didn't detected any impact of this process proliferation in the system, but it is strange and I'm not comfortable with this. Is this a know problem? Any ideas what is the problem here, or where to start searching? I think

I have a instance of Asterisk 1.2.14 that is being run from safe_asterisk. Asterisk is seg faulting and NOT generating a core dump. Why would that be? How can I make it dump core? Is there a setting in the safe_asterisk script that I am missing? Thanks, Doug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Went from 1.6.0.6 to 1.6.0.8 and resulted in segmentation fault. Reverted to 1.6.0.6 and back to normal. ------------------ Linux asterisk.hulber.com 2.6.18-128.1.1.el5 #1 SMP Mon Jan 26 13:58:24 EST 2009 x86_64 x86_64 x86_64 GNU/Linux Apr 3 11:49:56 asterisk kernel: asterisk[3780]: segfault at 00002ce1ac0537a8 rip 0000003e980715a8 rsp 00007fff5bf00c30 error 4 Apr 3 11:50:00 asterisk

Heya, I was just trying out the safe_asterisk-script. I think that the 2 asterisk-commands in the script always need the "-f"-option, else the script doesn't really do what it is intended for I think ... except only on startup. greetz, Michel

In fedora core 2 and 3 starting asterisk using contrib/init.d/rc.redhat.asterisk (installed by make config), if asterisk dies, it doesn't restart. Seems the problem is in initlog. The standard way to start services in fedora is by calling daemon <service> that results in: $nice initlog $INITLOG_ARGS -c "$*" Removing initlog works correctly. I don't know if this is a