ampache

Gamaliel,

Could you please provide some additional information. Do you have any other web servers installed which may be competing for port :80.

The reason I ask is due to this line in your error log:

apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName

**(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80**

no listening sockets available, shutting down

Unable to open logs

   ...fail!

invoke-rc.d: initscript apache2, action "restart" failed.

dpkg: error al procesar ampache (--configure):

 el subproceso post-installation script devolvió el código de salida de error 1

Charlie
(porthose)

This is not a bug in ampache but instead is a misconfiguration of the users system. According to the DpkgTerminalLog the user has three web servers installed on his system, caudium, apache2 and apache2-mpm-prefork.
1. On line 1543 apache2 is restarted with no problems.
2. On line 1896 the caudium web server is installed and started
3. On line 2545 apache2 attempts to restart after apache2-utils and apache2.2-common are installed. Starting apache2 fails and restarting fails. this could be due to caudium or apache2 webservers being bound to port :80 thus not allowing apache2-mpm-prefork from starting. From this point on apache2 never starts or restarts.

As restarting the apache2-mpm-prefork web server is part of ampache's postinst script. If apache2-mpm-prefork will not restart then this will return a exit status of 1 causing the installation to fail.