Sponsored Content
Operating Systems Solaris How to fix a fault with apache in SUN server Post 302195623 by vamshikrishnab on Thursday 15th of May 2008 01:05:04 PM
Old 05-15-2008
Quote:
Originally Posted by era
You should be able to see from error.log which URL the client tried to retrieve. Unless there is mod_rewrite voodoo or CGI involved, it should map straightforwardly to a local file. If you have seen that 404 error then you should be able to figure out which URL it was for.
not only the client, we also not able to access the url which consists of:

http://xxx.xx.xx.xx/hawk.htm


and the error page is:


The page cannot be found
The page you are looking for might have been removed, had its name changed, or is temporarily unavailable.

--------------------------------------------------------------------------------

Please try the following:

If you typed the page address in the Address bar, make sure that it is spelled correctly.

Open the 172.20.10.57 home page, and then look for links to the information you want.
Click the Back button to try another link.
Click Search to look for information on the Internet.



HTTP 404 - File not found
Internet Explorer
 

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Info Needed in Seting up An apache Web Server on A Sun Sparc with Solaris 8

I need help in the form of the complete procedures necessary in setting up an Apache web server on a Sun Sparc running Solaris 8 David Johnston P.S New to the Unix arena (1 Reply)
Discussion started by: David Johnston
1 Replies

2. Programming

Problem with Perl script after moving from a Windows/Apache Server to a UNIX server.

I have a Perl script that worked fine before moving it to justhost.com. It was on a Windows/Apache server. Just host is using UNIX. Other Perl scripts on other sites that were also moved work fine so I know Perl is functioning. The script is called cwrmail.pl and is located in my cgi-bin. When I... (9 Replies)
Discussion started by: BigBobbyB
9 Replies
apachectl(1)						      General Commands Manual						      apachectl(1)

NAME
apachectl - Apache HTTP server control interface SYNOPSIS
apachectl command [...] DESCRIPTION
apachectl is a front end to the Apache HyperText Transfer Protocol (HTTP) server. It is designed to help the administrator control the functioning of the Apache httpd daemon. NOTE: If your Apache installation uses non-standard paths, you will need to edit the apachectl script to set the appropriate paths to your PID file and your httpd binary. See the comments in the script for details. The apachectl script returns a 0 exit value on success, and >0 if an error occurs. For more details, view the comments in the script. Full documentation for Apache is available at http://httpd.apache.org/ OPTIONS
The command can be any one or more of the following options: start Start the Apache daemon. Gives an error if it is already running. stop Stops the Apache daemon. restart Restarts the Apache daemon by sending it a SIGHUP. If the daemon is not running, it is started. This command automatically checks the configuration files via configtest before initiating the restart to make sure Apache doesn't die. fullstatus Displays a full status report from mod_status. For this to work, you need to have mod_status enabled on your server and a text-based browser such as lynx available on your system. The URL used to access the status report can be set by editing the STATUSURL variable in the script. status Displays a brief status report. Similar to the fullstatus option, except that the list of requests currently being served is omitted. graceful Gracefully restarts the Apache daemon by sending it a SIGUSR1. If the daemon is not running, it is started. This differs from a normal restart in that currently open connections are not aborted. A side effect is that old log files will not be closed immediately. This means that if used in a log rotation script, a substantial delay may be necessary to ensure that the old log files are closed before processing them. This command automatically checks the configuration files via configtest before ini- tiating the restart to make sure Apache doesn't die. On certain platforms that do not allow SIGUSR1 to be used for a graceful restart, an alternative signal may be used (such as SIGWINCH). graceful will send the right signal for your platform. configtest Run a configuration file syntax test. It parses the configuration files and either reports Syntax Ok or detailed information about the particular syntax error. help Displays a short help message. SEE ALSO
httpd(8) September 1997 apachectl(1)
All times are GMT -4. The time now is 09:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy