hi i'm getting segfaults with Icecast thus: Feb 7 10:27:06 server kernel: icecast[19308]: segfault at a36bc3db eip 0805d5e3 esp b78fd120 error 4 Feb 7 12:01:06 server kernel: icecast[20417]: segfault at dc2d718e eip 080571df esp b62540f0 error 5 i cron a script every minute to restart Icecast if it fails and to notify me - so i know that this is happening about once every 12 hours or so. when this happens i get dropped connections from encoders and clients. the server's running FC8 with this kernel: [root@server ~]# uname -a Linux server 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 2007 i686 i686 i386 GNU/Linux and here's what top shows: top - 23:46:24 up 1 day, 20:25, 3 users, load average: 0.00, 0.00, 0.00 Tasks: 118 total, 1 running, 117 sleeping, 0 stopped, 0 zombie Cpu(s): 0.5%us, 1.3%sy, 0.0%ni, 97.4%id, 0.0%wa, 0.2%hi, 0.7%si, 0.0%st Mem: 2073984k total, 1932832k used, 141152k free, 111092k buffers Swap: 2031608k total, 0k used, 2031608k free, 1649972k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 9625 iceadmin 20 0 58664 11m 1616 S 2 0.6 0:14.56 icecast questions: i) any known reason for the seg faults? ii) any known cure for this? iii) any other advice? many thanks in advance for your help Chip Scooter
Hi, Anything helpful in your error.log? You may need to set the log level to 4 (debug). Geoff.
On 08/02/2008, Geoff Shang <Geoff@quitelikely.com> wrote:> Hi,hi geoff> Anything helpful in your error.log? You may need to set the log level to 4 > (debug).good point. i'll do this and see what i get.> Geoff.many thanks. Chip Scooter
Hi On 08/02/2008, Geoff Shang <Geoff@quitelikely.com> wrote:> Hi, > > Anything helpful in your error.log? You may need to set the log level to 4 > (debug).Ok - I've had 5 seg faults in the last 24 hours which is a pain, as you can imagine. I crona script once per minute to restart Icecast in the event that it fails so the service is never down for more than 59 secs but it drops encoder/client connections in that time. However I now have some clues - preceding each seg fault I get this: [2008-02-10 18:36:10] INFO source/source_main listener count on /radiofm.mp3 now 0 [2008-02-10 18:36:10] DBUG admin/admin_handle_request Admin request (/admin/metadata) [2008-02-10 18:36:10] DBUG admin/admin_handle_request Got command (metadata) [2008-02-10 18:36:10] INFO admin/admin_handle_request Received admin command metadata on mount "/radiofm.mp3" [2008-02-10 18:36:10] DBUG admin/command_metadata Got metadata update request ^NS^S??7h_????R<86>''-10 18:36:10] INFO admin/command_metadata Metadata on mountpoint /radiofm.mp3 changed to ";V^^<90>LQZ????<90>g^C<8f>n%"U??&B??<9b>0di? <90><8d>^Y^Q<9c>&^]^Pl4^N^Y<89><9a><95><80>?Q???(R)?<8d><89>-;??<94>?????<8b>Y?????e<95><95>qwxn+?T<93>??a<97>?<9c>r???U??F$??<8a>?2+c?g6y7^V?<81>%???(R)??<9c>!<???<97>????W????" [2008-02-10 18:36:10] DBUG fserve/fserve_add_client Adding client to file serving engine [2008-02-10 18:37:01] INFO main/main Icecast 2.3.1 server started or here's another: [2008-02-11 06:44:11] INFO admin/command_metadata Metadata on mountpoint /radiofm.mp3 changed to ";<87>??&???s<8d>??^Db"^L?<96><82>??Ak???_^?)<94>??<8f>??<g$??<87>h????e<96>O^Gt??^N<9e>C?8?????3?(R)W?<90>??<94>^G??p??? ??@?????????????k}o????'w????????<98>b<88>???????^Q^A??n?^PSQL?<8e>M?" [2008-02-11 06:44:11] DBUG fserve/fserve_add_client Adding client to file serving engine [2008-02-11 06:45:01] INFO main/main Icecast 2.3.1 server started Currently looking at status.xsl at my rogue webcaster there entry for this chap is thus (names changed to protect the innocent/guilty): Stream Title: Radio FM Stream Description: Radio FM Bitrate: 32 Stream Listeners: 0 Stream Genre: Various Stream URL: http://path.to.my.server:8000/radiofm.mp3 Current Song: ?r?uX??s?7_?n??GYF???<+R???V%??(:?)??oE??pX??!k?)~?w?+c5?2O?1f??GhE?2*??xC?6?LzFH??"??/*???H5????G??,?L?7M?f?Z?? Listen: Click to Listen The stream plays fine but the song title is obviously borked. I have only recently switched to this new server setup (FC8, 2.6.23.9-85.fc8) and my previous instance of Icecast was not vulnerable to this problem - could this be something like I don't have Unicode/UTF8 installed? As my previous Icecast installation was not vulnerable to this issue, I think there must be something that can be done server side to accommodate this webcaster who is sending us this 'broken' metadata. Many thanks in advance for your help. Chip Scooter