Hi,
This question has appeared a few times on the forum, but I’m not sure a definite answer is available…
Sometimes I need to delete/rename/replace an FLV file that is in use by Wowza (because someone is watching it). When I try to do so, Windows obviously tells me that the file is in use by another application (possibly java.exe?).
Is there a procedure/software I can install or run that would allow me to “unlock” the file and perform these operations? Obviously, the end users who are watching that file would receive some sort of error… but that’s not a problem. In case of a mistake or an urgent need for a change, having an error message is better than watching a 1-hour video that is altogether wrong.
Thanks in advance for your help.
Helder Conde
I am not sure how well it works but I believe this will do it:
http://download.cnet.com/Unlocker/3000-2248_4-10493998.html
Charlie
Windows is very flaky in this regard. I might try Java 7 to see if it is better. I am pretty sure Wowza is not holding on to the file. You may also try a tool such as this to forcefully unlock the file:
http://download.cnet.com/Unlocker/3000-2248_4-10493998.html
Charlie
Has there been any progress on this issue?
I am recording live streams (FLV), and then allowing another client to play them back.
After a while (20 mins), I want to move the stream files into an archive folder.
I can guarantee that no users are watching the streams when this happens.
Unfortunately the files are still locked by Wowza.
I have tried calling stopMediaCasterStream (on the application instance) before moving … but still… files locked…
Any help appreciated, as this is now becoming a critical issue for me.
Thanks
Tom
ok… thanks a lot for that, it works. (cant believe I didn’t try earlier)
I am only developing on windows, but runninmg a linux server, and on Linux I can move the files moved just fine.
There’s also this module for stopping/starting streams which may be of some use to you: https://www.wowza.com/docs/how-to-set-up-a-command-line-interface-to-wowza-api
You could stop that particular stream, rename the file, then start it again. Probably preferable to deleting locked files which may have unexpected side effects, or at least an I/O error.