| Summary: | ASTERISK-00868: after a stop gracefully using remote console, things hang | ||
| Reporter: | mochouinard (mochouinard) | Labels: | |
| Date Opened: | 2004-01-17 18:46:18.000-0600 | Date Closed: | 2011-06-07 14:10:10 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When you start your server as daemon, and you asterisk -vvvvr and you type stop gracefully, it should say : Waiting for inactivity to perform halt... But it doesn't and go back to prompt, and if you type anything, the prompt finish by freezing ****** ADDITIONAL INFORMATION ****** -- IAX2[NuFone]/4 answered SIP/2001-e036 asterisk*CLI> stop gracefully asterisk*CLI> FREEZE HERE | ||
| Comments: | By: Brian West (bkw918) 2004-01-17 20:32:12.000-0600 Works fine here.... what do you do to that poor box? :P By: mochouinard (mochouinard) 2004-01-18 13:33:02.000-0600 I dont know bkw ;) It seem im really mean... Will change the RAM and test again after By: zoa (zoa) 2004-01-18 14:56:26.000-0600 it's the same on my machine, restart gracefully and stop gracefully sometimes seem to cause a deadlock. But when i reconnect to asterisk, i can see that its not dead yet. (only the -r session seems to hang) By: mochouinard (mochouinard) 2004-01-19 08:25:33.000-0600 Yes exactly. Like if you do it in -vvvvc, it hang the console until it shutdown. So I guess it freeze at about the same place on the main thread By: jrollyson (jrollyson) 2004-01-19 08:30:55.000-0600 I'm occasionally seeing this on the remote console - the main process dies/restarts as expected, but the remote console doesn't. By: kalle (kalle) 2004-01-20 06:03:30.000-0600 I remember seeing such behaviour after a client crash (kphone). After stop gracefully asterisk hangs. The result was, that asterisk could not stop the mpg123-prozesses. After killing them manually (kill -9, normal kill doesn't work), asterisk finishing the shutdown. By: Brian West (bkw918) 2004-01-28 00:55:25.000-0600 Seems to be a local hardware issue. | ||