PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Apache Start Problem



*~LinuxHEF~*
23.02.04, 11:09
Will mein Apache starten und dies geht nicht! In der error_log steht folgendes:

[Mon Feb 23 11:05:28 2004] [alert] (2)No such file or directory: getpwuid: could
getpeername: Socket operation on non-socket
getsockname: Socket operation on non-socket
Error getting local address

Was hat das zu bedeuten und wie kann ich den Fehler beseitigen?

Danke!

steve-bracket
23.02.04, 11:24
Im Configfile die IP Adresse und den Port angeben.

Gruß
Steve

*~LinuxHEF~*
23.02.04, 11:31
Original geschrieben von steve-bracket
Im Configfile die IP Adresse und den Port angeben.

Gruß
Steve

Habe ich jetzt gemacht und nun bringt er folgendes:

Linux-9:/etc/httpd/logs # apachectl start
[Mon Feb 23 11:31:53 2004] [warn] NameVirtualHost 192.168.1.1:80 has no VirtualHosts
/usr/sbin/apachectl start: httpd could not be started

was sagt mir das?

Jorge
23.02.04, 12:10
Das sagt Dir, dass Deine httpd.conf völlig kaputt ist. Brauchst Du vHost, oder entfernst Du alle '#' in der httpd.conf die nicht bei drei auf dem Baum sind?

Mittels



ths-lx:~# apachectl configtest
Syntax OK
ths-lx:~#


kannst Du die Syntax der httpd.conf auf Fehler überprüfen. Sollte dies Fehler bringen, bitte den entsprechenden Teil der httpd.conf korregieren und nochmals testen. Bei Problemen lies bitte die folgenden Dokumentationen:

Solltest Du Apache 1.3.x verwenden, dann das hier:
http://httpd.apache.org/docs/

Sollterst Du Apache 2.0.x verwednen, dann bist Du hier richtig:
http://httpd.apache.org/docs-2.0/


Solltest Du wirklich vHosts benötigen dann lies

für Apache 1.3.x das hier (http://httpd.apache.org/docs/vhosts/)
für Apache 2.0.x das hier (http://httpd.apache.org/docs-2.0/de/vhosts/) (das hier ist sogar auf Deutsch!)


Nur durch lesen, kommst Du zu einem lauffähigen System. Durch pures wiederkäuen dessen was man Dir hier evtl. an Komplettlösungen vorkaut, lernst Du nichts. Und vor allem, mach nicht ständig ein neues Thema auf, das dürfte mitterweile der 5. Thread zu dem Thema sein...

*~LinuxHEF~*
23.02.04, 12:38
Ja sorry! Tut mir leid, aber ich lese und lese und lese, aber solche Probleme sind nirgends beschrieben und als Linux Newbie hat man es echt schwer.

Da freut man sich über jede hilfe :p

Jorge
23.02.04, 12:58
Na klar, jeder fängt mal klein an. Aber Deine Fehler deuten auf "willkürliches ausprobieren" hin. Nach der erfolgreichen Installation hast Du i.d.R. eine funktionsfähige httpd.conf, das nur so nebenbei :)

Kennst Du das schon: Apache 2 eBook (http://www.internetworld.de/iw_downloads/eBookApache/Apache20.pdf)

Was sagt denn nun apachectl configtest?

*~LinuxHEF~*
23.02.04, 13:20
Danke erstmal für den Link!!!

Aber ich habe nicht rumprobiert! Habe es nach Anleitung von der apache.org gemacht!
:(

Jorge
23.02.04, 13:24
Poste mal Deine httpd.conf, möchte da mal reingucken.

*~LinuxHEF~*
23.02.04, 13:25
Habe den Apache jetzt nochmal neu installiert und da sagt er mir wieder den gleichen Fehler wie oben!

Die httpd.conf wurde auch nciht neu geschrieben! Kann ich die irgendwie ganz einfach austauschen? :confused:

Jorge
23.02.04, 13:41
Häng die existierende httpd.con einfach hier an einen Post an. Ich schau mal rein.

*~LinuxHEF~*
23.02.04, 14:14
hier die httpd.conf:



AddType text/vnd.wap.wml wml
AddType text/vnd.wap.wmlscript wmls
AddType application/vnd.wap.wmlc wmlc
AddType application/vnd.wap.wmlscriptc wmlsc
Addtype image/vnd.wap.wbmp wbmp
#
# AddHandler allows you to map certain file extensions to "handlers",
# actions unrelated to filetype. These can be either built into the server
# or added with the Action command (see below)
#
# If you want to use server side includes, or CGI outside
# ScriptAliased directories, uncomment the following lines.
#
# To use CGI scripts:
#
AddHandler cgi-script .cgi

#
# To use server-parsed HTML files
#
AddType text/html .shtml
AddHandler server-parsed .shtml

#
# Uncomment the following line to enable Apache's send-asis HTTP file
# feature
#
#AddHandler send-as-is asis

#
# If you wish to use server-parsed imagemap files, use
#
#AddHandler imap-file map

#
# To enable type maps, you might want to use
#
#AddHandler type-map var

</IfModule>
# End of document types.

#
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
#

#
# MetaDir: specifies the name of the directory in which Apache can find
# meta information files. These files contain additional HTTP headers
# to include when sending the document
#
#MetaDir .web

#
# MetaSuffix: specifies the file name suffix for the file containing the
# meta information.
#
#MetaSuffix .meta

#
# Customizable error response (Apache style)
# these come in three flavors
#
# 1) plain text
#ErrorDocument 500 "The server made a boo boo.
# n.b. the single leading (") marks it as text, it does not get output
#
# 2) local redirects
#ErrorDocument 404 /missing.html
# to redirect to local URL /missing.html
#ErrorDocument 404 /cgi-bin/missing_handler.pl
# N.B.: You can redirect to a script or a document using server-side-includes.
#
# 3) external redirects
#ErrorDocument 402 http://some.other-server.com/subscription_info.html
# N.B.: Many of the environment variables associated with the original
# request will *not* be available to such a script.

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

#
# The following directives modify normal HTTP response behavior.
# The first directive disables keepalive for Netscape 2.x and browsers that
# spoof it. There are known problems with these browser implementations.
# The second directive is for Microsoft Internet Explorer 4.0b2
# which has a broken HTTP/1.1 implementation and does not properly
# support keepalive when it is used on 301 or 302 (redirect) responses.
#
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

#
# Allow server status reports, with the URL of http://servername/server-status
# Change the ".your-domain.com" to match your domain to enable.
#
# Note: apache is started (by /etc/init.d/apache) with -D STATUS if
# HTTPD_SEC_ACCESS_SERVERINFO is set to "yes" in
# /etc/sysconfig/apache.

<IfDefine STATUS>
<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
Allow from localhost
</Location>

#
# Allow remote server configuration reports, with the URL of
# http://servername/server-info (requires that mod_info.c be loaded).
# Change the ".your-domain.com" to match your domain to enable.
#
<Location /server-info>
SetHandler server-info
Order deny,allow
Deny from all
Allow from localhost
</Location>

#
# enable perl-status for mod_perl
#
<IfModule mod_perl.c>
<Location /perl-status>
SetHandler perl-script
PerlHandler Apache::Status
order deny,allow
deny from all
allow from localhost
</Location>
</IfModule>
</IfDefine>


#
# There have been reports of people trying to abuse an old bug from pre-1.1
# days. This bug involved a CGI script distributed as a part of Apache.
# By uncommenting these lines you can redirect these attacks to a logging
# script on phf.apache.org. Or, you can record them yourself, using the script
# support/phf_abuse_log.cgi.
#
#<Location /cgi-bin/phf*>
# Deny from all
# ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi
#</Location>

#
# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
#
#<IfModule mod_proxy.c>
# ProxyRequests On

# <Directory proxy:*>
# Order deny,allow
# Deny from all
# Allow from .your-domain.com
# </Directory>

#
# Enable/disable the handling of HTTP/1.1 "Via:" headers.
# ("Full" adds the server version; "Block" removes all outgoing Via: headers)
# Set to one of: Off | On | Full | Block
#
# ProxyVia On

#
# To enable the cache as well, edit and uncomment the following lines:
# (no cacheing without CacheRoot)
#
# CacheRoot "/var/cache/httpd"
# CacheSize 5
# CacheGcInterval 4
# CacheMaxExpire 24
# CacheLastModifiedFactor 0.1
# CacheDefaultExpire 1
# NoCache a-domain.com another-domain.edu joes.garage-sale.com

#</IfModule>
# End of proxy directives.

### Section 3: Virtual Hosts
#
# VirtualHost: If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at <URL:http://www.apache.org/docs/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.

#
# Use name-based virtual hosting.
#
#NameVirtualHost *:80

#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for requests without a known
# server name.
#
#<VirtualHost *:80>
# ServerAdmin webmaster@dummy-host.example.com
# DocumentRoot /www/docs/dummy-host.example.com
# ServerName dummy-host.example.com
# ErrorLog logs/dummy-host.example.com-error_log
# CustomLog logs/dummy-host.example.com-access_log common
#</VirtualHost>

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

##
## SSL Global Context
##
## All SSL configuration in this context applies both to
## the main server and all SSL-enabled virtual hosts.
##

#
# Some MIME-types for downloading Certificates and CRLs
#
<IfDefine SSL>
AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl .crl
</IfDefine>

<IfModule mod_ssl.c>

# Pass Phrase Dialog:
# Configure the pass phrase gathering process.
# The filtering dialog program (`builtin' is a internal
# terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog builtin

# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds, default=300).
# shm means the same as shmht.
# Note that on most platforms shared memory segments are not allowed to be on
# network-mounted drives, so in that case you need to use the dbm method.
#SSLSessionCache none
#SSLSessionCache shmht:/var/run/ssl_scache(512000)
#SSLSessionCache shmcb:/var/run/ssl_scache(512000)
#SSLSessionCache dbm:/var/run/ssl_scache
SSLSessionCache shmcb:/var/lib/httpd/ssl_scache
SSLSessionCacheTimeout 600

# Semaphore:
# Configure the path to the mutual exclusion semaphore the
# SSL engine uses internally for inter-process synchronization.
#SSLMutex file:/var/run/ssl_mutex
SSLMutex sem

# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the
# SSL library. The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random 512
#SSLRandomSeed startup file:/dev/urandom 512
#SSLRandomSeed connect file:/dev/random 512
#SSLRandomSeed connect file:/dev/urandom 512

# Logging:
# The home of the dedicated SSL protocol logfile. Errors are
# additionally duplicated in the general error log file. Put
# this somewhere where it cannot be used for symlink attacks on
# a real server (i.e. somewhere where only root can write).
# Log levels are (ascending order: higher ones include lower ones):
# none, error, warn, info, trace, debug.
SSLLog /var/log/httpd/ssl_engine_log
SSLLogLevel info

</IfModule>

<IfDefine SSL>

##
## SSL Virtual Host Context
##

<VirtualHost _default_:443>

# General setup for the virtual host
DocumentRoot "/srv/www/htdocs"
ServerName new.host.name
ServerAdmin you@your.address
ErrorLog /var/log/httpd/error_log
TransferLog /var/log/httpd/access_log

# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
SSLEngine on

# SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSL v2:+EXP:+eNULL

# Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate. If
# the certificate is encrypted, then you will be prompted for a
# pass phrase. Note that a kill -HUP will prompt again. A test
# certificate can be generated with `make certificate' under
# built time. Keep in mind that if you've both a RSA and a DSA
# certificate you can configure both in parallel (to also allow
# the use of DSA ciphers, etc.)
SSLCertificateFile /etc/httpd/ssl.crt/server.crt
#SSLCertificateFile /etc/httpd/ssl.crt/server-dsa.crt

# Server Private Key:
# If the key is not combined with the certificate, use this
# directive to point at the key file. Keep in mind that if
# you've both a RSA and a DSA private key you can configure
# both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/httpd/ssl.key/server.key
#SSLCertificateKeyFile /etc/httpd/ssl.key/server-dsa.key

# Server Certificate Chain:
# Point SSLCertificateChainFile at a file containing the
# concatenation of PEM encoded CA certificates which form the
# certificate chain for the server certificate. Alternatively
# the referenced file can be the same as SSLCertificateFile
# when the CA certificates are directly appended to the server
# certificate for convinience.
#SSLCertificateChainFile /etc/httpd/ssl.crt/ca.crt

# Certificate Authority (CA):
# Set the CA certificate verification path where to find CA
# certificates for client authentication or alternatively one
# huge file containing all of them (file must be PEM encoded)
# Note: Inside SSLCACertificatePath you need hash symlinks
# to point to the certificate files. Use the provided
# Makefile to update the hash symlinks after changes.
#SSLCACertificatePath /etc/httpd/ssl.crt
#SSLCACertificateFile /etc/httpd/ssl.crt/ca-bundle.crt

# Certificate Revocation Lists (CRL):
# Set the CA revocation path where to find CA CRLs for client
# authentication or alternatively one huge file containing all
# of them (file must be PEM encoded)
# Note: Inside SSLCARevocationPath you need hash symlinks
# to point to the certificate files. Use the provided
# Makefile to update the hash symlinks after changes.
#SSLCARevocationPath /etc/httpd/ssl.crl
#SSLCARevocationFile /etc/httpd/ssl.crl/ca-bundle.crl

# Client Authentication (Type):
# Client certificate verification type and depth. Types are
# none, optional, require and optional_no_ca. Depth is a
# number which specifies how deeply to verify the certificate
# issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth 10

# Access Control:
# With SSLRequire you can do per-directory access control based
# on arbitrary complex boolean expressions containing server
# variable checks and other lookup directives. The syntax is a
# mixture between C and Perl. See the mod_ssl documentation
# for more details.
#<Location />
#SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
# and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
# and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
# and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
# and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
# or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#</Location>

# SSL Engine Options:
# Set various options for the SSL engine.
# o FakeBasicAuth:
# Translate the client X.509 into a Basic Authorisation. This means that
# the standard Auth/DBMAuth methods can be used for access control. The
# user name is the `one line' version of the client's X.509 certificate.
# Note that no password is obtained from the user. Every entry in the user
# file needs this password: `xxj31ZMTZzkVA'.
# o ExportCertData:
# This exports two additional environment variables: SSL_CLIENT_CERT and
# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
# server (always existing) and the client (only existing when client
# authentication is used). This can be used to import the certificates
# into CGI scripts.
# o StdEnvVars:
# This exports the standard SSL/TLS related `SSL_*' environment variables.
# Per default this exportation is switched off for performance reasons,
# because the extraction step is an expensive operation and is usually
# useless for serving static content. So one usually enables the
# exportation for CGI and SSI requests only.
# o CompatEnvVars:
# This exports obsolete environment variables for backward compatibility
# to Apache-SSL 1.x, mod_ssl 2.0.x, Sioux 1.0 and Stronghold 2.x. Use this
# to provide compatibility to existing CGI scripts.
# o StrictRequire:
# This denies access when "SSLRequireSSL" or "SSLRequire" applied even
# under a "Satisfy any" situation, i.e. when it applies access is denied
# and no other module can change it.
# o OptRenegotiate:
# This enables optimized SSL connection renegotiation handling when SSL
# directives are used in per-directory context.
#SSLOptions +FakeBasicAuth +ExportCertData +CompatEnvVars +StrictRequire
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
SSLOptions +StdEnvVars
</Files>
<Directory "/srv/www/cgi-bin">
SSLOptions +StdEnvVars
</Directory>

# SSL Protocol Adjustments:
# The safe and default but still SSL/TLS standard compliant shutdown
# approach is that mod_ssl sends the close notify alert but doesn't wait for
# the close notify alert from client. When you need a different shutdown
# approach you can use one of the following variables:
# o ssl-unclean-shutdown:
# This forces an unclean shutdown when the connection is closed, i.e. no
# SSL close notify alert is send or allowed to received. This violates
# the SSL/TLS standard but is needed for some brain-dead browsers. Use
# this when you receive I/O errors because of the standard approach where
# mod_ssl sends the close notify alert.
# o ssl-accurate-shutdown:
# This forces an accurate shutdown when the connection is closed, i.e. a
# SSL close notify alert is send and mod_ssl waits for the close notify
# alert of the client. This is 100% SSL/TLS standard compliant, but in
# practice often causes hanging connections with brain-dead browsers. Use
# this only for browsers where you know that their SSL implementation
# works correctly.
# Notice: Most problems of broken clients are also related to the HTTP
# keep-alive facility, so you usually additionally want to disable
# keep-alive for those clients, too. Use variable "nokeepalive" for this.
# Similarly, one has to force some clients to use HTTP/1.0 to workaround
# their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
# "force-response-1.0" for this.
SetEnvIf User-Agent ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0

# Per-Server Logging:
# The home of a custom SSL log file. Use this when you want a
# compact non-error SSL logfile on a virtual host basis.
CustomLog /var/log/httpd/ssl_request_log \
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

</VirtualHost>

</IfDefine>



# Note:
#
# The file that is included below is generated by SuSEconfig.
#
# In this file, SuSEconfig puts Include statements it finds
# in /etc/httpd/modules/* (lines with "File:..." or "Include:...").
# If such a module file also contains a "Variable:..." statement, the settings
# in /etc/sysconfig/apache will be honored.
#
# In addition, any files listed in the HTTPD_CONF_INCLUDE_FILES variable
# in /etc/sysconfig/apache will be included here by SuSEconfig.
# This allows you to add e.g. VirtualHost statements without touching
# /etc/httpd/httpd.conf itself, which means that SuSEconfig will continue doing its
# job (since it would not touch httpd.conf any longer as soon it detects changes
# made by the admin via the md5sum mechanism)

Include /etc/httpd/suse_include.conf

Jorge
23.02.04, 14:21
Was steht in der /etc/httpd/suse_include.conf drin? Hattest Du den Apache nicht aus den Sourcen installiert?

Jorge
23.02.04, 14:25
Ich weiss schon warum ich kein SuSE mehr verwende: Die httpd.conf ist ja furchterregend schlecht, völlig wirr. :rolleyes:

Pack mal nocht die /etc/httpd/suse_include.conf hier rein, ohne die kann man nichts sagen.

*~LinuxHEF~*
23.02.04, 14:43
Original geschrieben von Jorge
Ich weiss schon warum ich kein SuSE mehr verwende: Die httpd.conf ist ja furchterregend schlecht, völlig wirr. :rolleyes:

Pack mal nocht die /etc/httpd/suse_include.conf hier rein, ohne die kann man nichts sagen.



#
#
# Automatically generated by SuSEconfig on Mon Feb 23 14:34:36 CET 2004
#
# PLEASE DO NOT EDIT THIS FILE!
#

Include /etc/httpd/apache-example-pages.conf
Include /etc/httpd/mod_php4.conf
Include /etc/httpd/suse_public_html.conf
Include /etc/httpd/susehelp_acl.conf

Jorge
23.02.04, 14:55
Grrrr, diese verdammte SuSE Konfiguration. Warum müssen die einen Inklude nach dem anderen machen. Da blickt doch keiner mehr durch. :mad:

Was steht in /etc/httpd/apache-example-pages.conf drin? Wenn das auch 1000 Inkludes enthält, geb ich auf :rolleyes:

steve-bracket
23.02.04, 15:01
Original geschrieben von Jorge
Grrrr, diese verdammte SuSE Konfiguration. Warum müssen die einen Inklude nach dem anderen machen. Da blickt doch keiner mehr durch. :mad:

Was steht in /etc/httpd/apache-example-pages.conf drin? Wenn das auch 1000 Inkludes enthält, geb ich auf :rolleyes:

Hehe, ja das kenne ich, sobald die Ansprüche etwas über den Mainstream hinausgehen wird es kompliziert.
Aber an der aktuellen Distrie und Apache2 ist eigentlich nichts auszusetzten.
Und bislang hat die Out-of-the-Box Installation bei SuSE immer funktioniert.

@*~LinuxHEF~*
Welchen Softwarestand verwendest du?

Gruß

*~LinuxHEF~*
23.02.04, 15:35
Ihr werde es nicht glauben, es funktioniert endlich!

Habe Apache noch 5 mal installiert und jetzt geht es!

Danke nochmal :p

kadei
24.02.04, 21:50
Das ist aber nicht der sinn der Sache, alles 5tausend mal zu installieren bis es geht.:D

steve-bracket
24.02.04, 22:09
Original geschrieben von *~LinuxHEF~*
Ihr werde es nicht glauben, es funktioniert endlich!

Habe Apache noch 5 mal installiert und jetzt geht es!

Danke nochmal :p

*Kopfschüttel*
Freut mich für dich das es funktioniert, aber normal ist das nicht.
Wenn du das gleiche Softwarepaket 20 mal installierst sollte es 20 mal das gleiche Resultat bringen.
Eventuell ein Hardwareproblem.

Gruß

*~LinuxHEF~*
25.02.04, 10:48
Original geschrieben von steve-bracket
*Kopfschüttel*
Freut mich für dich das es funktioniert, aber normal ist das nicht.
Wenn du das gleiche Softwarepaket 20 mal installierst sollte es 20 mal das gleiche Resultat bringen.
Eventuell ein Hardwareproblem.

Gruß


Vielen Dank euch allen nochmal!

Der Fehler war nicht Hardwareseitig, war mal wieder ein Konfigurationsfehler :D

Doh!
25.02.04, 13:20
Original geschrieben von *~LinuxHEF~*

Error getting local address


Glaube nicht, dass das am Apache liegt. Ich denke eher, Deine Netzwerkkonfig ist versaut.

Poste mal bitte:

/etc/sysconfig/network/ifcfg-eth0

sowie die Ausgabe von

ifconfig -a

und

netstat -r