Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: RHEL, Ubuntu, Solaris 11, NetBSD, OpenBSD
Posts: 225
Rep:
Hi,
Sorry, been busy!
So when you try and start apache, you receive no error message, but when you check the running processes using
Code:
ps -ef
then there's definitely no httpd process?
Strange. I'm assuming that you've set this up under a Linux distro? I've only ever done it on OpenBSD, where it actually comes preconfigured to run chroot'd.
What result do you get if you carry out a config test? Syntax OK?
Also, what do you see in /var/log/apache/error.log (or wherever it is on your system that apache logs to).
Cheers,
Steve
P.S. You have told apache to listen on port 80 in the httpd.conf file right?
Distribution: RHEL, Ubuntu, Solaris 11, NetBSD, OpenBSD
Posts: 225
Rep:
Hi,
Still having the problem?
I would guess that this error means that you have a user to run apache as set in your httpd.conf file that does not actually exist on your system - i.e. the user wwwrun so it fails to start.
You would either need to create this user, or run as another user.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.