package psad 2.4.3-1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1711500 reported by Eric
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
psad (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10

Failed to start LSB

Result of systemctl status psad.service
● psad.service - LSB: Port Scan Attack Detector (psad)
   Loaded: loaded (/etc/init.d/psad; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2017-08-18 10:44:46 +07; 4min 24s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 23652 ExecStart=/etc/init.d/psad start (code=exited, status=1/FAILURE)
      CPU: 138ms

Aug 18 10:44:46 -1 psad[23677]: imported TOS-based passive OS fingerprinting signatures
Aug 18 10:44:46 -1 psad[23677]: imported original Snort rules in /etc/psad/snort_rules/ for reference info
Aug 18 10:44:46 -1 psad[23652]: [*] import_signatures(): bad signature on line: 1 at /usr/sbin/psad line 4192, <SIGS> line 1.
Aug 18 10:44:46 -1 psad[23652]: * Unable to start the daemon
Aug 18 10:44:46 -1 psad[23652]: * Starting Port Scan Attack Detector psad
Aug 18 10:44:46 -1 psad[23652]: ...fail!
Aug 18 10:44:46 -1 systemd[1]: psad.service: Control process exited, code=exited status=1
Aug 18 10:44:46 -1 systemd[1]: Failed to start LSB: Port Scan Attack Detector (psad).
Aug 18 10:44:46 -1 systemd[1]: psad.service: Unit entered failed state.
Aug 18 10:44:46 -1 systemd[1]: psad.service: Failed with result 'exit-code'.

Result of journalctl -xe
Aug 18 10:45:01 -1 CRON[23754]: pam_unix(cron:session): session opened for user root by (uid=0)
Aug 18 10:45:01 -1 CRON[23756]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 10:45:01 -1 CRON[23754]: pam_unix(cron:session): session closed for user root
Aug 18 10:45:05 -1 gnome-terminal-[4732]: Allocating size to GtkBox 0x7e44995f40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Aug 18 10:45:05 -1 xdg-document-portal[5175]: unique: 38, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 4318
Aug 18 10:45:05 -1 xdg-document-portal[5175]: unique: 38, success, outsize: 96
Aug 18 10:46:05 -1 xdg-document-portal[5175]: unique: 39, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 4318
Aug 18 10:46:05 -1 xdg-document-portal[5175]: unique: 39, success, outsize: 96
Aug 18 10:46:16 -1 systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start timed out.
Aug 18 10:46:16 -1 systemd[1]: Timed out waiting for device dev-mapper-cryptswap1.device.
-- Subject: Unit dev-mapper-cryptswap1.device has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit dev-mapper-cryptswap1.device has failed.
--
-- The result is timeout.
Aug 18 10:46:16 -1 systemd[1]: Dependency failed for Cryptography Setup for cryptswap1.
-- Subject: Unit <email address hidden> has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit <email address hidden> has failed.
--
-- The result is dependency.
Aug 18 10:46:16 -1 systemd[1]: <email address hidden>: Job <email address hidden>/start failed with result 'dependency'.
Aug 18 10:46:16 -1 systemd[1]: Dependency failed for /dev/mapper/cryptswap1.
-- Subject: Unit dev-mapper-cryptswap1.swap has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit dev-mapper-cryptswap1.swap has failed.
--
-- The result is dependency.
Aug 18 10:46:16 -1 systemd[1]: dev-mapper-cryptswap1.swap: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
Aug 18 10:46:16 -1 systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'timeout'.
Aug 18 10:46:16 -1 systemd[1]: Unnecessary job for dev-disk-by\x2duuid-60c74751\x2d5304\x2d4cb9\x2db08e\x2de0c70e655655.device was removed.
-- Subject: Unit dev-disk-by\x2duuid-60c74751\x2d5304\x2d4cb9\x2db08e\x2de0c70e655655.device has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit dev-disk-by\x2duuid-60c74751\x2d5304\x2d4cb9\x2db08e\x2de0c70e655655.device has failed.
--
-- The result is collected.
Aug 18 10:46:39 -1 gnome-shell[4130]: JS ERROR: TypeError: app is null
                                             Indicator<._onSettingsClicked@resource:///org/gnome/shell/ui/status/system.js:441:9
                                             wrapper@resource:///org/gnome/gjs/modules/lang.js:178:22
Aug 18 10:47:05 -1 xdg-document-portal[5175]: unique: 40, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 4318
Aug 18 10:47:05 -1 xdg-document-portal[5175]: unique: 40, success, outsize: 96
Aug 18 10:48:05 -1 xdg-document-portal[5175]: unique: 41, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 4318
Aug 18 10:48:05 -1 xdg-document-portal[5175]: unique: 41, success, outsize: 96
Aug 18 10:49:05 -1 xdg-document-portal[5175]: unique: 42, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 4318
Aug 18 10:49:05 -1 xdg-document-portal[5175]: unique: 42, success, outsize: 96

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: psad 2.4.3-1.1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
Date: Fri Aug 18 10:28:51 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-04-19 (120 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5~beta1ubuntu1
SourcePackage: psad
Title: package psad 2.4.3-1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.psad.psad.conf: 2017-05-30T08:58:00.065386
mtime.conffile..etc.psad.signatures: 2017-05-30T10:51:24.504319

Revision history for this message
Eric (eric-grimaldi) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
tags: removed: need-duplicate-check
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.