| Summary: | ASTERISK-00571: safe_asterisk does not properly restart asterisk after a crash | ||
| Reporter: | jonect (jonect) | Labels: | |
| Date Opened: | 2003-11-25 16:17:59.000-0600 | Date Closed: | 2011-06-07 14:00:24 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | On Red Hat 9, safe_asterisk does not properly restart asterisk if it exited due to a crash. safe_asterisk attempts to restart asterisk immediately which does not give the application time to clean up and results in the restarted asterisk exiting with return code 1 which causes safe_asterisk to exit. ****** ADDITIONAL INFORMATION ****** Adding a "sleep 5" just below the line "echo Restarting Asterisk." corrects the problem but may not be the best fix. | ||
| Comments: | By: Tilghman Lesher (tilghman) 2003-11-25 16:58:42.000-0600 You said the magic words "RedHat 9". There seems to be quite a number of issues relating to this release. Might I suggest RedHat 8 or perhaps another distribution, such as Mandrake 9.1? By: jonect (jonect) 2003-11-25 17:43:04.000-0600 Personally, I plan to migrate off of Red Hat 9 since it will not be supported as of next year now that Red Hat has abandoned the end user market but the fact remains that many people use it. The solution that I found may not be the best but it should work in all flavors of Linux. By: Brian West (bkw918) 2003-11-26 11:21:21.000-0600 This isn't a bug in asterisk. This is an issue with RH9. | ||