Bug 275
Summary: | /etc/httpd/conf/mime.types is missing and server doesn't start | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | simon.mudd |
Component: | apache | Assignee: | David Lawrence <dkl> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1998-12-03 16:53:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
simon.mudd
1998-12-03 15:43:41 UTC
the file mime.types is located now in /etc and is provided by the mailcap rpm package. You are right it that it will not run if this file is missing in /etc. If you do a rpm -qR of the apache rpm, it will show that /etc/mime.types is required for installation and should state so when installing apache. dkl, I understand your comments. My problem has come from piecemeal upgrading to 5.2. It is not easy to upgrade the server in one go and I'd prefer to catch small problems like this early, upgrading the packages one be one, finally performing an upgrade which has little few kinks to iron out. I've been caught once by upgrading in one go especially when using non-redhat rpms (not this case) which stopped working on the upgrade. Thus I'm installing the 5.2 apache on 5.1 redhat. I have mailcap-1.0-7 and this does has /etc/mime.types. Nevertheless I can only start apache if I have mime.types in /etc/httpd/conf/ (as stated in my previous messages). There is obviously some other dependency missing somewhere which doesn't catch my situation, and must be related to mixing 5.1 and 5.2 rpms. (something which I guess isn't that uncommon). For the time being I'm not sure which dependency I'm missing and I'll put a symbolic link in place to fix my situation. Upgrading "properly" should resolve the problem. Simon |