yum update shows warnings

[Akami]

Hello,

System: CentOS Linux 7.6.1810 (Core)‬ with Plesk Onyx Version 17.8.11

I'm very new in this, so please do not laugh at me

I get a "package update manager notification" mail

The following package updates are available:
- ImageMagick 6.7.8.9-16.el7_6 from updates repo (currently installed version: 6.7.8.9-15.el7_2 from updates repo)
- bind 32:9.9.4-73.el7_6 from updates repo (currently installed version: 32:9.9.4-72.el7 from base repo)
- bind-libs 32:9.9.4-73.el7_6 from updates repo (currently installed version: 32:9.9.4-72.el7 from base repo)
- bind-libs-lite 32:9.9.4-73.el7_6 from updates repo (currently installed version: 32:9.9.4-72.el7 from base repo)
- bind-license 32:9.9.4-73.el7_6 from updates repo (currently installed version: 32:9.9.4-72.el7 from base repo)
- bind-utils 32:9.9.4-73.el7_6 from updates repo (currently installed version: 32:9.9.4-72.el7 from base repo)
- device-mapper 7:1.02.149-10.el7_6.3 from updates repo (currently installed version: 7:1.02.149-10.el7_6.2 from updates repo)
- device-mapper-libs 7:1.02.149-10.el7_6.3 from updates repo (currently installed version: 7:1.02.149-10.el7_6.2 from updates repo)
- freetype 2.8-12.el7_6.1 from updates repo (currently installed version: 2.8-12.el7 from base repo)
- glibc 2.17-260.el7_6.3 from updates repo (currently installed version: 2.17-260.el7 from base repo)
- glibc-common 2.17-260.el7_6.3 from updates repo (currently installed version: 2.17-260.el7 from base repo)
- glibc-devel 2.17-260.el7_6.3 from updates repo (currently installed version: 2.17-260.el7 from base repo)
- glibc-headers 2.17-260.el7_6.3 from updates repo (currently installed version: 2.17-260.el7 from base repo)
- grub2 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-common 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-pc 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-pc-modules 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-tools 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-tools-extra 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-tools-minimal 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- krb5-libs 1.15.1-37.el7_6 from updates repo (currently installed version: 1.15.1-34.el7 from base repo)
- libgudev1 219-62.el7_6.3 from updates repo (currently installed version: 219-62.el7_6.2 from updates repo)
- mesa-libEGL 18.0.5-4.el7_6 from updates repo (currently installed version: 18.0.5-3.el7 from base repo)
- mesa-libGL 18.0.5-4.el7_6 from updates repo (currently installed version: 18.0.5-3.el7 from base repo)
- mesa-libgbm 18.0.5-4.el7_6 from updates repo (currently installed version: 18.0.5-3.el7 from base repo)
- mesa-libglapi 18.0.5-4.el7_6 from updates repo (currently installed version: 18.0.5-3.el7 from base repo)
- nss 3.36.0-7.1.el7_6 from updates repo (currently installed version: 3.36.0-7.el7_5 from updates repo)
- nss-sysinit 3.36.0-7.1.el7_6 from updates repo (currently installed version: 3.36.0-7.el7_5 from updates repo)
- nss-tools 3.36.0-7.1.el7_6 from updates repo (currently installed version: 3.36.0-7.el7_5 from updates repo)
- nss-util 3.36.0-1.1.el7_6 from updates repo (currently installed version: 3.36.0-1.el7_5 from updates repo)
- openldap 2.4.44-21.el7_6 from updates repo (currently installed version: 2.4.44-20.el7 from base repo)
- policycoreutils 2.5-29.el7_6.1 from updates repo (currently installed version: 2.5-29.el7 from base repo)
- policycoreutils-devel 2.5-29.el7_6.1 from updates repo (currently installed version: 2.5-29.el7 from base repo)
- policycoreutils-python 2.5-29.el7_6.1 from updates repo (currently installed version: 2.5-29.el7 from base repo)
- python-perf 3.10.0-957.5.1.el7 from updates repo (currently installed version: 3.10.0-957.1.3.el7 from updates repo)
- selinux-policy 3.13.1-229.el7_6.9 from updates repo (currently installed version: 3.13.1-229.el7_6.6 from updates repo)
- selinux-policy-devel 3.13.1-229.el7_6.9 from updates repo (currently installed version: 3.13.1-229.el7_6.6 from updates repo)
- selinux-policy-targeted 3.13.1-229.el7_6.9 from updates repo (currently installed version: 3.13.1-229.el7_6.6 from updates repo)
- systemd 219-62.el7_6.3 from updates repo (currently installed version: 219-62.el7_6.2 from updates repo)
- systemd-libs 219-62.el7_6.3 from updates repo (currently installed version: 219-62.el7_6.2 from updates repo)
- systemd-networkd 219-62.el7_6.3 from updates repo (currently installed version: 219-62.el7_6.2 from updates repo)
- systemd-sysv 219-62.el7_6.3 from updates repo (currently installed version: 219-62.el7_6.2 from updates repo)

So I start a yum update and see three warnings

Cleanup : 32:bind-9.9.4-72.el7.x86_64 [49/96]
ValueError: SELinux policy is not managed or store cannot be accessed.
warning: %postun(bind-32:9.9.4-72.el7.x86_64) scriptlet failed, exit status 1
Non-fatal POSTUN scriptlet failure in rpm package 32:bind-9.9.4-72.el7.x86_64
Cleanup : 32:bind-utils-9.9.4-72.el7.x86_64 [50/96]
...
...
Cleanup : kernel-3.10.0-862.6.3.el7.x86_64 [75/96]
warning: file /lib/modules/3.10.0-862.6.3.el7.x86_64/updates: remove failed: No such file or directory
Cleanup : 1:grub2-tools-extra-2.02-0.76.el7.centos.x86_64 [76/96]
...
...
Cleanup : glibc-2.17-260.el7 [96/96]
OSError: No such file or directory
ValueError: SELinux policy is not managed or store cannot be accessed.
warning: %posttrans(bind-32:9.9.4-73.el7_6.x86_64) scriptlet failed, exit status 1
Non-fatal POSTTRANS scriptlet failure in rpm package 32:bind-9.9.4-73.el7_6.x86_64
Verifying : nss-sysinit-3.36.0-7.1.el7_6.x86_64 [1/96]

My question is here; are this warnings irrelevant or its possible I can make "something" so next time the update run without this warnings? Thanks.

[desertcat]

Hello,

System: CentOS Linux 7.6.1810 (Core)‬ with Plesk Onyx Version 17.8.11

I'm very new in this, so please do not laugh at me

I get a "package update manager notification" mail

The following package updates are available:
- ImageMagick 6.7.8.9-16.el7_6 from updates repo (currently installed version: 6.7.8.9-15.el7_2 from updates repo)
- bind 32:9.9.4-73.el7_6 from updates repo (currently installed version: 32:9.9.4-72.el7 from base repo)
- bind-libs 32:9.9.4-73.el7_6 from updates repo (currently installed version: 32:9.9.4-72.el7 from base repo)
- bind-libs-lite 32:9.9.4-73.el7_6 from updates repo (currently installed version: 32:9.9.4-72.el7 from base repo)
- bind-license 32:9.9.4-73.el7_6 from updates repo (currently installed version: 32:9.9.4-72.el7 from base repo)
- bind-utils 32:9.9.4-73.el7_6 from updates repo (currently installed version: 32:9.9.4-72.el7 from base repo)
- device-mapper 7:1.02.149-10.el7_6.3 from updates repo (currently installed version: 7:1.02.149-10.el7_6.2 from updates repo)
- device-mapper-libs 7:1.02.149-10.el7_6.3 from updates repo (currently installed version: 7:1.02.149-10.el7_6.2 from updates repo)
- freetype 2.8-12.el7_6.1 from updates repo (currently installed version: 2.8-12.el7 from base repo)
- glibc 2.17-260.el7_6.3 from updates repo (currently installed version: 2.17-260.el7 from base repo)
- glibc-common 2.17-260.el7_6.3 from updates repo (currently installed version: 2.17-260.el7 from base repo)
- glibc-devel 2.17-260.el7_6.3 from updates repo (currently installed version: 2.17-260.el7 from base repo)
- glibc-headers 2.17-260.el7_6.3 from updates repo (currently installed version: 2.17-260.el7 from base repo)
- grub2 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-common 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-pc 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-pc-modules 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-tools 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-tools-extra 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- grub2-tools-minimal 1:2.02-0.76.el7.centos.1 from updates repo (currently installed version: 1:2.02-0.76.el7.centos from base repo)
- krb5-libs 1.15.1-37.el7_6 from updates repo (currently installed version: 1.15.1-34.el7 from base repo)
- libgudev1 219-62.el7_6.3 from updates repo (currently installed version: 219-62.el7_6.2 from updates repo)
- mesa-libEGL 18.0.5-4.el7_6 from updates repo (currently installed version: 18.0.5-3.el7 from base repo)
- mesa-libGL 18.0.5-4.el7_6 from updates repo (currently installed version: 18.0.5-3.el7 from base repo)
- mesa-libgbm 18.0.5-4.el7_6 from updates repo (currently installed version: 18.0.5-3.el7 from base repo)
- mesa-libglapi 18.0.5-4.el7_6 from updates repo (currently installed version: 18.0.5-3.el7 from base repo)
- nss 3.36.0-7.1.el7_6 from updates repo (currently installed version: 3.36.0-7.el7_5 from updates repo)
- nss-sysinit 3.36.0-7.1.el7_6 from updates repo (currently installed version: 3.36.0-7.el7_5 from updates repo)
- nss-tools 3.36.0-7.1.el7_6 from updates repo (currently installed version: 3.36.0-7.el7_5 from updates repo)
- nss-util 3.36.0-1.1.el7_6 from updates repo (currently installed version: 3.36.0-1.el7_5 from updates repo)
- openldap 2.4.44-21.el7_6 from updates repo (currently installed version: 2.4.44-20.el7 from base repo)
- policycoreutils 2.5-29.el7_6.1 from updates repo (currently installed version: 2.5-29.el7 from base repo)
- policycoreutils-devel 2.5-29.el7_6.1 from updates repo (currently installed version: 2.5-29.el7 from base repo)
- policycoreutils-python 2.5-29.el7_6.1 from updates repo (currently installed version: 2.5-29.el7 from base repo)
- python-perf 3.10.0-957.5.1.el7 from updates repo (currently installed version: 3.10.0-957.1.3.el7 from updates repo)
- selinux-policy 3.13.1-229.el7_6.9 from updates repo (currently installed version: 3.13.1-229.el7_6.6 from updates repo)
- selinux-policy-devel 3.13.1-229.el7_6.9 from updates repo (currently installed version: 3.13.1-229.el7_6.6 from updates repo)
- selinux-policy-targeted 3.13.1-229.el7_6.9 from updates repo (currently installed version: 3.13.1-229.el7_6.6 from updates repo)
- systemd 219-62.el7_6.3 from updates repo (currently installed version: 219-62.el7_6.2 from updates repo)
- systemd-libs 219-62.el7_6.3 from updates repo (currently installed version: 219-62.el7_6.2 from updates repo)
- systemd-networkd 219-62.el7_6.3 from updates repo (currently installed version: 219-62.el7_6.2 from updates repo)
- systemd-sysv 219-62.el7_6.3 from updates repo (currently installed version: 219-62.el7_6.2 from updates repo)

So I start a yum update and see three warnings

Cleanup : 32:bind-9.9.4-72.el7.x86_64 [49/96]
ValueError: SELinux policy is not managed or store cannot be accessed.
warning: %postun(bind-32:9.9.4-72.el7.x86_64) scriptlet failed, exit status 1
Non-fatal POSTUN scriptlet failure in rpm package 32:bind-9.9.4-72.el7.x86_64
Cleanup : 32:bind-utils-9.9.4-72.el7.x86_64 [50/96]
...
...
Cleanup : kernel-3.10.0-862.6.3.el7.x86_64 [75/96]
warning: file /lib/modules/3.10.0-862.6.3.el7.x86_64/updates: remove failed: No such file or directory
Cleanup : 1:grub2-tools-extra-2.02-0.76.el7.centos.x86_64 [76/96]
...
...
Cleanup : glibc-2.17-260.el7 [96/96]
OSError: No such file or directory
ValueError: SELinux policy is not managed or store cannot be accessed.
warning: %posttrans(bind-32:9.9.4-73.el7_6.x86_64) scriptlet failed, exit status 1
Non-fatal POSTTRANS scriptlet failure in rpm package 32:bind-9.9.4-73.el7_6.x86_64
Verifying : nss-sysinit-3.36.0-7.1.el7_6.x86_64 [1/96]

My question is here; are this warnings irrelevant or its possible I can make "something" so next time the update run without this warnings? Thanks.

OK you have me stumped, but this would not be the first time: What is "Plesk Onyx Version 17.8.11"? Is this a package that normally comes with CentOS 7?

2. Do you have SELinux ENABLED or disabled. It should be ENABLED by default. If not you need to slowly bring it up to ENABLED.

3. Is this "Plesk Onyx Version 17.8.11" a 32 bit or a 64 bit package? If this program is not normally found in CentOS it *could* be -- or it might NOT be -- due to missing libraries.

4. Final note: What kernel version was this using? kernel-3.10.0-862.6.3.el7.x86_64 was used in CentOS 7.5. Did this program run in 7.5?? Again your problem *may* be due to missing libraries.

I'm tapped out this might the type of question to ask our local guru TrevorH, he might be able to point you in the right direction.

[MartinR]

To quote Trevor:

I believe that what you have was probably once CentOS but we do not support panels on this forum. Not of any type. Plesk/cpanel/directadmin - the whole lot, all modify CentOS to the point where it is not CentOS any more. They have their own configuration methods and ways - none of them standard CentOS ones. If we tell you how to fix a CentOS system that doesn't have Plesk on it and you apply that solution to one with Plesk, you might break it even more than it is now. ...

You have Plesk and that means you need to ask them for support for your problem.

[Ubiquitous]

Hello,

I'm not running Plesk or any such thing, although I'm encountering a similar issue:

Code: Select all

# rpm -q centos-release
centos-release-7-6.1810.2.el7.centos.x86_64

# yum upgrade
...
Updating   : 32:bind-chroot-9.9.4-73.el7_6.x86_64                                        50/134 
...
Cleanup    : 32:bind-9.9.4-72.el7.x86_64                                                 90/134 
ValueError: SELinux policy is not managed or store cannot be accessed.
warning: %postun(bind-32:9.9.4-72.el7.x86_64) scriptlet failed, exit status 1
Non-fatal POSTUN scriptlet failure in rpm package 32:bind-9.9.4-72.el7.x86_64
...
OSError: No such file or directory
ValueError: SELinux policy is not managed or store cannot be accessed.
warning: %posttrans(bind-32:9.9.4-73.el7_6.x86_64) scriptlet failed, exit status 1
Non-fatal POSTTRANS scriptlet failure in rpm package 32:bind-9.9.4-73.el7_6.x86_64
...
Updated:
  ...                                                         
  bind.x86_64 32:9.9.4-73.el7_6                                                                   
  bind-chroot.x86_64 32:9.9.4-73.el7_6                                                            
  bind-libs.x86_64 32:9.9.4-73.el7_6                                                              
  bind-libs-lite.x86_64 32:9.9.4-73.el7_6                                                         
  bind-license.noarch 32:9.9.4-73.el7_6                                                           
  bind-utils.x86_64 32:9.9.4-73.el7_6   

So it does seem that bind was updated, but I'm not sure why the error and such.

[desertcat]

Hello,

I'm not running Plesk or any such thing, although I'm encountering a similar issue:
[snip]

So it does seem that bind was updated, but I'm not sure why the error and such.

OK WHERE did you download the 7.6 iso? If you did not download it from a CentOS official mirror that *might* be your problem. If you *did* download from an official CemtOS mirror site, then it is a puzzle. If you rolled it over from CentOS 7.5 to 7.6 had you installed anything or program that might have used the cursed program.

There are two options here:

1) remove the cursed Plesk Onyx program (yum remove Plesk Onyx or yum erase Plesk Onyx )

2) download a fresh copy of CentOS 7.6 dvd.iso from an OFFICIAL CentOS miror. AFAIK there is NO "CentOS Linux 7.6.1810 (Core)‬ with Plesk Onyx Version 17.8.11"but I could be wrong. There is only CentOS 7.x but NO CentOS 7.x w/Plesk Onyx. If Plesk Onyx is some sort "CentOS Web Panel" read TrveorH's Announcement at the top of the this forums page.

[TrevorH]

That selinux error is one that has been reported elsewhere and the reason for it is as yet undetermined.

[fishface]

For the record, I got this error this morning, first time I've ever seen it. This host has been patched monthly for the last 3 years without a single issue until today.

Minimal software installed, entire root is only 2.2GB, it runs BIND and that is it.

Code: Select all

OSError: No such file or directory
ValueError: SELinux policy is not managed or store cannot be accessed.
warning: %posttrans(bind-32:9.9.4-73.el7_6.x86_64) scriptlet failed, exit status 1
Non-fatal POSTTRANS scriptlet failure in rpm package 32:bind-9.9.4-73.el7_64 

It did update BIND though, and seems to work fine.

I'll let you know what I find.

[fishface]

Well, I may have find a cause, but cannot be certain.

I have 2 identical hosts running BIND, I updated one host and got the scriptlet error, so I held off updating the other one.

From what I read, this type of error can often be down to selinux mislabeling, so I went and checked my selinux status on the host that had the scriptlet error, and sure enough it was disabled, but enabled on the other host, and that jogged my memory, I was troubleshooting something a few weeks back and I had temporarily disabled selinux, my bad.

I double checked that something was up with selinux by using

Code: Select all

ls -Z /usr/bin/rpm

and it came back with no security context, so I re-enabled selinux, rebooted to get everything re-labelled, and now when I check I get

Code: Select all

ls -Z  /usr/bin/rpm

Code: Select all

rpm_exec_t

I cannot be certain that this fixes the issue, but it might be worth check the status of selinux

Code: Select all

sestatus

I'l will know for certain when I next patch, this still maybe be a bug in the scriptlet, as I would have thought it should have handled the selinux status without throwing an error like that.

[Akami]

My selinux is disabled too. The most server host disable selinux by default.

[fishface]

Well, all I can say is this, I've just patched updated the other identical host, when I say identical, one is a VM clone of the other, the only differences being host identity stuff, IP. hostname etc, and of course, BIND is configured as a secondary and the other as a primary, and it updated without issue, the only difference, which I mentioned in a previous post, is I had forgotten I had temporarily disabled selinux on the one that had the issue.

Is there a reason why you have disabled selinux?

This is what everything looks like with selinux enabled

Code: Select all

[me@foo ~]# sestatus
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   enforcing
Mode from config file:          enforcing
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Max kernel policy version:      31
[me@foo ~]# ls -Z /usr/bin/rpm
-rwxr-xr-x. root root system_u:object_r:rpm_exec_t:s0  /usr/bin/rpm