Sponsored Content
Full Discussion: Error when starting apache
Operating Systems HP-UX Error when starting apache Post 302980909 by anaigini45 on Monday 5th of September 2016 01:41:42 AM
Old 09-05-2016
Hi,

I tried killing one of the processes listed from the netstat command like this :

Code:
# kill -15 37274
kill: 37274: The specified process does not exist.
#

The error is as shown.

How else can I clear all these hogging processes?
Also are these processes the cause of port 80 being blocked? Clearing them will resolve this problem and allow me to start apache without any problem?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

starting Apache on Solaris 8

I am not by any means a UNIX guru if you can't already tell by the question I'm about to ask. How do I launch Apache web server on my SOlaris 8 server without rebooting it? Any help would be much appreciated!!! -Thanks (5 Replies)
Discussion started by: jskillet
5 Replies

2. UNIX for Dummies Questions & Answers

Starting Apache

I successfully installed Apache, but When I tried to start it I experienced problems. After installing and compiling, I typed the PREFIX "usr/local/ apache/bin/apachect1 start." The output was path not found. After checking the apachect1 file using vi, I found the file empty. There was no... (4 Replies)
Discussion started by: cstovall
4 Replies

3. Programming

starting with APR (Apache Portable Runtime)

Hi I am new to APR and I started programming using APR 1.2.2. So please guide me how to start learning it? (0 Replies)
Discussion started by: sumsin
0 Replies

4. Shell Programming and Scripting

Docbase starting Error

Hi All, I am trying to start the docbase but i am getting the following error-: $ ./dm_start_ncsglorbiprd00 interpreter "/bin/sh" not found file link resolves to "/usr/bin/sh" sh: ./dm_start_ncsglorbiprd00: not found. Can anyone please help me in this regard. Thanks in advance ... (0 Replies)
Discussion started by: Divyac
0 Replies

5. Solaris

Problems starting apache 1.3 with mysql

I've been working on a project to replace one of the my group's primary NIS servers. It also runs mysql and apache, as it is the host for the our team's hardware tracking database and website. Its running apache 1.3, and for some odd reason, I can't get apache to start on system boot. The... (1 Reply)
Discussion started by: godspunk32
1 Replies

6. UNIX for Dummies Questions & Answers

Error about SSLProtocol when starting Apache

I just installed Apache 2.2.6 & when trying to start it i got this: Invalid command 'SSLProtocol', perhaps misspelled or defined by a module not included in the server configuration Any help? (3 Replies)
Discussion started by: moe2266
3 Replies

7. Web Development

Problems starting Apache 2.0.54

Hi, I just installed Apache 2.0.54 and when I try and start httpd I get mohit@mohit-desktop:/sw/pkg/apache/bin$ ./httpd -k start httpd: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName (13): make_sock: could not bind to address :80 no listening... (1 Reply)
Discussion started by: mojoman
1 Replies

8. UNIX for Advanced & Expert Users

Starting an Apache Server

Sir, I have installed an Apache server in Fedora 9 (packages) and when i go to etc folder and try the command httpd -k start it says command not found....can any one help me out!!! ---------- Post updated at 12:02 PM ---------- Previous update was at 11:46 AM ---------- When i... (4 Replies)
Discussion started by: bssandeshbs
4 Replies

9. Red Hat

Error while starting Apache after compiling PHP and Curl

Hello, I am facing an issue while starting the apache server after compiling php and curl. Below are the versions i am using. php-5.2.17 httpd-2.2.17 curl-7.16.0 CentOS5.5x64 Compiling above packages without curl working very fine but when trying to compile php with curl below error is... (1 Reply)
Discussion started by: sunnysthakur
1 Replies

10. UNIX for Dummies Questions & Answers

How to grep a line not starting with # from a file (there are two lines starting with # and normal)?

e.g. File name: File.txt cat File.txt Result: #INBOUND_QUEUE=FAQ1 INBOUND_QUEUE=FAQ2 I want to get the value for one which is not commented out. Thanks, (3 Replies)
Discussion started by: Tanu
3 Replies
KILLALL(1)							   User Commands							KILLALL(1)

NAME
killall - kill processes by name SYNOPSIS
killall [-e,--exact] [-g,--process-group] [-i,--interactive] [-q,--quiet] [-v,--verbose] [-w,--wait] [-V,--version] [-S,--sid] [-c,--con- text] [-s,--signal signal] [--] name ... killall -l killall -V,--version DESCRIPTION
killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent. Signals can be specified either by name (e.g. -HUP) or by number (e.g. -1). If the command name contains a slash (/), processes executing that particular file will be selected for killing, independent of their name. killall returns a zero return code if at least one process has been killed for each ilisted command. killall returns zero otherwise. A killall process never kills itself (but may kill other killall processes). OPTIONS
-e, --exact Require an exact match for very long names. If a command name is longer than 15 characters, the full name may be unavailable (i.e. it is swapped out). In this case, killall will kill everything that matches within the first 15 characters. With -e, such entries are skipped. killall prints a message for each skipped entry if -v is specified in addition to -e, -g, --process-group Kill the process group to which the process belongs. The kill signal is only sent once per group, even if multiple processes belong- ing to the same process group were found. -i, --interactive Interactively ask for confirmation before killing. -l, --list List all known signal names. -q, --quiet Do not complain if no processes were killed. -v, --verbose Report if the signal was successfully sent. -V, --version Display version information. -w, --wait Wait for all killed processes to die. killall checks once per second if any of the killed processes still exist and only returns if none are left. Note that killall may wait forever if the signal was ignored, had no effect, or if the process stays in zombie state. -S (Flask only) Specify SID: kill only processes with given SID. Mutually exclusive with -c argument. Must precede other arguments on command line. -c (Flask only) Specify security context: kill only processes with given security context. Mutually exclusive with -s. Must precede other arguments on the command line. FILES
/proc location of the proc file system KNOWN BUGS
Killing by file only works for executables that are kept open during execution, i.e. impure executables can't be killed this way. Be warned that typing killall name may not have the desired effect on non-Linux systems, especially when done by a privileged user. killall -w doesn't detect if a process disappears and is replaced by a new process with the same PID between scans. AUTHORS
Werner Almesberger <Werner.Almesberger@epfl.ch> wrote the original version of psmisc. Since version 20 Craig Small <csmall@small.drop- bear.id.au> can be blamed. SEE ALSO
kill(1), fuser(1), pgrep(1), pidof(1), ps(1), kill(2) Linux March 25, 2001 KILLALL(1)
All times are GMT -4. The time now is 09:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy