Red Hat Bugzilla – Bug 1408314
memcached.service results in Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service'
Last modified: 2018-02-05 14:02:04 EST
Description of problem: I noticed during the installation of a controller node, that the following warnings were being outputted repeatedly: Dec 22 21:24:11 host-192-168-24-7 systemd: [/usr/lib/systemd/system/memcached.service:43] Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service' It appears that we have an invalid setting in the default memcached.service file. Version-Release number of selected component (if applicable): memcached-1.4.33-2.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install memcached-1.4.33-2.el7.x86_64 2. Reload systemd 3. See logs Actual results: No warnings should be emitted Expected results: Additional info:
Also
Also seeing this error in RHOSP 10 (QCI 1.1): Jan 10 13:25:40 <hostname> systemd: Started memcached daemon. Jan 10 13:25:40 <hostname> systemd: Starting memcached daemon... Jan 10 13:25:40 <hostname> systemd: Reloading. Jan 10 13:25:40 <hostname> systemd: [/usr/lib/systemd/system/memcached.service:43] Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service'
Per https://bugs.launchpad.net/tripleo/+bug/1638646/comments/7 "Fix was included in memcached-1.4.33-2 https://cbs.centos.org/koji/buildinfo?buildID=13784" but yum list is showing "1.4.33-2.1.el7ost" from the qciooo 1.1 repo.
So that tripleo bug is different than this. I believe this bug about the "Unknown lvalue" was a side effect from the update to 1.4.33. The message in the logs seems to be only cosmetic as it still functions, but may lead to operators incorrectly assuming there are issues with memcached. 1.4.33-1 which the LP bug 1638646 was a larger issue as memcached did not start when maxconns was > 1024.
*** Bug 1396590 has been marked as a duplicate of this bug. ***
Fixed in RDO by the following commit: https://github.com/rdo-common/memcached/commit/6d37b6bb5f8b7f38d97a1d15073fac91b72cc5d1 Note that it updates memcached to 1.4.39 (bugfixes release)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462