Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] esmond issue after update (SElinux related)

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] esmond issue after update (SElinux related)


Chronological Thread 
  • From: Jon Clausen <>
  • To:
  • Subject: [perfsonar-user] esmond issue after update (SElinux related)
  • Date: Thu, 14 Sep 2017 11:56:50 +0200
  • Ironport-phdr: 9a23:qw0qxB9NHdfzkv9uRHKM819IXTAuvvDOBiVQ1KB40OwcTK2v8tzYMVDF4r011RmSDNWds6oMotGVmpioYXYH75eFvSJKW713fDhBt/8rmRc9CtWOE0zxIa2iRSU7GMNfSA0tpCnjYgBaF8nkelLdvGC54yIMFRXjLwp1Ifn+FpLPg8it2e2//57ebx9UiDahfLh/MAi4oQLNu8cMnIBsMLwxyhzHontJf+RZ22ZlLk+Nkhj/+8m94odt/zxftPw9+cFAV776f7kjQrxDEDsmKWE169b1uhTFUACC+2ETUmQSkhpPHgjF8BT3VYr/vyfmquZw3jSRMMvrRr42RDui9b9mRhHohikZKjA3827YhdBtg61Vux+hqABzzpTObY2JLvdyYKXQds4aS2pbWcZRUjRMDIe7b4sJEuEMI+JYoJPgp1sVsxS+AxSnCeTtyjBSmnD7xqs60+M7EQ7bwQwsBdQOv2rIrNjsMqoZTOO7zLHQwDndc/9axSrx5Y3Jfx86vf2BWLF9fM/PxUQqEg7JkEmcpZL9Mz+IyugAt3KX4/d8We+vkWIrth19rzm1yssxloXEgJ8exEre+iVj2ok1IMW1SE5lbt6gF5tdrz+VO5JzQsw4QmFovCg6yrwCuZ6nYicK0ogrywDFZ/ycboiI5AzsVPqLLTdjmn1pYLO/hxCs/ki80uDwSNW43EpXoidAk9TDrWwB2hnQ58WCVPdw+0Ks1SiT2wzN8u1EJFo7lavfK54v2L4wkZ8TvFzBHiDshEr7l6mWdkI++ue19uTreLPmqYGAN4NskAHxLrwumtCjAeQ/KgUOR3aU+f6y1L34+k35Rq9FjucvnqnEq5DVO94bq7W9Aw9UyYYj9w2/Aym83NQZm3kHMExKeAiBj4f3J1HCPur0AumijFSxw39XwKXeM6fvGZLLJ2KGjazsZ5587VJR0gw+0YoZ6p5JWZ8bJ/emeEj3/PfcBwIiPgr8l+TuA/170ZkSRCSJD7PPY/CaikOB+u96e7rEX4QSojuoc/U=

Hi

Our measurement archive is installed from the CentOS 7 *.iso, with perfSonar
components installed from the internet2 repo.

I chose to leave SELinux active/enforcing, which is actually not causing
many problems, generally - to my pleasant surprise.

The system has yum-cron installed, so updates happen 'whenever'.

Early this morning there were a lot of package updates, and subsequently the
toolkit URL was unable to load test results, showing an 'internal server
error' message instead.

The cause turned out to be a change in SELinux 'type' on a couple of log
files, which resulted in permission denied errors in
/var/log/httpd/error_log

[Thu Sep 14 10:59:19.652856 2017] [:error] [pid 14147] [remote
109.105.99.90:132
] ValueError: Unable to configure handler 'esmond_handler': [Errno 13]
Permission denied: '/var/log/esmond/esmond.log'

The 'cure' would have been to change object type using chcon, or as I did:
move the log file out of the way and restart apache.

The object type change can be seen here:
[jac@psma01 ~]$ ls -Z /var/log/esmond/esmond.log*
-rw-r--r--. apache apache system_u:object_r:httpd_log_t:s0
/var/log/esmond/esmond.log
-rw-r--r--. apache apache system_u:object_r:var_log_t:s0
/var/log/esmond/esmond.log.2017-08-21


This mail is mostly a 'heads up' to other people running the measurement
archive under SELinux, but I guess the info may be relevant to the perfSonar
packagers too.

Should I submit the info somwhere?

br
/jon
--

Attachment: signature.asc
Description: PGP signature



  • [perfsonar-user] esmond issue after update (SElinux related), Jon Clausen, 09/14/2017

Archive powered by MHonArc 2.6.19.

Top of Page