Apache2ctl 87 Ulimit Error Setting Limit
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow
Ulimit Error Setting Limit (invalid Argument)
the company Business Learn more about hiring developers or posting ads with us Server Fault apache ulimit error setting limit Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join
Docker Ulimit: Error Setting Limit (operation Not Permitted)
them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top apache2ctl: 87: ulimit: error setting ulimit: error setting limit (operation not permitted) varnish limit (Operation not permitted) up vote 11 down vote favorite 6 The server is running fine -- or at least it seems to -- but there's always the following error: apache2/usr/sbin/apache2ctl: 87: ulimit: error setting limit (Operation not permitted) It happens with Apache 2.2.22-9 on Debian Wheezy. # apache2ctl configtest /usr/sbin/apache2ctl: 87: ulimit: error setting limit (Operation not permitted) Syntax OK # service apache2 reload [....] Reloading web server config: apache2/usr/sbin/apache2ctl: 87: ulimit: error setting ulimit failed. see readme.debian for more information setting limit (Operation not permitted) . ok # service apache2 restart [....] Restarting web server: apache2/usr/sbin/apache2ctl: 87: ulimit: error setting limit (Operation not permitted) ... waiting /usr/sbin/apache2ctl: 87: ulimit: error setting limit (Operation not permitted) . ok # service apache2 status Apache2 is running (pid 32045). apache-2.2 debian debian-wheezy share|improve this question edited Nov 29 '12 at 13:42 Hangin on in quiet desperation 88k9113199 asked Aug 5 '12 at 12:02 Pascal Polleunus 3532313 1 Have a look at what you have in /etc/security/limits.conf and /etc/security/limits.d. It seems that you have APACHE_ULIMIT_MAX_FILES (see it in /usr/sbin/apache2ctl) variable set to something larger than the limit in that files. –HUB Aug 6 '12 at 9:44 add a comment| 2 Answers 2 active oldest votes up vote 16 down vote This might help:- http://ubuntuforums.org/showthread.php?p=11950245#post11950245 BTW, sudo service apache2 restart # no errors service apache2 restart # errors share|improve this answer answered Aug 9 '12 at 10:59 Mukesh Chapagain 26147 Thanks, I already saw that but it doesn't help. Using sudo or not doesn't change anything, I have the same error. –Pascal Polleunus Aug 26 '12 at 15:00 1 Worked for me! Totally forgot sudo. –ThomasReggi Nov 15 '12 at 16:19 2 +1 magic sudo always does the trick –bicycle Sep 11 '13 at 0:06 ev
87: ulimit: error setting limit (Operation not cassandra ulimit error setting limit (operation not permitted) permitted) graham on 26-11-2013 04:19 To change this, I first checked
Ulimit: Max Locked Memory: Cannot Modify Limit: Operation Not Permitted
the ulimit for root by typingulimit -awhich among many results gave me the following line:open files (-n) https://serverfault.com/questions/414420/apache2ctl-87-ulimit-error-setting-limit-operation-not-permitted/415865 65535So then I went to edit file /ect/security/limits.conf and added the following lines:root soft nofile 65535root hard nofile 65535Then I relogged and was able to fire off Apache without the error message. graham on 26-11-2013 04:21 http://wordgraphs.com/faq/18100/apache2-usr-sbin-apache2ctl--87--ulimit--error-setting-limit--Operation-not-permitted- Post an answer Do you have a solution to this problem, or want to comment on it? Other users will appreciate your help! Your answer or comment: Show formatting hints HTML is disallowed, but in your text you can use the following markup [code][/code] for a block of code [tt][/tt] for inline code [link]link href|link anchor[/link] for links [b][/b] for bold text + Ask a question If you have a technical question related to programming and computers, ask it here. Other users will help you solve it! Unanswered questions Share your knowledge by helping others solve their problems Wordgraphs © 2013
Support Search GitHub This repository Watch 2,907 Star 35,488 Fork 10,436 docker/docker Code Issues 1,775 Pull requests 159 Projects 0 Wiki https://github.com/docker/docker/issues/1900 Pulse Graphs New issue Problem running Apache/Ubuntu from docker #1900 Closed nonsense opened this Issue Sep 17, 2013 · 4 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 5 participants nonsense commented Sep 17, 2013 I am trying to run Apache from Ubuntu (12.04 or 12.10). My Dockerfile looks like: FROM ubuntu:12.10 error setting RUN apt-get update RUN apt-get install -y apache2 RUN apt-get install -y vim ENV APACHE_RUN_USER www-data ENV APACHE_RUN_GROUP www-data ENV APACHE_LOG_DIR /var/log/apache2 When trying to run service apache2 restart, or apache2ctl restart, I get: * Starting web server apache2 │root@precise64:/home/vagrant/dacodi_apache# docker ps /usr/sbin/apache2ctl: 87: ulimit: error setting limit (Operation not permitted) │ID IMAGE COMMAND CREATED STATUS PORTS apache2: apr_sockaddr_info_get() error setting limit failed for e06c27ef9007 │650d74eba504 tony-apache:latest /bin/bash About a minute ago Up About a minute apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName Docker daemon is ran as root: root 1849 1 0 08:30 ? 00:00:06 /usr/bin/docker -d I noticed that the default ulimit for www-data is 1024, whereas the default for apache is 8192. However I don't understand why it is not able to change it. Furthermore it appears that for many people it is just working, without changing any ulimit variables. I am running docker from vagrant, and the VM has 2GB memory. nonsense closed this Sep 17, 2013 nonsense reopened this Sep 17, 2013 creack commented Sep 18, 2013 I didn't get what was the issue, The messages you show are warnings, they are not preventing me from using apache2. If you really need to change the ulimit, you can start the container with -privileged ex: docker run -p :80 -privileged IMAGE apache2ctl -D FOREGROUND crosbymichael commented Oct 9, 2013 @nonsense Please see the response