![]() So as more client connection you have as more processes you will get. ![]() When you are finished, you can apply the new settings by rebuilding the container first delete it with docker-compose down, then restart it with docker-compose up -d. You should not use the default mariadb passphrases, for example. In this way, clients do not need to wait for a new child processes to be forked before their requests can be served. There are also some things in the docker-compose.yml which you may want to change. Apache always tries to maintain several spare or idle server processes, which stand ready to serve incoming requests. It did not show anything apart from telling that The diagnostic bundle was uploaded successfully to the Bitnami servers. In the default installation you would use Apache MPM (Multi-Processing Module) Prefork.įrom the Apache Apache MPM prefork documentation:Ī single control process is responsible for launching child processes which listen for connections and serve them when they arrive. Each Bitnami stack includes a control script that lets you easily stop, start and restart services. The Apache error log may have more information. If ownCloud clients cannot connect to your ownCloud server, check to see if PROPFIND requests receive HTTP/1.1 401 Unauthorized responses. ![]() Yes thats normal and does not have to do anything with OwnCloud itself but how you have configured apache. if I run sudo /etc/init.d/apache2 restart I get: Restarting web server apache2 (98)Address already in use: makesock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs Action 'start' failed.
0 Comments
Leave a Reply. |