Apache startup: "Woops, blew up" a few thousand times
Wolfram Schlich <[email protected]> Mon, 14 Oct 2002 22:13:41 +0200
| Newsgroups | gmane.comp.apache.mod-mp3 |
|---|---|
| Message-ID | <[email protected]> |
Hi, I have a small problem with mod_mp3: on startup, Apache spits out a few thousand messages saying "Woopw, blew up". Looks like there's a memory problem. This does only occur when specifying a *huge* mp3 collection (~16k files) in an "MP3 /some/path" directive. Using Apache 1.3.27, mod_mp3 0.39. Another crazy thing is that Apache segfaults when I do the following: set "MP3DispatchAgent" to "internal" *but* specify MP3MySQLConnectInfo, MP3MySQLInfo, MP3MySQLTokenTable. I mean, the three latter one's aren't supposed to do *anything* when the MySQL dispatch isn't enabled, right? Also I don't get the point why the website says something about four different dispatchers, while Apache says: --8<-- [Mon Oct 14 22:08:02 2002] [error] The dispatch you requested doesn't seem to exist [Mon Oct 14 22:08:02 2002] [error] The following are valid: [Mon Oct 14 22:08:02 2002] [error] internal [Mon Oct 14 22:08:02 2002] [error] mysql --8<-- Any ideas? Damn, this is *really* crazy! It recovered after commenting out "MP3Cache Off" :-/ Sorry to say but mod_mp3 looks really messy to me :-/ I mean, it's really cool (when it does work!), but... *sigh* I've spent too much time on it today ;-) Nevermind :o) -- Wolfram Schlich; Friedhofstr. 8, D-88069 Tettnang; +49-(0)178-SCHLICH