Puppet: System Administration Automated

Support

Ticket #1206 (new defect)

Opened 5 months ago

Last modified 4 months ago

aptitude provider does not recognize recovery efforts

Reported by: RNHurt Assigned to: community
Priority: normal Milestone:
Component: Debian Version: 0.24.4
Severity: normal Keywords: aptitude dpkg error recover
Cc: Triage Stage: Needs more info
Attached Patches: None Complexity: Unknown

Description

The boxbackup 0.10 package from Debian backports is failing to install via Puppet 0.2.24. It looks as though there is an error in the package and the initial configuration fails. However, aptitude (and I assume apt-get) by default tries to recover from the error and in this case succeeds. Subsequent aptitude purge & installs work just fine and only the initial install causes this error.

The problem is that Puppet flags this install as a complete loss for some reason and keeps trying to install the package. I took the command out of the Puppet log file and ran it manually and captured the output as seen below. After I ran this install Puppet accepted the install and everything looks OK. The only problem is the initial install. Is there an option to the apt(itude) providers to allow them to perform the recovery or should I use a force 

2D0987B9:~# /usr/bin/aptitude -y -o DPkg::Options::=--force-confold install boxbackup-client=0.10-1~bpo.1
Reading package lists... Done
Building dependency tree... Done
Reading extended state information       
Initializing package states... Done
Writing extended state information... Done
Reading task descriptions... Done         
Building tag database... Done    
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done
Setting up boxbackup-client (0.10-1~bpo.1) ...

Creating config file /etc/boxbackup/bbackupd.conf with new version

Creating config file /etc/boxbackup/bbackupd/notifyadmin with new version
/etc/init.d/boxbackup-client: line 27: [: too many arguments
/etc/init.d/boxbackup-client: line 30: [: too many arguments
Starting boxbackup-client: Box Backup Client v0.10, (c) Ben Summers and contributors 2003-2006
bbackupd: failed to start: failed to open configuration file: /var/run/bbackupd.pidinvoke-rc.d: initscript boxbackup-client, action "start" failed.
dpkg: error processing boxbackup-client (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 boxbackup-client
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up boxbackup-client (0.10-1~bpo.1) ...
Replacing config file /etc/boxbackup/bbackupd.conf with new version
Replacing config file /etc/boxbackup/bbackupd/notifyadmin with new version

2D0987B9:~#

Attachments

puppetd.log.gz (2.1 kB) - added by RNHurt on 04/28/08 16:12:33.
puppetd trace log file output

Change History

04/28/08 13:59:46 changed by jamtur01

  • stage changed from Unreviewed to Needs more info.

Can you capture the output from Puppet too?

04/28/08 14:18:14 changed by RNHurt

Yes. Is there any specific type of output you would like? Do I have to run puppet in standalone with debug on or something? Would it be something like /usr/bin/puppetd --no-daemonize --debug --onetime --verbose? Just let me know and I'll get it going.

Thanx!

Richard

(follow-up: ↓ 4 ) 04/28/08 14:35:25 changed by jamtur01

something like puppetd --verbose --debug --trace would be perfect. Don't forget to use to ensure the wiki format works.

04/28/08 16:12:33 changed by RNHurt

  • attachment puppetd.log.gz added.

puppetd trace log file output

(in reply to: ↑ 3 ) 04/28/08 16:14:38 changed by RNHurt

Replying to jamtur01:

something like puppetd --verbose --debug --trace would be perfect. Don't forget to use to ensure the wiki format works.

Done. The output had quite a bit of control character "noise" so I gzipped & attached it instead of pasting it in the text. I hope that's alright. I also turned off most of my manifests to keep the output simple and small.

(follow-up: ↓ 7 ) 05/12/08 23:40:32 changed by luke

What does dpkg-query show as the status of the package now? That's what puppet uses to determine what to do.

05/20/08 12:26:06 changed by RNHurt

Darn it! It looks like they have fixed the bug in the Debian Box Backup? package that was causing the install to fail. I'll have to see if I can reproduce it by using the old package.

(in reply to: ↑ 5 ) 05/21/08 03:06:17 changed by RNHurt

Replying to luke:

What does dpkg-query show as the status of the package now? That's what puppet uses to determine what to do.

Here is the output from apt-cache and dpkg-query:

joey-18ABF00D:~# apt-cache policy boxbackup-client boxbackup-client:

Installed: 0.10-1~bpo.1 Candidate: 0.10-1~bpo.1 Version table:

0.11~rc2-3~bpo40+1 0

1 http://update.kangaroobox.com etch-backports/main Packages

*** 0.10-1~bpo.1 0

500 http://update.kangaroobox.com stable/main Packages 100 /var/lib/dpkg/status

joey-18ABF00D:~# /usr/bin/dpkg-query -W --showformat '${Status} ${Package} ${Version}\n' boxbackup-client install ok half-configured boxbackup-client 0.10-1~bpo.1 joey-18ABF00D:~#

05/21/08 03:10:27 changed by RNHurt

Lets try that again. 

joey-18ABF00D:~# apt-cache policy boxbackup-client
boxbackup-client:
  Installed: 0.10-1~bpo.1
  Candidate: 0.10-1~bpo.1
  Version table:
     0.11~rc2-3~bpo40+1 0
          1 http://update.kangaroobox.com etch-backports/main Packages
 *** 0.10-1~bpo.1 0
        500 http://update.kangaroobox.com stable/main Packages
        100 /var/lib/dpkg/status
joey-18ABF00D:~# /usr/bin/dpkg-query -W --showformat '${Status} ${Package} ${Version}\n' boxbackup-client
install ok half-configured boxbackup-client 0.10-1~bpo.1
joey-18ABF00D:~#