LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 04-08-2004, 03:55 PM   #1
paijm021
LQ Newbie
 
Registered: Apr 2004
Location: Germany
Distribution: Slackware 9.1
Posts: 20

Rep: Reputation: 0
Unhappy Apache segmentation fault with with default index files


<b>I have a problem with Apache,</b>

I have apache 1.3.29 with php 4.3.5 , mod_perl 1.29 and mod_ssl 2.8.16-1.3.29 staticly loaded in the httpd binary. Webserver (LAN Ip is 10.0.0.150) is running on slackware 9.1. When I connect to my webserver with a browser (http://10.0.0.150/ in the adres bar) I get..... nothing! not even an error message. but there is an index.html file in the /www/htdocs directory. so when I type http://10.0.0.150/index.html it works.
The mod_dir.c module in the httpd.conf file is set to accept index.html as default index files.

The error_log file gives an segmentation error:

--When I try to load index.html with just /10.0.0.150/ I get this error in the log file. When I access the file with 10.0.0.150/index.html there are no errors at all.

[Thu Apr 8 19:15:29 2004] [notice] child pid 639 exit signal Segmentation fault (11)

This is my httpd.conf file:

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

##
## httpd.conf -- Apache HTTP server configuration file
##

#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://www.apache.org/docs/> for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# After this file is processed, the server will look for and process
# /usr/local/apache/conf/srm.conf and then /usr/local/apache/conf/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/usr/local/apache" will be interpreted by the
# server as "/usr/local/apache/logs/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerType is either inetd, or standalone. Inetd mode is only supported on
# Unix platforms.
#
ServerType standalone

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation
# (available at <URL:http://www.apache.org/docs/mod/core.html#lockfile>);
# you will save yourself a lot of trouble.
#
ServerRoot "/usr/local/apache"

#
# The LockFile directive sets the path to the lockfile used when Apache
# is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
# USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at
# its default value. The main reason for changing it is if the logs
# directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL
# DISK. The PID of the main server process is automatically appended to
# the filename.
#
#LockFile /usr/local/apache/logs/httpd.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile /usr/local/apache/logs/httpd.pid

#
# ScoreBoardFile: File used to store internal server process information.
# Not all architectures require this. But if yours does (you'll know because
# this file will be created when you run Apache) then you *must* ensure that
# no two invocations of Apache share the same scoreboard file.
#
ScoreBoardFile /usr/local/apache/logs/httpd.scoreboard

#
# In the standard configuration, the server will process httpd.conf (this
# file, specified by the -f command line option), srm.conf, and access.conf
# in that order. The latter two files are now distributed empty, as it is
# recommended that all directives be kept in a single file for simplicity.
# The commented-out values below are the built-in defaults. You can have the
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#
#ResourceConfig /usr/local/apache/conf/srm.conf
#AccessConfig /usr/local/apache/conf/access.conf

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

#
# Server-pool size regulation. Rather than making you guess how many
# server processes you need, Apache dynamically adapts to the load it
# sees --- that is, it tries to maintain enough server processes to
# handle the current load, plus a few spare servers to handle transient
# load spikes (e.g., multiple simultaneous requests from a single
# Netscape browser).
#
# It does this by periodically checking how many servers are waiting
# for a request. If there are fewer than MinSpareServers, it creates
# a new spare. If there are more than MaxSpareServers, some of the
# spares die off. The default values are probably OK for most sites.
#
MinSpareServers 5
MaxSpareServers 10

#
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
#
StartServers 5

#
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
#
MaxClients 150

#
# MaxRequestsPerChild: the number of requests each child process is
# allowed to process before the child dies. The child will exit so
# as to avoid problems after prolonged use when Apache (and maybe the
# libraries it uses) leak memory or other resources. On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries. For these platforms, set to something like 10000
# or so; a setting of 0 means unlimited.
#
# NOTE: This value does not include keepalive requests after the initial
# request per connection. For example, if a child process handles
# an initial request and 10 subsequent "keptalive" requests, it
# would only count as 1 request towards this limit.
#
MaxRequestsPerChild 0

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
#Listen 3000
#Listen 12.34.56.78:80

#
# BindAddress: You can support virtual hosts with this option. This directive
# is used to tell the server which IP address to listen to. It can either
# contain "*", an IP address, or a fully qualified Internet domain name.
# See also the <VirtualHost> and Listen directives.
#

BindAddress *

### Section 2: 'Main' server configuration
#

Port 80

##
## SSL Support
##

<IfDefine SSL>
Listen 80
Listen 443
</IfDefine>


User www
Group www

ServerAdmin webmaster@paijmans.nl.eu.org

ServerName blitz.paijmans.nl.eu.org

DocumentRoot "/www/htdocs"

<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/www/htdocs">

#
# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
Options Indexes FollowSymLinks MultiViews

#
# This controls which options the .htaccess files in directories can
# override. Can also be "All", or any combination of "Options", "FileInfo",
# "AuthConfig", and "Limit"
#
AllowOverride None

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all
</Directory>

#
# UserDir: The name of the directory which is appended onto a user's home
# directory if a ~user request is received.
#
<IfModule mod_userdir.c>
UserDir public_html
</IfModule>

#
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#
#<Directory /home/*/public_html>
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# <Limit GET POST OPTIONS PROPFIND>
# Order allow,deny
# Allow from all
# </Limit>
# <LimitExcept GET POST OPTIONS PROPFIND>
# Order deny,allow
# Deny from all
# </LimitExcept>
#</Directory>

#
# DirectoryIndex: Name of the file or files to use as a pre-written HTML
# directory index. Separate multiple entries with spaces.
#
<IfModule mod_dir.c>
DirectoryIndex index.html home.html
</IfModule>

#
# AccessFileName: The name of the file to look for in each directory
# for access control information.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess files from being viewed by
# Web clients. Since .htaccess files often contain authorization
# information, access is disallowed for security reasons. Comment
# these lines out if you want Web visitors to see the contents of
# .htaccess files. If you change the AccessFileName directive above,
# be sure to make the corresponding changes here.
#
# Also, folks tend to use names such as .htpasswd for password
# files, so this will protect those as well.
#
<Files ~ "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</Files>

#
# CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each
# document that was negotiated on the basis of content. This asks proxy
# servers not to cache the document. Uncommenting the following line disables
# this behavior, and proxies will be allowed to cache the documents.
#
#CacheNegotiatedDocs

#
# UseCanonicalName: (new for 1.3) With this setting turned on, whenever
# Apache needs to construct a self-referencing URL (a URL that refers back
# to the server the response is coming from) it will use ServerName and
# Port to form a "canonical" name. With this setting off, Apache will
# use the hostnameort that the client supplied, when possible. This
# also affects SERVER_NAME and SERVER_PORT in CGI scripts.
#
UseCanonicalName On

#
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
#
<IfModule mod_mime.c>
TypesConfig /usr/local/apache/conf/mime.types
</IfModule>

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
# mod_mime_magic is not part of the default server (you have to add
# it yourself with a LoadModule [see the DSO paragraph in the 'Global
# Environment' section], or recompile the server and include mod_mime_magic
# as part of the configuration), so it's enclosed in an <IfModule> container.
# This means that the MIMEMagicFile directive will only be processed if the
# module is part of the server.
#
<IfModule mod_mime_magic.c>
MIMEMagicFile /usr/local/apache/conf/magic
</IfModule>

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog /var/log/apache/error_log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel debug

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog /var/log/apache/access_log common

#
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#
#CustomLog /usr/local/apache/logs/referer_log referer
#CustomLog /usr/local/apache/logs/agent_log agent

#
# If you prefer a single logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog /usr/local/apache/logs/access_log combined

#
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (error documents, FTP directory listings,
# mod_status and mod_info output etc., but not CGI generated documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
#
ServerSignature On

# EBCDIC configuration:
# (only for mainframes using the EBCDIC codeset, currently one of:
# Fujitsu-Siemens' BS2000/OSD, IBM's OS/390 and IBM's TPF)!!
# The following default configuration assumes that "text files"
# are stored in EBCDIC (so that you can operate on them using the
# normal POSIX tools like grep and sort) while "binary files" are
# stored with identical octets as on an ASCII machine.
#
# The directives are evaluated in configuration file order, with
# the EBCDICConvert directives applied before EBCDICConvertByType.
#
# If you want to have ASCII HTML documents and EBCDIC HTML documents
# at the same time, you can use the file extension to force
# conversion off for the ASCII documents:
# > AddType text/html .ahtml
# > EBCDICConvert Off=InOut .ahtml
#
# EBCDICConvertByType On=InOut text/* message/* multipart/*
# EBCDICConvertByType On=In application/x-www-form-urlencoded
# EBCDICConvertByType On=InOut application/postscript model/vrml
# EBCDICConvertByType Off=InOut */*


#
# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
#
<IfModule mod_alias.c>

#
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL. So "/icons" isn't aliased in this
# example, only "/icons/". If the fakename is slash-terminated, then the
# realname must also be slash terminated, and if the fakename omits the
# trailing slash, the realname must also omit it.
#
Alias /icons/ "/usr/local/apache/icons/"

<Directory "/usr/local/apache/icons">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>

# This Alias will project the on-line documentation tree under /manual/
# even if you change the DocumentRoot. Comment it if you don't want to
# provide access to the on-line documentation.
#
Alias /manual/ "/usr/local/apache/htdocs/manual/"

<Directory "/usr/local/apache/htdocs/manual">
Options Indexes FollowSymlinks MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
#
ScriptAlias /cgi-bin/ "/www/cgi-bin/"

#
# "/usr/local/apache/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/www/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>

</IfModule>
# End of aliases.

#
# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Format: Redirect old-URI new-URL
#

#
# Directives controlling the display of server-generated directory listings.
#
<IfModule mod_autoindex.c>

#
# FancyIndexing is whether you want fancy directory indexing or standard
#
IndexOptions FancyIndexing

#
# AddIcon* directives tell the server which icon to show for different
# files or filename extensions. These are only displayed for
# FancyIndexed directories.
#
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip

AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*

AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core

AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^

#
# DefaultIcon is which icon to show for files which do not have an icon
# explicitly set.
#
DefaultIcon /icons/unknown.gif

ReadmeName README
HeaderName HEADER

IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t

</IfModule>
# End of indexing directives.

#
# Document types.
#
<IfModule mod_mime.c>

AddLanguage da .dk
AddLanguage nl .nl
AddLanguage en .en
AddLanguage et .ee
AddLanguage fr .fr
AddLanguage de .de
AddLanguage el .el
AddLanguage he .he
AddCharset ISO-8859-8 .iso8859-8
AddLanguage it .it
AddLanguage ja .ja
AddCharset ISO-2022-JP .jis
AddLanguage kr .kr
AddCharset ISO-2022-KR .iso-kr
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pl .po
AddCharset ISO-8859-2 .iso-pl
AddLanguage pt .pt
AddLanguage pt-br .pt-br
AddLanguage ltz .lu
AddLanguage ca .ca
AddLanguage es .es
AddLanguage sv .sv
AddLanguage cs .cz .cs
AddLanguage ru .ru
AddLanguage zh-TW .zh-tw
AddCharset Big5 .Big5 .big5
AddCharset WINDOWS-1251 .cp-1251
AddCharset CP866 .cp866
AddCharset ISO-8859-5 .iso-ru
AddCharset KOI8-R .koi8-r
AddCharset UCS-2 .ucs2
AddCharset UCS-4 .ucs4
AddCharset UTF-8 .utf8

# LanguagePriority allows you to give precedence to some languages
# in case of a tie during content negotiation.
#
# Just list the languages in decreasing order of preference. We have
# more or less alphabetized them here. You probably want to change this.
#
<IfModule mod_negotiation.c>
LanguagePriority en da nl et fr de el it ja kr no pl pt pt-br ru ltz ca es sv tw
</IfModule>

AddType application/x-tar .tgz
AddType application/x-httpd-php .php .phtml
Addtype application/x-httpd-php-source .phps

AddEncoding x-compress .Z
AddEncoding x-gzip .gz .tgz

AddHandler cgi-script .cgi

</IfModule>
# End of document types.

#
# Customize behaviour based on the browser
#
<IfModule mod_setenvif.c>

BrowserMatch "Mozilla/2" nokeepalive
BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0

#
# The following directive disables HTTP/1.1 responses to browsers which
# are in violation of the HTTP/1.0 spec by not being able to grok a
# basic 1.1 response.
#
BrowserMatch "RealPlayer 4\.0" force-response-1.0
BrowserMatch "Java/1\.0" force-response-1.0
BrowserMatch "JDK/1\.0" force-response-1.0

</IfModule>
# End of browser customization directives

<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
Allow from .paijmans.nl.eu.org
</Location>

### Section 3: Virtual Hosts
#

NameVirtualHost *:80


<VirtualHost *:80>
ServerAdmin webmaster@paijmans.nl.eu.org
DocumentRoot /www/htdocs/paijmans/
ServerName www.paijmans.nl.eu.org
DirectoryIndex home.htm home.html index.htm index.html
# ErrorLog logs/dummy-host.example.com-error_log
# CustomLog logs/dummy-host.example.com-access_log common
</VirtualHost>

#<VirtualHost _default_:*>
#</VirtualHost>



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

Can there be a problem with the mod_dir.c module?

<b>How can I access my index.html' ? </b>

Please help!
 
Old 04-08-2004, 08:55 PM   #2
rootboy
Member
 
Registered: Oct 2001
Distribution: Mint 15
Posts: 770

Rep: Reputation: 51
Comment out your php stuff and try again.

http://www.google.com/linux?hl=en&lr...=Google+Search


John
 
Old 04-12-2004, 08:32 AM   #3
paijm021
LQ Newbie
 
Registered: Apr 2004
Location: Germany
Distribution: Slackware 9.1
Posts: 20

Original Poster
Rep: Reputation: 0
What 'php stuff' do I need to uncomment/ comment ?

Thanks for the google but I couldn't find a solution.

Can someone please help me!

Bye ,

Joris.
 
Old 04-13-2004, 02:13 AM   #4
AutOPSY
Member
 
Registered: Mar 2004
Location: US
Distribution: Redhat 9 - Linux 2.6.3
Posts: 836

Rep: Reputation: 31
if document root and server root directories are supposed to be different, then I don't know.

I run apache with indexes and the server root is /var/www
Document root is /var/www/html

So unless you are sure, then that may be your problem.
 
Old 04-13-2004, 01:31 PM   #5
paijm021
LQ Newbie
 
Registered: Apr 2004
Location: Germany
Distribution: Slackware 9.1
Posts: 20

Original Poster
Rep: Reputation: 0
Quote:
if document root and server root directories are supposed to be different, then I don't know.

I run apache with indexes and the server root is /var/www
Document root is /var/www/html

So unless you are sure, then that may be your problem
Document-root and server-root can be different.

Notice that the webserver works finde (openssl, php, mod_perl), but the only thing that is bugging me is the segfault when I try to load /localhost/ instead of /localhost/index.html !

Can anyone please help me!!!

ps: Can anyone tell me why the granitecanyon.com newsgroups are down and where I can find an other one?
 
Old 04-15-2004, 03:07 AM   #6
rootboy
Member
 
Registered: Oct 2001
Distribution: Mint 15
Posts: 770

Rep: Reputation: 51
Quote:
Originally posted by paijm021
What 'php stuff' do I need to uncomment/ comment ?
I guess that it would be these two lines:

AddType application/x-httpd-php .php .phtml
Addtype application/x-httpd-php-source .phps


John
 
Old 04-15-2004, 04:18 AM   #7
paijm021
LQ Newbie
 
Registered: Apr 2004
Location: Germany
Distribution: Slackware 9.1
Posts: 20

Original Poster
Rep: Reputation: 0
Quote:
I guess that it would be these two lines:

AddType application/x-httpd-php .php .phtml
Addtype application/x-httpd-php-source .phps
Yes, but would ik work.
 
Old 04-17-2004, 02:30 PM   #8
paijm021
LQ Newbie
 
Registered: Apr 2004
Location: Germany
Distribution: Slackware 9.1
Posts: 20

Original Poster
Rep: Reputation: 0
Still no success,

I have recompiled apache with openssl/mod-ssl and php 4.3.6 and mod_perl. Nothing but succes... But when I type http://localhost/ it still does nothing and gives an segmentation fault! Can someone please help me. This one is bugging me for two weeks now.

I googeld for the apache segfault and some guys with the same problem had to change their mod_perl configuration. I have mod_perl installed with;

perl Makefile.PL APACHE_PREFIX=/usr/local/apache \ APACHE_SRC=../apache_1.3.29/src \
USE_APACI=1

Well its time to show my installation... maby it helps:

php;

#./configure --with-apache=../apache_1.3.29
#make
#make install

openssl;

#cd openssl-0.9.7d
#perl util/perlpath.pl /usr/bin/perl (Path to Perl)
#./config
#make
#make test

mod_perl;

#perl Makefile.PL APACHE_PREFIX=/usr/local/apache \ APACHE_SRC=../apache_1.3.29/src \
USE_APACI=1

modssl;

#cd mod_ssl-2.5.0-1.3.11
#./configure --with-apache=../apache_1.3.29 \
--prefix=/usr/local/apache \
--with-ssl=../openssl-0.9.4 \
--activate-module=src/modules/php4/libphp4.a \
--activate-module=src/modules/perl/libperl.a
#cd ..

#cd apache_1.3.29
#make
#make certificate blablabla
#make install

#apachectl start
#http://localhost/ --> nothing
./error_log --> segfault!!!!!

once again, Help.
 
Old 04-19-2004, 10:52 AM   #9
paijm021
LQ Newbie
 
Registered: Apr 2004
Location: Germany
Distribution: Slackware 9.1
Posts: 20

Original Poster
Rep: Reputation: 0
I did some research myself and found out that mod_perl-1.29 causes the error (segfault) . When I compile httpd with just mod_perl staticly loaded in the binary I get the same error.

Notice that the webserver works fine (openssl, php, mod_perl), but the only thing that is bugging me is the segfault when I try to load /localhost/ instead of /localhost/index.html !

Compiled mod_with with;

#perl Makefile.PL APACHE_PREFIX=/usr/local/apache \ APACHE_SRC=../apache_1.3.29/src \
USE_APACI=1

#Compile httpd? > no

And apache with;

./configure \
--prefix=/usr/local/apache \
--enable-module=all \
--activate-module=src/modules/perl/libperl.a

Can someone help me?

Joris
 
Old 04-21-2004, 01:03 PM   #10
paijm021
LQ Newbie
 
Registered: Apr 2004
Location: Germany
Distribution: Slackware 9.1
Posts: 20

Original Poster
Rep: Reputation: 0
I did some research again and found out that when I do DO_HHTPD=1, when compiling mod_perl, apache runs without segfaults! But when I compile mod_perl first and then apache (so without DO_HTTPD=1) with the same options, I get the segfault error again! Why!!!!!!!!!!!!!!!!

So what is the difference between a DO_HTTPD=1 and a 'manual' installation?
And how to solve this bug at all?

ps: It seems that quite a few people are reading this thread but I'm the only one who reply's! Why?

Last edited by paijm021; 04-21-2004 at 01:04 PM.
 
Old 04-21-2004, 01:45 PM   #11
eztup
LQ Newbie
 
Registered: Apr 2004
Location: Frankfurt/Germany
Distribution: Fedora Core 1
Posts: 3

Rep: Reputation: 0
Hi!

I have got the same problem today, without having installed mod_perl or mod_php... Suddenly two different webserver-installations got this segfaults...

I'm waiting for an answer of our webserver-admins... I googled out following links:

http://www.php-resource.de/forum/sho...threadid=32521
http://www.zend.com/phorum/read.php?...112&thread=107

1st) Seems to be no problem of installed os.
2nd) It could be a hardware-defect.

greetz
eztup

Last edited by eztup; 04-21-2004 at 01:49 PM.
 
Old 04-22-2004, 06:34 AM   #12
eztup
LQ Newbie
 
Registered: Apr 2004
Location: Frankfurt/Germany
Distribution: Fedora Core 1
Posts: 3

Rep: Reputation: 0
Hello again!

I remember a situation 3 years ago on a Suse 7.0-Fujitsu-Siemens-workstation. An Oracle-process was receiving segfaults after running some time. It was the same message, I think. Siemens-technicians came and changed mainboard, cpu and RAM - as far as I can remember... After that it had worked.

regards
eztup
 
Old 04-22-2004, 08:30 AM   #13
eztup
LQ Newbie
 
Registered: Apr 2004
Location: Frankfurt/Germany
Distribution: Fedora Core 1
Posts: 3

Rep: Reputation: 0
Hello!

We got it - 'was a really strange thing...

Our /-partition was full. There where only 80MB of freespace, which seem to be too less für Apache's tmp-files or sth. like that.

Now we have moved our applications to a bigger partition and - all webservers work fine

Unfortunately the segmentation fault-message is absolutely confusing... Why doesn't Apache just tell us that there is no space left ?)

greetz
eztup
 
Old 04-22-2004, 09:51 AM   #14
paijm021
LQ Newbie
 
Registered: Apr 2004
Location: Germany
Distribution: Slackware 9.1
Posts: 20

Original Poster
Rep: Reputation: 0
[----PROBLEM 'SOLVED'----]

Thanks Eztup, I 'solved' my problem to!

Quote:
Our /-partition was full. There where only 80MB of freespace, which seem to be too less für Apache's tmp-files or sth. like that.
I had enougth space on my my H.D.

My error was with mod_perl,

I wanted to load php4 AND mod_perl staticly in to the httpd binary. But that gave segfaults. Now ONLY php4 andd mod_ssl are staticly loaded in to httpd.

So I decided to use mod_perl as an DSO. I Compiled mod_perl with (mod_perl compilation/ installation AFTER apache is compiled with mod_ssl and mod_php4) :

#cd /usr/local/src/lamps/mod_perl-1.27
#perl Makefile.PL \
#USE_APXS=1 \
#WITH_APXS=/usr/local/apache/current/bin/apxs \
#EVERYTHING=1

# >yes
#> yes

#make
#make install

Php4 , mod_ssl and mod_perl work file without segfaults.

Thanks for everything,

Joris.

Last edited by paijm021; 04-22-2004 at 09:52 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Apache Default Index Cool_Hand_Luke Linux - Newbie 7 03-25-2005 12:16 PM
apache segmentation fault kloppster Linux - Software 6 07-19-2004 02:56 PM
Apache won't default to index.html TexasDex Linux - Software 5 04-05-2004 09:33 AM
HELP PLEASE! Apache Segmentation Fault gabriele_101 Linux - Software 4 08-01-2003 01:56 AM
Apache Segmentation Fault.... morbo Linux - General 2 12-14-2001 04:14 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 04:07 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration