Sponsored Content
Full Discussion: apache cannot start
Operating Systems Solaris apache cannot start Post 302331226 by reborg on Saturday 4th of July 2009 08:17:54 PM
Old 07-04-2009
Quote:
Originally Posted by h@foorsa.biz
@reborg thanks a lot
I deleted httpd.pid now it works fine
by the way is there any guide or document to set up apache server with non privileged user
Thanks again
With Solaris 10 it should be possible using pfexec and appropriate privileges, but it's more usual to start it as root and use the "User" and "Group" in the config file for normal runtime use as Neo suggested.

Any user can run Apache ( provided the pid file and logs can be written by the user ), but you need extra privileges to run it on the standard ports. If you set the port number > 1024 any normal user could start it. I have in the past allowed certain users to control the Apache server on certain servers without giving them root access by creating an IPFilter to forward from port 80 to an unprivileged port that apache was listening on. To an external user there is no difference but there is no need to grant any extra permissions to the user running the server.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Apache wont start

Hi, like a lot of people that post here, I am new at UNIX. The only UNIX I have ever messed with is my iBook running MacOSX (10.1). I have a grasp of the basic commands and understanding of the system but only to a point. I searched the archive and FreeBSD.org and apache.org but I couldn't find... (4 Replies)
Discussion started by: Alpha_Harblo
4 Replies

2. UNIX for Dummies Questions & Answers

Apache start (Was in:how can i?) [Split by LF]

I need to know, which script starts the apache web server on start up? If anyone could help me that would be great. I'm in deep trouble if I can't find the script. thanks very much dan donohd If you know my e-mail is donohd@sage.edu thanks:( (1 Reply)
Discussion started by: donohd
1 Replies

3. AIX

Start Stop Apache

I am in the process of reorging my Lawson db. I need to turn off the RMI server...not a problem. However my instructions also state that I must also shutdown my Servlet Container....I believe it is Apache. I have looked in /usr/apache/bin/apachectl What is the command for stopping and... (2 Replies)
Discussion started by: MILLERJ62
2 Replies

4. Solaris

Apache start problem

Hi, I have installed apache webserver on my solaris 10(x86). When I tried to start the server it gives following error, ld.so.1: /usr/local/apache2/bin/httpd: fatal: libssl.so.0.9.8: open failed: No such file or directory Killedld.so.1:: Too many arguments Can somebody please guide me how... (1 Reply)
Discussion started by: maheshsri
1 Replies

5. Solaris

help me........... my apache can't start

help me please.................bro i was install apache2 and i have been configure httpd.conf on my solaris 10 machine n i already running my httd service but why my webserver couldn't run on my browser? some buddy help me.............:confused::confused::confused::confused::confused: (5 Replies)
Discussion started by: yatmianto
5 Replies

6. Solaris

Apache start issue

Hi group, I need help to start apache in following scenario: 1) Say apache is installed on solaris OS by user 'root'. 2) An entry is there in httpd.conf that says to start apache process as user: #User <RUN_AS_USER> is edited as User user1 2) Now say user2 has logged and tries to start... (6 Replies)
Discussion started by: rs266
6 Replies

7. UNIX for Advanced & Expert Users

Apache does not start

After i added this line to my apache httpd.conf it does not start. AuthUserFile /apps/apache22/conf/httpd.passwd and i see the below error. Syntax error on line 876 of /apps/apache22/conf/httpd.conf: AuthUserFile not allowed here Kindly help. (4 Replies)
Discussion started by: mohtashims
4 Replies

8. Red Hat

Apache start error

I have a new server, installed everything and tried to get it all up and running. Got the following issue: # /usr/local/apache/bin/apachectl start httpd: Syntax error on line 54 of /usr/local/apache/conf/httpd.conf: Cannot load /usr/local/apache/modules/libphp5.so into server:... (0 Replies)
Discussion started by: Tommyk
0 Replies

9. Web Development

Unable to start the apache web server

Hi All, I'm getting this below error bash-4.1$ ./apachectl -k start (98)Address already in use: make_sock: could not bind to address hostname:18000 no listening sockets available, shutting down Unable to open logs I tried to change the port number, still same error: ... (5 Replies)
Discussion started by: raghur77
5 Replies

10. Shell Programming and Scripting

Display status of instances in apache - Where to start

Hello, I know this is not a simple question so I just need to know where to start for below project: I am running under Ubuntu 18.04 What I'd like to see in apache page is to display status of particular process pids. ps aux | grep keywords.txt keywords.txt word1 word2 word3 word4... (9 Replies)
Discussion started by: baris35
9 Replies
GSEXEC(8)							  GridSite Manual							 GSEXEC(8)

NAME
gsexec - Switch user before executing external programs SYNOPSIS
gsexec [-V] SUMMARY
gsexec is used by the Apache HTTP Server to switch to another user before executing CGI programs. In order to achieve this, it must run as root. Since the HTTP daemon normally doesn't run as root, the gsexec executable needs the setuid bit set and must be owned by root. It should never be writable for any other person than root. gsexec is based on Apache's suexec, and its behaviour is controlled with the Apache configuration file directives GridSiteExecMethod and GridSiteUserGroup added to Apache by mod_gridsite(8) Four execution methods are supported: nosetuid, suexec, X509DN and directory, and these may be set on a per-directory basis within the Apache configuration file. NOSETUID METHOD
This is the default behaviour, but can also be produced by giving GridSiteExecMethod nosetuid CGI programs will then be executed without using gsexec, and will run as the Unix user given by the User and Group Apache directives (nor- mally apache.apache on Red Hat derived systems.) SUEXEC METHOD
If GridSiteExecMethod suexec is given for this virtual host or directory, then CGI programs will be executed using the user and group given by the GridSiteUserGroup user group directive, which may also be set on a per-directory basis (unlike suexec's SuexecUserGroup which is per-server only.) The CGI program must either be owned by root, the Apache user and group specified at gsexec build-time (normally apache.apache) or by the user and group given with the GridSiteUserGroup directive. X509DN METHOD If GridSiteExecMethod X509DN is given, then the CGI program runs as a pool user, detemined using lock files in the exec mapping directory chosen as build time of gsexec. The pool user is chosen according to the client's full certificate X.509 DN (ie with any trailing GSI proxy name components stripped off.) Subsequent requests by the same X.509 identity will be mapped to the same pool user. The CGI program must either be owned by root, the Apache user and group specified at gsexec build-time (normally apache.apache) or by the pool user selected. DIRECTORY METHOD
If GridSiteExecMethod directory is given, then the CGI program runs as a pool user chosen according to the directory in which the CGI is located: all CGIs in that directory run as the same pool user. The CGI program must either be owned by root, the Apache user and group specified at gsexec build-time (normally apache.apache) or by the pool user selected. EXECMAPDIR
The default exec mapping directory is /var/www/execmapdir and this is fixed when the gsexec executable is built. The exec mapping directory and all of its lock files must be owned and only writable by root. To initialise the lock files, create an empty lock file for each pool user, with the pool username as the filename (eg user0001, user0002, ...) As the pool users are leased to X.509 identities or directories, they will become hard linked to lock files with the URL-encoded X.509 DN or full directory path. You can recycle pool users by removing the corresponding URL-encoded hard link. stat(1) and ls(1) with option -i can be used to print the inodes of lock files to match up the hard links. However, you must ensure that all files and processes owned by the pool user are deleted before recycling! OPTIONS
-V If you are root, this option displays the compile options of gsexec. For security reasons all configuration options are changeable only at compile time. MORE INFORMATION
For further information about the concepts and the security model of the original Apache suexec please refer to the suexec documentation: http://httpd.apache.org/docs-2.0/suexec.html For examples using the gsexec extensions, please see the GridSite gsexec page: http://www.gridsite.org/wiki/Gsexec AUTHORS
Apache project, for original suexec Andrew McNab <Andrew.McNab@manchester.ac.uk> for gsexec modifications. gsexec is part of GridSite: http://www.gridsite.org/ SEE ALSO
httpd(8), suexec(8), mod_gridsite(8) gsexec October 2005 GSEXEC(8)
All times are GMT -4. The time now is 02:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy