Hi,
ich habe Apache2 installiert aber er mag nicht starten. Leider kann ich mit den Statusmeldungen nicht viel anfangen:
apache2 status
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2)
Active: active (exited) since Mo 2015-04-27 15:29:49 CEST; 32s ago
Apr 27 15:29:49 thinkpad apache2[30268]: Starting web server: apache2AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127...this message
Apr 27 15:29:49 thinkpad apache2[30268]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Apr 27 15:29:49 thinkpad apache2[30268]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Apr 27 15:29:49 thinkpad apache2[30268]: no listening sockets available, shutting down
Apr 27 15:29:49 thinkpad apache2[30268]: AH00015: Unable to open logs
Apr 27 15:29:49 thinkpad apache2[30268]: Action 'start' failed.
Apr 27 15:29:49 thinkpad apache2[30268]: The Apache error log may have more information.
Apr 27 15:29:49 thinkpad apache2[30268]: .
Die error.log vom apache ist leer. Weiß jemand Rat?
What happens after you do this
systemctl stop apache2.service
systemctl start apache2.service
systemctl enable apache2.service
And as root show the output of
netstat -ltnp | grep ':80'
I found the problem: pywwetha used the port 80. First I killed the process and then I have to stop first apache although is was not running! Then after a restart it works.
Do the system need pywwetha or can I remove the package?
Peter,
pywwetha brauchst du für die lokale Version vom Siduction Manual.
Quote from: harley-peterI found the problem: pywwetha used the port 80. First I killed the process and then I have to stop first apache although is was not running! Then after a restart it works.
Do the system need pywwetha or can I remove the package?
Yup, why I asked for
netstat -ltnp | grep ':80'
as root (if you don't use manual)
kill -9 19971then
apt-get remove --purge pywwethaThat removes
pywwetha* sidu-manual* sidu-manual-data*You can always reinstall if needed
Thank's!
or one could use apache with the right settings ....
it is utter bullshit (false since years) that apache say: I'm your only god - and i claim all *:80 Adresses for me :) - so changing the default vhost to 127.0.0.1:80 will change this stupid apache behaviour.
Quote from: melmarkeror one could use apache with the right settings ....
it is utter bullshit (false since years) that apache say: I'm your only god - and i claim all *:80 Adresses for me
- so changing the default vhost to 127.0.0.1:80 will change this stupid apache behaviour.
True, and if he said he used manual, I would have said to change vhost, my bad because I was in a hurry and shouldn't have replied at all without the correct answer(s) :)
Quote from: melmarker on 2015/04/27, 17:36:52
changing the default vhost to 127.0.0.1:80 will change this stupid apache behaviour.
had i to change the data file /etc/apache2/sites-available/000-default.conf ?
old <VirtualHost *:80>
new <VirtualHost 127.0.0.1:88>
yes - and i would suggest the usage of port 80 instead 88
Nope you have to update /etc/apache2/ports.conf:
Listen <IPv4>:80
Listen [<IPv6>]:80
<IfModule ssl_module>
Listen <IPv4>:443
</IfModule>
<IfModule mod_gnutls.c>
Listen <IPv4>:443
</IfModule>
The ports.conf discribe all ports/ips that apache will listen to. The VirtualHost is only a logic on what <IP> it should give you awnser. You don't have to touch <VirtualHost *:80>. This only means, for all ip addresse, that apache will listen to give me the result. If you wanna change the port from 80->88 than you also have to add this port to port.conf first.