New Comment on Issue #github

[pcp:master] New Comment on Issue #118 reported pmDestroyContext: pthread_mutex_destroy(c_lock) failed: Device or resource busy, failed second try as well ( https://github.com/performancecopilot/pcp/issues/118 )
By fche ( https://github.com/fche ) :

Mark, the issue was always intermittent, so we're working backward from the symptoms (with the c_lock messages etc.), and don't have proof that this was the only cause of the symptoms. It's nice to eliminate the whole possibility though.

> 
> 
> 
> Also, is pmwebd supposed to support derived metrics?
> 
> 

In principle, a pmwebd client could ask for derived metrics, so "yes". But I bet that is only one possible path to trigger this problem.