Richard G
Verified User
Sorry to also bump this old thread, but I had the exact same problem this night after updating with yum.
I fixed it now by doing a ./build update, but is there any cause known so we can prevent this in the future?
Is it apr-util from Centos and can we safely remove that (yum remove apr-util) without doing harm to other things?
I only had this on the CB 2.0 servers with apache 2.4.x, not on the one running with CB 1.2. with 2.2.29.
I fixed it now by doing a ./build update, but is there any cause known so we can prevent this in the future?
Is it apr-util from Centos and can we safely remove that (yum remove apr-util) without doing harm to other things?
I only had this on the CB 2.0 servers with apache 2.4.x, not on the one running with CB 1.2. with 2.2.29.
Last edited: