Bug 1408314

Summary:	memcached.service results in Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service'
Product:	Red Hat OpenStack	Reporter:	Alex Schultz <aschultz>
Component:	memcached	Assignee:	hguemar
Status:	CLOSED ERRATA	QA Contact:	Shai Revivo <srevivo>
Severity:	low	Docs Contact:
Priority:	low
Version:	11.0 (Ocata)	CC:	agurenko, aludwar, apevec, jschluet, karlthered, lhh, mburns, mcornea, mhalas, slinaber, tcarlin
Target Milestone:	ga	Keywords:	Triaged
Target Release:	12.0 (Pike)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	memcached-1.4.39-2.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-13 20:57:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alex Schultz 2016-12-22 21:29:20 UTC

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:

Comment 1 Thom Carlin 2017-01-10 21:40:16 UTC

Also

Comment 2 Thom Carlin 2017-01-10 21:44:24 UTC

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'

Comment 3 Thom Carlin 2017-01-10 21:52:04 UTC

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.

Comment 4 Alex Schultz 2017-01-10 22:08:40 UTC

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.

Comment 5 Alex Schultz 2017-02-08 00:04:53 UTC

*** Bug 1396590 has been marked as a duplicate of this bug. ***

Comment 6 Haïkel Guémar 2017-08-04 21:38:30 UTC

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)

Comment 13 errata-xmlrpc 2017-12-13 20:57:54 UTC

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