Since the script once worked and hasn't changed, looking to the operating environment for a problem will probably be more fruitful. It sounds like you've upgraded to a new version of the operating system and something is configured in a slightly different way. Perhaps there is now a long running process that has the log file in question locked so no other process, such as this perl script, may operate on it.

Check out : Rename unreliable on Windows