package puppetmaster-passenger 2.7.11-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1015582 reported by john davies
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
puppet (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Once puppetmaster installed, nagios and munin stopped outputting responding, configs altered since the installation

just thought you should know

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: puppetmaster-passenger 2.7.11-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic i686
ApportVersion: 2.0.1-0ubuntu10
Architecture: i386
Date: Wed Jun 20 14:37:03 2012
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
PackageArchitecture: all
SourcePackage: puppet
Title: package puppetmaster-passenger 2.7.11-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to precise on 2012-05-03 (48 days ago)

Revision history for this message
john davies (jr-davies2) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Robie Basak (racb) wrote :

From log:

Setting up puppetmaster-passenger (2.7.11-1ubuntu2) ...
Enabling module ssl.
See /usr/share/doc/apache2.2-common/README.Debian.gz on how to configure SSL and create self-signed certificates.
To activate the new configuration, you need to run:
  service apache2 restart
Module headers already enabled
Enabling site puppetmaster.

To activate the new configuration, you need to run:
  service apache2 reload
 * Restarting web server apache2  apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
 ... waiting .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:8140
no listening sockets available, shutting down
Unable to open logs
Action 'start' failed.
The Apache error log may have more information.

[fail]
invoke-rc.d: initscript apache2, action "restart" failed.
dpkg: error processing puppetmaster-passenger (--configure):
 subprocess installed post-installation script returned error exit status 1

Revision history for this message
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in puppet (Ubuntu):
status: New → Incomplete
Revision history for this message
Steven Kurylo (skurylo) wrote :
Download full text (3.3 KiB)

I can reproduce this error in Percise. What's happening is that apache is being restarted a second time to soon. I've included the postinst script output below.

To test the theory I ran 'invoke-rc.d apache2 restart;invoke-rc.d apache2 restart' - the second restart failed. If I add a sleep 'invoke-rc.d apache2 restart; sleep 1; invoke-rc.d apache2 restart' then the second restart succeeds.

The postinst script could be changed so that it would only ever call restart once.

Looks like there is already a bug files against apache https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1018171

bash -x /var/lib/dpkg/info/puppetmaster-passenger.postinst configure
+ set -e
+ '[' configure = configure ']'
+ dpkg-statoverride --list /usr/share/puppet/rack/puppetmasterd/config.ru
+ '[' '' = '' ']'
++ puppet config print hostcert
+ '[' '!' -e /var/lib/puppet/ssl/certs/example.com.pem ']'
++ puppet config print
++ wc -l
++ grep 'Could not parse'
+ '[' 0 '!=' 0 ']'
+ APACHE2_SITE_FILE=/etc/apache2/sites-available/puppetmaster
+ '[' '!' -e /etc/apache2/sites-available/puppetmaster ']'
+ a2enmod ssl
Module ssl already enabled
+ a2enmod headers
Module headers already enabled
+ a2ensite puppetmaster
Site puppetmaster already enabled
+ '[' -x /etc/init.d/apache2 ']'
++ which invoke-rc.d
+ '[' -x /usr/sbin/invoke-rc.d ']'
+ invoke-rc.d apache2 restart
 * Restarting web server apache2 apache2: Could not reliably determine the server's fully qualified domain name, using example.com for ServerName
[Wed Jul 04 10:54:55 2012] [warn] NameVirtualHost *:80 has no VirtualHosts
 ... waiting apache2: Could not reliably determine the server's fully qualified domain name, using example.com for ServerName
[Wed Jul 04 10:54:56 2012] [warn] NameVirtualHost *:80 has no VirtualHosts
                                                                                                                                          [ OK ]
+ dpkg --compare-versions '' lt-nl 2.6.1-1
+ dpkg --compare-versions '' le 2.7.11-1
+ APACHE2_SITE_FILE=/etc/apache2/sites-available/puppetmaster
+ '[' -e /etc/apache2/sites-available/puppetmaster ']'
+ sed -r -i 's|/etc/puppet/rack|/usr/share/puppet/rack/puppetmasterd|' /etc/apache2/sites-available/puppetmaster
+ a2enmod headers
Module headers already enabled
+ '[' -x /etc/init.d/apache2 ']'
++ which invoke-rc.d
+ '[' -x /usr/sbin/invoke-rc.d ']'
+ invoke-rc.d apache2 restart
 * Restarting web server apache2 apache2: Could not reliably determine the server's fully qualified domain name, using example.com for ServerName
[Wed Jul 04 10:54:57 2012] [warn] NameVirtualHost *:80 has no VirtualHosts
apache2: Could not reliably determine the server's fully qualified domain name, using example.com for ServerName
[Wed Jul 04 10:54:57 2012] [warn] NameVirtualHost *:80 has no VirtualHosts
(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
             ...

Read more...

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

[Expired for puppet (Ubuntu) because there has been no activity for 60 days.]

Changed in puppet (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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