Whenever i forward the incoming call to voice mail or self voicemail asterisk get stopped automatically without throwing any issue.
Please i need help on this issues
when i run asterisk -vvvvvg -c command when asterisk disconnected it throws an error
“illegal instruction (core dumped)”
Actually what this mean?
The CPU has tried to decode a machine instruction that it doesn’t recognize. As a result, the operating systm has written a copy of writeable parts of the memory used by Asterisk to a file called core in the current directory.
See my previous reply for what to do with that file.
i seen your post i tried the command gdb -se “asterisk” -c core | tee /tmp/backtrace.txt
it throws
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6)
Copyright © 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and “show warranty” for details.
This GDB was configured as “i686-redhat-linux-gnu”.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/…
Reading symbols from /XXX/XXXX/usr/sbin/asterisk…done.
/XXXX/XXX/XXX/usr/sbin/core: No such file or directory.
(gdb)
What to do now?
i’m a new baby so please help me to resolve this issue
Run it with the correct directory for the core file.
Note that safe_asterisk moves the files to /tmp and appends the date.
Correct directory in the sense from /usr/sbin
I have to run it from this location ah ?
If so i tried that still i have the same issue
when i run from the correct location /usr/sbin/
gdb -se “safe_asterisk” -c core | tee /tmp/backtrace.txt i get following output
“/usr/sbin/safe_asterisk”: not in executable format: File format not recognized
"/usr/sbin/core" is not a core dump: File format not recognized
i’m getting this error
/usr/sbin/core" is not a core dump: File format not recognized
what this mean and what i have to do ?
Please help me ?
Use the core file created by the crash. This will initially be created in the current directory at the time of the crash, but will be moved and renamed by safe_asterisk, if you are using that.
You probably need to find someone local to you with Linux system management experience.
Note the simplest cause for an illegal instruction would be running a binary that was compiled for a slightly different processor. Some people also report problems running on virtual machines (although, in my view, running Asterisk on one is never a good idea).
i found a core file and execute the same line i got a message
Reading symbols from /lib/ld-linux.so.2…(no debugging symbols found)…done.
Loaded symbols for /lib/ld-linux.so.2
725 utils.c: No such file or directory.
Core was generated by `/XXX/XXXX/XXXXX/usr/sbin/asterisk -g’.
Program terminated with signal 4, Illegal instruction.
#0 0x080f78b9 in tvfix (a=…, b=…) at utils.c:725
in utils.c
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.107.el6.i686
We already knew that it was an illegal instruction. You have to get the back trace to find out what it was doing. You should also look at the logs, as they should tell you what it did successfully just before the crash.
I should ask which version is this, as if it is no longer supported, there may be little that one can do other than avoid doing whatever broke it, and it if it is not recent, the bug may already have been fixed.
Thanks for your help
This is the message i have got in backtrace.txt file
Reading symbols from /lib/ld-linux.so.2…(no debugging symbols found)…done.
Loaded symbols for /lib/ld-linux.so.2
Core was generated by `/XXXX/XXXX/usr/sbin/asterisk -g’.
Program terminated with signal 4, Illegal instruction.
#0 0x080f78b9 in tvfix (a=…, b=…) at utils.c:725
in utils.c
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.107.el6.i686
The same setup i’m running in another machine is works fine without any issue but it throws a error
in main machine what i’m facing now .
Suggest or give some idea
Compile Asterisk on the machine that you are using now.
Compile means you want me to reinstall the thing
That is not possible to do that except voicemail other functions are working perfect in that machine
Keep the configuration, but rebuild the executables from source code.
At the moment, the most likely cause is that it has been compiled for a CPU that supports a feature is not present in the machine that is causing the problem. If that is the case, you need to either compile it on the target machine, which should make it limit itself to the features that supported, or compile with an explicit target architecture that is more limited that the target machine.
You should probably also try 11.5.0, in case the default build environment has been changed to avoid this problem. If that still doesn’t work, you will need to submit a bug report. If you are using a package, you will need to submit it to the package maintainer. You will need more complete backtrace information, and the output of “cat /proc/cpuinfo”.
If you are using a virtual machine, that will be relevant information.
Based on information i got in backtrack file is there any problem in my machine level
power management:
Thanks in advance
I’ve no idea for what machine the binary you are using was compiled. I’d have to talk you through some detailed use of GDB to find out what instruction faulted, and therefore what is likely to be the feature that is missing in the target machine. I’ve already spent more time that is reasonable, on this.
The incompatibility is probably on the flags line, but you would need to know what flags the binaries assume are enabled. It is almost certainly something that is not there, rather than something that is there.
You will need it recompiled to run on that machine, whether you or the package builder actually does the recompilation, unless a later version avoids the issue.