[Résolu] RPI3B+ nginx et apache 2

[Debian_Alain]

bonjour ,

dans le but de faire du monitoring , j'ai voulu installer nginx .

je possédais déjà en plus apache2 7.0 et W.P.

l'installation de nginx s'est mal passée . ,j'ai eu des échecs à la fin de l'installation et surtout des erreurs .

j'ai donc , avec apt retiré ngingx .

depuis , apache 2 ne se lance plus .

voilà mes  messages d'erreur :

Code :

[email protected]:~ $ sudo journalctl -r -p err
-- Logs begin at Thu 2016-11-03 17:16:42 GMT, end at Sat 2019-01-19 09:30:33 GMT. --
janv. 19 09:29:58 raspberrypi bluetoothd[689]: Failed to set privacy: Rejected (0x0b)
janv. 19 09:29:58 raspberrypi bluetoothd[689]: sap-server: Operation not permitted (1)
janv. 19 09:29:58 raspberrypi bluetoothd[689]: Sap driver initialization failed.
janv. 19 09:29:58 raspberrypi bluetoothd[689]: Failed to obtain handles for "Service Changed" characteristic
janv. 19 09:29:51 raspberrypi systemd[1]: Failed to start The Apache HTTP Server.
janv. 19 09:29:47 raspberrypi kernel: brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09 18:56:28
janv. 19 09:29:47 raspberrypi kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
janv. 19 09:29:47 raspberrypi kernel: brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006

[email protected]:~ $ sudo service apache2 status
● apache2.service - The Apache HTTP Server
  Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
  Active: failed (Result: exit-code) since Sat 2019-01-19 09:29:51 GMT; 1min 10s ago
 Process: 390 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)

janv. 19 09:29:50 raspberrypi apachectl[390]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
janv. 19 09:29:50 raspberrypi apachectl[390]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
janv. 19 09:29:50 raspberrypi apachectl[390]: no listening sockets available, shutting down
janv. 19 09:29:50 raspberrypi apachectl[390]: AH00015: Unable to open logs
janv. 19 09:29:50 raspberrypi apachectl[390]: Action 'start' failed.
janv. 19 09:29:50 raspberrypi apachectl[390]: The Apache error log may have more information.
janv. 19 09:29:51 raspberrypi systemd[1]: apache2.service: Control process exited, code=exited status=1
janv. 19 09:29:51 raspberrypi systemd[1]: Failed to start The Apache HTTP Server.
janv. 19 09:29:51 raspberrypi systemd[1]: apache2.service: Unit entered failed state.
janv. 19 09:29:51 raspberrypi systemd[1]: apache2.service: Failed with result 'exit-code'.

[email protected]:~ $ sudo apt update
Atteint:1 http://archive.raspberrypi.org/debian stretch InRelease
Réception de:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15,0 kB]
15,0 ko réceptionnés en 0s (15,9 ko/s)
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances      
Lecture des informations d'état... Fait
All packages are up to date.

[email protected]:~ $ sudo apt dist-upgrade
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances      
Lecture des informations d'état... Fait
Calcul de la mise à jour... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
1 partiellement installés ou enlevés.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] o
Paramétrage de nginx-full (1.10.3-1+deb9u2) ...
[ ok ] Upgrading binary: nginx.
W: APT had planned for dpkg to do more than it reported back (0 vs 4).
  Affected packages: nginx-full:armhf

[email protected]:~ $ sudo service apache2 start
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.


[email protected]:~ $ systemctl status apache2.service
● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2019-01-19 09:46:31 GMT; 56s ago
  Process: 6222 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)

janv. 19 09:46:31 raspberrypi apachectl[6222]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
janv. 19 09:46:31 raspberrypi apachectl[6222]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
janv. 19 09:46:31 raspberrypi apachectl[6222]: no listening sockets available, shutting down
janv. 19 09:46:31 raspberrypi apachectl[6222]: AH00015: Unable to open logs
janv. 19 09:46:31 raspberrypi apachectl[6222]: Action 'start' failed.
janv. 19 09:46:31 raspberrypi apachectl[6222]: The Apache error log may have more information.
janv. 19 09:46:31 raspberrypi systemd[1]: apache2.service: Control process exited, code=exited status=1
janv. 19 09:46:31 raspberrypi systemd[1]: Failed to start The Apache HTTP Server.
janv. 19 09:46:31 raspberrypi systemd[1]: apache2.service: Unit entered failed state.
janv. 19 09:46:31 raspberrypi systemd[1]: apache2.service: Failed with result 'exit-code'.

[email protected]:~ $ journalctl  -xe
janv. 19 09:46:31 raspberrypi systemd[1]: Starting The Apache HTTP Server...
-- Subject: L'unité (unit) apache2.service a commencé à démarrer
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- L'unité (unit) apache2.service a commencé à démarrer.
janv. 19 09:46:31 raspberrypi apachectl[6222]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive gl
janv. 19 09:46:31 raspberrypi apachectl[6222]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
janv. 19 09:46:31 raspberrypi apachectl[6222]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
janv. 19 09:46:31 raspberrypi apachectl[6222]: no listening sockets available, shutting down
janv. 19 09:46:31 raspberrypi apachectl[6222]: AH00015: Unable to open logs
janv. 19 09:46:31 raspberrypi apachectl[6222]: Action 'start' failed.
janv. 19 09:46:31 raspberrypi apachectl[6222]: The Apache error log may have more information.
janv. 19 09:46:31 raspberrypi systemd[1]: apache2.service: Control process exited, code=exited status=1
janv. 19 09:46:31 raspberrypi systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: L'unité (unit) apache2.service a échoué
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- L'unité (unit) apache2.service a échoué, avec le résultat failed.
janv. 19 09:46:31 raspberrypi systemd[1]: apache2.service: Unit entered failed state.
janv. 19 09:46:31 raspberrypi systemd[1]: apache2.service: Failed with result 'exit-code'.
janv. 19 09:46:31 raspberrypi sudo[6195]: pam_unix(sudo:session): session closed for user root

si vous pouviez m'aider .

merci

[crazycat]

Tu n'as pas supprimé nginx, il y a une alerte APT. Le port 80 est toujours utilisé, donc apache ne peut pas démarrer.
Donc, tu coupes nginx à la main (/etc/init.d/nginx stop) et tu le retires (apt-get remove --purge nginx).

ensuite, tu dois pouvoir relancer apache.

[Debian_Alain]

ah , donc c'était çà , ce que voulait dire :

Code :

janv. 19 09:46:31 raspberrypi apachectl[6222]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
janv. 19 09:46:31 raspberrypi apachectl[6222]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80

[crazycat]

Exactement.

Maintenant, je déconseille fortement l'utilisation d'apache sur RPi, il vaut mieux utiliser nginx + php-fpm qui se révèle bien moins lourd.