Discussion :

[oussa_7]

Salut tout le monde

j'ai un probléme demarrage service httpd . voici la résultat de la command :

[root@xxx ~]# service httpd start
Démarrage de httpd : [ÉCHOUÉ]
[root@xxx ~]#

et dans le fichier error_log

[Tue Mar 25 07:18:19 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 07:18:19 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)


merci d'avance

[Invité]

Salut,

As-tu une erreur avant le core dump?

[oussa_7]

Salut,

As-tu une erreur avant le core dump?

je ne sais pas comment le faire pour vérifier si le problème dans core dump

[Invité]

Fournis les lignes du log d'erreur qui sont avant le message "[Tue Mar 25 07:18:19 2014] [notice] core dump file size limit raised to 4294967295 bytes" s'il y en a

[oussa_7]

Fournis les lignes du log d'erreur qui sont avant le message "[Tue Mar 25 07:18:19 2014] [notice] core dump file size limit raised to 4294967295 bytes" s'il y en a

voici le fichier Log

[root@xxx ~]# more /etc/httpd/logs/error_log
[Tue Mar 25 07:18:19 2014] [notice] core dump file size limit raised to 42949672
95 bytes
[Tue Mar 25 07:18:19 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin
/suexec)
[Tue Mar 25 07:18:28 2014] [notice] core dump file size limit raised to 42949672
95 bytes
[Tue Mar 25 07:18:28 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin
/suexec)
[Tue Mar 25 07:21:22 2014] [notice] core dump file size limit raised to 42949672
95 bytes
[Tue Mar 25 07:21:22 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin
/suexec)
[Tue Mar 25 07:22:16 2014] [notice] core dump file size limit raised to 42949672
95 bytes
[Tue Mar 25 07:22:16 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin
/suexec)
[Tue Mar 25 07:51:05 2014] [notice] core dump file size limit raised to 42949672
95 bytes
[Tue Mar 25 07:51:05 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin
/suexec)
[Tue Mar 25 07:52:54 2014] [notice] core dump file size limit raised to 42949672
95 bytes
[Tue Mar 25 07:52:54 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin
/suexec)
[Tue Mar 25 07:54:55 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 07:54:55 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Mar 25 07:55:01 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 07:55:01 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Mar 25 07:56:24 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 07:56:24 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Mar 25 08:03:27 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 08:03:27 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Mar 25 08:05:58 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 08:05:58 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Mar 25 08:12:21 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 08:12:21 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Mar 25 08:28:06 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 08:28:07 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Mar 25 08:37:34 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 08:37:34 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Mar 25 09:42:19 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 09:42:19 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Mar 25 09:42:34 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 09:42:34 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Mar 25 10:05:56 2014] [notice] core dump file size limit raised to 4294967295 bytes
[Tue Mar 25 10:05:56 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[root@xxx ~]#

[Invité]

Quelle distribution utilises-tu?

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
 
cat /etc/issue

Est-ce que selinux est actif sur ta machine?

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
 
getenforce

Peux-tu vérifier la configuration apache?

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
 
httpd -t

[oussa_7]

Quelle distribution utilises-tu?

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
 
cat /etc/issue

Est-ce que selinux est actif sur ta machine?

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
 
getenforce

Peux-tu vérifier la configuration apache?

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
 
httpd -t

Voici mon chef

[root@xxx ~]# cat /etc/issue
Red Hat Enterprise Linux Server release 5.4 (Tikanga)
Kernel \r on an \m

[root@xxx ~]# getenforce
Disabled
[root@www ~]# httpd -t
Syntax OK
[root@xxx ~]#

[oussa_7]

d'acc mon chef le probléme est résolu

Pour partager les informations voici les étapes :

=================================================================================

Apache Error [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
One fine morning I have discovered that my Apache (httpd) service is down and can't be started

Step 1: Checking httpd Service Status:
#/etc/init.d/httpd status
httpd dead but pid file exists

Step 2: Search httpd processes and kill those
#ps -ef | grep httpd

# killall -9 httpd

Step 3: Remove httpd lock file if exist
# rm -f /var/lock/subsys/httpd

Step4: Restart Apache/httpd Service
# service httpd restart
Stop httpd [FAILED]
Start httpd [FAILED]

Need to dig down more.

Step 5: Check httpd error log file
# grep suexec /var/log/httpd/error_log
[Sun Sep 22 10:32:06 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Sep 22 10:33:51 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Sep 22 10:38:03 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Sep 22 10:45:53 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)

Step 6: Check httpd nss error log file
#tail -300 /var/log/httpd/nss_error_log
[Sun Sep 22 04:03:27 2013] [error] Certificate not verified: 'Server-Cert'
[Sun Sep 22 04:03:27 2013] [error] SSL Library Error: -8181 Certificate has expired
[Sun Sep 22 04:03:27 2013] [error] Unable to verify certificate 'Server-Cert'. Add "NSSEnforceValidCerts off" to nss.conf so the server can start until the problem can be resolved.
[Sun Sep 22 10:38:03 2013] [error] Certificate not verified: 'Server-Cert'
[Sun Sep 22 10:38:03 2013] [error] SSL Library Error: -8181 Certificate has expired
[Sun Sep 22 10:38:03 2013] [error] Unable to verify certificate 'Server-Cert'. Add "NSSEnforceValidCerts off" to nss.conf so the server can start until the problem can be resolved.
[Sun Sep 22 10:45:53 2013] [error] Certificate not verified: 'Server-Cert'
[Sun Sep 22 10:45:53 2013] [error] SSL Library Error: -8181 Certificate has expired

[Sun Sep 22 10:45:53 2013] [error] Unable to verify certificate 'Server-Cert'. Add "NSSEnforceValidCerts off" to nss.conf so the server can start until the problem can be resolved.

root cause of this issue is in a module called nss. mod_nss is an alternative to mod_ssl; it does a few things that mod_ssl doesn't do, and can run along side mod_ssl. For more information's, please go through the links [What is mod_nss , On Setting up Mod_NSS ,More detail ]

Step 7: Remove nss.conf file from httpd conf.d directory

#cd /etc/httpd/conf.d
#mv nss.conf nss.conf.orig
#/etc/init.d/httpd start
Start httpd [OK]