package collectd-core 5.9.2.g-1ubuntu5 failed to install/upgrade: installed collectd-core package post-installation script subprocess returned error exit status 1

[Jay Deiman]

This was part of the upgrade from 19.10 -> 20.04

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: collectd-core 5.9.2.g-1ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Apr 23 23:25:20 2020
ErrorMessage: installed collectd-core package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2014-10-18 (2014 days ago)
InstallationMedia:

Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2
SourcePackage: collectd
Title: package collectd-core 5.9.2.g-1ubuntu5 failed to install/upgrade: installed collectd-core package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jay Deiman (jay-splitstreams)]

I found out what the issue seems to be here. In the version of collectd that shipped with 18.04, the parsing of the config file was much more lenient. Specifically it would allow you to have a configuration for plugin that wasn't actually loaded. For example, you could have something like:

```
#LoadPlugin x

<Plugin x>
   Option y
</Plugin>
```

This was perfectly fine in the version on 18.04 (5.7.2-2ubuntu1.2), but in 20.04 (5.9.2.g-1ubuntu5), this will cause collectd to fail to startup until you comment out the `<Plugin x>` section.

[Denys Fedoryshchenko (nuclearcat)]

Happened same for me during upgrade