Jump to content
Welcome to our new Citrix community!
  • 0

stop and deleting log file opcualds.log file from inside my VM



Dear all,

         VM : windows server 2008 R2 Enterprise, C drive near full , opcualds.log is 12GB size .

        some guys suggest to open config file ualds.ini and modify log level to error to stop logging process 

         and now i want to release some volume by deleting this log file opcualds.log

        my question : your suggestion to delete this log file without affecting services on this VM.








Link to comment

4 answers to this question

Recommended Posts

  • 0

Dealing with the log file size issue isn't going to make this stop; I would suggest reviewing exactly why it is filling up to find out what's causing this. Deleting a log can lead to issues; if you want to zero it out you can run "cat /dev/null > /path-to-directory/opcualds.log" which won't delete the original file. Some log processes will not automatically re-create files, so you have to be careful.

Link to comment
  • 0

The log file will be 'locked' by the running Service, on Windows machines, you must release the handle to the file from the running process that has the file locked.  The safest way to do this is to stop the running service.  Delete the file or it's content.   As the vendor recommends, change the logging level to reduce the rate of growth on that logfile. 

Link to comment
  • 0

thanks topias , thanks dclark116

so tobias,you want me to write this command:"cat /dev/null > /path-to-directory/opcualds.log" to console of xenserver to deleting the log? ,i want to be sure from my taken  actions ,so you mean it must be appeared in files directory from console also


Link to comment
  • 0

You could do that, as well, to zero out the file contents. Some rotation scripts will copy the original to a backup log and instead of deleting ad re-creating the log file, just cat the null device to that file. The reason for that is that some logging engines freak out if they were writing to a file and suddenly, the file disappears; in that case, the logging has to be temporarily suspended, a "touch" command run to create a new empty file, and the logging then resumed to that file.



Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...