Now you will either see apache still running -> it means something is restarting it and you need to find it why. If you will see process ID with apache, try to firstly send kill signalĪgain, list processes with ps commmand and if you see apache, kill it with SIGKILL I would firstly try to stop Apache sudo /opt/bitnami/ctlscript.sh stop apacheĪfter that it is smart to see if apache was really shutted down I think that kill of the first process got it to work, but after server restart I get the same error message and killing the process and start apache is necessary :( opt/bitnami/apache2/scripts/ctl.sh : httpd started at port 80 Well, it's working now, ps aux | grep apache I can still access the "Apache2 Debian default page" when I enter ip in the browser. When I stop apache with this /opt/bitnami/ctlscript.sh status apacheĪpache not netstat -tulpn | grep apache2 Tcp6 0 0 :::80 :::* sudo netstat -ltnp | grep also change the ownership of the log to www-data, but nothing changed. Tcp6 0 0 :::80 :::* netstat -tulpn | grep apache2 I tried this : sudo netstat -ltnp | grep ':80' Most answers to similar problems with binding were about killing the second apache processes, but I found only one apache2 listening. I tried to search web for the solution, but I did'nt find exactly the same error message.
opt/bitnami/apache2/scripts/ctl.sh : httpd could not be started No listening sockets available, shutting down (98)Address already in use: AH00073: make_sock: unable to listen for When I try to start apache, I get this: sudo /opt/bitnami/ctlscript.sh start apache When I enter the ip in the browser, I get the initial screen of apache web server, but the web page don't work. I suppose the apachetop installation caused this problem. I tried to secure apache server according to best practices and the last two things I changed was adding "FileETag None" in some config files and installed apachetop to monitor web server. I have Debian 9 installation (Bitnami appliance) with Moodle learning system and Lambda theme.
0 kommentar(er)
