Writing to log failed from time to time

[abaganuv]

I have a list of errors that I print to the console and to the log and I get this errors, that means that not all the rows are printed to the log. Tried to add a sleep for 300 millisecond but still have the issue

Add-Content : Stream was not readable.
At C:\Program Files\WindowsPowerShell\Modules\TUN.Logging\1.1.2\TUN.Logging.psm1:861 char:17

• ... Add-Content -Path $script:LogFile -Value $Message -NoNewl ...

•             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidArgument: (\g...22-15-04-56.log:String) [Add-Content], ArgumentException
  • FullyQualifiedErrorId : GetContentWriterArgumentError,Microsoft.PowerShell.Commands.AddContentCommand

[echalone]

What were the parameters you called Start-Log and (I persume) Write-HostLog with (or whatever function you called when that error happened)?

[abaganuv]

I called to Write-ErrorLog
I have more than 600 entries in the list and at least 10 getting this error

[abaganuv]

Any idea?
I googled it and it seems someone solved it with -force
Hi, I found that adding -force option to the end of add-content seemed to resolve my issues with "Stream was not readable".
This is something I can edit? the module is editable? or you should make the changes?

[echalone]

Hi, that would mean that your log files are read-only for some reason?
Can you give me the parameters with which you are calling Start-Log and Write-ErrorLog? Or under what circumstances this errors happen? It's hard to analyze what the problem is without any information ;)

I would need to be able to recreate this behaviour to fix it. So if you could write down a scenario or script with which this would happen I might be able to help you or fix a potential problem.