Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Starting apache fails
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Starting apache fails

ChristianChristian Member
edited November 2011 in Help

Hi there,

I'm having a problem on one of my servers apache crashed. When I tried to start "httpd" I'm getting the following error:

-bash-3.2# /sbin/service httpd restart

/etc/init.d/httpd: line 15: ulimit: open files: cannot modify limit: Operation n ot permitted

/etc/init.d/httpd: line 16: ulimit: open files: cannot modify limit: Operation n ot permitted

/etc/init.d/httpd: line 17: ulimit: open files: cannot modify limit: Operation n ot permitted

Warning: DocumentRoot [/home/xxx/public_html/teszt] does not exist

Warning: DocumentRoot [/home/xxx/public_html/teszt2] does not exist

httpd not running, trying to start

Could some one help me, what should I do?

Comments

  • Whats your output of ulimit (just type ulimit in Terminal and give the response)

    Thanked by 1Christian
  • your open files value is too low, increase it.

    Thanked by 1Christian
  • @Daniel said: f ulimit (just type ulimit in Terminal and

    -bash-3.2# ulimit

    unlimited

  • @tux said: value

    Where should I increase it? In /etc/init.d/httpd?

  • Did you start apache with the correct user?

  • @japon said: user

    I tried to start it with "root"

  • japonjapon Member
    edited November 2011

    AFAIK ulimit just lets you set the limit set according to the hard limit that is set for the shell. So you need to change that value and restart the shell. Have a look at the limits.conf on your system.

    Thanked by 1Christian
  • Thank you guys for your help, but the problem was due to using up to many resources for a short time and my VPS was starting swaping out. My provider solved the problem.

  • Go59954Go59954 Member
    edited November 2011

    Well, thanks for sharing how it worked, I had at once to reload OS after hours and hours trying and researching, in order to solve similar issue (not Apache though), and was solved with OS reload.

    But I believe now it was out of a provider side issue, the thing that I never thought could be the reason! Furthermore, it happened after node maintenance. I just didn't think right.

  • The real problem is that you're using apache.

    Thanked by 1tux
  • @Kairus said: The real problem is that you're using apache.

    Hahahaha, lol

  • I mainly use nginx. However on specified projects I have to use Apache :S

Sign In or Register to comment.