Received: (qmail 6624 invoked by uid 2012); 13 Jul 1998 10:20:12 -0000 Message-Id: <19980713102012.6623.qmail@hyperreal.org> Date: 13 Jul 1998 10:20:12 -0000 From: Michael McLagan Reply-To: Michael.McLagan@Linux.ORG To: apbugs@hyperreal.org Subject: silent failure if mime.types is not found X-Send-Pr-Version: 3.2 >Number: 2603 >Category: mod_mime >Synopsis: silent failure if mime.types is not found >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Jul 13 03:30:00 PDT 1998 >Last-Modified: Thu Feb 11 13:11:49 PST 1999 >Originator: Michael.McLagan@Linux.ORG >Organization: >Release: 1.3 >Environment: Redhat 4.2, etc... >Description: Using a set of configs without the "TypesConfig" pointing at "conf/mime.types" explicitly, including mod_mime.so. Start the server, the "Configuring Apache to use suexec wrapper" appears, and the server exits. No message is placed on the console or in the error file. :( To make matters worse, if your ServerRoot is /etc/httpd and there is a mime.types in /etc, the server starts up and runs without comment either. I wasted 12 hours finding out that it was mod_mime that was causing the server to quit without explanation, and then a couple more figuring out why it worked on one system and not the other (both systems were identical except for mailcap-1.0-3 vs mailcap-1.0-7) >How-To-Repeat: See full description >Fix: Hows about a meaningful error message in mod_mime.c? >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: rbbloom@us.ibm.com State-Changed-When: Mon Sep 28 09:36:02 PDT 1998 State-Changed-Why: I have just tried this, and an error was reported in my error_log. I believe it is fixed in the latest release, 1.3.2. Could you please try to reproduce this, and let us know what happens? Thank you. Comment-Added-By: lars Comment-Added-When: Sat Nov 14 09:08:53 PST 1998 Comment-Added: [This is a standard response.] This Apache problem report has not been updated recently. Please reply to this message if you have any additional information about this issue, or if you have answers to any questions that have been posed to you. If there are no outstanding questions, please consider this a request to try to reproduce the problem with the latest software release, if one has been made since last contact. If we don't hear from you, this report will be closed. If you have information to add, BE SURE to reply to this message and include the apbugs@Apache.Org address so it will be attached to the problem report! State-Changed-From-To: feedback-closed State-Changed-By: lars State-Changed-When: Thu Feb 11 13:11:49 PST 1999 State-Changed-Why: [This is a standard response.] No response from submitter, assuming issue has been resolved. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]