| View previous topic :: View next topic |
| Author |
Message |
greatmenjmt
Joined: 18 Jan 2012
Posts: 23
|
 Posted: Mon Feb 13, 2012 7:57 pm Post subject: Icecast 2.3.2-kh31 logs exceed maximum log size |
 |
|
i have a centos vps for 1 month now and my Icecast 2.3.2-kh31 logs exceed maximum log size and i activated the log archive but this didn't make any change.
here is some fragments of my configure file:
| Code: |
<limits>
<clients>1600</clients>
<sources>100</sources>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>30</source-timeout>
<!-- same as burst-on-connect, but this allows for being more
specific on how much to burst. Most people won't need to
change from the default 64k. Applies to all mountpoints -->
<burst-size>131070</burst-size>
<!--
<max-bandwidth>80M</max-bandwidth>
-->
</limits>
<listen-socket>
<port>80</port>
<!-- <bind-address>127.0.0.1</bind-address> -->
<!-- use <shoutcast-mount> in here to implicitly define port n+1 -->
</listen-socket>
<mount>
<mount-name>/primero</mount-name>
<password>**********</password>
<max-listeners>64</max-listeners>
<stream-url>http://www.******.***</stream-url>
</mount>
<mount>
<mount-name>/segundo</mount-name>
<password>**********</password>
<max-listeners>64</max-listeners>
<stream-url>http://www.******.***</stream-url>
<hidden>1</hidden>
</mount>
<mount>
<mount-name>/tercero</mount-name>
<password>**********</password>
<max-listeners>64</max-listeners>
<fallback-mount>/segundo</fallback-mount>
<fallback-override>1</fallback-override>
<stream-url>http://www.******.***</stream-url>
</mount>
<mount>
<mount-name>/cuarto</mount-name>
<password>**********</password>
<max-listeners>64</max-listeners>
<stream-url>http://www.******.***</stream-url>
<hidden>1</hidden>
</mount>
<mount>
<mount-name>/quinto</mount-name>
<password>**********</password>
<max-listeners>64</max-listeners>
<fallback-mount>/cuarto</fallback-mount>
<fallback-override>1</fallback-override>
<stream-url>http://www.******.***</stream-url>
</mount>
<mount>
<mount-name>/sexto</mount-name>
<password>**********</password>
<max-listeners>64</max-listeners>
<stream-url>http://www.**********.***</stream-url>
<hidden>1</hidden>
</mount>
<mount>
<mount-name>/septimo</mount-name>
<password>**********</password>
<max-listeners>64</max-listeners>
<fallback-mount>/sexto</fallback-mount>
<fallback-override>1</fallback-override>
<stream-url>http://www.******.***</stream-url>
</mount>
<mount>
<mount-name>/octavo</mount-name>
<password>**********</password>
<max-listeners>64</max-listeners>
<stream-url>http://www.**********.***</stream-url>
</mount>
<mount>
<mount-name>/aparte1</mount-name>
<password>**********</password>
<max-listeners>15</max-listeners>
<hidden>1</hidden>
</mount>
<mount>
<mount-name>/noveno</mount-name>
<password>**********</password>
<max-listeners>300</max-listeners>
<stream-url>http://******.***</stream-url>
</mount>
<mount>
<mount-name>/aparte9</mount-name>
<password>**********</password>
<max-listeners>3</max-listeners>
<hidden>1</hidden>
</mount>
<mount>
<mount-name>/aparte2</mount-name>
<password>**********</password>
<max-listeners>15</max-listeners>
<hidden>1</hidden>
</mount>
<mount>
<mount-name>/decimo</mount-name>
<password>**********</password>
<max-listeners>64</max-listeners>
<stream-url>http://www.******.***</stream-url>
</mount>
<paths>
<!-- basedir is only used if chroot is enabled -->
<basedir>/usr/local/share/icecast</basedir>
<!-- Note that if <chroot> is turned on below, these paths must both
be relative to the new root, not the original root -->
<logdir>/usr/local/var/log/icecast</logdir>
<webroot>/usr/local/share/icecast/web</webroot>
<adminroot>/usr/local/share/icecast/admin</adminroot>
<!-- <pidfile>/usr/local/share/icecast/icecast.pid</pidfile> -->
<!-- <ssl-certificate>/usr/local/share/icecast/icecast.pem</ssl-certificate> -->
<!-- <deny-ip>/path/to/file-with-IPs</deny-ip> -->
<!-- <allow-ip>/path/to/file-with-IPs</allow-ip> -->
<!-- <deny-agents>/path/to/file-with-useragents</deny-agents> -->
<!-- location of mime types files used for file serving -->
<!-- <mime-types>/etc/mime.types</mime-types> -->
<!-- Aliases: treat requests for 'source' path as being for 'dest' path
May be made specific to a port or bound address using the "port"
and "bind-address" attributes.
-->
<alias source="/" dest="/index.html"/>
<!-- Aliases: can also be used for simple redirections as well,
this example will redirect all requests for http://server:port/ to
the status page
-->
<alias source="/" dest="/index.html"/>
</paths>
<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<!-- <accesslog_ip>0<accesslog_ip> -->
<playlistlog>playlist.log</playlistlog>
<loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
<logsize>5000</logsize> <!-- Max size of a logfile -->
<!-- If logarchive is enabled (1), then when logsize is reached
the logfile will be moved to [error|access|playlist].log.DATESTAMP,
otherwise it will be moved to [error|access|playlist].log.old.
Default is non-archive mode (i.e. overwrite)
-->
<logarchive>1</logarchive>
</logging>
<security>
<chroot>0</chroot>
<changeowner>
<user>icecast</user>
<group>nogroup</group>
</changeowner>
</security>
</icecast> |
please let me know if im doing something wrong. |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Tue Feb 14, 2012 1:30 am Post subject: |
|
|
That would tend to indicate that the internal size value is incorrect, not sure of a case leading to that as the size is queried from the file when it is opened and then increased as each line is added.
I could query those from a core file from a debug build but I suspect you don't have that yet and those details are not exposed externally. Unless I've screwed up the backward compatible option for setting the 5Meg limit (and icecast is aware of it) then should it should trigger, try reloading the xml (HUP) and see if the file is cycled then
karl. |
|
| Back to top |
|
|
greatmenjmt
Joined: 18 Jan 2012
Posts: 23
|
| Posted: Tue Feb 14, 2012 8:20 pm Post subject: |
|
|
| karlH wrote: |
That would tend to indicate that the internal size value is incorrect, not sure of a case leading to that as the size is queried from the file when it is opened and then increased as each line is added.
I could query those from a core file from a debug build but I suspect you don't have that yet and those details are not exposed externally. Unless I've screwed up the backward compatible option for setting the 5Meg limit (and icecast is aware of it) then should it should trigger, try reloading the xml (HUP) and see if the file is cycled then
karl. |
i manually shutdown the icecast process 6 days ago cause the logs was so big that the server was lagged and now the access log is now 9.2 Mb, the error log is 6.4 Mb and counting... i reload the xml and nothing happen... what else should i do? all the config file fragments are right? |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Wed Feb 15, 2012 12:56 am Post subject: |
|
|
I tried the same options here and the cycle triggered, you can of course renamed and HUP it manually, it doesn't require to actually stop the server. I'm wondering whether there is some issue with the permissions for the log directory/file seeing that you are using changeowner. renaming the log file and sending a HUP signal would be enough of a test to see if a new file is created.
karl. |
|
| Back to top |
|
|
greatmenjmt
Joined: 18 Jan 2012
Posts: 23
|
| Posted: Wed Feb 15, 2012 12:38 pm Post subject: |
|
|
| karlH wrote: |
...I'm wondering whether there is some issue with the permissions for the log directory/file seeing that you are using changeowner...
karl. |
this reminds me to check directory permissions and after i set it properly it automatically triggered... 
my fault, but i learned something and hope forum visitors will from this topic.
thanks a lot karl and keep up the good work. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
