How to disable "New software packages available" Mailing

S

s.gruner

Active Member
Proxmox Subscriber
Sep 28, 2011
34
1
28
Hey,

how can i disable the "New software packages available" mailing in proxmox 3.4?
i want to receive error messages and other important messages, but i don't need this
update information.


root@proxmox01:~# pveversion
pve-manager/3.4-6/102d4547 (running kernel: 2.6.32-38-pve)
root@proxmox01:~# pveversion -v
proxmox-ve-2.6.32: 3.4-155 (running kernel: 2.6.32-38-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-38-pve: 2.6.32-155
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-17
qemu-server: 3.4-5
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

thanks for help
gruner
 
there is no easy way to disable this. btw, this is an important message.
 
we have a productive environment with multiple pve instances, so we can't an won't update if there are only a few new packages.
If we update our pve instances, then we perform multiple test-scenarios in a seperate environment, before we upgrade our productive system.
For this reason, we have very long update-cycles and we won't get these messages all 1 to 2 weeks.
 
if there is no possibility to disable these Messages, then i want you to create a feature request for configuring what messages are reported through mailing.

regards,
gruner
 
Is there still no easy way to disable "New software packages available" messages in Proxmox VE 5.1? For us, this information is of no importance as anyway we are monitoring new package availability with apticron on every host.
 
Hi,

I'm stumbled over this Problem again in PVE 5.1. The only solution i Found is to comment out the matching section in the responsible script.
The script is located in /usr/bin/pveupdate. Make a backup-copy first. The upgrade section you have to comment out is shown below:

Code: 
...
if (my $info = PVE::INotify::read_file('subscription')) {
    # We assume that users with subscriptions want informations
    # about new packages.
    if ($info->{status} eq 'Active') {
        eval { PVE::API2::APT->update_database({ node => $nodename, notify => 1, quiet => 1 }); };
        if (my $err = $@) {
            syslog ('err', "update apt database failed: $err");
        }
    }
}
...

this solution worked for me. i can't found an other way around this mailing...

kind regards
gruner
 
You must log in or register to reply here.
Top Bottom