Hello.
I can see in the docs a method to roll over logs, but I don’t see anything on purging old logs. Is that possible using wowza or must I use an external script for that?
Hello.
I can see in the docs a method to roll over logs, but I don’t see anything on purging old logs. Is that possible using wowza or must I use an external script for that?
There is not really any built in way of purging old files. You will need to do it with an external script.
I don’t think it will take too well to removing the log file. I have tried moving the current log file before and it doesn’t complain but then it doesn’t create a new one either. http://nicerhttpd.blogspot.com/2008/11/logrotate-and-log4j.html This gives a example on how to use both.
We have access and error logs building up on our server - can we not just delete the ones a few months old we do not use?
Also (we re-configured to use sawmill) is this expected:
user/local/wowzamediaserver/logs - access daily logs (about 300 Megs each), error logs
user/local/wowzamediaserver/logs/defaultVHost - access daily logs (about 200 Megs each, error logs and stats logs (probably for Sawmill)
user/local/wowzamediaserver/logs/defaultVHost/myStreamingDirectory - access daily logs (about 15 megs each), error logs and stats logs
Should we have so many different logs going on?
Thanks.
Looks like you have configured /conf/log4j.properties to do VHost and Application logging. These are commented out by default, so someone enabled them on that server. You can easily comment those sections out.
It’s up to you how long to keep logs. Wowza does not need logs for operations. You can disable all logging if you wanted to.
Richard
If I use logrotate to manage the logs rather than use the internal Wowza mechansim, do I need to restart Wowza or will it happily notice the log file has disappeared and create a new one? Or is there a way to get Wowza to recreate the log file without restarting the app and disrupting currently connected users?