Når jeg prøver å kjøre apache, viser den meg denne feilen:

[manideep@localhost ~]$ sudo httpd -t Syntax OK [manideep@localhost ~]$ sudo service httpd start Redirecting to /bin/systemctl start httpd.service Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. [manideep@localhost ~]$ sudo service httpd status Redirecting to /bin/systemctl status httpd.service ● httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sun 2017-03-05 15:52:12 PST; 6s ago Docs: man:httpd(8) man:apachectl(8) Process: 4115 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE) Process: 4110 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE) Main PID: 4110 (code=exited, status=1/FAILURE) Mar 05 15:52:12 localhost.localdomain httpd[4110]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80 Mar 05 15:52:12 localhost.localdomain httpd[4110]: (98)Address already in use: AH00072: make_sock: could not bind to address ...0.0:80 Mar 05 15:52:12 localhost.localdomain httpd[4110]: no listening sockets available, shutting down Mar 05 15:52:12 localhost.localdomain httpd[4110]: AH00015: Unable to open logs Mar 05 15:52:12 localhost.localdomain systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE Mar 05 15:52:12 localhost.localdomain kill[4115]: kill: cannot find process "" Mar 05 15:52:12 localhost.localdomain systemd[1]: httpd.service: control process exited, code=exited status=1 Mar 05 15:52:12 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server. Mar 05 15:52:12 localhost.localdomain systemd[1]: Unit httpd.service entered failed state. Mar 05 15:52:12 localhost.localdomain systemd[1]: httpd.service failed. Hint: Some lines were ellipsized, use -l to show in full. 

Kommentarer

  • " Adresse som allerede er i bruk " er ganske selvforklarende 🙂 Du har enten noe annet å høre på: 80, eller Listen 80 flere ganger i konfigurasjonsfiler.

Svar

Du må finne ut hvilket program som okkuperer port 80,

netstat -ltp | grep :80 

Drep deretter prosessen og start apache-tjenesten på nytt

Svar

Kan være et problem med nettsted *.conf -fil. Denne kommandoen kan gi et hint:

apachectl configtest 

Svar

Jeg hadde det samme problemet og fikset det.

sudo service apache2 start

Jobb for apache2.service failed becau se kontrollprosessen avsluttet med feilkode. Se systemctl status apache2.service og «journalctl -xe» for detaljer.

Det var konfigurasjonsproblem i 000-default.conf. Jeg hadde ikke lukket VirtualHost-taggen ordentlig.

Legg igjen en kommentar

Din e-postadresse vil ikke bli publisert. Obligatoriske felt er merket med *