[asterisk-bugs] [JIRA] (ASTERISK-28699) ast_coredumper does not find asterisk running process and silently fails
Addons Zz (JIRA)
noreply at issues.asterisk.org
Fri Jan 17 14:42:25 CST 2020
[ https://issues.asterisk.org/jira/browse/ASTERISK-28699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Addons Zz updated ASTERISK-28699:
---------------------------------
Description:
I do not use command line configurations, because I had set:
File: /etc/asterisk/asterisk.conf
...
[options]
verbose = 3
debug = 0
highpriority = yes ; Run realtime priority (same as -p at
dumpcore = yes ; Dump core on crash (same as -g at startup).
Now, when I run:
root at debian9:~/Downloads# /var/lib/asterisk/scripts/ast_coredumper --running --latest
It outputs nothing. Then I edited the file `/var/lib/asterisk/scripts/ast_coredumper` and removed the line `set -e`
After that, when running the command, it started outputting:
root at debian9:~/Downloads# /var/lib/asterisk/scripts/ast_coredumper --running --latest
Asterisk is not running
However, I have the asterisk process up and running: (pid 11529)
root at debian9:~/Downloads# ps aux | grep asterisk
root 11529 26.2 14.5 2243256 73400 ? SLsl 15:02 18:07 asterisk
root 11530 0.0 0.3 15232 1560 ? S 15:02 0:00 astcanary /var/run/asterisk/alt.asterisk.canary.tweet.tweet.tweet 11529
root 27971 0.0 0.1 132344 964 pts/0 R+ 16:11 0:00 grep --color=auto asterisk
root 29065 0.0 1.8 98488 9100 pts/6 S+ 15:22 0:00 rasterisk r
I managed to make it work, by replacing the line `pids=$(pgrep -f "$asterisk_bin")` directly with my asterisk pid 11529:
root at debian9:~/Downloads# /var/lib/asterisk/scripts/ast_coredumper --running --latest
Found a single asterisk instance running as process 11529
WARNING: Taking a core dump of the running asterisk instance will suspend call processing while the dump is saved. Do you wish to continue? (y/N) y
Dumping running asterisk process to /tmp/core-asterisk-running-2020-01-17T17-21-35-0300
Processing /tmp/core-asterisk-running-2020-01-17T17-21-35-0300
Creating /tmp/core-asterisk-running-2020-01-17T17-21-35-0300-thread1.txt
Creating /tmp/core-asterisk-running-2020-01-17T17-21-35-0300-brief.txt
Creating /tmp/core-asterisk-running-2020-01-17T17-21-35-0300-full.txt
Creating /tmp/core-asterisk-running-2020-01-17T17-21-35-0300-locks.txt
was:
I do not use command line configurations, because I had set:
File: /etc/asterisk/asterisk.conf
...
[options]
verbose = 3
debug = 0
highpriority = yes ; Run realtime priority (same as -p at
dumpcore = yes ; Dump core on crash (same as -g at startup).
Now, when I run:
root at debian9:~/Downloads# /var/lib/asterisk/scripts/ast_coredumper --running --latest
It outputs nothing. Then I edited the file `/var/lib/asterisk/scripts/ast_coredumper` and removed the line `set -e`
After that, when running the command, it started outputting:
root at debian9:~/Downloads# /var/lib/asterisk/scripts/ast_coredumper --running --latest
Asterisk is not running
However, I have the asterisk process up and running: (pid 11529)
root at debian9:~/Downloads# ps aux | grep asterisk
root 11529 26.2 14.5 2243256 73400 ? SLsl 15:02 18:07 asterisk
root 11530 0.0 0.3 15232 1560 ? S 15:02 0:00 astcanary /var/run/asterisk/alt.asterisk.canary.tweet.tweet.tweet 11529
root 27971 0.0 0.1 132344 964 pts/0 R+ 16:11 0:00 grep --color=auto asterisk
root 29065 0.0 1.8 98488 9100 pts/6 S+ 15:22 0:00 rasterisk r
Environment:
root at debian9:~/Downloads# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
was:
root at debian9:~/Downloads# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
> ast_coredumper does not find asterisk running process and silently fails
> ------------------------------------------------------------------------
>
> Key: ASTERISK-28699
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28699
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/ACL
> Affects Versions: 17.1.0
> Environment: root at debian9:~/Downloads# cat /etc/os-release
> PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
> NAME="Debian GNU/Linux"
> VERSION_ID="9"
> VERSION="9 (stretch)"
> ID=debian
> HOME_URL="https://www.debian.org/"
> SUPPORT_URL="https://www.debian.org/support"
> BUG_REPORT_URL="https://bugs.debian.org/"
> Reporter: Addons Zz
> Severity: Trivial
>
> I do not use command line configurations, because I had set:
> File: /etc/asterisk/asterisk.conf
> ...
> [options]
> verbose = 3
> debug = 0
> highpriority = yes ; Run realtime priority (same as -p at
> dumpcore = yes ; Dump core on crash (same as -g at startup).
> Now, when I run:
> root at debian9:~/Downloads# /var/lib/asterisk/scripts/ast_coredumper --running --latest
> It outputs nothing. Then I edited the file `/var/lib/asterisk/scripts/ast_coredumper` and removed the line `set -e`
> After that, when running the command, it started outputting:
> root at debian9:~/Downloads# /var/lib/asterisk/scripts/ast_coredumper --running --latest
> Asterisk is not running
> However, I have the asterisk process up and running: (pid 11529)
> root at debian9:~/Downloads# ps aux | grep asterisk
> root 11529 26.2 14.5 2243256 73400 ? SLsl 15:02 18:07 asterisk
> root 11530 0.0 0.3 15232 1560 ? S 15:02 0:00 astcanary /var/run/asterisk/alt.asterisk.canary.tweet.tweet.tweet 11529
> root 27971 0.0 0.1 132344 964 pts/0 R+ 16:11 0:00 grep --color=auto asterisk
> root 29065 0.0 1.8 98488 9100 pts/6 S+ 15:22 0:00 rasterisk r
> I managed to make it work, by replacing the line `pids=$(pgrep -f "$asterisk_bin")` directly with my asterisk pid 11529:
> root at debian9:~/Downloads# /var/lib/asterisk/scripts/ast_coredumper --running --latest
> Found a single asterisk instance running as process 11529
> WARNING: Taking a core dump of the running asterisk instance will suspend call processing while the dump is saved. Do you wish to continue? (y/N) y
> Dumping running asterisk process to /tmp/core-asterisk-running-2020-01-17T17-21-35-0300
> Processing /tmp/core-asterisk-running-2020-01-17T17-21-35-0300
> Creating /tmp/core-asterisk-running-2020-01-17T17-21-35-0300-thread1.txt
> Creating /tmp/core-asterisk-running-2020-01-17T17-21-35-0300-brief.txt
> Creating /tmp/core-asterisk-running-2020-01-17T17-21-35-0300-full.txt
> Creating /tmp/core-asterisk-running-2020-01-17T17-21-35-0300-locks.txt
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list