ampache installer doesn't create apache2 configuration

Bug #996507 reported by pheidrias
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
ampache (Ubuntu)
Fix Released
Undecided
Charlie_Smotherman

Bug Description

When installing ampache 3.6~alpha1-0ubuntu6 on a Ubuntu 12.04 server, the installer asks wether to create the lighttpd and ampache configs, but fails to create the ampache configuration file.

The subsequent error message is:
"Something weird has happened, unable to create ampache vhost."
which is surely because there ist no such file in /et/ampache to be symlinked!

Expected: Create apache2-config file in /etc/ampache and symlink it to /etc/apache2/conf.d/

Happened: No config was created in /etc/ampache

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ampache 3.6~alpha1-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Tue May 8 14:10:58 2012
InstallationMedia:

PackageArchitecture: all
SourcePackage: ampache
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
pheidrias (5-launchpad-net-pheidrias-info) wrote :
Changed in ampache (Ubuntu):
assignee: nobody → Charlie_Smotherman (porthose) (cjsmo)
Revision history for this message
Charlie_Smotherman (cjsmo) wrote :

pheidrias,

To help me figure out what went wrong could you please provide some additional information?
Do you still have the install log? if so would you please attache it.
How did you answer the second debconf question "Configure and restart the web server?" yes or no? If you answered no then you may simply need to restart/reload the web server.
Ampaches post installation script has a number of sanity checks namely what was the output for sc010, sc101, sc102, sc103, sc104 they should have been printed right before the error message you posted.
Is /etc/apache2/sites-available/AmpacheApache present?
Is /etc/apache2/sites-available/ampvhadd present?

FWIW ampaches packaging is being totally reworked (simplified) for the apache2.4 transition currently taking place in debian.

Revision history for this message
pheidrias (5-launchpad-net-pheidrias-info) wrote :

Where could I find the install log?

I tried answering the debconf-questions all ways and combinations: lighttpd AND/OR apache2, restart yes OR no

I've never seen /etc/apache2/sites-available/AmpacheApache and ampvhadd was not created.

However, if I take the DEB (all) of the latest 3.5-release, the ampvhadd is created! I had to symlink it manually to /etc/apache2/sites-enabled to get in working (having had to modify it, too, du to some "access forbidden" errors with the original ampvhadd file).

If you provide me with instructions on how to create a better report for you, I can run the new installer again!

Revision history for this message
Charlie_Smotherman (cjsmo) wrote :

No need to run the installer again, you have given me enough information to determine where the postinst is failing. However with the apache2.4 transition going on in debian this particular section of code will be going away. UDS is in progress right now but I would suspect the server team will probably transition over to apache2.4 during this cycle. Contengent on what is decided at UDS, will determine if I do an upload to fix this. We should have a clearer path forward at the end of this week

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ampache - 3.6-git408e713+dfsg-1

---------------
ampache (3.6-git408e713+dfsg-1) unstable; urgency=low

  * New upstream git snapshot, using commit
    408e71344ade84685c181cd326e2ec5e79c9157b Closes: #668932, #668936
  * Prep for apache2.4 transition.
  * Removed files ApacheAmpache, lighttpd_ampache.conf, mythbuntu.ampache.conf
    and vhost, they are no longer needed.
  * Added debain/conf/ampache.conf to be more inline with the apache2.4
    transition. This required a rewrite of the postinst, postrm, and preinst.
    Closes: #668639, #656553 LP: #996507
  * Split package into ampache and ampache-common. Ampache behaves the same
    and installs the apache2 web server, as where ampache-common will not.
    This will allow users to deploy ampache on other web servers if they wish.
    Removed support for lighttpd and mythbuntu as I do not feel comfortable
    supporting web servers I no longer use. Closes: #666005
  * Removed debconf question from ampache.config and ampache.templates,
    updated po files with debconf-updatepo.
  * Updated README.Debian to mention the package split.
  * Removed cruft from debian/rules and updated get-orig-source to retrieve
    source files from upstreams git repo. Added additional rules to remove
    embedded copies of code and nonfree fonts. Disabled debian/watch.
  * debian/control added ampache-common binary stanza and adjusted
    dependencies to remove mythbuntu and lighttpd support. Added php-gettext
    to dependencies as upstream now uses it.
  * Update debian/copyright with the fresh theme copyright info, udated
    header information. Added missing CC-BY-3.0 license field. Corrected
    typo's.

 -- Charlie Smotherman <email address hidden> Thu, 31 May 2012 15:25:52 -0500

Changed in ampache (Ubuntu):
status: New → Fix Released
Revision history for this message
liberal-animation (liberal-animation) wrote :

Where was this fix released? I just installed ampache from the 12.04 repositories, and I have the exact same problem. There is no /etc/ampache.conf although I do have /etc/sites-available/ApacheAmpache.
Is there a ppa that I should set up, or will the fix be in the repos soon?
Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.