package sabnzbdplus 1.1.1+dfsg-1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

[Peter Havekes]

Could not install on clean ubuntu 17.10 setup

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: sabnzbdplus 1.1.1+dfsg-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Fri Nov 10 10:11:35 2017
DuplicateSignature:
 package:sabnzbdplus:1.1.1+dfsg-1
 Setting up sabnzbdplus (1.1.1+dfsg-1) ...
 dpkg: error processing package sabnzbdplus (--configure):
  subprocess installed post-installation script was killed by signal (Terminated)
ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated)
InstallationDate: Installed on 2017-10-30 (10 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5
SourcePackage: sabnzbdplus
Title: package sabnzbdplus 1.1.1+dfsg-1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
UpgradeStatus: No upgrade log present (probably fresh install)

[jcfp (jcfp)]

Was your system under heavy load at the time (the logs mention of host of cryptominers)?
Is this issue reproducible if you retry the install?

Please post the full output of: sudo /bin/sh -x /var/lib/dpkg/info/sabnzbdplus.postinst configure

[Peter Havekes (peter-havekes)]

A second attempt to install went without issues.

[jcfp (jcfp)]

Given that the script contains only automatically inserted code from debhelper and worked fine on retry, I don't think this problem is caused by sabnzbdplus. You failed to provide an answer as to the system load at the time, so I'm going to have to assume this is the oom killer or similar mechanisms at work.

Closing for now, feel free to reopen if you find a way to reproduce.