View Issue Details

IDProjectCategoryView StatusLast Update
0015691CentOS-7memcachedpublic2019-01-10 12:17
Reporterifettich 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Product Version7.5.1804 
Target VersionFixed in Version 
Summary0015691: bad start when using socket
DescriptionWith a /etc/sysconfig/memcached config like

#PORT="11211"
#OPTIONS="-l 127.0.0.1"
USER="memcached"
MAXCONN="1024"
CACHESIZE="256"
OPTIONS="-s /var/run/memcached/memcached.sock -a 0766 "

- which seems the proper one to use memcached with an Unix socket - memcached will start (using the commanline given in /usr/lib/systemd/system/memcached.service,
ExecStart=/usr/bin/memcached -u $USER -p $PORT -m $CACHESIZE -c $MAXCONN $OPTIONS)

obeying to command

/usr/bin/memcached -u memcached -p -m 256 -c 1024 -s /var/run/memcached/memcached.sock -a 0766

No error given, and memcached uses the Unix socket, as intended.

BUT: the missing port makes memcached use the default value for max memory, which is 64 MB. Instead of the intended 256 MB, memcached will run using only 64 MB.
Additional InformationChanging ExecStart to be
ExecStart=/usr/bin/memcached -u $USER -m $CACHESIZE -c $MAXCONN $OPTIONS
works fine for me, as a patch.
But I guess a proper patch would allow to not have to edit ExecStart within /usr/lib/systemd/system/memcached.service when modifying the sysconfig values.
TagsNo tags attached.
abrt_hash
URL

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-01-10 12:17 ifettich New Issue