5 thoughts on - Asterisk 16.23.0 Doesn’t Respond Anymore

• Complement: restarting asterisk does the job and everything come back to normal.

  Le 13/12/2021 à 18:13, Administrator a écrit :

  —
  Daniel

  —

• Hi,

  1) You should change your name on your email client so it doesn’t say
  “Administrator”

  2) Please follow the instructions at https://wiki.asterisk.org/wiki/display/AST/Installing+Asterisk+From+Source

  3) Compile with DEBUG_THREADS and DONT_OPTIMIZE, but note this will incur a performance hit. Test this on a lab/testing environment if you can.

  4) Reproduce your lockup problem.

  5) Save the output of ‘core show locks’

  6) Enable core dumps in your environment, Get a core dump https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

  7) Post your findings back to the list and/or submit a bug report following the guidelines here:
  https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

  —

• Hi Mark

  Le 13/12/2021 à 22:53, Mark Murawski a écrit :

  This is a production server which is running well over years (asterisk
  11-13-16) and this happend with the latest version. Only valid option you gave is the core show locks. I ask the list before opening a bug report, as usually.

  And for the name, emails are always signed with first name 😉

  —
  Daniel

  —

• Still this is a PITA. Just use your name so we know who we are talking to from the headers without looking at the body. There should only ever be one “Administrator” on a mailing list, which is the admin of the list itself. If you are admin in your own domain, we simply shouldn’t care about.

  So please change your name or use another email for this list.

  FLORIAN FLOIMAIR
  Symphony Cloud Services (1568)

  Am 13.12.21, 23:39 schrieb “asterisk-users im Auftrag von Administrator” :

  CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

  Hi Mark

  Le 13/12/2021 à 22:53, Mark Murawski a écrit :
  > Hi,
  >
  > 1) You should change your name on your email client so it doesn’t say
  > “Administrator”
  >

  And for the name, emails are always signed with first name 😉

  —

• Hi Daniel,

  Please don’t let the fact that the system has been running just fine with no issue affect anything in your process related to this problem. 
  Sure… Asterisk 11 was okay for you.   Sure: Asterisk 13 was okay with you… and so on.  But obviously something is new and different with the new Asterisk you’ve set up with has nothing to do with what your Asterisk did a year ago.  None of that helps with debugging the current problem you’re facing.

  In order to get this fixed you’ll 100% need to be able to submit a bug report with enough information in order for someone to investigate this and get a resolution.  The information required is generally laid out in the guidelines linked to earlier.   It will also help to upload your log file from several minutes prior and up until the lockup.  Please feel free to mask out any confidential information from the logs that you don’t want shared publicly.

  The email is signed with the first name of the account information that your email system is set up with… not your actual name.  You definitely should change your name away from Administrator

  That’s typical of most software… this in itself is not a fix. Needing to restart Asterisk because it stops responding is a really bad problem and definitely needs to be fixed.  And with your help the developers can find this issue and make sure this doesn’t happen to other people as well.

  Thanks!

  —