Forwarded to devs Issue - Package Update Manager notification

[trialotto]

TITLE:

Issue - Package Update Manager notification​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Product version: Plesk Onyx 17.8.11 Update #67
Update date: 2019/09/08 06:27
Build date: 2019/08/23 04:42
OS version: Ubuntu 18.04
Revision: 0c83d4cc5c2d9988bb3b51f3951ce9d89580fd83
Architecture: 64-bit
Wrapper version: 1.2

Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic​

PROBLEM DESCRIPTION:

Notification mail of Plesk Update Manager (PUM) shows errors.

In essence, a false notification - reason unknown (see below).

Might be related to this issue.​

STEPS TO REPRODUCE:

Activate PUM notifications by mail.​

ACTUAL RESULT:

A mail notification of issues with the content :

Some problems occurred with the System Updates tool on your server [domain].[tld]. Please resolve them manually.

Reason: 2019-09-12 06:25:12 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2019-09-12 06:25:23 ERROR:
2019-09-12 06:25:23 ERROR: Exited with returncode 1.​

EXPECTED RESULT:

EXPECTED : no issues.

VERIFY : steps to verify that no issues are present:

1) run the command

plesk sbin pum --check

and the result is

2019-09-12 07:09:31 INFO: pum is called with arguments: ['--check']

and that is just to verify that everything is ok and that other issues do not affect any analysis of the current issue.

2) run the command

plesk sbin pum --list --repo-info --json

to replicate the command indicated in the mail notification - the result is

[ ... json file ...]
2019-09-12 07:00:58 INFO: pum completed successfully

and that is a clear indication that the mail notification is false.​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

Developer wrote:

After installing kernelcare-plesk extension (w/o license):

# dpkg -l '*kernel*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                    Version          Architecture     Description
+++-=======================-================-================-===================================================
iU  kernelcare              2.21-1           amd64            Tools for KernelCare
un  linux-kernel-log-daemon <none>           <none>           (no description available)
un  nfs-kernel-server       <none>           <none>           (no description available)
# plesk sbin pum --list --repo-info --json
2019-09-13 18:19:32 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
...
2019-09-13 18:22:00 INFO: pum completed successfully
# echo $?
0
# plesk sbin pum --check
2019-09-13 18:43:52 INFO: pum is called with arguments: ['--check']
2019-09-13 18:43:55 ERROR: Exited with returncode 1.
The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure
menu option in dselect for them to work:
 kernelcare           Tools for KernelCare
 
exit status 1

Turning PUM email notifications on and running plesk daily didn't result in any notification emails.
So I couldn't reproduce the problem.

 

[IgorG]

You can contact Plesk Support Team for providing access for the further investigation directly on your server.

 

[trialotto]

@IgorG

Not an issue anymore - seems to be the case that a number of unrelated issues concerning packages were occurring at more or less the same time interval, causing a stack of package related issues that -coincidentally- do affect each other.

In short, not systematic in the sense of permanent bug.

Nevertheless, I did some testing on various servers with almost identical setups, with the exception of the aum and modsecurity packages - small differences were added.

From the small config differences -added on purpose- it seemed to be the case that the aum package, combined with a setting of automatic upgrades, could be causing (but is not certain to cause) the issues mentioned.

However, I can say that the bug report can be closed - it should not really matter due to mu #68.

Kind regards......