monit monitor <foo> fails after upgrade to 1:5.16-2ubuntu0.1

Bug #1787623 reported by Jim on 2018-08-17
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
monit (Ubuntu)
Undecided
Unassigned

Bug Description

If I downgrade to 1:5.16-2 it works fine (and 1:5.16-2ubuntu0.1 seems to work fine on 14.04)

$ sudo monit monitor postfix
Invalid action "action=monitor"
$

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: monit 1:5.16-2ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
Uname: Linux 4.4.0-133-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Aug 17 12:54:07 2018
InstallationDate: Installed on 2013-11-05 (1745 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
SourcePackage: monit
UpgradeStatus: Upgraded to xenial on 2018-04-23 (115 days ago)
modified.conffile..etc.monit.conf-available.apache2: [modified]
modified.conffile..etc.monit.monitrc: [inaccessible: [Errno 13] Permission denied: '/etc/monit/monitrc']
modified.conffile..etc.monit.templates.rootbin: [modified]
modified.conffile..etc.monit.templates.rootrc: [modified]
modified.conffile..etc.monit.templates.rootstrict: [modified]
mtime.conffile..etc.monit.conf-available.apache2: 2017-07-20T17:06:11.309116
mtime.conffile..etc.monit.templates.rootbin: 2017-11-03T12:27:27.329460
mtime.conffile..etc.monit.templates.rootrc: 2017-11-03T12:27:21.065539
mtime.conffile..etc.monit.templates.rootstrict: 2017-11-03T12:27:14.249625

Jim (clausing) wrote :
Launchpad Janitor (janitor) wrote :

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

Changed in monit (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers