Sponsored Content
Full Discussion: Apache wont start
Top Forums UNIX for Dummies Questions & Answers Apache wont start Post 12519 by Neo on Wednesday 2nd of January 2002 08:23:12 PM
Old 01-02-2002
Sounds like you have a lot of basic leaning to do with TCP/IP like hostnames, nameservers, IP addresses,etc. The best approach is to get the O'Reilly book on Apache and read it, step-by-step; if you need more information on TCP/IP you might consider keeping the O'Reilly book TCP/IP Network Adminstration next to the Apache book.

Prior to setting up Apache, you need to insure your TCP/IP infrastructure is up and running. What is your IP address? The IP address of your nameserver(s)? Your host and domain names? What is the IP address of your web server?

These are all basic TCP/IP network administration 'things' that you need to know prior to trying to configure an Apache web server.
 

10 More Discussions You Might Find Interesting

1. Solaris

SMC wont start

Today I attempted to use SMC for the first time on SUNSVR01 since 4 November. The SMC toolbox loads just fine but when I attempt to run any of the tools in SMC, I get red stop signs with labels like "com.sun.admin.hostmgr.client.vhostmgr" in the GUI. At the bottom of the screen, I get the... (0 Replies)
Discussion started by: wjseaman
0 Replies

2. 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

3. 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

4. UNIX for Dummies Questions & Answers

startup script wont start up

I've put this script in /etc/rc.d and made a symbolic link to it from S99pctb in /etc/rc.d/rc3.d but it wont start up. Anyone know why ? This is the script: --------------------------- #!/bin/sh c=1 case "$1" in start) echo -n "starting pctb ..." > /etc/logger while ; do... (7 Replies)
Discussion started by: msearson1
7 Replies

5. UNIX for Advanced & Expert Users

Xwindows wont start

I have one machince where X crashes with some weird error on boot... Fatal server error: Cannot move old logfile "/var/log/XFree86.0.log.old" This is running redhat enterprise ES 3, I cant figure out how to get past this error. I have tried deleting the logfiles and recreating them, however... (1 Reply)
Discussion started by: frankkahle
1 Replies

6. 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

7. 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

8. Solaris

apache cannot start

hi all i'm having a problem with apache on solaris 10 SPARC I'm trying to start httpd as root but it fails with the following error /usr/local/apache2/bin/httpd -k start httpd: Could not determine the server's fully qualified domain name, using 192.168.1.11 for ServerName (20014)Error... (16 Replies)
Discussion started by: h@foorsa.biz
16 Replies

9. 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

10. 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
logger(1)						      General Commands Manual							 logger(1)

NAME
logger - Makes entries in the system log SYNOPSIS
/usr/bin/logger [-f file] [-i] [-p[facility.]priority] [-t tag] [message...] logger [-b] [message...] STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: logger: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
[Tru64 UNIX] Logs the informational message to the binary event logger instead of the syslog() subroutine and enters information in the binary event log file. The uerf command with the -r 250 option reports the informational messages that are in the binary event log file, which is used for system maintenance and troubleshooting. The -b option cannot be used with any other options. [Tru64 UNIX] Logs all lines in file. [Tru64 UNIX] Logs the process ID (PID) of the logger process with each line. [Tru64 UNIX] Enters the message with the specified priority and, if specified, from the specified facility. [Tru64 UNIX] You can specify priority as either an alphabetic string or its integer equivalent. You can specify the following val- ues for the priority variable: [Tru64 UNIX] (0) [Tru64 UNIX] The system is unusable. (0) [Tru64 UNIX] Action must be taken imme- diately. (1) [Tru64 UNIX] Critical conditions. (2) [Tru64 UNIX] Error conditions. (3) [Tru64 UNIX] (3) [Tru64 UNIX] (4) [Tru64 UNIX] Warning conditions. (4) [Tru64 UNIX] Normal but significant condition. (5) [Tru64 UNIX] Informational. (6) [Tru64 UNIX] Debug-level messages. (7) [Tru64 UNIX] You can also specify a value for the facility variable, which indicates the source of the event. You can specify facility as either an alphabetic string or its integer equivalent. The integer values appear in parentheses. You can specify the following values for the facility variable: [Tru64 UNIX] Kernel messages. (0) [Tru64 UNIX] Random user-level messages. (8) [Tru64 UNIX] Mail system. (16) [Tru64 UNIX] System daemons. (24) [Tru64 UNIX] Security/authorization messages. (32) [Tru64 UNIX] (32) [Tru64 UNIX] Messages syslogd generates internally. (40) [Tru64 UNIX] Line printer subsystem. (48) [Tru64 UNIX] Network news subsystem. (56) [Tru64 UNIX] UUCP subsystem. (64) [Tru64 UNIX] Clock daemon. (72) [Tru64 UNIX] (128) [Tru64 UNIX] (136) [Tru64 UNIX] (144) [Tru64 UNIX] (152) [Tru64 UNIX] (160) [Tru64 UNIX] (168) [Tru64 UNIX] (176) [Tru64 UNIX] (184) [Tru64 UNIX] Precedes each entry in the log with tag. OPERANDS
You can specify the message to be used for entries on the command line or with the -f file option, which specifies that each line in file be logged as an entry. If you do not specify message or -f, logger reads standard input. DESCRIPTION
The logger command makes the specified entries in the system log file. The logger command provides a program and shell script interface to the syslog() subroutine. The file in which entries are made depends on the current system log configuration; see syslog and syslogd for more information. NOTES
The effects of the environment variable LC_MESSAGES apply only to diagnostic messages generated by logger, and not to any messages written by the use of the command. EXIT STATUS
The following exit values are returned: Successful completion. An error occurred. EXAMPLES
To log the system reboot, including the process ID of the process running logger, enter: logger -i System rebooted To log each line in the file build.events with the tag trial build preceding them, enter: logger -f build.events -t "trial build" The following commands are equiv- alent and enter events of warning priority to the log: logger -p warning logger -p 4 The following commands are equivalent and enter events from the daemon facility of warning priority: logger -p daemon.warning logger -p 24.4 To specify the debug priority with a priority name, enter: logger -p debug my message To specify the debug priority with a priority number, enter: logger -p 7 my message To specify both debug priority and the user facility, enter: logger -p user.debug my message To specify the same facility/priority pair using numeric values, enter: logger -p 8.7 my message You can also combine alphabetic and numeric specifications: logger -p user.7 my message logger -p 8.debug my message ENVIRONMENT VARIABLES
The following environment variables affect the execution of logger: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization variables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments). Determines the locale for the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. SEE ALSO
Commands: binlogd(8), syslogd(8), uerf(8) Functions: syslog(3) Standards: standards(5) logger(1)
All times are GMT -4. The time now is 04:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy