El programa Apache no arranca en mi PC y ya no sé que hacer.

Hola Juan tus respuestas anteriores me ayudan bastante,sin embargo me encuentro con nuevos (quizas antiguos no descubiertos) errores. Por algun motivo el apache no quiere arrancar, ahora solo arroja el mensaje:
/usr/local/apache/bin/httpsdctl start:httpd coul not be started
ya se que esta pregunta la habias contestado a un tal alexis pero no puedo acceder a su pregunta, pues creo que era privada.
1

1 respuesta

Respuesta
1
"httpd could not be started" es el típico error que da apache cuando el fichero de configuración aparentemente es correcto, pero en el fondo hay alguna mala configuración.
Para averiguar el motivo del error, nada más ejecutarlo echa un vistazo a los logs:
/var/log/messages
y
/var/log/httpd/error.log o similares
Posiblemente haya algún parámetro mal en /etc/httpd/httpsd.conf
Suerte!
en el archivo /var/log/httpd/httpsd_error_log esta la causa del problema, dice:
Required SSLCache ServerPort missing.
que puedo hacer?
"Required SSLCache ServerPort missing" indica que no sabe la configuración de lo que se llama el SSLCache. Tienes que editar el fichero de configuración, y añadir las líneas de SSLCache:
# Set the path for the global cache server executable.
# If this facility gives you trouble, you can disable it by setting
# CACHE_SESSIONS to FALSE in apache_ssl.c
SSLCacheServerPath /usr/src/apache/src/modules/ssl/gcache
# Set the global cache server port number, or path. If it is a path, a Unix
# domain socket is used. If a number, a TCP socket.
SSLCacheServerPort logs/gcache_port
# Directory for the cache server to run in (in case of crashes). Optional.
SSLCacheServerRunDir /tmp
# Set the session cache timeout, in seconds (set to 15 for testing, use a
# higher value in real life)
SSLSessionCacheTimeout 15
# 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.
SSLCertificateFile /usr/local/apache/conf/ssl.crt/server.crt
# Server Private Key:
# If the key is not combined with the certificate, use this
# directive to point at the key file.
SSLCertificateKeyFile /usr/local/apache/conf/ssl.key/server.key
# Set SSLVerifyClient to:
# 0 if no certicate is required
# 1 if the client may present a valid certificate
# 2 if the client must present a valid certificate
# 3 if the client may present a valid certificate but it is not required to
# have a valid CA
SSLVerifyClient 0
# How deeply to verify before deciding they don't have a valid certificate
SSLVerifyDepth 10
# Translate the client X509 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 X509 certificate. Note that no
# password is obtained from the user. Every entry in the user file needs this
# password: xxj31ZMTZzkVA. See the code for further explanation.
SSLFakeBasicAuth
# List the ciphers that the client is permitted to negotiate. See the source
# for a definitive list. For example:
#SSLRequiredCiphers RC4-MD5:RC4-SHA:IDEA-CBC-MD5:DES-CBC3-SHA
# These two can be used per-directory to require or ban ciphers. Note that (at
# least in the current version) Apache-SSL will not attempt to renegotiate if a
# cipher is banned (or not required).
# You should probably at least ban the null encryption ciphers.
#SSLRequireCipher
SSLBanCipher NULL-MD5:NULL-SHA
Todo esto lo puedes encontrar en http://jips.kipelhouse.com/linux/apache/ssl/httpsd.html
Lo mismo de antes te digo. Si te sirvo de ayuda.

Añade tu respuesta

Haz clic para o

Más respuestas relacionadas