Sponsored Content
Operating Systems Solaris How to fix a fault with apache in SUN server Post 302195750 by sparcguy on Thursday 15th of May 2008 10:56:29 PM
Old 05-15-2008
You first said when you try to surf to yur url you get 404 error.

I told you to telnet localhost 80 GET / but you told me no error in the ascii output. And you also said socket cannot bind to port 80. So I really assumed that another webprocess started up before apache did. Because when you telnet to port 80 and GET / if you dun see an ascii output of the error page that means port 80 is really in use and a webserver is running. But you never pasted the output here so I assumed you don't want to reveal too much info abt your site, fair enuf, thats why I told you to go into /etc/init.d directories to do a quick check to see if there is a startup script for another possible http webserver application.

I'm assuming here that your apache installation is 100% perfect and that you previously able to bring up and use your webserver but now couldn't probably due to some network related or config issue which causing your problem. if my assumption is wrong you better say so because from what I gather you dun seem to know very much abt the server you are managing even when I told you to grep you use a non-root account to do it which strikes me as quite odd.

anyway I'm thinking 2 more possibilities here.

Go to your webserver, open up the web browser on the server and type http://localhost

and see what you get? Do you see your webpage or do you see another webpage?

The other one is quite remote but sometimes can be affected. Clear your browser cache delete all the cookies or go to another PC and try to surf to the website.
 

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
AMULEWEB(1)							  aMule utilities						       AMULEWEB(1)

NAME
amuleweb - aMule web server SYNOPSIS
amuleweb [-h <host>] [-p <port>] [-P <password>] [-f <path>] [-q] [-v] [-l <lang>] [-w] [-t <name>] [-s <port>] [-u] [-U <port>] [-z] [-Z] [-A <password>] [-G <password>] [-a | -d] [-L] [--no-php] [-N] amuleweb [--create-config-from=<path>] amuleweb [--help] amuleweb [--version] amuleweb [--amule-config-file=<path>] DESCRIPTION
amuleweb manages your access to amule through a web browser. You can start amuleweb together with amule(1), or separately, any time later. Options can be specified via command-line or via config-file. Command-line options take precedence over config-file options. [ -h <host>, --host=<host> ] Host where aMule is running (default: localhost). <host> might be an IP address or a DNS name [ -p <port>, --port=<port> ] aMule's port for External Connections, as set in Preferences->Remote Controls (default: 4712) [ -P <password>, --password=<password> ] External Connections password. [ -f <path>, --config-file=<path> ] Use the given configuration file. Default configuration file is ~/.aMule/remote.conf [ -q, --quiet ] Do not print any output to stdout. [ -v, --verbose ] Be verbose - show also debug messages. [ -l <lang>, --locale=<lang> ] Sets program locale (language). See the NOTES section for the description of the <lang> parameter. [ -w, --write-config ] Write command line options to config file and exit [ -t <name>, --template=<name> ] Loads the template named <name>. See the SKIN SUPPORT section for details. [ -s <port>, --server-port=<port> ] Webserver's HTTP port. This is the port you must point your browser to (default: 4711). [ -u ] Enable UPnP. [ -U <port>, --upnp-port <port> ] UPnP port. [ -z, --enable-gzip ] Enables using gzip compression in HTTP traffic to save bandwidth. [ -Z, --disable-gzip ] Disables using gzip compression (this is the default). [ -A <passwd>, --admin-pass=<passwd> ] Full access password for webserver. [ -G <passwd>, --guest-pass=<passwd> ] Guest password for webserver. [ -a, --allow-guest ] Allows guest access. [ -d, --deny-guest ] Denies guest access (default). [ -L, --load-settings ] Load/save webserver settings from/to remote aMule. This causes amuleweb to ignore command-line and config-file settings, and load them from aMule. When saving preferences none will be written to the config file, but to aMule. (Of course, this works only for those settings that can be set in aMule's Preferences->Remote Controls.) [ --no-php ] Disable PHP interpreter (deprecated) [ -N, --no-script-cache ] Recompiles PHP pages on each request. [ --create-config-from=<path> ] Create config file based upon <path>, which must point to a valid aMule config file, and then exit. [ --help ] Prints a short usage description. [ --version ] Displays the current version number. [ --amule-config-file=<path> ] aMule config file path. DO NOT USE DIRECTLY! aMule uses this option when starting amuleweb at aMule startup. This option causes all other command-line and config-file settings to be ignored, preferences to be read from the given config file, and also implies the -q -L options. NOTES
Paths For all options which take a <path> value, if the path contains no directory part (i.e. just a plain filename), then it is considered to be under the aMule configuration directory, ~/.aMule. Languages The <lang> parameter for the -l option has the following form: lang[_LANG][.encoding][@modifier] where lang is the primary language, LANG is a sublanguage/territory, encoding is the character set to use and modifier allows the user to select a specific instance of localization data within a single category. For example, the following strings are valid: de de_DE de_DE.iso88591 de_DE@euro de_DE.iso88591@euro Though all the above strings are accepted as valid language definitions, encoding and modifier are yet unused. In addition to the format above, you can also specify full language names in English - so -l german is also valid and is equal to -l de_DE. When no locale is defined, either on command-line or in config file, system default language will be used. SKIN SUPPORT
amuleweb is capable of displaying information in different skins. These skins are called templates, and you can make amuleweb load a spe- cific template via the -t command line option. Templates are searched in two places: first in ~/.aMule/webserver/ and then in /usr/share/amule/webserver/ if you installed with --prefix=/usr. Each template must be in a subdirectory of the template name, and this directory must contain all files the template needs. FILES
~/.aMule/remote.conf ~/.aMule/webserver/ $(pkgdatadir)/webserver/ EXAMPLE
Typically amuleweb will be first run as: amuleweb -h hostname -p ECport -P ECpassword -s HTTPport -A AdminPassword -w or amuleweb --create-config-from=/home/username/.aMule/amule.conf These will save settings to $HOME/.aMule/remote.conf, and later you only need to type: amuleweb Of course, you may specify any more or less options on the first example line, and you may also totally omit it. REPORTING BUGS
Please report bugs either on our forum (http://forum.amule.org/), or in our bugtracker (http://bugs.amule.org/). Please do not report bugs in e-mail, neither to our mailing list nor directly to any team member. COPYRIGHT
aMule and all of its related utilities are distributed under the GNU General Public License. SEE ALSO
amule(1), amulecmd(1) AUTHOR
This manpage was written by Vollstrecker <amule@vollstreckernet.de> aMule webserver v2.3.1 November 2011 AMULEWEB(1)
All times are GMT -4. The time now is 11:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy