View previous topic :: View next topic |
Author |
Message |
djrvencode
Joined: 13 Jun 2011 Posts: 12
|
Posted: Thu Mar 29, 2012 8:29 pm Post subject: Icecast 2.3.2-kh31.13 - Centova and Log files |
|
|
Hi, first of all I have to clarify I'm using Icecast 2.3.2-kh31.13 along centova cast and broadcasting one 48kbps aac+ stream to jwplayer 4.3 version. The problem is the following:
Centova is reporting constantly a bunch of logs using some useful space on server disk, I'm talking about almost 100MBytes in 4 days, the data it logs is the following(see below). It does that even without any live broadcast! The only way to stop it doing that is turning off icecast server. I guess Icecast is who is reporting such quantity data and centova just report it, but I don't know if that is the normal behaviour of icecast, I'm a newbie in this icecast world.
THESE ARE UNDER CENTOVA'S ERROR LOG:
[2012-03-29 12:33:48] DBUG stats/modify_node_event update "global" banned_IPs (0)
[2012-03-29 12:33:48] DBUG stats/modify_node_event update "global" outgoing_kbitrate (0)
[2012-03-29 12:33:49] DBUG stats/modify_node_event update "global" banned_IPs (0)
[2012-03-29 12:33:49] DBUG stats/modify_node_event update "global" outgoing_kbitrate (0)
[2012-03-29 12:33:49] DBUG stats/modify_node_event update "/stream1" outgoing_kbitrate (0)
[2012-03-29 12:33:49] DBUG stats/modify_node_event update "/stream1" incoming_bitrate (48064)
[2012-03-29 12:33:49] DBUG stats/modify_node_event update "/stream1" total_bytes_read (27674403)
[2012-03-29 12:33:49] DBUG stats/modify_node_event update "/stream1" total_bytes_sent (7989248)
[2012-03-29 12:33:49] DBUG stats/modify_node_event update "/stream1" total_mbytes_sent (7)
[2012-03-29 12:33:49] DBUG stats/modify_node_event update "/stream1" queue_size (65018)
THESE ARE UNDER CENTOVA'S ACCESS LOG:
208.85.xxx.xxx - - [29/Mar/2012:12:15:02 -0400] "GET /centovacast.xsl HTTP/1.1" 200 495 "-" "HTTPRetriever/1.1.11" 0
208.85.xxx.xx - - [29/Mar/2012:12:15:08 -0400] "GET /centovacast.xsl HTTP/1.1" 200 496 "-" "HTTPRetriever/1.1.11" 0
208.85.xxx.xxx - - [29/Mar/2012:12:16:13 -0400] "GET /centovacast.xsl HTTP/1.1" 200 496 "-" "HTTPRetriever/1.1.11" 0
190.204.xxx.xxx - source [29/Mar/2012:12:16:14 -0400] "GET /admin/metadata?mode=updinfo&mount=%2Fstream1&song=Roy%20Orbison%20%2D%20You%20Got%20It&url=%26artist%3DRoy%2520Orbison%26title%3DYou%2520Got%2520It%26album%3DThe%2520Very%2520Best%2520Of%2520Roy%2520Orbison%26duration%3D212651%26songtype%3DS%26overla" 200 184 "-" "Mozilla/3.0 (compatible)" 0
208.85.xxx.xxx - - [29/Mar/2012:12:17:18 -0400] "GET /centovacast.xsl HTTP/1.1" 200 489 "-" "HTTPRetriever/1.1.11" 0
208.85.xxx.xxx - - [29/Mar/2012:12:18:23 -0400] "GET /centovacast.xsl HTTP/1.1" 200 489 "-" "HTTPRetriever/1.1.11" 0
208.85.xxx.xxx - - [29/Mar/2012:12:19:28 -0400] "GET /centovacast.xsl HTTP/1.1" 200 489 "-" "HTTPRetriever/1.1.11" 0
Well thanks in advance I'd appreciate your advice on this! |
|
Back to top |
|
|
greatmenjmt
Joined: 18 Jan 2012 Posts: 23
|
Posted: Fri Apr 20, 2012 3:32 am Post subject: |
|
|
look like somebody or a script you have is accessing to centovacast.xsl too frequently... try to post this on centova forums instead... and please if you get some info post it here so we all can learn. |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Fri Apr 20, 2012 12:30 pm Post subject: |
|
|
Firstly, as a normal user you do not need log level 4 on, that is debug logging so tends to be rather noisy on the logs, useful to me and others for diagnosis but generally others no. Change log level to 2 or maybe 3.
The /centovacast.xsl is a regular request check that the panel does to make sure the server/stream is alive. icecast just reacts to that request nothing more.
karl. |
|
Back to top |
|
|
djrvencode
Joined: 13 Jun 2011 Posts: 12
|
Posted: Fri Apr 20, 2012 12:34 pm Post subject: |
|
|
Thanks guys for your opinion, so karl, what would be the correct log level as normal user? thanks! |
|
Back to top |
|
|
greatmenjmt
Joined: 18 Jan 2012 Posts: 23
|
Posted: Mon May 21, 2012 2:26 am Post subject: |
|
|
i would use 2 or 3, but now im using centova a bit more and i can say that centova itself will process and delete the old logs so you dont have to worry too much about it... |
|
Back to top |
|
|
|