Summary:	ASTERISK-05813: monmp3 thread error
Reporter:	denon (denon)	Labels:
Date Opened:	2005-12-10 20:11:19.000-0600	Date Closed:	2011-06-07 14:10:22
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Resources/res_musiconhold
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I'm seeing this every couple of minutes on a box I just ugpraded to 1.2.1. A quick google shows a couple others seeing it, but I didn't see an open bug. "Dec 10 21:09:20 NOTICE[28207]: res_musiconhold.c:507 monmp3thread: Request to schedule in the past?!?!" MOH seems to be working, but haven't monitored it closely to see if it's otherwise affected.
Comments:	By: denon (denon) 2005-12-10 20:12:26.000-0600 Actually, MOH does seem to stutter momentarily as the error is displayed. Tested using stock MOH files. By: Kevin P. Fleming (kpfleming) 2005-12-13 10:46:23.000-0600 You didn't see a bug report on this because it's not a bug :-) It's typically caused by too much load on the system; it's also caused by using MP3s for streaming moh when it's not needed... By: Russell Bryant (russell) 2005-12-13 11:05:10.000-0600 I have also seen this more frequently when zaptel timing was not available By: denon (denon) 2005-12-13 11:05:36.000-0600 load average: 0.00, 0.00, 0.00 I literally never saw this message on 1.2.0, and see it every minute or two on 1.2.1. Is it a new error message, or is it just showing up now? The box has pretty much no load (as the above average shows), and the MP3s are on the local drive. By: Russell Bryant (russell) 2005-12-13 11:30:22.000-0600 That message has been there since pre-1.0 ... By: Russell Bryant (russell) 2005-12-21 03:02:01.000-0600 Closing this out since there doesn't appear to be a bug here By: denon (denon) 2006-01-04 07:25:16.000-0600 Talked to drumkilla - seems like this may still be a bug, so he suggested I could re-open. By: Tilghman Lesher (tilghman) 2006-03-01 16:02:34.000-0600 Is this still an issue?  // Housekeeping By: denon (denon) 2006-03-02 10:45:13.000-0600 This has been "resolved" by blowing away and old redhat install, and installing debian. You can close this bug.