Hi @Geoff Burke i did a little write up for another case a while ago, hope this helps!
Happy to elaborate further if needed
Hi @Geoff Burke i did a little write up for another case a while ago, hope this helps!
Happy to elaborate further if needed
I knew there were some smart folks here I remember seeing that but will re-read. By the way my mutex has this: “PM Error Failed to rescan service provider Error: Failed to wait mutex “
Failed to wait mutex. Perhaps the mutex was having a slow day or something and the bus left without him?
So that’ll be some single-threaded code that has to complete before the next task, but instead it’s timed out based on failing to wait.
Makes sense as “I’ve tried to rescan, I can’t do anything with the data until I’ve got the scan complete, and I failed to wait because some timeout threshold or other such parameter was exceeded”
Surrounding data might provide further insights into the problem.
That makes sense. The mutex in this case could just be.. “I timed out” but Veeam want it to sound sexy so they through in the mutex part. I mean not a bad idea, I can say to my boss, there was a problem with the Mutex and… the conversation will end quickly :)
Have you tried saying “sorry boss would love to look at this problem but we need the PayReviewMutex to complete first”?