> -----Original Message----- > From: Graves, Jan [mailto:Jan.Graves@xxxxxxx] > > You say "now matter what I cannot access the web site": what > does this mean? > > I meant no matter what. *I* meant "how are you accessing the server?" - if the only way you are aware of is via a browser, admittedly this might seem a silly question. In fact, there are lots of other ways of hitting a server that reveal much more information than a browser usually gives. If you just say things like "no matter what", we've no idea exactly what you tried. Even "cannot access the web site" is uninformative since there are numerous failure conditions in HTTP, all of which have distinct sources. If, however, you state the HTTP response code (eg, 404) then all is clear at this end... > - what error do you get in the browser (real error please)? > > Page not found Great - a 404. So, apache cannot find the file that the resource leads to. This is actually good news - apache is listening and responding to requests... Now, if you look in the error log (see below for definition), you will find a line that gives the path to the file it can't find. That might help you understand the misconfiguration. > > in the error logs? > > Which error log should I look at? The one defined by your "ErrorLog" directive. You can call log files by whatever name you like, so we have no idea what the name might be on your system. Only you know... BTW, the tail you sent was from the file defined by your "TransferLog" directive. It might be called "error_log" on your system, but it contains the log messages apache generates for each request - this is usually called "access_log". Rgds, Owen Boyle Disclaimer: Any disclaimer attached to this message may be ignored. > I have access_log, > access_log_webakuzer, agent_log, error_log (the one I sent > the end of), referrer_log, ssl.log, ssl_engine_log, ssl_request_log. > > > Thanks. > > At a guess, I'd say you have a minor misconfiguration that > means apache can't route your request to a VH or can't find > the docroot - but we need more info... > > Rgds, > Owen Boyle > Disclaimer: Any disclaimer attached to this message may be ignored. > > > > [Thu Jul 6 09:25:12 2006] [notice] Accept mutex: flock > > (Default: flock) > > > > > > Jan Graves > > Network Administrator/Engineer > > Lenawee Intermediate School District > > 4107 N. Adrian Highway > > Adrian, MI 49221 > > Phone: 517-265-1634 > > Fax: 517-265-7405 > > Visit us on the web at http://lisd.k12.mi.us > > > > > > -----Original Message----- > > From: Boyle Owen [mailto:Owen.Boyle@xxxxxxx] > > Sent: Thursday, July 06, 2006 9:25 AM > > To: users@xxxxxxxxxxxxxxxx > > Subject: RE: [users@httpd] How to tell if Apache is really running > > > > > -----Original Message----- > > > From: Graves, Jan [mailto:Jan.Graves@xxxxxxx] > > > Sent: Thursday, July 06, 2006 4:16 PM > > > To: users@xxxxxxxxxxxxxxxx > > > Subject: [users@httpd] How to tell if Apache is really running > > > > > > First I have to apologize to all of you Apache experts for > > > what will sound like a stupid question. However, I am new to > > > Apache and will admit that I have not a clue what I am doing > > > with it. How can I tell if Apache is really running, since > > > now matter what I cannot access the web site this server > > > should be hosting? > > > > > > This command ps -ax |grep http produces the > > > following results: > > > 1029 ?? Ss 0:00.46 /usr/local/sbin/httpd > > > 1030 ?? I 0:00.00 /usr/local/sbin/httpd > > > 1031 ?? I 0:00.00 /usr/local/sbin/httpd > > > 1032 ?? I 0:00.00 /usr/local/sbin/httpd > > > 1033 ?? I 0:00.00 /usr/local/sbin/httpd > > > > > > > > > I am running Apache Version 1.3 on a Unix system. Things > > > were running fine until storms took out the power over the > > > week-end and the system needed to be re-started. This system > > > was set up by a third party company who no longer provides > > > support. So, I am trying to determine what the problem is. > > > The Unix system itself starts and all of the processes that I > > > expect, except Apache. > > > > > > I have attached the error log file. > > > > Please post the tail of the log in plain text - I (and > > others) cannot open MS word docs from untrusted sources.. > > > > Rgds, > > Owen Boyle > > Disclaimer: Any disclaimer attached to this message may be ignored. > > > > If anyone needs further > > > information, please let me know. I will try to find it. In > > > looking at the Apache site, I know that things were not left > > > in default places. > > > > > > > > > Thanks in advance for any suggestions. > > > > > > > > > Jan Graves > > > Network Administrator/Engineer > > > Lenawee Intermediate School District > > > 4107 N. Adrian Highway > > > Adrian, MI 49221 > > > Phone: 517-265-1634 > > > Fax: 517-265-7405 > > > Visit us on the web at http://lisd.k12.mi.us > > > > > > > > > > > Diese E-mail ist eine private und persönliche Kommunikation. > > Sie hat keinen Bezug zur Börsen- bzw. Geschäftstätigkeit der > > SWX Gruppe. This e-mail is of a private and personal nature. > > It is not related to the exchange or business activities of > > the SWX Group. Le présent e-mail est un message privé et > > personnel, sans rapport avec l'activité boursière du Groupe SWX. > > > > > > This message is for the named person's use only. It may > > contain confidential, proprietary or legally privileged > > information. No confidentiality or privilege is waived or > > lost by any mistransmission. If you receive this message in > > error, please notify the sender urgently and then immediately > > delete the message and any copies of it from your system. > > Please also immediately destroy any hardcopies of the > > message. You must not, directly or indirectly, use, disclose, > > distribute, print, or copy any part of this message if you > > are not the intended recipient. The sender's company reserves > > the right to monitor all e-mail communications through their > > networks. Any views expressed in this message are those of > > the individual sender, except where the message states > > otherwise and the sender is authorised to state them to be > > the views of the sender's company. > > > > > --------------------------------------------------------------------- > > The official User-To-User support forum of the Apache HTTP > > Server Project. > > See <URL:http://httpd.apache.org/userslist.html> for more info. > > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > > > > > --------------------------------------------------------------------- > > The official User-To-User support forum of the Apache HTTP > > Server Project. > > See <URL:http://httpd.apache.org/userslist.html> for more info. > > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP > Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP > Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|