sysctl: permission denied on key 'vm.max_map_count' - OpenVZ Elasticsearch 0.90.9 compatibility issue #4978

bline79 · 2014-01-31T22:52:05Z

Hello,

Elasticsearch 0.90.9 and higher do not work with openvz (tested with debian wheezy i386) with the following error showing on startup:

Starting ElasticSearch Server:sysctl: permission denied on key 'vm.max_map_count'

spinscale · 2014-02-03T09:47:17Z

Hey,

can you please check, if the process started anyway? It should have been. The error is just a permission problem due to your VM, but should not prevent elasticsearch from starting usually.

dmikhaylov · 2014-02-24T13:57:18Z

I've got the same issue, and on my VM it's not starting.

spinscale · 2014-02-24T14:01:22Z

can you add set -x to the elasticsearch init script and paste the output from /etc/init.d/elasticsearch start here?

dmikhaylov · 2014-02-24T14:13:35Z

do you mean /etc/init.d/elasticsearch start set -x?

spinscale · 2014-02-24T14:55:26Z

sorry for not being clear. You can do the following: Open /etc/init.d/elasticsearch in your favourite editor and change the current setup

#!/bin/sh
#

to

#!/bin/sh
set -x
#

Then run /etc/init.d/elasticsearch start and copy paste all that output into this ticket. You might want to comment out or remove that line again after that, so you do not get his verbose output all the time.

Thanks a lot for helping!

dmikhaylov · 2014-02-24T16:49:29Z

PATH=/bin:/usr/bin:/sbin:/usr/sbin
NAME=elasticsearch
DESC='ElasticSearch Server'
DEFAULT=/etc/default/elasticsearch
++ id -u
'[' 0 -ne 0 ']'
. /lib/lsb/init-functions
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ . /etc/lsb-base-logging.sh
+++ LOG_DAEMON_MSG=
'[' -r /etc/default/rcS ']'
. /etc/default/rcS
++ TMPTIME=0
++ SULOGIN=no
++ DELAYLOGIN=no
++ UTC=yes
++ VERBOSE=no
++ FSCKFIX=no
ES_USER=elasticsearch
ES_GROUP=elasticsearch
JDK_DIRS='/usr/lib/jvm/java-7-oracle /usr/lib/jvm/java-7-openjdk /usr/lib/jvm/java-7-openjdk-amd64/ /usr/lib/jvm/java-7-openjdk-armhf /usr/lib/jvm/java-7-openjdk-i386/ /usr/lib/jvm/java-6-sun /usr/lib/jvm/java-6-openjdk /usr/lib/jvm/java-6-openjdk-amd64 /usr/lib/jvm/java-6-openjdk-armhf /usr/lib/jvm/java-6-openjdk-i386 /usr/lib/jvm/default-java'
for jdir in '$JDK_DIRS'
'[' -r /usr/lib/jvm/java-7-oracle/bin/java -a -z '' ']'
for jdir in '$JDK_DIRS'
'[' -r /usr/lib/jvm/java-7-openjdk/bin/java -a -z '' ']'
for jdir in '$JDK_DIRS'
'[' -r /usr/lib/jvm/java-7-openjdk-amd64//bin/java -a -z '' ']'
for jdir in '$JDK_DIRS'
'[' -r /usr/lib/jvm/java-7-openjdk-armhf/bin/java -a -z '' ']'
for jdir in '$JDK_DIRS'
'[' -r /usr/lib/jvm/java-7-openjdk-i386//bin/java -a -z '' ']'
for jdir in '$JDK_DIRS'
'[' -r /usr/lib/jvm/java-6-sun/bin/java -a -z '' ']'
for jdir in '$JDK_DIRS'
'[' -r /usr/lib/jvm/java-6-openjdk/bin/java -a -z '' ']'
JAVA_HOME=/usr/lib/jvm/java-6-openjdk
for jdir in '$JDK_DIRS'
'[' -r /usr/lib/jvm/java-6-openjdk-amd64/bin/java -a -z /usr/lib/jvm/java-6-openjdk ']'
for jdir in '$JDK_DIRS'
'[' -r /usr/lib/jvm/java-6-openjdk-armhf/bin/java -a -z /usr/lib/jvm/java-6-openjdk ']'
for jdir in '$JDK_DIRS'
'[' -r /usr/lib/jvm/java-6-openjdk-i386/bin/java -a -z /usr/lib/jvm/java-6-openjdk ']'
for jdir in '$JDK_DIRS'
'[' -r /usr/lib/jvm/default-java/bin/java -a -z /usr/lib/jvm/java-6-openjdk ']'
export JAVA_HOME
ES_HOME=/usr/share/elasticsearch
MAX_OPEN_FILES=65535
LOG_DIR=/var/log/elasticsearch
DATA_DIR=/var/lib/elasticsearch
WORK_DIR=/tmp/elasticsearch
CONF_DIR=/etc/elasticsearch
CONF_FILE=/etc/elasticsearch/elasticsearch.yml
MAX_MAP_COUNT=65535
'[' -f /etc/default/elasticsearch ']'
. /etc/default/elasticsearch
PID_FILE=/var/run/elasticsearch.pid
DAEMON=/usr/share/elasticsearch/bin/elasticsearch
DAEMON_OPTS='-p /var/run/elasticsearch.pid -Des.default.config=/etc/elasticsearch/elasticsearch.yml -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/var/lib/elasticsearch -Des.default.path.work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch'
export ES_HEAP_SIZE
export ES_HEAP_NEWSIZE
export ES_DIRECT_SIZE
export ES_JAVA_OPTS
test -x /usr/share/elasticsearch/bin/elasticsearch
case "$1" in
checkJava
'[' -x /usr/lib/jvm/java-6-openjdk/bin/java ']'
JAVA=/usr/lib/jvm/java-6-openjdk/bin/java
'[' '!' -x /usr/lib/jvm/java-6-openjdk/bin/java ']'
'[' -n '' -a -z '' ']'
log_daemon_msg 'Starting ElasticSearch Server'
'[' -z 'Starting ElasticSearch Server' ']'
log_use_fancy_output
TPUT=/usr/bin/tput
EXPR=/usr/bin/expr
'[' -t 1 ']'
'[' xxterm '!=' x ']'
'[' xxterm '!=' xdumb ']'
'[' -x /usr/bin/tput ']'
'[' -x /usr/bin/expr ']'
/usr/bin/tput hpa 60
/usr/bin/tput setaf 1
'[' -z ']'
FANCYTTY=1
case "$FANCYTTY" in
true
/usr/bin/tput xenl
++ /usr/bin/tput cols
COLS=80
'[' 80 ']'
'[' 80 -gt 6 ']'
++ /usr/bin/expr 80 - 7
COL=73
log_use_plymouth
'[' n = y ']'
plymouth --ping
printf ' * Starting ElasticSearch Server '
- Starting ElasticSearch Server ++ /usr/bin/expr 80 - 1
/usr/bin/tput hpa 79
+ printf ' '
++ pidofproc -p /var/run/elasticsearch.pid elasticsearch
++ local pidfile line i pids= status specified pid
++ pidfile=
++ specified=
++ OPTIND=1
++ getopts p: opt
++ case "$opt" in
++ pidfile=/var/run/elasticsearch.pid
++ specified=1
++ getopts p: opt
++ shift 2
++ base=elasticsearch
++ '[' '!' 1 ']'
++ '[' -n /var/run/elasticsearch.pid -a -r /var/run/elasticsearch.pid ']'
++ read pid
++ '[' -n 16987 ']'
+++ kill -0 16987
++ ps 16987
++ return 1
pid=
'[' -n '' ']'
mkdir -p /var/log/elasticsearch /var/lib/elasticsearch /tmp/elasticsearch
chown elasticsearch:elasticsearch /var/log/elasticsearch /var/lib/elasticsearch /tmp/elasticsearch
touch /var/run/elasticsearch.pid
chown elasticsearch:elasticsearch /var/run/elasticsearch.pid
'[' -n 65535 ']'
ulimit -n 65535
'[' -n '' ']'
'[' -n 65535 ']'
sysctl -q -w vm.max_map_count=65535
error: permission denied on key 'vm.max_map_count'
start-stop-daemon --start -b --user elasticsearch -c elasticsearch --pidfile /var/run/elasticsearch.pid --exec /usr/share/elasticsearch/bin/elasticsearch -- -p /var/run/elasticsearch.pid -Des.default.config=/etc/elasticsearch/elasticsearch.yml -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/var/lib/elasticsearch -Des.default.path.work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch
log_end_msg 0
'[' -z 0 ']'
'[' 73 ']'
'[' -x /usr/bin/tput ']'
log_use_plymouth
'[' n = y ']'
plymouth --ping
printf '\r'
/usr/bin/tput hpa 73
+ '[' 0 -eq 0 ']'
echo '[ OK ]'
[ OK ]
return 0
exit 0

spinscale · 2014-02-24T17:21:49Z

can you run ps p $(cat /var/run/elasticsearch.pid) - this actually looks as if elasticsearch was started...

dmikhaylov · 2014-02-25T13:22:36Z

Returns just header, i've tried service elasticsearch status and it says * elasticsearch is not running.

spinscale · 2014-02-25T14:29:27Z

Can you make sure elasticsearch does not run, and try this on the commandline (as root!):

touch /var/run/elasticsearch.pid
chown elasticsearch:elasticsearch /var/run/elasticsearch.pid
start-stop-daemon -v --start --user elasticsearch -c elasticsearch --pidfile /var/run/elasticsearch.pid --exec /usr/share/elasticsearch/bin/elasticsearch -- -p /var/run/elasticsearch.pid -Des.default.config=/etc/elasticsearch/elasticsearch.yml -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/var/lib/elasticsearch -Des.default.path.work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch

and paste the output here?

dmikhaylov · 2014-02-25T17:24:38Z

{0.90.8}: Initialization Failed ...

ElasticSearchIllegalStateException[Failed to obtain node lock, is the following location writable?: [/var/data/elasticsearch/hostname]]
IOException[failed to obtain lock on /var/data/elasticsearch/hostname/nodes/49]
IOException[Cannot create directory: /var/data/elasticsearch/hostname/nodes/49]
Turns out I just forgot to create /var/data directory. Now everything works. Thank you, @spinscale.

spinscale · 2014-02-26T07:32:07Z

@empirik One last question: Did this message also occur in the log file at /var/log/elasticsearch or was it just printed to stdout? Would be awesome if you could check it!

dmikhaylov · 2014-02-26T18:16:14Z

@spinscale I don't see this message in logs.

derEremit · 2014-03-16T23:53:59Z

Just for the record. Getting same error on startup in openvz, but elasticsearch runs without problems for now. A bit irritating as normaly a service start error means the service won't run. As opposed to a warning.
I expect without correct vm.max_map_count I should expect "only" performace problems?

spinscale · 2014-04-25T19:51:32Z

I dont know openvz enough, but not setting this setting can also result in lucene exceptions and indexing problems, it is not only about performance here - I dont how openvz is handling this. Can you get us any insight here @derEremit?

13h3r · 2014-05-12T02:07:15Z

Got the same on openvz

kritik · 2014-05-14T08:53:35Z

I see the same message on big index but after allocating more memmory elasticsearch starts at least :) Using OpenVZ too and elasticsearch 1.1.1.

idanov · 2014-06-03T13:00:04Z

Got the same on OpenVZ and elasticsearch 1.2.0.

r0mdau · 2014-06-10T21:59:03Z

Got the same on OpenVZ and elasticsearch 1.2.0
Template : debian-7.0-x86_64.tar.gz
Host Server : Proxmox 3.1-21

derEremit · 2014-06-11T14:58:31Z

Basically openvz does not allow modifications of kernel parameters as these would affect the host and every other guest machine.
I think that setting should be removed from init scripts and put in a README.
The init script could check for the correct setting and output a warning but not set these kernel parameters itself!

joke2k · 2014-06-26T13:23:59Z

👍

scamianbas · 2014-07-02T17:51:44Z

Hi all,
kinda newbie here.
I'm using Proxmox, Ubuntu OpenVZ container, Elasticsearch 1.2.1.
I had the same service starting issues and I fixed that by removing the "-d" option in DAEMON_OPTS (a directory path shoud have been provided here)
Also I changed the line
if [ -n "$MAX_MAP_COUNT" ]
with
if [ -n "$MAX_MAP_COUNT" ] && [ ! -f /proc/sys/vm/max_map_count ]
to address the unwanted sysctl issue.
Hope it helps.

adeleglise · 2014-08-10T13:58:01Z

Hi all,

Thanks to scamianbas for his tips, I tested this on proxmox 3.2-4, debian7-x64 template, works like a charm !

Thanks to the elasticsearch guys too for this great piece of software ;)

andykillen · 2014-08-12T10:28:36Z

FYI: fresh install of Unbuntu 12.4 with elastic search 1.3.1 over the top, following this Gist (easy way) for install https://gist.github.com/wingdspur/2026107

I get the error

Starting Elasticsearch Server
error: permission denied on key 'vm.max_map_count'

when I do a ps check, I get

ps p $(cat /var/run/elasticsearch.pid)
PID TTY STAT TIME COMMAND
8246 ? Sl 0:08 /usr/lib/jvm/java-7-openjdk-i386//bin/java -Xms256m -Xmx1g -Xss256k -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX

and finally when doing "service elasticsearch status"

it says it is running.

So the error has a slightly different prefix (error: and not sysctl:) but as with other information above it is not stopping the server. If needed I have the screen output with set -x in the elasticsearch config file.

grepwood · 2014-09-02T14:29:43Z

I'm having the same issue on CentOS 6.5 with elasticsearch 1.3.2 in OpenVZ.
ps p $(cat /var/run/elasticsearch/elasticsearch.pid)
PID TTY STAT TIME COMMAND
1132 ? Sl 0:05 /usr/bin/java -Xms256m -Xmx1g -Xss256k -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Delastics
Just like andykillen, the service is running after all.

deric · 2014-09-30T12:38:16Z

Same issue with LXC and Ubuntu 14.04

sysctl: permission denied on key 'vm.max_map_count'

though elasticsearch is running, is it a huge problem for production environment?

karmux · 2014-10-29T16:09:29Z

I also get this error on VPS running Ubuntu 14.04 when I (re)start Elasticsearch but is running at least.

sysctl: permission denied on key 'vm.max_map_count'

sts · 2014-11-13T15:05:03Z

Can someone please merge this? This works! 👍

if [ -n "$MAX_MAP_COUNT" ]
with
if [ -n "$MAX_MAP_COUNT" ] && [ ! -f /proc/sys/vm/max_map_count ]

grepwood · 2015-12-28T08:04:22Z

@jogaco Absolutely no practical consequences other than having this message in the logs

karmi · 2016-03-10T12:48:22Z

@spinscale, this issue is still linked from the TravisCI docs, maybe we can look into it?

spinscale · 2016-03-18T10:35:13Z

@karmi it is trivial to add another check if the proc file is writable and silence out the message, I just tested that locally on non OpenVZ and everything works as expected.

What I dont know is, if just adding another check, that checks if the file in the proc file system is writable, actually changes anything for OpenVZ users. Maybe one OpenVZ user can shed some light on this? If we check for being able to write /proc/sys/vm/max_map_count instead that it is being a file (what we do now), would the sysctl call not be done on OpenVZ?

Altareq · 2016-04-22T19:22:52Z

same problem on ES 2.3.0 Ubuntu 14.04

consistime · 2016-04-27T10:45:23Z

there is no solutions for this problem? fresh install of ubuntu server will be fix them?

consistime · 2016-04-28T01:40:27Z

this is caused on ubuntu 14 on proc/sys/vm permitted

consistime · 2016-04-28T01:44:40Z

now i know the problem is on server host is use openvz or any virtualization that doesnt support editing

consistime · 2016-04-28T01:46:23Z

then it is posible on how to make elasticsearch and java not without editing this request

consistime · 2016-04-28T01:46:37Z

omg help mee

grepwood · 2016-04-28T08:51:25Z

@rectoid The bug isn't causing any actual issues. Your Elasticsearch will work fine. It's just annoying to see in the logs.

I can't believe it's been over 2 years.

adamgontarz · 2016-06-23T10:54:54Z

on /etc/init.d/elasticsearch init script comment lines:

#       if [ -n "$MAX_MAP_COUNT" ]; then
#               sysctl -q -w vm.max_map_count=$MAX_MAP_COUNT
#       fi

talaikis · 2016-10-16T13:14:24Z

Same on 2.4.1, Ubuntu 14.04.

arypurnomoz · 2016-10-29T07:12:49Z

steps that i took to make es 5 run in an environment when i can't change vm.max_map_count

make es bind to localhost, (when binding to localhost es will start development mode, which wont do the check)
use nginx to forward http traffic to es, or you can use iptables to route the tcp request from outside network to localhost

but remember, es will run on DEVELOPMENT mode

here is my workaround for making it run inside docker container
https://gist.github.com/arypurnomoz/8d24155f024f8d4b6bee6b053c6e47d9

florian-asche · 2016-10-29T11:19:34Z

You should not have to. My is running fine, except that error/warning message...

clintongormley · 2016-11-06T11:53:47Z

As of 5.0, Elasticsearch will not start in production mode if vm.max_map_count is not high enough. Silencing the warning when we are not able to apply the MAX_MAP_COUNT setting on openvz will just make debugging the issue harder, as it will not be obvious why the setting is not being applied. Instead, if you are running on a system where you cannot set vm.max_map_count, but it is set to be high enough for Elasticsearch's bootstrap checks, then you can silence the warning by removing the MAX_MAP_COUNT setting. If the value on your system is NOT high enough, then your cluster is going to crash and burn at some stage and you will lose data. Instead of trying to work around it with hacks like #4978 (comment), you should either speak to your sysadmin to configure vm.max_map_count correctly, or move to a platform where you can set it.

jasontedor · 2016-11-07T14:01:27Z

@arypurnomoz Your workaround is overly complicated if all you want to do is expose a node via HTTP on an interface other than localhost. You can set http.host independently of transport.host (network.host sets both); the bootstrap checks are only enforced if a node is able to form a cluster with other instances not on localhost.

vanthome · 2016-12-16T14:29:00Z

you should provide a flag to prevent this check or better do not conduct it in development mode. this currently prevents me from running tests on travis.ci.

jeswinkninan · 2016-12-29T14:23:00Z

I have this issue before and solved by running my docker container in privileged mode, The actual reason behind this error is quite simple, Elasticsearch needs to change the "vm.max_map_count" to run, so changing via sysctl by Elasticseach itself and action is denied due to lack of permission. The issue will occur even the it is also a root user(Docker).

Simply run the container in privileged mode and this will fix the similar type of issues.

root@Zion:/home/jeswin/dockerproject# docker run -i -t --privileged ecc4953c8296 "/bin/bash"

When elasticsearch is bound to localhost it runs in development mode. This mode makes a few startup checks of elasticsearch less strict (they become warnings), allowing it to boot anyway. On circleci its servers the value for is too low and elasticsearch wont start. So we make sure we are running in dev mode so we can at least run our tests elastic/elasticsearch#4978 (comment)

x-itec · 2017-08-11T20:47:28Z

This problem really drives me mad with docker !!!!!!!! --privileged does not work anymore, nothing works anymore!!!! memory is set, but not checked correctly by ES5.x so it tries to write for no reason! result: ERROR

davron112 · 2018-05-11T05:38:24Z

My version: elasticsearch: 5.6.4 (but not working 6.2.3)
I added elasticsearch.yml : network.bind_host: "0.0.0.0"
To set this value permanently, update the vm.max_map_count setting in /etc/sysctl.conf.
vm.max_map_count=262144
To verify after rebooting, run sysctl vm.max_map_count.

docker-compose build elasticsearch
docker-compose up -d elasticsearch
docker-compose ps (double, because first worked, but second not worked)

result:

laradock_elasticsearch /bin/bash bin/es- Up 0.0.0.0:9200->9200/tcp

LuizFJP · 2022-08-08T19:01:43Z

I changed permission with chmod 777 and I edited sysctl.conf in the last line with #vm.max_map_count=262144 using a tool to edit text. Obs: I don't know it's the best way to solve that, but it worked to me.

spinscale self-assigned this Feb 3, 2014

BanzaiMan mentioned this issue Mar 24, 2014

Error starting ElasticSearch server travis-ci/travis-ci#2094

Closed

spinscale added the packaging label Jul 18, 2014

clintongormley added the >bug label Mar 14, 2016

clintongormley closed this as completed Nov 6, 2016

dadoonet mentioned this issue Nov 7, 2016

elasticsearch 5.0 can not running via docker run ,seems bootstrap check failed #21369

Closed

tianon mentioned this issue Dec 19, 2016

Figure out what's up with 5.0 docker-library/elasticsearch#98

Closed

yosifkit mentioned this issue Dec 20, 2016

Add upstream quote about elastic 5.x vm.max_map_count check docker-library/docs#778

Merged

joelwurtz mentioned this issue Jan 11, 2017

[RFC] Avoid boostrap check by not using elasticsearch in a cluster mode docker-library/elasticsearch#153

Merged

WingsLikeEagles mentioned this issue Aug 21, 2019

Allow max_map_count=65536 on single nodes for Docker containers #45815

Closed

mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020

sysctl: permission denied on key 'vm.max_map_count' - OpenVZ Elasticsearch 0.90.9 compatibility issue #4978

sysctl: permission denied on key 'vm.max_map_count' - OpenVZ Elasticsearch 0.90.9 compatibility issue #4978

Comments

bline79 commented Jan 31, 2014

spinscale commented Feb 3, 2014

dmikhaylov commented Feb 24, 2014

spinscale commented Feb 24, 2014

dmikhaylov commented Feb 24, 2014

spinscale commented Feb 24, 2014

dmikhaylov commented Feb 24, 2014

spinscale commented Feb 24, 2014

dmikhaylov commented Feb 25, 2014

spinscale commented Feb 25, 2014

dmikhaylov commented Feb 25, 2014

spinscale commented Feb 26, 2014

dmikhaylov commented Feb 26, 2014

derEremit commented Mar 16, 2014

spinscale commented Apr 25, 2014

13h3r commented May 12, 2014

kritik commented May 14, 2014

idanov commented Jun 3, 2014

r0mdau commented Jun 10, 2014

derEremit commented Jun 11, 2014

joke2k commented Jun 26, 2014

scamianbas commented Jul 2, 2014

adeleglise commented Aug 10, 2014

andykillen commented Aug 12, 2014

grepwood commented Sep 2, 2014

deric commented Sep 30, 2014

karmux commented Oct 29, 2014

sts commented Nov 13, 2014

grepwood commented Dec 28, 2015

karmi commented Mar 10, 2016

spinscale commented Mar 18, 2016

Altareq commented Apr 22, 2016

consistime commented Apr 27, 2016

consistime commented Apr 28, 2016

consistime commented Apr 28, 2016

consistime commented Apr 28, 2016

consistime commented Apr 28, 2016

grepwood commented Apr 28, 2016

adamgontarz commented Jun 23, 2016 • edited

talaikis commented Oct 16, 2016

arypurnomoz commented Oct 29, 2016 • edited

florian-asche commented Oct 29, 2016

clintongormley commented Nov 6, 2016

jasontedor commented Nov 7, 2016 • edited

vanthome commented Dec 16, 2016

jeswinkninan commented Dec 29, 2016 • edited

x-itec commented Aug 11, 2017 • edited

davron112 commented May 11, 2018 • edited

LuizFJP commented Aug 8, 2022

adamgontarz commented Jun 23, 2016 •

edited

arypurnomoz commented Oct 29, 2016 •

edited

jasontedor commented Nov 7, 2016 •

edited

jeswinkninan commented Dec 29, 2016 •

edited

x-itec commented Aug 11, 2017 •

edited

davron112 commented May 11, 2018 •

edited