Re: [CentOS] yum update security updates only

[Laack, Andrea P]

We utilize Spacewalk and the errata from https://cefs.steve-meier.de/ to 
provide this function for CentOS.

Andrea

-Original Message-
From: CentOS  On Behalf Of Jon Pruente
Sent: Friday, November 13, 2020 7:08 PM
To: CentOS mailing list 
Subject: {EXTERNAL} Re: [CentOS] yum update security updates only


CAUTION:  This email originated outside of BSWH; avoid action unless you know 
the content is safe. Send suspicious emails as attachments to 
badem...@bswhealth.org.

On Fri, Nov 13, 2020 at 6:02 PM Eric Chennells 
wrote:

> Frank,
>
> Interesting thank you I didn't realize that.  It used to be supported 
> I believe, and there is a lot of out of date 3rd party documentation 
> floating around google that suggests it does.
>
> Well it's just that many enterprises have policies which state that 
> only security updates should be installed, which I suspect is exactly 
> why that feature is no longer supported..
>

There are ways to get the metadata to do that, but it's still not officially 
supported. And as for enterprises mandating only security updates, they 
would/should pay for RHEL to get that kind of feature.
___
CentOS mailing list
CentOS@centos.org
https://urldefense.com/v3/__https://lists.centos.org/mailman/listinfo/centos__;!!JA_k2roV-A!XuXhHdKtZFfgqvwdbBq9PZb3K3TydTqyOHYfhFUGuM5eVBWP-eY3A7sFdZEJM8J5vg$
 

**
The information contained in this e-mail may be privileged and/or confidential, 
and protected from disclosure, and no waiver of any attorney-client, work 
product, or other privilege is intended.  If you are the intended recipient, 
further disclosures are prohibited without proper authorization. If you are not 
the intended recipient (or have received this e-mail in error) please notify 
the sender immediately and destroy this e-mail. Any unauthorized copying, 
disclosure or distribution of the material in this e-mail is strictly forbidden 
and possibly a violation of federal or state law and regulations. The sender 
and Baylor Scott & White Health, and its affiliated entities, hereby expressly 
reserve all privileges and confidentiality that might otherwise be waived as a 
result of an erroneous or misdirected e-mail transmission. No employee or agent 
is authorized to conclude any binding agreement on behalf of Baylor Scott & 
White Health, or any affiliated entity, by e-mail without express written 
confirmation by the CEO, the Senior Vice President of Supply Chain Services or 
other duly authorized representative of Baylor Scott & White Health.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update security updates only

[Jon Pruente]

On Fri, Nov 13, 2020 at 6:02 PM Eric Chennells 
wrote:

> Frank,
>
> Interesting thank you I didn't realize that.  It used to be supported I
> believe, and there is a lot of out of date 3rd party documentation floating
> around google that suggests it does.
>
> Well it's just that many enterprises have policies which state that only
> security updates should be installed, which I suspect is exactly why that
> feature is no longer supported..
>

There are ways to get the metadata to do that, but it's still not
officially supported. And as for enterprises mandating only security
updates, they would/should pay for RHEL to get that kind of feature.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update security updates only

[Jonathan Billings]

On Nov 13, 2020, at 19:01, Eric Chennells  wrote:
> 
> Frank,
> 
> Interesting thank you I didn't realize that.  It used to be supported I
> believe, and there is a lot of out of date 3rd party documentation floating
> around google that suggests it does.
> 
> Well it's just that many enterprises have policies which state that only
> security updates should be installed, which I suspect is exactly why that
> feature is no longer supported..

I don’t believe CentOS has ever supported it in any of the supported releases, 
although repos like EPEL do provide security metadata. 

RHEL supports the security flag to yum update, because they curate their repo 
metadata with that data, but it isn’t available to CentOS users.  

--
Jonathan Billings 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update security updates only

[Eric Chennells]

Frank,

Interesting thank you I didn't realize that.  It used to be supported I
believe, and there is a lot of out of date 3rd party documentation floating
around google that suggests it does.

Well it's just that many enterprises have policies which state that only
security updates should be installed, which I suspect is exactly why that
feature is no longer supported..

Eric


On Fri, Nov 13, 2020 at 3:55 PM Frank Cox  wrote:

> On Fri, 13 Nov 2020 15:52:08 -0800
> Eric Chennells wrote:
>
> > Does anyone know what's going on here?
>
> That is unsupported by Centos.  So the short answer is, you can't do that.
>
> Any particular reason you can't just update your system fully?
>
> --
> Can we uninstall 2020 and install it again? This one has a virus.
> MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update security updates only

[Frank Cox]

On Fri, 13 Nov 2020 15:52:08 -0800
Eric Chennells wrote:

> Does anyone know what's going on here?

That is unsupported by Centos.  So the short answer is, you can't do that.

Any particular reason you can't just update your system fully?

-- 
Can we uninstall 2020 and install it again? This one has a virus.
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update security updates only

[Eric Chennells]

Hello,

I'm trying to do a yum update and only apply the security patches.

I'm aware of yum update --security , however when I do that it fails to
install any updates.  I've tried this on a fresh 7.8.2003 (core) system, as
well as the Centos 7 AMI on AWS, specifically ami-04a25c39dc7a8aebb and I
get the same results.

There are definitely security updates to apply.

For each package which needs to be updated, it lists "" from
updates removed (updateinfo).

Does anyone know what's going on here?

Thanks,
Eric
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update / kernal update failed - remove or repair

[Anthony K]

On 25/1/20 11:56 am, Anthony K wrote:


[0]: https://anindya.me/2011/09/17/grub-fallback-after-kernel-panic/

I've just discovered that the article I posted is a rather old post so 
went hunting.


If you have a RHEL subscription (I'm using the free developer 
subscription) you can see the official Red Hat documentation at [0].  I 
was unable to find similar instructions for CentOS but here's a post of 
the same vintage as the RHEL one [1].


[0]: https://access.redhat.com/solutions/1567883
[1]: https://forums.centos.org/viewtopic.php?t=60220

PS: I haven't tested either of these so no idea if they work as one 
would expect.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update / kernal update failed - remove or repair

[Anthony K]

On 23/1/20 12:44 am, Gary Stainburn wrote:

...
As I will probably only have one chance to fix this (without having to get the 
ISP's help again) I was wondering if there are any clear instructions on how to 
remove a failed kernel RPM update, returning the server to the state it was in 
prior to the YUM update?
...
If you do not want to involve the ISP ever again when a kernel won't 
boot, you can configure a fallback kernel [0].  I've used something 
similar a very long time ago when the main boot loader was LILO - it was 
much easier to do this kind of thing with it.


[0]: https://anindya.me/2011/09/17/grub-fallback-after-kernel-panic/


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update / kernal update failed - remove or repair

[Gary Stainburn]

On Thursday 23 January 2020 15:22:32 Simon Matter via CentOS wrote:
> >
> > Before you try the update again, you'll have to fix the reason for the
> > failure - add memory, or at least add a swap file.
> >
> > You could check with
> > rpm -qa --last | head -20
> > which the latest packages are that were installed.
> >
> > If the rpm database is corrupted, rebuild it with
> > rpm --rebuilddb
> >
> > You can reinstall packages that may not be completely installed, using
> > rpm --reinstall PACKAGE_FILE
> 
> Well, there may be more to check and above steps may not help.
> 
> Do you have duplicates in rpmdb? Which one of the duplicates are already
> on the filesystem?

I do not believe that I have any duplicate RPM's installed, and I do not 
believe that the database is actually wrong. I believe that it is purely that 
the installs did not complete successfully.

I have managed to remove the latest kernel RPM and 'yum update kernel*' 
re-applied the update without errors.

I am going to go through the list of failed RPM's and to a 'rpm --reinstall' 
for each one in turn and hopefully they will work too.

Before doing that I will do as Kay suggested and find out why I had the memory 
problem in the first place.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update / kernal update failed - remove or repair

[Simon Matter via CentOS]

> On 1/22/20 3:57 PM, Gary Stainburn wrote:
>> I have managed to find out what happened in the yum update and it turns
>> out it was a mess.  It looks like the server ran out of memory in the
>> middle and things then started to fail.  Any advice on how to recover
>> from this would be greatly appreciated
>>
>> The log below shows:
>>
>> [root@vps2 ~]# yum history info 22
>> Loaded plugins: fastestmirror, langpacks
>> Repository mariadb is listed more than once in the configuration
>> Transaction ID : 22
>> Begin time : Sun Jan 19 18:15:33 2020
>> Begin rpmdb: 795:6c5cd82e3ada047c7071fea1524f41fd13fab6a1
>> End time   :19:19:32 2020 (63 minutes)
>> End rpmdb  : 801:6d1b278ccbeef6f68ff494cb28eaed5c7be4124b
>> User   : root 
>> Return-Code: Failure: 1
>> Command Line   : update
>> Transaction performed with:
>> Installed rpm-4.11.3-40.el7.x86_64
>> @anaconda
>> Installed yum-3.4.3-163.el7.centos.noarch
>> @anaconda
>> Installed yum-plugin-fastestmirror-1.1.31-52.el7.noarch
>> @anaconda
>> Packages Altered:
>> Updated MariaDB-client-10.4.10-1.el7.centos.x86_64@mariadb
>> Update 10.4.11-1.el7.centos.x86_64@mariadb
>> Updated MariaDB-common-10.4.10-1.el7.centos.x86_64@mariadb
>> Update 10.4.11-1.el7.centos.x86_64@mariadb
>> Updated MariaDB-compat-10.4.10-1.el7.centos.x86_64@mariadb
>> Update 10.4.11-1.el7.centos.x86_64@mariadb
>>  ** Updated MariaDB-server-10.4.10-1.el7.centos.x86_64@mariadb
>> Loading mirror speeds from cached hostfile
>>  * base: mirror.as29550.net
>>  * epel: www.mirrorservice.org
>>  * extras: www.mirrorservice.org
>>  * remi-php73: mirrors.ukfast.co.uk
>>  * remi-safe: mirrors.ukfast.co.uk
>>  * updates: www.mirrorservice.org
>>  ** Update 10.4.11-1.el7.centos.x86_64@?mariadb
>>  ** Updated MariaDB-shared-10.4.10-1.el7.centos.x86_64@mariadb
>> Update 10.4.11-1.el7.centos.x86_64@mariadb
>>  ** Updated ca-certificates-2018.2.22-70.0.el7_5.noarch   @anaconda
>>  ** Update  2019.2.32-76.el7_7.noarch @?updates
>> Updated certbot-0.39.0-1.el7.noarch   @epel
>> Update  1.0.0-1.el7.noarch@epel
>> Updated clamav-0.101.4-1.el7.x86_64   @epel
>> Update 0.101.5-1.el7.x86_64   @epel
>> Updated clamav-data-0.101.4-1.el7.noarch  @epel
>> Update  0.101.5-1.el7.noarch  @epel
>> Updated clamav-devel-0.101.4-1.el7.x86_64 @epel
>> Update   0.101.5-1.el7.x86_64 @epel
>> Updated clamav-filesystem-0.101.4-1.el7.noarch@epel
>> Update0.101.5-1.el7.noarch@epel
>> Updated clamav-lib-0.101.4-1.el7.x86_64   @epel
>> Update 0.101.5-1.el7.x86_64   @epel
>> Updated clamav-update-0.101.4-1.el7.x86_64@epel
>> Update0.101.5-1.el7.x86_64@epel
>> Updated clamd-0.101.4-1.el7.x86_64@epel
>> Update0.101.5-1.el7.x86_64@epel
>> Updated curl-7.29.0-54.el7.x86_64 @anaconda
>> Update   7.29.0-54.el7_7.1.x86_64 @updates
>> Updated fail2ban-0.9.7-1.el7.noarch   @epel
>> Update   0.10.4-1.el7.noarch  @epel
>> Updated fail2ban-firewalld-0.9.7-1.el7.noarch @epel
>> Update 0.10.4-1.el7.noarch@epel
>> Updated fail2ban-sendmail-0.9.7-1.el7.noarch  @epel
>> Update0.10.4-1.el7.noarch @epel
>> Updated fail2ban-server-0.9.7-1.el7.noarch@epel
>> Update  0.10.4-1.el7.noarch   @epel
>> Updated fail2ban-systemd-0.9.7-1.el7.noarch   @epel
>> Update   0.10.4-1.el7.noarch  @epel
>> Updated fribidi-1.0.2-1.el7.x86_64@anaconda
>> Update  1.0.2-1.el7_7.1.x86_64@updates
>> Updated iproute-4.11.0-25.el7.x86_64  @anaconda
>> Update  4.11.0-25.el7_7.2.x86_64  @updates
>> Install kernel-3.10.0-1062.9.1.el7.x86_64 @updates
>> Updated kernel-headers-3.10.0-1062.4.3.el7.x86_64 @updates
>> Update 3.10.0-1062.9.1.el7.x86_64 @updates
>> Updated kernel-tools-3.10.0-1062.4.3.el7.x86_64   @updates
>> Update   3.10.0-1062.9.1.el7.x86_64   @updates
>> Updated kernel-tools-libs-3.10.0-1062.4.3.el7.x86_64  @updates
>> Update 

Re: [CentOS] yum update / kernal update failed - remove or repair

[Kay Diederichs]

On 1/22/20 3:57 PM, Gary Stainburn wrote:
> I have managed to find out what happened in the yum update and it turns out 
> it was a mess.  It looks like the server ran out of memory in the middle and 
> things then started to fail.  Any advice on how to recover from this would be 
> greatly appreciated
> 
> The log below shows:
> 
> [root@vps2 ~]# yum history info 22
> Loaded plugins: fastestmirror, langpacks
> Repository mariadb is listed more than once in the configuration
> Transaction ID : 22
> Begin time : Sun Jan 19 18:15:33 2020
> Begin rpmdb: 795:6c5cd82e3ada047c7071fea1524f41fd13fab6a1
> End time   :19:19:32 2020 (63 minutes)
> End rpmdb  : 801:6d1b278ccbeef6f68ff494cb28eaed5c7be4124b
> User   : root 
> Return-Code: Failure: 1
> Command Line   : update
> Transaction performed with:
> Installed rpm-4.11.3-40.el7.x86_64  @anaconda
> Installed yum-3.4.3-163.el7.centos.noarch   @anaconda
> Installed yum-plugin-fastestmirror-1.1.31-52.el7.noarch @anaconda
> Packages Altered:
> Updated MariaDB-client-10.4.10-1.el7.centos.x86_64@mariadb
> Update 10.4.11-1.el7.centos.x86_64@mariadb
> Updated MariaDB-common-10.4.10-1.el7.centos.x86_64@mariadb
> Update 10.4.11-1.el7.centos.x86_64@mariadb
> Updated MariaDB-compat-10.4.10-1.el7.centos.x86_64@mariadb
> Update 10.4.11-1.el7.centos.x86_64@mariadb
>  ** Updated MariaDB-server-10.4.10-1.el7.centos.x86_64@mariadb
> Loading mirror speeds from cached hostfile
>  * base: mirror.as29550.net
>  * epel: www.mirrorservice.org
>  * extras: www.mirrorservice.org
>  * remi-php73: mirrors.ukfast.co.uk
>  * remi-safe: mirrors.ukfast.co.uk
>  * updates: www.mirrorservice.org
>  ** Update 10.4.11-1.el7.centos.x86_64@?mariadb
>  ** Updated MariaDB-shared-10.4.10-1.el7.centos.x86_64@mariadb
> Update 10.4.11-1.el7.centos.x86_64@mariadb
>  ** Updated ca-certificates-2018.2.22-70.0.el7_5.noarch   @anaconda
>  ** Update  2019.2.32-76.el7_7.noarch @?updates
> Updated certbot-0.39.0-1.el7.noarch   @epel
> Update  1.0.0-1.el7.noarch@epel
> Updated clamav-0.101.4-1.el7.x86_64   @epel
> Update 0.101.5-1.el7.x86_64   @epel
> Updated clamav-data-0.101.4-1.el7.noarch  @epel
> Update  0.101.5-1.el7.noarch  @epel
> Updated clamav-devel-0.101.4-1.el7.x86_64 @epel
> Update   0.101.5-1.el7.x86_64 @epel
> Updated clamav-filesystem-0.101.4-1.el7.noarch@epel
> Update0.101.5-1.el7.noarch@epel
> Updated clamav-lib-0.101.4-1.el7.x86_64   @epel
> Update 0.101.5-1.el7.x86_64   @epel
> Updated clamav-update-0.101.4-1.el7.x86_64@epel
> Update0.101.5-1.el7.x86_64@epel
> Updated clamd-0.101.4-1.el7.x86_64@epel
> Update0.101.5-1.el7.x86_64@epel
> Updated curl-7.29.0-54.el7.x86_64 @anaconda
> Update   7.29.0-54.el7_7.1.x86_64 @updates
> Updated fail2ban-0.9.7-1.el7.noarch   @epel
> Update   0.10.4-1.el7.noarch  @epel
> Updated fail2ban-firewalld-0.9.7-1.el7.noarch @epel
> Update 0.10.4-1.el7.noarch@epel
> Updated fail2ban-sendmail-0.9.7-1.el7.noarch  @epel
> Update0.10.4-1.el7.noarch @epel
> Updated fail2ban-server-0.9.7-1.el7.noarch@epel
> Update  0.10.4-1.el7.noarch   @epel
> Updated fail2ban-systemd-0.9.7-1.el7.noarch   @epel
> Update   0.10.4-1.el7.noarch  @epel
> Updated fribidi-1.0.2-1.el7.x86_64@anaconda
> Update  1.0.2-1.el7_7.1.x86_64@updates
> Updated iproute-4.11.0-25.el7.x86_64  @anaconda
> Update  4.11.0-25.el7_7.2.x86_64  @updates
> Install kernel-3.10.0-1062.9.1.el7.x86_64 @updates
> Updated kernel-headers-3.10.0-1062.4.3.el7.x86_64 @updates
> Update 3.10.0-1062.9.1.el7.x86_64 @updates
> Updated kernel-tools-3.10.0-1062.4.3.el7.x86_64   @updates
> Update   3.10.0-1062.9.1.el7.x86_64   @updates
> Updated kernel-tools-libs-3.10.0-1062.4.3.el7.x86_64  @updates
> Update3.10.0-1062.9.1.el7.x86_64  @updates
>   

Re: [CentOS] yum update / kernal update failed - remove or repair

[Simon Matter via CentOS]

> I have managed to find out what happened in the yum update and it turns
> out it was a mess.  It looks like the server ran out of memory in the
> middle and things then started to fail.  Any advice on how to recover from
> this would be greatly appreciated

I may sound old school but my suggestion would be to forget yum aka dnf
for now and just fix the real stuff using rpm.

I always considered yum a wrapper for rpm (I wish it was) and was able to
fix a system with rpm alone and later make yum behave again.

It usually boils down to analyzing what is in the rpm db and what is on
the filesystem actually. You can then remove invalid rpm db content as
well as wrong filesystem content. It's a bit of work and you may create
helper scripts as needed but you can fix almost everything that way.

Regards,
Simon

>
> The log below shows:
>
> [root@vps2 ~]# yum history info 22
> Loaded plugins: fastestmirror, langpacks
> Repository mariadb is listed more than once in the configuration
> Transaction ID : 22
> Begin time : Sun Jan 19 18:15:33 2020
> Begin rpmdb: 795:6c5cd82e3ada047c7071fea1524f41fd13fab6a1
> End time   :19:19:32 2020 (63 minutes)
> End rpmdb  : 801:6d1b278ccbeef6f68ff494cb28eaed5c7be4124b
> User   : root 
> Return-Code: Failure: 1
> Command Line   : update
> Transaction performed with:
> Installed rpm-4.11.3-40.el7.x86_64  @anaconda
> Installed yum-3.4.3-163.el7.centos.noarch   @anaconda
> Installed yum-plugin-fastestmirror-1.1.31-52.el7.noarch @anaconda
> Packages Altered:
> Updated MariaDB-client-10.4.10-1.el7.centos.x86_64@mariadb
> Update 10.4.11-1.el7.centos.x86_64@mariadb
> Updated MariaDB-common-10.4.10-1.el7.centos.x86_64@mariadb
> Update 10.4.11-1.el7.centos.x86_64@mariadb
> Updated MariaDB-compat-10.4.10-1.el7.centos.x86_64@mariadb
> Update 10.4.11-1.el7.centos.x86_64@mariadb
>  ** Updated MariaDB-server-10.4.10-1.el7.centos.x86_64@mariadb
> Loading mirror speeds from cached hostfile
>  * base: mirror.as29550.net
>  * epel: www.mirrorservice.org
>  * extras: www.mirrorservice.org
>  * remi-php73: mirrors.ukfast.co.uk
>  * remi-safe: mirrors.ukfast.co.uk
>  * updates: www.mirrorservice.org
>  ** Update 10.4.11-1.el7.centos.x86_64@?mariadb
>  ** Updated MariaDB-shared-10.4.10-1.el7.centos.x86_64@mariadb
> Update 10.4.11-1.el7.centos.x86_64@mariadb
>  ** Updated ca-certificates-2018.2.22-70.0.el7_5.noarch   @anaconda
>  ** Update  2019.2.32-76.el7_7.noarch @?updates
> Updated certbot-0.39.0-1.el7.noarch   @epel
> Update  1.0.0-1.el7.noarch@epel
> Updated clamav-0.101.4-1.el7.x86_64   @epel
> Update 0.101.5-1.el7.x86_64   @epel
> Updated clamav-data-0.101.4-1.el7.noarch  @epel
> Update  0.101.5-1.el7.noarch  @epel
> Updated clamav-devel-0.101.4-1.el7.x86_64 @epel
> Update   0.101.5-1.el7.x86_64 @epel
> Updated clamav-filesystem-0.101.4-1.el7.noarch@epel
> Update0.101.5-1.el7.noarch@epel
> Updated clamav-lib-0.101.4-1.el7.x86_64   @epel
> Update 0.101.5-1.el7.x86_64   @epel
> Updated clamav-update-0.101.4-1.el7.x86_64@epel
> Update0.101.5-1.el7.x86_64@epel
> Updated clamd-0.101.4-1.el7.x86_64@epel
> Update0.101.5-1.el7.x86_64@epel
> Updated curl-7.29.0-54.el7.x86_64 @anaconda
> Update   7.29.0-54.el7_7.1.x86_64 @updates
> Updated fail2ban-0.9.7-1.el7.noarch   @epel
> Update   0.10.4-1.el7.noarch  @epel
> Updated fail2ban-firewalld-0.9.7-1.el7.noarch @epel
> Update 0.10.4-1.el7.noarch@epel
> Updated fail2ban-sendmail-0.9.7-1.el7.noarch  @epel
> Update0.10.4-1.el7.noarch @epel
> Updated fail2ban-server-0.9.7-1.el7.noarch@epel
> Update  0.10.4-1.el7.noarch   @epel
> Updated fail2ban-systemd-0.9.7-1.el7.noarch   @epel
> Update   0.10.4-1.el7.noarch  @epel
> Updated fribidi-1.0.2-1.el7.x86_64@anaconda
> Update  1.0.2-1.el7_7.1.x86_64@updates
> Updated iproute-4.11.0-25.el7.x86_64  @anaconda
> Update  4.11.0-25.el7_7.2.x86_64  @updates
>   

Re: [CentOS] yum update / kernal update failed - remove or repair

[Gary Stainburn]

I have managed to find out what happened in the yum update and it turns out it 
was a mess.  It looks like the server ran out of memory in the middle and 
things then started to fail.  Any advice on how to recover from this would be 
greatly appreciated

The log below shows:

[root@vps2 ~]# yum history info 22
Loaded plugins: fastestmirror, langpacks
Repository mariadb is listed more than once in the configuration
Transaction ID : 22
Begin time : Sun Jan 19 18:15:33 2020
Begin rpmdb: 795:6c5cd82e3ada047c7071fea1524f41fd13fab6a1
End time   :19:19:32 2020 (63 minutes)
End rpmdb  : 801:6d1b278ccbeef6f68ff494cb28eaed5c7be4124b
User   : root 
Return-Code: Failure: 1
Command Line   : update
Transaction performed with:
Installed rpm-4.11.3-40.el7.x86_64  @anaconda
Installed yum-3.4.3-163.el7.centos.noarch   @anaconda
Installed yum-plugin-fastestmirror-1.1.31-52.el7.noarch @anaconda
Packages Altered:
Updated MariaDB-client-10.4.10-1.el7.centos.x86_64@mariadb
Update 10.4.11-1.el7.centos.x86_64@mariadb
Updated MariaDB-common-10.4.10-1.el7.centos.x86_64@mariadb
Update 10.4.11-1.el7.centos.x86_64@mariadb
Updated MariaDB-compat-10.4.10-1.el7.centos.x86_64@mariadb
Update 10.4.11-1.el7.centos.x86_64@mariadb
 ** Updated MariaDB-server-10.4.10-1.el7.centos.x86_64@mariadb
Loading mirror speeds from cached hostfile
 * base: mirror.as29550.net
 * epel: www.mirrorservice.org
 * extras: www.mirrorservice.org
 * remi-php73: mirrors.ukfast.co.uk
 * remi-safe: mirrors.ukfast.co.uk
 * updates: www.mirrorservice.org
 ** Update 10.4.11-1.el7.centos.x86_64@?mariadb
 ** Updated MariaDB-shared-10.4.10-1.el7.centos.x86_64@mariadb
Update 10.4.11-1.el7.centos.x86_64@mariadb
 ** Updated ca-certificates-2018.2.22-70.0.el7_5.noarch   @anaconda
 ** Update  2019.2.32-76.el7_7.noarch @?updates
Updated certbot-0.39.0-1.el7.noarch   @epel
Update  1.0.0-1.el7.noarch@epel
Updated clamav-0.101.4-1.el7.x86_64   @epel
Update 0.101.5-1.el7.x86_64   @epel
Updated clamav-data-0.101.4-1.el7.noarch  @epel
Update  0.101.5-1.el7.noarch  @epel
Updated clamav-devel-0.101.4-1.el7.x86_64 @epel
Update   0.101.5-1.el7.x86_64 @epel
Updated clamav-filesystem-0.101.4-1.el7.noarch@epel
Update0.101.5-1.el7.noarch@epel
Updated clamav-lib-0.101.4-1.el7.x86_64   @epel
Update 0.101.5-1.el7.x86_64   @epel
Updated clamav-update-0.101.4-1.el7.x86_64@epel
Update0.101.5-1.el7.x86_64@epel
Updated clamd-0.101.4-1.el7.x86_64@epel
Update0.101.5-1.el7.x86_64@epel
Updated curl-7.29.0-54.el7.x86_64 @anaconda
Update   7.29.0-54.el7_7.1.x86_64 @updates
Updated fail2ban-0.9.7-1.el7.noarch   @epel
Update   0.10.4-1.el7.noarch  @epel
Updated fail2ban-firewalld-0.9.7-1.el7.noarch @epel
Update 0.10.4-1.el7.noarch@epel
Updated fail2ban-sendmail-0.9.7-1.el7.noarch  @epel
Update0.10.4-1.el7.noarch @epel
Updated fail2ban-server-0.9.7-1.el7.noarch@epel
Update  0.10.4-1.el7.noarch   @epel
Updated fail2ban-systemd-0.9.7-1.el7.noarch   @epel
Update   0.10.4-1.el7.noarch  @epel
Updated fribidi-1.0.2-1.el7.x86_64@anaconda
Update  1.0.2-1.el7_7.1.x86_64@updates
Updated iproute-4.11.0-25.el7.x86_64  @anaconda
Update  4.11.0-25.el7_7.2.x86_64  @updates
Install kernel-3.10.0-1062.9.1.el7.x86_64 @updates
Updated kernel-headers-3.10.0-1062.4.3.el7.x86_64 @updates
Update 3.10.0-1062.9.1.el7.x86_64 @updates
Updated kernel-tools-3.10.0-1062.4.3.el7.x86_64   @updates
Update   3.10.0-1062.9.1.el7.x86_64   @updates
Updated kernel-tools-libs-3.10.0-1062.4.3.el7.x86_64  @updates
Update3.10.0-1062.9.1.el7.x86_64  @updates
Updated libblkid-2.23.2-61.el7.x86_64 @anaconda
Update   2.23.2-61.el7_7.1.x86_64 @updates
Updated libcurl-7.29.0-54.el7.x86_64  

[CentOS] yum update / kernal update failed - remove or repair

[Gary Stainburn]

I have a VPS running C7. I ran a 'yum update' which included a kernel update. 
The yum update wasn't a total success because mariadb updates failed. However 
everything else appeared to work.

However, when I rebooted the server it did not restart. I have managed to get 
the ISP's support desk to boot the server by selecting the previous kernel, and 
I now have access to my box again.

As I will probably only have one chance to fix this (without having to get the 
ISP's help again) I was wondering if there are any clear instructions on how to 
remove a failed kernel RPM update, returning the server to the state it was in 
prior to the YUM update?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update gitlab-ci-multi-runner

[Helmut Drodofsky]

I'm doing
yum update
in CentOS 7 since some 10 hours.

Last terminal message is:
Updating   : gitlab-ci-multi-runner-9.5.1-1.x86_64

ps aux:
root 15296  0.3  2.5 1554608 204988 pts/0  S+   06:23   2:01 
/usr/bin/python /bin/yum update


to kill yum is not a good idea. Alternative?

for what is yum waiting? can I stop an application process?

systemctl stop gitlab-runner does not help, same with giltlab-ctl stop

best regards

--
Viele Grüße
Helmut Drodofsky

Internet XS Service GmbH
Heßbrühlstraße 15
70565 Stuttgart

Geschäftsführung
Helmut Drodofsky
HRB 21091 Stuttgart
USt.ID: DE190582774
Fon: 0711 781941 0 
Fax: 0711 781941 79
Mail: i...@internet-xs.de
www.internet-xs.de
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update info output

[Thomas Roth]

Thanks for the explanation.

Yes, I see both of these lines, including systemd-sysv-219-42.el7_4.4.x86_64, but as quoted it also 
has the label "removed" - that had me confused.


'yum info systemd-sysv' shows that systemd-sysv-219-42.el7_4.1 is installed - as expected. And if I 
run the actual update, the 4.4 package gets installed as an update - so everything is o.k.


Regards
Thomas




On 11/07/2017 03:16 PM, Johnny Hughes wrote:

On 11/06/2017 01:01 PM, Thomas Roth wrote:

Hi all,

when I check for updates with yum, it gives me a list of packages, with
some additional info, e.g.

  --> systemd-sysv-219-42.el7_4.1.x86_64 from @updates removed (updateinfo)
  --> systemd-sysv-219-42.el7_4.4.x86_64 from updates removed (updateinfo)


yum info will tell me that I have 4.1 of this package installed, and
that 4.4 is available - from the repo updates.

What is the meaning of the "@" - it marks the older package?


@updates means currently installed.  updates without @ means available
to be installed.



And why are all packages always "removed"?



The first one would be removed because the .4 package SHOULD be
installed.  Does the list of updated packages also include
systemd-sysv-219-42.el7_4.4.x86_64?


It would seem that both mentioned packages are still available...



Yes, both are available.



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update info output

[Johnny Hughes]

On 11/06/2017 01:01 PM, Thomas Roth wrote:
> Hi all,
> 
> when I check for updates with yum, it gives me a list of packages, with
> some additional info, e.g.
> 
>  --> systemd-sysv-219-42.el7_4.1.x86_64 from @updates removed (updateinfo)
>  --> systemd-sysv-219-42.el7_4.4.x86_64 from updates removed (updateinfo)
> 
> 
> yum info will tell me that I have 4.1 of this package installed, and
> that 4.4 is available - from the repo updates.
> 
> What is the meaning of the "@" - it marks the older package?

@updates means currently installed.  updates without @ means available
to be installed.

> 
> And why are all packages always "removed"?
> 

The first one would be removed because the .4 package SHOULD be
installed.  Does the list of updated packages also include
systemd-sysv-219-42.el7_4.4.x86_64?

> It would seem that both mentioned packages are still available...
>

Yes, both are available.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update info output

[Thomas Roth]

Hi all,

when I check for updates with yum, it gives me a list of packages, with some 
additional info, e.g.

 --> systemd-sysv-219-42.el7_4.1.x86_64 from @updates removed (updateinfo)
 --> systemd-sysv-219-42.el7_4.4.x86_64 from updates removed (updateinfo)


yum info will tell me that I have 4.1 of this package installed, and that 4.4 is available - from the 
repo updates.


What is the meaning of the "@" - it marks the older package?

And why are all packages always "removed"?

It would seem that both mentioned packages are still available...

Regards,
Thomas
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update problem - dependancy problem

[James A. Peltier]

While you may have them disabled _now_ at some point they were enabled and so a 
conflicting package was installed and is now causing the issue.

- On 26 Sep, 2017, at 05:23, Gary Stainburn g...@ringways.co.uk wrote:

| On Tuesday 26 September 2017 11:56:06 Joseph L. Casale wrote:
|> The error is actually pretty straight forward. You are using a repo
|> (atrpms) that has not been updated in years, it's not surprise that it
|> finally has lost compatibility with the platform.
|>
|> Find a modern and up to date replacement for any packages you reference
|> from atrpms and without the switches.
| 
| When looking at your suggestions I found that the atrpms were actually
| disabled (enabled=0)
| 
| I have enabled them and now it appears to be working.  Although the opposite
| of your suggestion, thanks for the fix.
| 
| I will remember for future installs to not use the atrpms.
| 
| Gary
| ___
| CentOS mailing list
| CentOS@centos.org
| https://lists.centos.org/mailman/listinfo/centos

-- 
James A. Peltier
IT Services - Research Computing Group
Simon Fraser University - Burnaby Campus
Phone   : 604-365-6432
Fax : 778-782-3045
E-Mail  : jpelt...@sfu.ca
Website : http://www.sfu.ca/itservices
Twitter : @sfu_rcg
Powering Engagement Through Technology
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update problem - dependancy problem

[Gary Stainburn]

On Tuesday 26 September 2017 15:32:50 Leon Fauster wrote:
> Sorry to be pedantic, the symptom is fixed not the problem.
>
> To check which packages are from atrpms try this one:
>
> # rpm -qa --qf '%{NAME}-%{VENDOR}\n'  | grep -v CentOS
>
> It will list package name along with the corresponding repo tag.
>
> That list can then be used to plan a package migration.

Leon,

There's nothing wrong with being pedantic, and thanks for the command. It was 
very useful. However, for the box that has the problem, it's not worth the 
time and effort involved in doing the correct fix.

Gary
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update problem - dependancy problem

[Leon Fauster]

> Am 26.09.2017 um 15:38 schrieb Gary Stainburn :
> 
> On Tuesday 26 September 2017 14:27:43 Mark Haney wrote:
>> On 09/26/2017 09:23 AM, James B. Byrne wrote:
>>> You have a conflicting package installed from repository @atrpms.  You
>>> need to remove that package and/or disable that repository to get past
>>> the dependency issue.  'Skip broken' is not going to handle this
>>> situation nor will any other set of yum options.
>> 
>> Christ, how long as ATRPMs been dead?  I think I stopped using it in
>> 2008/9.
> 
> I don't know. I will have installed then when following instrunctions found 
> online.  I generally check the dates on any web page I use, maybe I missed 
> one.
> 
> Anyway, enabling it again for this box fixed the problem.


Sorry to be pedantic, the symptom is fixed not the problem.

To check which packages are from atrpms try this one:

# rpm -qa --qf '%{NAME}-%{VENDOR}\n'  | grep -v CentOS

It will list package name along with the corresponding repo tag.

That list can then be used to plan a package migration.

--
LF


 

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update problem - dependancy problem

[Gary Stainburn]

On Tuesday 26 September 2017 14:27:43 Mark Haney wrote:
> On 09/26/2017 09:23 AM, James B. Byrne wrote:
> > You have a conflicting package installed from repository @atrpms.  You
> > need to remove that package and/or disable that repository to get past
> > the dependency issue.  'Skip broken' is not going to handle this
> > situation nor will any other set of yum options.
>
> Christ, how long as ATRPMs been dead?  I think I stopped using it in
> 2008/9.

I don't know. I will have installed then when following instrunctions found 
online.  I generally check the dates on any web page I use, maybe I missed 
one.

Anyway, enabling it again for this box fixed the problem.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update problem - dependancy problem

[Mark Haney]

On 09/26/2017 09:23 AM, James B. Byrne wrote:

You have a conflicting package installed from repository @atrpms.  You
need to remove that package and/or disable that repository to get past
the dependency issue.  'Skip broken' is not going to handle this
situation nor will any other set of yum options.


Christ, how long as ATRPMs been dead?  I think I stopped using it in 
2008/9.



--
Mark Haney
Network Engineer at NeoNova
919-460-3330 option 1
mark.ha...@neonova.net
www.neonova.net

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update problem - dependancy problem

[Gary Stainburn]

On Tuesday 26 September 2017 14:23:46 James B. Byrne wrote:
> You have a conflicting package installed from repository @atrpms.  You
> need to remove that package and/or disable that repository to get past
> the dependency issue.  'Skip broken' is not going to handle this
> situation nor will any other set of yum options.

Hi James,

Thanks for this. The actual problem was that the repo had been disabled.  I 
have made a note to not use atrpms in future.

Gary
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update problem - dependancy problem

[James B. Byrne]

You have a conflicting package installed from repository @atrpms.  You
need to remove that package and/or disable that repository to get past
the dependency issue.  'Skip broken' is not going to handle this
situation nor will any other set of yum options.


On Tue, September 26, 2017 05:32, Gary Stainburn wrote:

> --> Processing Dependency: /usr/sbin/ldconfig for package:
> libbluray1-0.4.0-6.el7.x86_64
> --> Finished Dependency Resolution
> Error: Package: libbluray1-0.4.0-6.el7.x86_64 (@atrpms)
>Requires: /usr/sbin/ldconfig
>Removing: glibc-2.17-157.el7_3.1.i686 (@updates)
>Not found
>Updated By: glibc-2.17-196.el7.i686 (base)
>Not found
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
> [root@lcomp5 ~]#
>
>


-- 
***  e-Mail is NOT a SECURE channel  ***
Do NOT transmit sensitive data via e-Mail
 Do NOT open attachments nor follow links sent by e-Mail

James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update problem - dependancy problem

[Gary Stainburn]

On Tuesday 26 September 2017 11:56:06 Joseph L. Casale wrote:
> The error is actually pretty straight forward. You are using a repo
> (atrpms) that has not been updated in years, it's not surprise that it
> finally has lost compatibility with the platform.
>
> Find a modern and up to date replacement for any packages you reference
> from atrpms and without the switches.

When looking at your suggestions I found that the atrpms were actually 
disabled (enabled=0)

I have enabled them and now it appears to be working.  Although the opposite 
of your suggestion, thanks for the fix.

I will remember for future installs to not use the atrpms.

Gary
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update problem - dependancy problem

[Joseph L. Casale]

-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Gary Stainburn
Sent: Tuesday, September 26, 2017 3:32 AM
To: centos@centos.org
Subject: [CentOS] yum update problem - dependancy problem

> For a while I've been updating using the command
> 
> yum -y --skip-broken  --exclude rpcbind update

I wish the yum maintainers would remove that suggestion:(

> Error: Package: libbluray1-0.4.0-6.el7.x86_64 (@atrpms)
>Requires: /usr/sbin/ldconfig
>Removing: glibc-2.17-157.el7_3.1.i686 (@updates)
>Not found
>Updated By: glibc-2.17-196.el7.i686 (base)
>Not found

The error is actually pretty straight forward. You are using a repo (atrpms)
that has not been updated in years, it's not surprise that it finally has lost
compatibility with the platform.

Find a modern and up to date replacement for any packages you reference
from atrpms and without the switches.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update problem - dependancy problem

[Gary Stainburn]

I'm sure this is a FAQ, and a simple answer is available, but I've not managed 
it yet.  I've tried all of the RPM database tidy routines. I've tried 
uninstalling the libblueray1 library but the ever growning dependency tree 
was too big.


For a while I've been updating using the command 

yum -y --skip-broken  --exclude rpcbind update

which I though t was working,  but the list of rpm's not updated is ever 
growing so i need to find a solution. Here is the output from the yum update. 
I've remove the bulk of the output for brevity but I can include it if 
needed.

Gary



[root@lcomp5 ~]# yum -y update
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * base: mirror.netweaver.uk
 * epel: mirrors.ukfast.co.uk
 * extras: mirror.netweaver.uk
 * nux-dextop: mirror.li.nux.ro
 * remi-safe: rpms.remirepo.net
 * rpmforge: ftp.nluug.nl
 * updates: repo.uk.bigstepcloud.com
 * webtatic: uk.repo.webtatic.com
Resolving Dependencies
--> Running transaction check
---> Package NetworkManager.x86_64 1:1.4.0-20.el7_3 will be obsoleted
---> Package NetworkManager.x86_64 1:1.4.0-20.el7_3 will be updated
---> Package NetworkManager.x86_64 1:1.8.0-9.el7 will be obsoleting
---> Package NetworkManager-adsl.x86_64 1:1.4.0-20.el7_3 will be updated
[..]
---> Package xmlsec1.x86_64 0:1.2.20-7.el7_4 will be installed
---> Package xmlsec1-openssl.x86_64 0:1.2.20-7.el7_4 will be installed
--> Running transaction check
---> Package grub2-pc-modules.noarch 1:2.02-0.64.el7.centos will be installed
---> Package libblkid.i686 0:2.23.2-43.el7 will be installed
---> Package webkitgtk4-plugin-process-gtk2.x86_64 0:2.14.7-2.el7 will be 
installed
--> Processing Dependency: /usr/sbin/ldconfig for package: 
libbluray1-0.4.0-6.el7.x86_64
--> Finished Dependency Resolution
Error: Package: libbluray1-0.4.0-6.el7.x86_64 (@atrpms)
   Requires: /usr/sbin/ldconfig
   Removing: glibc-2.17-157.el7_3.1.i686 (@updates)
   Not found
   Updated By: glibc-2.17-196.el7.i686 (base)
   Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
[root@lcomp5 ~]# 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update pulls in lvm-cluster on 7

[me]

On Wed, 4 Jan 2017, Peter Kjellström wrote:


On Tue, 13 Dec 2016 08:16:06 -0500 (EST)
m...@tdiehl.org wrote:

I ran "yum update" this morning on a 7.2 machine with all of the cr
updates applied to it and yum wants to install lvm-cluster and a
bunch of deps.

...

==
  Package   Arch  VersionRepository   Size
==
Installing for group upgrade "Resilient Storage":
  lvm2-cluster  x86_647:2.02.166-1.el7_3.1updates

...

I understand why the centos-release wants to be updated but can
someone tell me why it wants to pull in lvm-cluster and friends? This
machine is not part of a cluster.


I don't see how the above output could be much more clear. It wants to
upgrade the installed group of packages named "Resilient Storage" and
the included packages have new dependencies.


Obviously, but I never installed a group called "Resilient Storage" nor
do I need that group and yum grouplist does not show that such a group
even exists.

What I was missing is that yum grouplist has a "hidden" option and that is what
you need to actually see what groups are installed on the machine.

Once I found that I discovered that in 7.2 the Resilient Storage group only
had gfs2-utils as a Mandatory package. In 7.3 lvm2-cluster was added as
an additional package to that group. Yum logs show that gfs2-utils has
been installed since the beginning of the machine's life (most likely by
anaconda) and now that lvm2-cluster was added as a mandatory package,
that is what caused the unnecessary deps to be required.

That was the mystery I was trying to understand and solve.

The bottom line is that I removed gfs2-utils and all is well.

Sorry for the confusion.

Regards,

--
Tom m...@tdiehl.org Spamtrap address
me...@tdiehl.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update pulls in lvm-cluster on 7.3

[Peter Kjellström]

On Tue, 13 Dec 2016 08:16:06 -0500 (EST)
m...@tdiehl.org wrote:
> I ran "yum update" this morning on a 7.2 machine with all of the cr
> updates applied to it and yum wants to install lvm-cluster and a
> bunch of deps.
...
> ==
>   Package   Arch  VersionRepository   Size
> ==
> Installing for group upgrade "Resilient Storage":
>   lvm2-cluster  x86_647:2.02.166-1.el7_3.1updates
...
> I understand why the centos-release wants to be updated but can
> someone tell me why it wants to pull in lvm-cluster and friends? This
> machine is not part of a cluster.

I don't see how the above output could be much more clear. It wants to
upgrade the installed group of packages named "Resilient Storage" and
the included packages have new dependencies.

Options:
 * realise you don't want the group and remove it
 * live with its new dependencies even though you wont use all of them
   (this is of course the situation more many other packages on your
   machine already)
 * hold off on the update

/Peter K
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update pulls in lvm-cluster on 7.3

[Gianluca Cecchi]

On Wed, Jan 4, 2017 at 6:30 AM,  wrote:

> Hi,
>
> Sorry for the delayed response.


No problem



> Hummm, According to the changelog your version of lvm2 is over a year old.
>

Yes, it was a test vm server not recently updated.


>
> So I guess what I am trying to figure out is what is pulling in the
> Resilient
> Storage group.
>
> Suggestions?
>
>
question: your .repo files under /etc/yum.repos.d contain official CentOS
mirrors or anything customized that could have broken repodata information?

question: why are you using priorities plugin?
See here for related files, in case:
https://wiki.centos.org/PackageManagement/Yum/Priorities

What I would test/try in order is:

- check all enabled contents in .repo files and verify it is correct in
respect with a standard CentOS 7 system

- yum update --disablerepo=cr
and see if anything changes

- it could be related with priorities plugin too, I would try
yum update --disableplugin=priorities
and/or
yum update --disableplugin=priorities --disablerepo=cr

- I never used changelog plugin and it should pop-in only if changelog
option has been given in yum command, anyway I would try
yum update --disableplugin=changelog
and/or
yum update --disableplugin=changelog --disablerepo=cr

- try running yum command with debug option enabled and see if anything
pops up
yum update -d 5

HIH,
Gianluca
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update pulls in lvm-cluster on 7.3

[me]

Hi,

Sorry for the delayed response.

On Tue, 13 Dec 2016, Gianluca Cecchi wrote:


On Tue, Dec 13, 2016 at 2:16 PM,  wrote:


Hi,

I ran "yum update" this morning on a 7.2 machine with all of the cr updates
applied to it and yum wants to install lvm-cluster and a bunch of deps.

Dependencies Resolved

==
 Package   Arch  VersionRepository   Size
==
Installing for group upgrade "Resilient Storage":
 lvm2-cluster  x86_647:2.02.166-1.el7_3.1updates  663 k



Hello,
which command did you execute, exactly?


Below is the whole transaction:

(shadow pts3) # yum clean metadata ; yum update
Loaded plugins: changelog, fastestmirror, langpacks, priorities
Cleaning repos: base cr extras updates
10 metadata files removed
8 sqlite files removed
0 metadata files removed
Loaded plugins: changelog, fastestmirror, langpacks, priorities
base

| 3.6 kB  00:00:00
cr  

| 3.3 kB  00:00:00
extras  

| 3.4 kB  00:00:00
updates 

| 3.4 kB  00:00:00
(1/5): cr/7/x86_64/primary_db   

| 1.2 kB  00:00:00
(2/5): base/7/x86_64/group_gz   

| 155 kB  00:00:00
(3/5): extras/7/x86_64/primary_db   

| 183 kB  00:00:00
(4/5): updates/7/x86_64/primary_db  

| 1.2 MB  00:00:00
(5/5): base/7/x86_64/primary_db 

| 5.6 MB  00:00:00
Loading mirror speeds from cached hostfile
Resolving Dependencies
--> Running transaction check
---> Package lvm2-cluster.x86_64 7:2.02.166-1.el7_3.1 will be installed
--> Processing Dependency: resource-agents >= 3.9.5-25 for package: 
7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
--> Processing Dependency: dlm >= 3.99.1-1 for package: 
7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
--> Processing Dependency: corosync >= 1.99.9-1 for package: 
7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
--> Processing Dependency: libquorum.so.5(COROSYNC_QUORUM_1.0)(64bit) for 
package: 7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
--> Processing Dependency: libcpg.so.4(COROSYNC_CPG_1.0)(64bit) for package: 
7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
--> Processing Dependency: libcmap.so.4(COROSYNC_CMAP_1.0)(64bit) for package: 
7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
--> Processing Dependency: libquorum.so.5()(64bit) for package: 
7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
--> Processing Dependency: libdlm.so.3()(64bit) for package: 
7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
--> Processing Dependency: libcpg.so.4()(64bit) for package: 
7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
--> Processing Dependency: libcmap.so.4()(64bit) for package: 
7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
--> Running transaction check
---> Package corosync.x86_64 0:2.4.0-4.el7 will be installed
--> Processing Dependency: libqb.so.0()(64bit) for package: 
corosync-2.4.0-4.el7.x86_64
---> Package corosynclib.x86_64 0:2.4.0-4.el7 will be installed
---> Package dlm.x86_64 0:4.0.6-1.el7 will be installed
---> Package dlm-lib.x86_64 0:4.0.6-1.el7 will be installed
---> Package resource-agents.x86_64 0:3.9.5-82.el7_3.3 will be installed
--> Running transaction check
---> Package libqb.x86_64 0:1.0-1.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

===
 Package  

Re: [CentOS] yum update pulls in lvm-cluster on 7.3

[Gianluca Cecchi]

On Tue, Dec 13, 2016 at 2:16 PM,  wrote:

> Hi,
>
> I ran "yum update" this morning on a 7.2 machine with all of the cr updates
> applied to it and yum wants to install lvm-cluster and a bunch of deps.
>
> Dependencies Resolved
>
> ==
>  Package   Arch  VersionRepository   Size
> ==
> Installing for group upgrade "Resilient Storage":
>  lvm2-cluster  x86_647:2.02.166-1.el7_3.1updates  663 k
>

Hello,
which command did you execute, exactly?
I have only experience with RHEL and not CentOS for what regards
lvm2-cluster; in my opinion it is correct that it is included in "Resilient
Storage" group.
So that if you already had this group installed but not lvm2-cluster rpm
package, it was a problem before, not now

Eg, in a CentOS 7.2 vm of mine I have:

[root@manageiq ~]# rpm -q lvm2-cluster
package lvm2-cluster is not installed
[root@manageiq ~]#

[root@manageiq ~]# rpm -q lvm2
lvm2-2.02.130-5.el7.x86_64
[root@manageiq ~]#

[root@manageiq ~]# yum update
. . .
centos-releasex86_64 7-3.1611.el7.centos
  base 23 k
. . .
lvm2  x86_64 7:2.02.166-1.el7_3.1
 updates 1.1 M
. . .
but no lvm2-cluster package proposed

but correctly if I run

[root@manageiq ~]# yum groupinstall "Resilient Storage"
...
Dependencies Resolved


 Package Arch Version
Repository Size

Installing for group install "Resilient Storage":
 dlm x86_64   4.0.6-1.el7
base   89 k
 gfs2-utils  x86_64   3.1.9-3.el7
base  302 k
 lvm2-clusterx86_64   7:2.02.166-1.el7_3.1
 updates   663 k
Installing for dependencies:
 corosyncx86_64   2.4.0-4.el7
base  213 k
 corosynclib x86_64   2.4.0-4.el7
base  125 k
 dlm-lib x86_64   4.0.6-1.el7
base   24 k
 libqb   x86_64   1.0-1.el7
base   92 k
 resource-agents x86_64   3.9.5-82.el7_3.1
 updates   360 k
Updating for dependencies:
 device-mapper   x86_64   7:1.02.135-1.el7_3.1
 updates   269 k
 device-mapper-event x86_64   7:1.02.135-1.el7_3.1
 updates   177 k
 device-mapper-event-libsx86_64   7:1.02.135-1.el7_3.1
 updates   177 k
 device-mapper-libs  x86_64   7:1.02.135-1.el7_3.1
 updates   333 k
 device-mapper-persistent-data   x86_64   0.6.3-1.el7
base  368 k
 lvm2x86_64   7:2.02.166-1.el7_3.1
 updates   1.1 M
 lvm2-libs   x86_64   7:2.02.166-1.el7_3.1
 updates   984 k

Transaction Summary

Install  3 Packages (+5 Dependent packages)
Upgrade ( 7 Dependent packages)

So it seems ok to me. It pulls the update of lvm2 package itself and also
the lvm2-cluster package (correctly pulled from the "updates" repo)

HIH,
Gianluca
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update pulls in lvm-cluster on 7.3

[me]

Hi,

I ran "yum update" this morning on a 7.2 machine with all of the cr updates
applied to it and yum wants to install lvm-cluster and a bunch of deps.

Dependencies Resolved

==
 Package   Arch  VersionRepository   Size
==
Installing for group upgrade "Resilient Storage":
 lvm2-cluster  x86_647:2.02.166-1.el7_3.1updates  663 k
Updating:
 centos-release   x86_64 7-3.1611.el7.centos base 23 k
Installing for dependencies:
 corosync x86_64 2.4.0-4.el7 base 213 k
 corosynclib  x86_64 2.4.0-4.el7 base 125 k
 dlm  x86_64 4.0.6-1.el7 base 89 k
 dlm-lib  x86_64 4.0.6-1.el7 base 24 k
 libqbx86_64 1.0-1.el7   base 92 k
 resource-agents  x86_64 3.9.5-82.el7_3.1updates  360 k

Transaction Summary
=
Install  1 Package (+6 Dependent packages)
Upgrade  1 Package

Total download size: 1.6 M
Is this ok [y/d/N]:
Exiting on user command
Your transaction was saved, rerun it with:
 yum load-transaction /tmp/yum_save_tx.2016-12-13.07-45.PcXumI.yumtx
(shadow pts3) #


I understand why the centos-release wants to be updated but can someone tell
me why it wants to pull in lvm-cluster and friends? This machine is not part
of a cluster.

Regards,

--
Tom m...@tdiehl.org Spamtrap address
me...@tdiehl.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update (first in a long time) - /var/log/dovecot no longer used

[m . roth]

Johnny Hughes wrote:

> Right.  And I do want to point out, this list is really not the place to
> discuss the positives and negatives of systemd vs. upstart vs. SysV.
> The goal of CentOS is to build RHEL source code with the absolute
> minimum changes required for branding.  So, we get the init system that
> is in the source code.
>
> Having that kind of discussion on a Fedora list might be appropriate if
> you are not a RHEL customer or on a RHEL list if you are.

Sorry, I hadn't read this when I posted my followup to Valeri. At any
rate, I *only* intended to make that one comment, and have no intention of
following up. I think that most of us do *NOT* want another flamewar that
buries actual question and answers related to what we're doing with CentOS
- administering and running it.

mark


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update (first in a long time) - /var/log/dovecot no longer used

[m . roth]

Valeri Galtsev wrote:
>
> On Fri, May 6, 2016 3:13 am, Gary Stainburn wrote:
>> On Thursday 05 May 2016 17:16:17 Valeri Galtsev wrote:
>>> There were several heated discussions on this list, and elsewhere. This
>>> is
>>> not intended to start the new one, but to help someone who missed them
>>> to
>>> define their statute.
>>>
>>> People split into two groups:
>>>
>>> Opponents of systemd (, firewqalld, etc.) who argue that from formerly
>>> Unix-like system Linux becomes Unix-unlike (or more MS Windows-like),
>>> and this is bad.
>>>
>>> Proponents of systemd etc. who argue that the life goes on, systems
>>> evolve and you better keep up with changes.
>>>

Or



mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update (first in a long time) - /var/log/dovecot no longer used

[Valeri Galtsev]

On Fri, May 6, 2016 8:46 am, Johnny Hughes wrote:
> On 05/06/2016 08:38 AM, Valeri Galtsev wrote:
>>
>> On Fri, May 6, 2016 3:13 am, Gary Stainburn wrote:
>>> On Thursday 05 May 2016 17:16:17 Valeri Galtsev wrote:
 There were several heated discussions on this list, and elsewhere.
 This
 is
 not intended to start the new one, but to help someone who missed them
 to
 define their statute.

 People split into two groups:

 Opponents of systemd (, firewqalld, etc.) who argue that from formerly
 Unix-like system Linux becomes Unix-unlike (or more MS Windows-like),
 and
 this is bad.

 Proponents of systemd etc. who argue that the life goes on, systems
 evolve
 and you better keep up with changes.

 Therefore, for new person who is about to, let's say, upgrade Linux
 system
 to the version with systemd, there is a decision that will define that
 person's future maintenance of this new system. And the decision has
 to
 be
 made before upgrade. Luckily for those who do decide to go with
 systemd,
 bugs (that always are present in new software) are being solved.
 Luckily
 for those who do not accept fundamental changes systemd brings (like
 binary logs or config files infested with XML garbage - sorry if I'm
 missing or misinterpreting something) there are Unix system one can
 migrate machine to.

 Either way one has to read and estimate what making that step
 (upgrading
 to systemd, firewalld based Linux or switching to some flavor of Unix)
 will entail in a long run for that server and the server admin. Either
 way, as in one of Unix handbooks they stress: read carefully the
 upgrade
 notes!

 I hope, this helps someone.

 Valeri

>>>
>>> I understand the arguments for the move to systemd - and I also
>>> understand
>>> the
>>> points of those arguments.  Like most arguments, there are some valid
>>> and
>>> positive points and some not so.
>>>
>>> There are times - such as the encompassing of the name resolver code -
>>> where
>>> it just seems a case of replacing old, mature code with new untested
>>> code
>>> for
>>> no reason.
>>>
>>> Either way, I now have to manage both traditional and systemd based
>>> systems.
>>> Okay, it just means learning new toolsets, but it's something else I
>>> have
>>> to
>>> learn, and something else I have to cope with for my bespoke systems
>>> and
>>> services.
>>
>> I guess, I didn't stress it well enough: read the upgrade notes! In case
>> of switching to systemd: read about what the change means.
>>
>> In other words, at least in minds of those who decided to migrate to
>> UNIX,
>> this change it not just about learning new tools. It is about how the
>> system works. I am not going to argue they (refugees to UNIX) are right,
>> or proponents of systemd (and friends) are right. The important part is
>> that each weighed the changed and will deal with the consequences of the
>> decision made conscientiously. But for that (to make good decision),
>> once
>> again:
>>
>> Read the "upgrade notes" [systemd documentation in this case]! This is
>> the
>> decision about your system and its future life.
>
> Right.  And I do want to point out, this list is really not the place to
> discuss the positives and negatives of systemd vs. upstart vs. SysV.
> The goal of CentOS is to build RHEL source code with the absolute
> minimum changes required for branding.  So, we get the init system that
> is in the source code.

Exactly. As I said in the first post (reply to which happened to hijack
the thread - my apologies that was not intended by me), it was only
intended to help those who are just about to make this step to really
think about what it will entail. And thanks everybody who added their
comments, they all do the same what I intended.

Valeri

>
> Having that kind of discussion on a Fedora list might be appropriate if
> you are not a RHEL customer or on a RHEL list if you are.
>
>>
>>>
>>> What I didn't expect, and what really threw me was that this has been
>>> implemented via a simply 'yum update' of an existing system, not at a
>>> major
>>> release level.
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update (first in a long time) - /var/log/dovecot no longer used

[Johnny Hughes]

On 05/06/2016 08:38 AM, Valeri Galtsev wrote:
> 
> On Fri, May 6, 2016 3:13 am, Gary Stainburn wrote:
>> On Thursday 05 May 2016 17:16:17 Valeri Galtsev wrote:
>>> There were several heated discussions on this list, and elsewhere. This
>>> is
>>> not intended to start the new one, but to help someone who missed them
>>> to
>>> define their statute.
>>>
>>> People split into two groups:
>>>
>>> Opponents of systemd (, firewqalld, etc.) who argue that from formerly
>>> Unix-like system Linux becomes Unix-unlike (or more MS Windows-like),
>>> and
>>> this is bad.
>>>
>>> Proponents of systemd etc. who argue that the life goes on, systems
>>> evolve
>>> and you better keep up with changes.
>>>
>>> Therefore, for new person who is about to, let's say, upgrade Linux
>>> system
>>> to the version with systemd, there is a decision that will define that
>>> person's future maintenance of this new system. And the decision has to
>>> be
>>> made before upgrade. Luckily for those who do decide to go with systemd,
>>> bugs (that always are present in new software) are being solved. Luckily
>>> for those who do not accept fundamental changes systemd brings (like
>>> binary logs or config files infested with XML garbage - sorry if I'm
>>> missing or misinterpreting something) there are Unix system one can
>>> migrate machine to.
>>>
>>> Either way one has to read and estimate what making that step (upgrading
>>> to systemd, firewalld based Linux or switching to some flavor of Unix)
>>> will entail in a long run for that server and the server admin. Either
>>> way, as in one of Unix handbooks they stress: read carefully the upgrade
>>> notes!
>>>
>>> I hope, this helps someone.
>>>
>>> Valeri
>>>
>>
>> I understand the arguments for the move to systemd - and I also understand
>> the
>> points of those arguments.  Like most arguments, there are some valid and
>> positive points and some not so.
>>
>> There are times - such as the encompassing of the name resolver code -
>> where
>> it just seems a case of replacing old, mature code with new untested code
>> for
>> no reason.
>>
>> Either way, I now have to manage both traditional and systemd based
>> systems.
>> Okay, it just means learning new toolsets, but it's something else I have
>> to
>> learn, and something else I have to cope with for my bespoke systems and
>> services.
> 
> I guess, I didn't stress it well enough: read the upgrade notes! In case
> of switching to systemd: read about what the change means.
> 
> In other words, at least in minds of those who decided to migrate to UNIX,
> this change it not just about learning new tools. It is about how the
> system works. I am not going to argue they (refugees to UNIX) are right,
> or proponents of systemd (and friends) are right. The important part is
> that each weighed the changed and will deal with the consequences of the
> decision made conscientiously. But for that (to make good decision), once
> again:
> 
> Read the "upgrade notes" [systemd documentation in this case]! This is the
> decision about your system and its future life.

Right.  And I do want to point out, this list is really not the place to
discuss the positives and negatives of systemd vs. upstart vs. SysV.
The goal of CentOS is to build RHEL source code with the absolute
minimum changes required for branding.  So, we get the init system that
is in the source code.

Having that kind of discussion on a Fedora list might be appropriate if
you are not a RHEL customer or on a RHEL list if you are.

> 
>>
>> What I didn't expect, and what really threw me was that this has been
>> implemented via a simply 'yum update' of an existing system, not at a
>> major
>> release level.




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update (first in a long time) - /var/log/dovecot no longer used

[Valeri Galtsev]

On Fri, May 6, 2016 3:13 am, Gary Stainburn wrote:
> On Thursday 05 May 2016 17:16:17 Valeri Galtsev wrote:
>> There were several heated discussions on this list, and elsewhere. This
>> is
>> not intended to start the new one, but to help someone who missed them
>> to
>> define their statute.
>>
>> People split into two groups:
>>
>> Opponents of systemd (, firewqalld, etc.) who argue that from formerly
>> Unix-like system Linux becomes Unix-unlike (or more MS Windows-like),
>> and
>> this is bad.
>>
>> Proponents of systemd etc. who argue that the life goes on, systems
>> evolve
>> and you better keep up with changes.
>>
>> Therefore, for new person who is about to, let's say, upgrade Linux
>> system
>> to the version with systemd, there is a decision that will define that
>> person's future maintenance of this new system. And the decision has to
>> be
>> made before upgrade. Luckily for those who do decide to go with systemd,
>> bugs (that always are present in new software) are being solved. Luckily
>> for those who do not accept fundamental changes systemd brings (like
>> binary logs or config files infested with XML garbage - sorry if I'm
>> missing or misinterpreting something) there are Unix system one can
>> migrate machine to.
>>
>> Either way one has to read and estimate what making that step (upgrading
>> to systemd, firewalld based Linux or switching to some flavor of Unix)
>> will entail in a long run for that server and the server admin. Either
>> way, as in one of Unix handbooks they stress: read carefully the upgrade
>> notes!
>>
>> I hope, this helps someone.
>>
>> Valeri
>>
>
> I understand the arguments for the move to systemd - and I also understand
> the
> points of those arguments.  Like most arguments, there are some valid and
> positive points and some not so.
>
> There are times - such as the encompassing of the name resolver code -
> where
> it just seems a case of replacing old, mature code with new untested code
> for
> no reason.
>
> Either way, I now have to manage both traditional and systemd based
> systems.
> Okay, it just means learning new toolsets, but it's something else I have
> to
> learn, and something else I have to cope with for my bespoke systems and
> services.

I guess, I didn't stress it well enough: read the upgrade notes! In case
of switching to systemd: read about what the change means.

In other words, at least in minds of those who decided to migrate to UNIX,
this change it not just about learning new tools. It is about how the
system works. I am not going to argue they (refugees to UNIX) are right,
or proponents of systemd (and friends) are right. The important part is
that each weighed the changed and will deal with the consequences of the
decision made conscientiously. But for that (to make good decision), once
again:

Read the "upgrade notes" [systemd documentation in this case]! This is the
decision about your system and its future life.

Valeri

>
> What I didn't expect, and what really threw me was that this has been
> implemented via a simply 'yum update' of an existing system, not at a
> major
> release level.


Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update (first in a long time) - /var/log/dovecot no longer used

[James B. Byrne]

On Fri, May 6, 2016 04:36, John Hodrien wrote:
> On Fri, 6 May 2016, Gary Stainburn wrote:
>
>> What I didn't expect, and what really threw me was that this has
>> been implemented via a simply 'yum update' of an existing system,
>> not at a major release level.
>
>
> Something like RHEL is stuck in a trap here.  Either they never
> change a default post-install (lots of rpmnew or deliberately
> not introducing new behaviours), or they bring in defaults as
> you update (to some extent doing things like rpmsave).  Some
> people would complain whichever option they chose.

Or have packagers divide configuration files into system and local
with local overriding system. Then restrict software updates such that
they modify only system configs leaving locals alone.  That way new
things can be added with old things are left as they are. Some
software already behaves like this.  There is no evident technical
reason why most of the rest could not as well.

If an update is such that old things cannot be left alone then that is
sufficient to require an rpmnew and a warning to the installer that
manual intervention is required to complete the update. In fact,
anything of that nature would benefit from requiring a special switch
to install so that 'yum update' would not break a running system.


-- 
***  e-Mail is NOT a SECURE channel  ***
Do NOT transmit sensitive data via e-Mail
 Do NOT open attachments nor follow links sent by e-Mail

James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update (first in a long time) - EXIM environment variable warning

[Johnny Hughes]

On 05/06/2016 05:45 AM, Johnny Hughes wrote:
> On 05/06/2016 03:30 AM, Gary Stainburn wrote:
>> Me again,
>>
>> Another problem I've found since doing my yum update is that EXIM is now 
>> showing the following error, on startup, and repeatedly in main.log
>>
>> [root@ollie2 ~]# exim -bt   localp...@example.com
>> 2016-05-06 09:27:04 WARNING: purging the environment.
>>  Suggested action: use keep_environment and add_environment.
>>
>> ...
>>
>> Googling says that to fix this all I need to do is add
>>
>> keep_environment
>>
>> to exim.conf.  What I'm struggling to find out is why it's suddenly needed 
>> and 
>> what the effects are
> 
> exim is not part of CentOS-7 .. it is part of EPEL (I think, based on my
> yum list).  Not sure who the maintainer is or if he/she is on this list.
>  Maybe they are on they EPEL mailing list.  Here is the output of yum
> list exim:
> 
> exim.x86_64   4.84.2-2.el7  epel
> 

BTW, I am not saying that you shouldn't discuss this on the CentOS
mailing list.  It is absolutely OK for you to discuss it here.  I am
just saying that you might be able to also find more help elsewhere too.

Just wanted to make sure my other post is not misinterpreted 'take this
off our list' .. it is instead a 'the helper you seek may not be
subscribed here' :)




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update (first in a long time) - EXIM environment variable warning

[Johnny Hughes]

On 05/06/2016 03:30 AM, Gary Stainburn wrote:
> Me again,
> 
> Another problem I've found since doing my yum update is that EXIM is now 
> showing the following error, on startup, and repeatedly in main.log
> 
> [root@ollie2 ~]# exim -bt   localp...@example.com
> 2016-05-06 09:27:04 WARNING: purging the environment.
>  Suggested action: use keep_environment and add_environment.
> 
> ...
> 
> Googling says that to fix this all I need to do is add
> 
> keep_environment
> 
> to exim.conf.  What I'm struggling to find out is why it's suddenly needed 
> and 
> what the effects are

exim is not part of CentOS-7 .. it is part of EPEL (I think, based on my
yum list).  Not sure who the maintainer is or if he/she is on this list.
 Maybe they are on they EPEL mailing list.  Here is the output of yum
list exim:

exim.x86_64   4.84.2-2.el7  epel




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update (first in a long time) - /var/log/dovecot no longer used

[John Hodrien]

On Fri, 6 May 2016, Gary Stainburn wrote:


What I didn't expect, and what really threw me was that this has been
implemented via a simply 'yum update' of an existing system, not at a major
release level.


journald has been there since you installed C7.

You appear to have seen a change in logging behaviour as a result of an
update.  Whether that's due to an update of dovecot, systemd, or something
else, I have no idea.

Something like RHEL is stuck in a trap here.  Either they never change a
default post-install (lots of rpmnew or deliberately not introducing new
behaviours), or they bring in defaults as you update (to some extent doing
things like rpmsave).  Some people would complain whichever option they chose.

jh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update (first in a long time) - EXIM environment variable warning

[Gary Stainburn]

Me again,

Another problem I've found since doing my yum update is that EXIM is now 
showing the following error, on startup, and repeatedly in main.log

[root@ollie2 ~]# exim -bt   localp...@example.com
2016-05-06 09:27:04 WARNING: purging the environment.
 Suggested action: use keep_environment and add_environment.

...

Googling says that to fix this all I need to do is add

keep_environment

to exim.conf.  What I'm struggling to find out is why it's suddenly needed and 
what the effects are
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update (first in a long time) - /var/log/dovecot no longer used

[Gary Stainburn]

On Thursday 05 May 2016 17:16:17 Valeri Galtsev wrote:
> There were several heated discussions on this list, and elsewhere. This is
> not intended to start the new one, but to help someone who missed them to
> define their statute.
>
> People split into two groups:
>
> Opponents of systemd (, firewqalld, etc.) who argue that from formerly
> Unix-like system Linux becomes Unix-unlike (or more MS Windows-like), and
> this is bad.
>
> Proponents of systemd etc. who argue that the life goes on, systems evolve
> and you better keep up with changes.
>
> Therefore, for new person who is about to, let's say, upgrade Linux system
> to the version with systemd, there is a decision that will define that
> person's future maintenance of this new system. And the decision has to be
> made before upgrade. Luckily for those who do decide to go with systemd,
> bugs (that always are present in new software) are being solved. Luckily
> for those who do not accept fundamental changes systemd brings (like
> binary logs or config files infested with XML garbage - sorry if I'm
> missing or misinterpreting something) there are Unix system one can
> migrate machine to.
>
> Either way one has to read and estimate what making that step (upgrading
> to systemd, firewalld based Linux or switching to some flavor of Unix)
> will entail in a long run for that server and the server admin. Either
> way, as in one of Unix handbooks they stress: read carefully the upgrade
> notes!
>
> I hope, this helps someone.
>
> Valeri
>

I understand the arguments for the move to systemd - and I also understand the 
points of those arguments.  Like most arguments, there are some valid and 
positive points and some not so.

There are times - such as the encompassing of the name resolver code - where 
it just seems a case of replacing old, mature code with new untested code for 
no reason.

Either way, I now have to manage both traditional and systemd based systems. 
Okay, it just means learning new toolsets, but it's something else I have to 
learn, and something else I have to cope with for my bespoke systems and 
services.

What I didn't expect, and what really threw me was that this has been 
implemented via a simply 'yum update' of an existing system, not at a major 
release level.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update (first in a long time) - /var/log/dovecot no longer used

[John Hodrien]

On Thu, 5 May 2016, Gary Stainburn wrote:


Another change to my Centos 7.2 system since my 'yum update' yesterday is
that /var/log/dovecot is no longer written to.

If I do 'systemctl status dovecot' I can see log entries. How can I now do
the equiv or 'tail -f '

Also, why has this changed, and where is it documented?


I'd take a stab at:

journalctl -fu dovecot

The full RHEL7 System Administrators Guide is well worth a read, but here's
the bit you're probably after.

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/s1-Using_the_Journal.html

Or maybe:

https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs

jh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update (first in a long time) - /var/log/dovecot no longer used

[Gary Stainburn]

Me again,

Another change to my Centos 7.2 system since my 'yum update' yesterday is 
that /var/log/dovecot is no longer written to.

If I do 'systemctl status dovecot' I can see log entries. How can I now do the 
equiv or 'tail -f '

Also, why has this changed, and where is it documented?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update (first in a long time) has broken clamd.exim

[Gary Stainburn]

I have just run a 'yum update' on a Centos 7.2 server which updated several 
hundred RPMs.

The update worked fine with no errors or warnings

I then rebooted the server and now my EXIM is rejecting emails because the 
clamd service isn't running.

So I tried:

[root@ollie2 ~]# systemctl restart clamd.exim
Failed to restart clamd.exim.service: Unit clamd.exim.service failed to load: 
No such file or directory.
[root@ollie2 ~]# systemctl list-unit-files --type=service|grep -i exim
exim.serviceenabled 
[root@ollie2 ~]# systemctl list-unit-files --type=service|grep -i clam
clamd.service   enabled 
clamd@.service  static  
[root@ollie2 ~]# systemctl restart clamd 
[root@ollie2 ~]# systemctl status clamd
● clamd.service - Home brewed module for the Clam Antivirus scanner
   Loaded: loaded (/usr/lib/systemd/system/clamd.service; enabled; vendor 
preset: disabled)
   Active: failed (Result: start-limit) since Wed 2016-05-04 16:34:16 BST; 5s 
ago
  Process: 14405 ExecStart=/root/bin/clamd.start (code=exited, 
status=1/FAILURE)
 Main PID: 14405 (code=exited, status=1/FAILURE)

May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: Unit clamd.service entered 
failed state.
May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: clamd.service failed.
May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: clamd.service holdoff time 
over, scheduling restart.
May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: start request repeated too 
quickly for clamd.service
May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: Failed to start Home brewed 
module for the Clam Antivirus scanner.
May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: Unit clamd.service entered 
failed state.
May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: clamd.service failed.
[root@ollie2 ~]# 

Can anyone tell me what happened to clamd.exim, and what I need to do to get 
it working again.  For now I've had to comment out:

  # Deny if the message contains a virus. Before enabling this check, you
  # must install a virus scanner and set the av_scanner option above.
  #
denyset acl_m0 = clamd:/var/run/clamd.exim/clamd.sock
malware= *
set acl_c_SPAM = 1
message= A virus has been detected ($malware_name).

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Yum update issues

[Greg Bailey]

On 03/16/2016 12:31 AM, John Cenile wrote:

Hello all,

When running yum update on a few of our servers, we get the following
errors:



[snip]



Traceback (most recent call last):
   File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 470, in
callback
 self._scriptStop(bytes, total, h);
   File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 636, in
_scriptStop
 name, txmbr = self._getTxmbr(h)
   File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 331, in
_getTxmbr
 assert len(txmbrs) == 1
AssertionError
error: python callback > failed, aborting!



This looks like https://bugzilla.redhat.com/show_bug.cgi?id=1259527

which I believe to be a bug in yum, that I also hit while running 
CloudLinux.


In my case, I removed "cpuspeed" (rpm -e cpuspeed) before running "yum 
upgrade" to upgrade all of the other components.


-Greg

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Yum update issues

[Frank Cox]

On Wed, 16 Mar 2016 18:31:59 +1100
John Cenile wrote:

> When running yum update on a few of our servers, we get the following
> errors:

It appears that you're not running Centos, but rather Cloudlinux.  Have you 
checked with their technical support?

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Yum update issues

[John Cenile]

Hello all,

When running yum update on a few of our servers, we get the following
errors:

Running Transaction
  Updating   : openssl-1.0.1e-42.el6_7.4.x86_64


   1/327
  Updating   : postgresql-libs-8.4.20-5.el6_7.cloudlinux.x86_64


   2/327
  Updating   : kernel-firmware-2.6.32-673.8.1.lve1.4.3.el6.noarch


   3/327
  Updating   : kmod-lve-1.4-3.1.el6.x86_64


4/327
  Installing :
kmod-lve-2.6.32-673.8.1.lve1.4.3.el6.x86_64-1.4-3.1.el6.x86_64

 5/327
  Installing : e1000e-3.3.3-2.el6.noarch


6/327
  Installing :
kmod-e1000e-2.6.32-673.8.1.lve1.4.3.el6.x86_64.debug-3.3.3-2.el6.x86_64

7/327
  Installing :
kmod-lve-2.6.32-673.8.1.lve1.4.3.el6.x86_64.debug-1.4-3.1.el6.x86_64

 8/327
  Installing : kernel-debug-2.6.32-673.8.1.lve1.4.3.el6.x86_64


9/327
  Updating   : liblve-1.4-1.3.el6.cloudlinux.x86_64


  10/327
  Updating   : lve-1.4-1.3.el6.cloudlinux.x86_64


   11/327
  Installing :
kmod-e1000e-2.6.32-673.8.1.lve1.4.3.el6.x86_64-3.3.3-2.el6.x86_64

   12/327
  Installing : kernel-2.6.32-673.8.1.lve1.4.3.el6.x86_64


   13/327

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 470, in
callback
self._scriptStop(bytes, total, h);
  File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 636, in
_scriptStop
name, txmbr = self._getTxmbr(h)
  File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 331, in
_getTxmbr
assert len(txmbrs) == 1
AssertionError
error: python callback > failed, aborting!


And if I try and run yum update again, I get the following:


--> Finished Dependency Resolution
Error: cagefs conflicts with liblve-1.3-1.10.el6.cloudlinux.x86_64
 You could try using --skip-broken to work around the problem
** Found 8 pre-existing rpmdb problem(s), 'yum check' output follows:
kernel-2.6.32-673.8.1.lve1.4.3.el6.x86_64 has missing requires of
kmod-ixgbe-2.6.32-673.8.1.lve1.4.3.el6.x86_64
kernel-debug-2.6.32-673.8.1.lve1.4.3.el6.x86_64 has missing requires of
kmod-ixgbe-2.6.32-673.8.1.lve1.4.3.el6.x86_64.debug
kernel-firmware-2.6.32-673.8.1.lve1.4.3.el6.noarch is a duplicate with
kernel-firmware-2.6.32-604.30.3.lve1.3.63.el6.noarch
kmod-lve-1.4-3.1.el6.x86_64 is a duplicate with kmod-lve-1.3-11.1.el6.x86_64
liblve-1.4-1.3.el6.cloudlinux.x86_64 is a duplicate with
liblve-1.3-1.10.el6.cloudlinux.x86_64
lve-1.4-1.3.el6.cloudlinux.x86_64 is a duplicate with
lve-1.3-1.10.el6.cloudlinux.x86_64
openssl-1.0.1e-42.el6_7.4.x86_64 is a duplicate with
openssl-1.0.1e-42.el6_7.2.x86_64
postgresql-libs-8.4.20-5.el6_7.cloudlinux.x86_64 is a duplicate with
postgresql-libs-8.4.20-4.el6_7.cloudlinux.x86_64


When I check for duplicate packages:

*# package-cleanup --dupes*
Loaded plugins: fastestmirror, rhnplugin
lve-1.4-1.3.el6.cloudlinux.x86_64
lve-1.3-1.10.el6.cloudlinux.x86_64
postgresql-libs-8.4.20-5.el6_7.cloudlinux.x86_64
postgresql-libs-8.4.20-4.el6_7.cloudlinux.x86_64
kmod-lve-1.4-3.1.el6.x86_64
kmod-lve-1.3-11.1.el6.x86_64
liblve-1.4-1.3.el6.cloudlinux.x86_64
liblve-1.3-1.10.el6.cloudlinux.x86_64
openssl-1.0.1e-42.el6_7.4.x86_64
openssl-1.0.1e-42.el6_7.2.x86_64


I then run package-cleanup --cleandupes and get the following:


Running Transaction
** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows:
kernel-2.6.32-673.8.1.lve1.4.3.el6.x86_64 has missing requires of
kmod-ixgbe-2.6.32-673.8.1.lve1.4.3.el6.x86_64
kernel-debug-2.6.32-673.8.1.lve1.4.3.el6.x86_64 has missing requires of
kmod-ixgbe-2.6.32-673.8.1.lve1.4.3.el6.x86_64.debug
kernel-firmware-2.6.32-673.8.1.lve1.4.3.el6.noarch is a duplicate with
kernel-firmware-2.6.32-604.30.3.lve1.3.63.el6.noarch



So I then run:

yum install kmod-ixgbe-2.6.32-673.8.1.lve1.4.3.el6.x86_64


Only after cleaning the duplicates, and installing kmod-ixgbe, can I *then* run
yum update -y, and it succeeds.

It's extremely annoying because the above error is preventing cPanel
updates from completing nightly (until I do the above), and I would love to
know why this is suddenly happening on so many servers, for seemingly no
reason.

Thanks in advance.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] Centos yum update detenido

[Eliud Cardenas]

Hola,

Ya supe cual fue el problema, revise con un ps uax y vi que el proceso 
de yum update estaba dormido (S+) lo que me parecio muy extraño, volvi a 
correr ps pero ahora con tree y me arrojo lo siguiente:


4129 pts/0S+ 0:00  \_ /bin/sh 
/sbin/service httpd condrestart
 4134 pts/0S+ 0:00  \_ 
/bin/bash /etc/init.d/httpd condrestart
 4147 pts/0S+ 0:00  \_ 
/bin/bash -c ulimit -S -c 0 /dev/null 21 ; /usr/sbin/httpd
 4148 pts/0S+ 0:00  \_ 
/usr/sbin/httpd


Al ver esto supe que se trataba del passphrase que usa mi certificado al 
reiniciar apache, por lo cual solo mate el proceso de reinicio y yum 
continuo su proceso.



Saludos!


Eliud Cardenas mailto:ecarde...@people-cloud.com
August 2, 2015 at 10:52 AM
Hola a todos,

Quisiera hacer una pregunta, recien estoy actualizando mi Centos 6.6 
con yum pero se ha quedado en el proceso de Cleanup, no avanza, ya 
esta en el ultimo paquete pero esto me ha detenido el apache y algunos 
otros servicios, es recomendable detenerlo con Ctrl-c o tendre que 
esperarme a realizar alguno otro movimiento? (Tengo acceso via ssh 
desde otra terminal, eso creo no se detuvo)


Saludos!


--




*Eliud Cardenas *

Infrastructure Engineer

ecarde...@people-cloud.com mailto:ecarde...@people-cloud.com

www.people-cloud.com http://www.people-cloud.com/
Tel. 83358829 tel://Tel.%2083358829  Ext. 109

Cel. 8180882982 tel://Cel.%208183960861

___
CentOS-es mailing list
CentOS-es@centos.org
http://lists.centos.org/mailman/listinfo/centos-es

[CentOS-es] Centos yum update detenido

[Eliud Cardenas]

Hola a todos,

Quisiera hacer una pregunta, recien estoy actualizando mi Centos 6.6 con 
yum pero se ha quedado en el proceso de Cleanup, no avanza, ya esta en 
el ultimo paquete pero esto me ha detenido el apache y algunos otros 
servicios, es recomendable detenerlo con Ctrl-c o tendre que esperarme a 
realizar alguno otro movimiento? (Tengo acceso via ssh desde otra 
terminal, eso creo no se detuvo)


Saludos!
--


___
CentOS-es mailing list
CentOS-es@centos.org
http://lists.centos.org/mailman/listinfo/centos-es

[CentOS] yum update on CentOS6 failing

[Rob Kampen]

Hi anyone else having this problem?
Error: Package: perl-IO-Compress-Bzip2-2.021-136.el6.x86_64 (@base)
   Requires: perl = 4:5.10.1-136.el6
   Removing: 4:perl-5.10.1-136.el6.x86_64 (@base)
   perl = 4:5.10.1-136.el6
   Updated By: 4:perl-5.10.1-136.el6_6.1.x86_64 (updates)
   perl = 4:5.10.1-136.el6_6.1
tried a yum clean all and still an issue
TIA
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update on CentOS6 failing

[Nicolas Thierry-Mieg]

On 12/02/2014 10:55 AM, Rob Kampen wrote:

Hi anyone else having this problem?
Error: Package: perl-IO-Compress-Bzip2-2.021-136.el6.x86_64 (@base)
Requires: perl = 4:5.10.1-136.el6
Removing: 4:perl-5.10.1-136.el6.x86_64 (@base)
perl = 4:5.10.1-136.el6
Updated By: 4:perl-5.10.1-136.el6_6.1.x86_64 (updates)
perl = 4:5.10.1-136.el6_6.1
tried a yum clean all and still an issue
TIA



perl-IO-Compress-Bzip2-2.021-136.el6_6.1.x86_64 is in updates. You must 
have an excludes, or an installed rpm that requires the older version of 
that package and prevents it from updating.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update success+failure

[James B. Byrne]

On Tue, September 30, 2014 10:07, ken wrote:
 Just doing yum update on two machines (and only two), both centos
 5.10, one of them updated something like 22 packages, the other just 4.
   Packages which were updated on the first, but didn't get updated on
 the second machine include: gcc, httpd, kernel-2.6.18-398.el5, and
 probably a couple more.  Trying the update on the second machine again
 (a few times), it always ends, No Packages marked for Update.

 So now the first has:

 gcc-4.1.2-55.el5
 httpd-2.2.3-91.el5.centos
 kernel-2.6.18-371.12.1.el5.centos.plus

 while the second has:

 gcc-4.1.2-54.el5
 httpd-2.2.3-87.el5.centos
 kernel-2.6.18-371.11.1.el5

 WTH???

Try this:

yum clean all ; yum update -y




-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte  Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update success+failure

[ken]

Just doing yum update on two machines (and only two), both centos 
5.10, one of them updated something like 22 packages, the other just 4. 
 Packages which were updated on the first, but didn't get updated on 
the second machine include: gcc, httpd, kernel-2.6.18-398.el5, and 
probably a couple more.  Trying the update on the second machine again 
(a few times), it always ends, No Packages marked for Update.


So now the first has:

gcc-4.1.2-55.el5
httpd-2.2.3-91.el5.centos
kernel-2.6.18-371.12.1.el5.centos.plus

while the second has:

gcc-4.1.2-54.el5
httpd-2.2.3-87.el5.centos
kernel-2.6.18-371.11.1.el5

WTH???
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update success+failure

[Gilbert Sebenste]

On Tue, 30 Sep 2014, ken wrote:

Just doing yum update on two machines (and only two), both centos 5.10, one 
of them updated something like 22 packages, the other just 4.  Packages which 
were updated on the first, but didn't get updated on the second machine 
include: gcc, httpd, kernel-2.6.18-398.el5, and probably a couple more. 
Trying the update on the second machine again (a few times), it always ends, 
No Packages marked for Update.


So now the first has:

gcc-4.1.2-55.el5
httpd-2.2.3-91.el5.centos
kernel-2.6.18-371.12.1.el5.centos.plus

while the second has:

gcc-4.1.2-54.el5
httpd-2.2.3-87.el5.centos
kernel-2.6.18-371.11.1.el5

WTH???


Looks like the server you were getting the updates from has an incomplete 
sync, or is in the process of syncing. Do a 'yum clean all, and try again

later today.

Gilbert

***
Gilbert Sebenste
(My opinions only!)  **
***
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update success+failure

[Valeri Galtsev]

On Tue, September 30, 2014 9:07 am, ken wrote:
 Just doing yum update on two machines (and only two), both centos
 5.10, one of them updated something like 22 packages, the other just 4.
   Packages which were updated on the first, but didn't get updated on
 the second machine include: gcc, httpd, kernel-2.6.18-398.el5, and
 probably a couple more.  Trying the update on the second machine again
 (a few times), it always ends, No Packages marked for Update.

 So now the first has:

 gcc-4.1.2-55.el5
 httpd-2.2.3-91.el5.centos
 kernel-2.6.18-371.12.1.el5.centos.plus

 while the second has:

 gcc-4.1.2-54.el5
 httpd-2.2.3-87.el5.centos
 kernel-2.6.18-371.11.1.el5

 WTH???

Quite likely they just hit two different mirrors, one mirror is probably
already fully in sync with master, the other is not. As it was already
mentioned on this list, with big release (5.11 it is this time) it takes
time for all mirrors to synchronize.

Valeri


Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update success+failure

[ken]

On 09/30/2014 12:00 PM Valeri Galtsev wrote:


On Tue, September 30, 2014 9:07 am, ken wrote:

Just doing yum update on two machines (and only two), both centos
5.10, one of them updated something like 22 packages, the other just 4.
   Packages which were updated on the first, but didn't get updated on
the second machine include: gcc, httpd, kernel-2.6.18-398.el5, and
probably a couple more.  Trying the update on the second machine again
(a few times), it always ends, No Packages marked for Update.

So now the first has:

gcc-4.1.2-55.el5
httpd-2.2.3-91.el5.centos
kernel-2.6.18-371.12.1.el5.centos.plus

while the second has:

gcc-4.1.2-54.el5
httpd-2.2.3-87.el5.centos
kernel-2.6.18-371.11.1.el5

WTH???


Quite likely they just hit two different mirrors, one mirror is probably
already fully in sync with master, the other is not. As it was already
mentioned on this list, with big release (5.11 it is this time) it takes
time for all mirrors to synchronize.

Valeri


That must have been it.  I just tried again and the second machine had 
41 packages updated, including those mentioned above.  For the record, 
no other yum commands were required.  I just needed to re-run the same 
old yum update.


Thanks to all for the kind counsel,
ken

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Yum update changes inode of file

[Meikel]

Hi folks,

on CentOS 6.5 I run tripwire software which verifies data integrity. My 
system is automatically updated by yum (as far as I understand the 
/etc/cron.daily/0yum.cron is responsible for the regular system 
updates). After a system update I'm then notified by tripwire about the 
changes on the file system.

By browsing those tripwire reports I found that there are files which 
did not change at all (i.e. the MD5 hash is the same as before) but the 
inode changed. I do not understand what yum did to the file that 
resulted in an inode change, especially I'm wondering how the inode can 
change although there was no modification on the file at all.

Thanks in advance for any clarification.

Find below an excerpt from the tripwire log (for /etc/nsswitch.conf) 
which shows that only inode changed.

Regards,

Meikel




Excerpt from tripwire report:

Modified object name:  /etc/nsswitch.conf

   Property:ExpectedObserved
   ---- ---
   Object Type  Regular FileRegular File
   Device Number64770   64770
* Inode Number 393292  393686
   Mode -rw-r--r--  -rw-r--r--
   Num Links1   1
   UID  root (0)root (0)
   GID  root (0)root (0)
   Size 16881688
   Modify Time  Tue 04 May 2010 09:22:21 PM CEST
Tue 04 May 2010 09:22:21 PM 
CEST
   Blocks   8   8
   CRC32DjDI7W  DjDI7W
   MD5  ANYAnN/RJkbSUehjA7wMSM  ANYAnN/RJkbSUehjA7wMSM


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Yum update changes inode of file

[Matthew Miller]

On Fri, Aug 22, 2014 at 11:13:40PM +0200, Meikel wrote:
 By browsing those tripwire reports I found that there are files which 
 did not change at all (i.e. the MD5 hash is the same as before) but the 
 inode changed. I do not understand what yum did to the file that 
 resulted in an inode change, especially I'm wondering how the inode can 
 change although there was no modification on the file at all.

Do you have redhat-lsb installed? I bet that this is related to this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=867124


-- 
Matthew Miller
mat...@fedoraproject.org
Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Yum update changes inode of file

[GKH]

Meikel,

Aside from the stupid way:

create a file org_name
copy it to new_name
rm org_name
mv new_name org_name

I don't know of a way to change inode
and keep md5 the same.

Does anyone know of a way?

This would be the perfect question for this forum.

GKH

 Hi folks,

 on CentOS 6.5 I run tripwire software which verifies data integrity. My
 system is automatically updated by yum (as far as I understand the
 /etc/cron.daily/0yum.cron is responsible for the regular system
 updates). After a system update I'm then notified by tripwire about the
 changes on the file system.

 By browsing those tripwire reports I found that there are files which
 did not change at all (i.e. the MD5 hash is the same as before) but the
 inode changed. I do not understand what yum did to the file that
 resulted in an inode change, especially I'm wondering how the inode can
 change although there was no modification on the file at all.

 Thanks in advance for any clarification.

 Find below an excerpt from the tripwire log (for /etc/nsswitch.conf)
 which shows that only inode changed.

 Regards,

 Meikel




 Excerpt from tripwire report:

 Modified object name:  /etc/nsswitch.conf

Property:ExpectedObserved
---- ---
Object Type  Regular FileRegular File
Device Number64770   64770
 * Inode Number 393292  393686
Mode -rw-r--r--  -rw-r--r--
Num Links1   1
UID  root (0)root (0)
GID  root (0)root (0)
Size 16881688
Modify Time  Tue 04 May 2010 09:22:21 PM CEST
 Tue 04 May 2010 09:22:21 
 PM CEST
Blocks   8   8
CRC32DjDI7W  DjDI7W
MD5  ANYAnN/RJkbSUehjA7wMSM  ANYAnN/RJkbSUehjA7wMSM


 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Yum update changes inode of file

[Keith Keller]

On 2014-08-22, GKH x...@darksmile.net wrote:
 Aside from the stupid way:

 create a file org_name
 copy it to new_name
 rm org_name
 mv new_name org_name

 I don't know of a way to change inode
 and keep md5 the same.

If the bug that Matthew cited is involved, then that's likely very much
what happened.  If the OP never changed nsswitch.conf, then the MD5
would be the same despite the package removing and creating a new file.

--keith


-- 
kkel...@wombat.san-francisco.ca.us


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update tries and fails to install libreswan

[Fred Smith]

On 6.5, I've got openswan installed, but yum update is wanting to install
libreswan.

If libreswan is intended to replace openswan, wouldn't the appropriate yum
transactions have been created to remove opnswan first?

I'm stumped. Advice appreciated.

Fred
-- 
---
Under no circumstances will I ever purchase anything offered to me as
the result of an unsolicited e-mail message. Nor will I forward chain
letters, petitions, mass mailings, or virus warnings to large numbers
of others. This is my contribution to the survival of the online
community.
 --Roger Ebert, December, 1996
- The Boulder Pledge -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update tries and fails to install libreswan

[Liam O'Toole]

On 2014-02-05, Fred Smith fre...@fcshome.stoneham.ma.us wrote:
 On 6.5, I've got openswan installed, but yum update is wanting to install
 libreswan.

 If libreswan is intended to replace openswan, wouldn't the appropriate yum
 transactions have been created to remove opnswan first?

 I'm stumped. Advice appreciated.

 Fred

Libreswan is from the epel repository, so it's not an official
replacement for openswan. You can exclude the package in your yum
configuration and carry on as before if you wish.

-- 

Liam


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update interruption recovery

[Louis Lagendijk]

On Wed, 2013-12-04 at 20:32 -0800, Hugh E Cruickshank wrote:
 From: Hugh E Cruickshank Sent: December 4, 2013 15:09
  From: Frank Cox Sent: December 4, 2013 15:04
   On Wed, 4 Dec 2013 14:55:03 -0800 Hugh E Cruickshank wrote:
Tried that but it failed. 
   
   Describe failed.
  
  That happened yesterday and I can not recall specifically what it
  said. I am currently in the process of backing up the hard drive
  before proceeding any further. I will see if I can get the error a
  little later today.
 
 Well I am unable to locate the error message as it does not appear to
 be logged. In the interim I have done a lot more research and I now
 suspect that I have two separate problems:
 
 1. Since the yum update did not complete then it never had a chance
to update the rpm database,
 
 2. We probably have one or more packages that have been install but
the predecessor has not be removed.
 
 I have done the following:
 
 a. Rebuilt the rpm database:
 
 rm -f /var/lib/rpm/__db*
 rpm --rebuilddb
 
 b. I then retried the yum update this aborted report conflicts in
systemtap packages.
 
 c. I listed the installed systemtap packages:
 
rpm -qa | grep systemtap | sort
 
This revealed that there were two systemtap-devel packages
installed and I removed the newer one.
 
 d. I then retried yum update and this appeared to work fine until it
got to:
 
Cleanup  : 1:xorg-x11-drv-nouveau-1.0.1-3.el6.x86_64  286/513
 
 At this point the system appears to be hung. I can not proceed any
 further this evening as I am working on this from home and I do not
 have physical access to the server to reboot it. In the morning I
 will reboot the server and try again but this time I am going to do
 a yum clean all to the rpm database rebuild.
 
 Any thoughts or comments would be appreciated.
 
Try package-cleanup --problems and see what it returns
package-cleanup --cleandupes  may helps with removal of duplicates

Louis

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update interruption recovery

[Les Mikesell]

On Wed, Dec 4, 2013 at 5:08 PM, Hugh E Cruickshank h...@forsoft.com wrote:

 That happened yesterday and I can not recall specifically what it said.
 I am currently in the process of backing up the hard drive before
 proceeding any further. I will see if I can get the error a little
 later today.


Sometimes 'yum-complete-transaction' will fix things - but yum will
normally tell you if it needs that. You can 'yum install yum-utils' if
you don't already have it.

-- 
  Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update interruption recovery

[Hugh E Cruickshank]

From: Louis Lagendijk Sent: December 5, 2013 13:37
 
 Try package-cleanup --problems and see what it returns
 package-cleanup --cleandupes  may helps with removal of duplicates

I jut finished cleaning it all up. It took a while and I ended up with
having to manually identify and delete a bout 40 duplicate packages
(your suggestions would probably have helped with that). It was also
necessary to reinstall the kernel packages but everything seems to be
humming along fine now (and up to date as well).

Thanks to all who provides feedback and suggestions.

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update interruption recovery

[Hugh E Cruickshank]

Hi All:

I am having problems with a CentOS 6.4 box that I was in the process
of doing a yum update to 6.5. Unfortunately the system hung during
the update and I was forced to reboot it and it is now a bit of a mess.
Can someone point me in the direction of any documentation that would
assist in the recovering from this.

TIA

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update interruption recovery

[Jitse Klomp]

On 12/04/2013 11:34 PM, Hugh E Cruickshank wrote:
 Hi All:

 I am having problems with a CentOS 6.4 box that I was in the process
 of doing a yum update to 6.5. Unfortunately the system hung during
 the update and I was forced to reboot it and it is now a bit of a mess.
 Can someone point me in the direction of any documentation that would
 assist in the recovering from this.

Run yum-complete-transaction.

Source: 
http://www.redhat.com/archives/rhl-devel-list/2008-September/msg00984.html

  - Jitse
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update interruption recovery

[Hugh E Cruickshank]

FromJitse Klomp Sent: December 4, 2013 14:47
 On 12/04/2013 11:34 PM, Hugh E Cruickshank wrote:
 
  I am having problems with a CentOS 6.4 box that I was in the process
  of doing a yum update to 6.5. Unfortunately the system hung during
  the update and I was forced to reboot it and it is now a bit of a
  mess. Can someone point me in the direction of any documentation
  that would assist in the recovering from this.
 
 Run yum-complete-transaction.

Tried that but it failed. I am now seriously looking at manually
deleting and/or reinstalling a large number of packages but I was
hoping that there might be some recommended procedures available out
there that might be easier.

TIA

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update interruption recovery

[Frank Cox]

On Wed, 4 Dec 2013 14:55:03 -0800
Hugh E Cruickshank wrote:

 Tried that but it failed. 

Describe failed.

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update interruption recovery

[Hugh E Cruickshank]

From: Frank Cox Sent: December 4, 2013 15:04
 On Wed, 4 Dec 2013 14:55:03 -0800 Hugh E Cruickshank wrote:
  Tried that but it failed. 
 
 Describe failed.

That happened yesterday and I can not recall specifically what it said.
I am currently in the process of backing up the hard drive before 
proceeding any further. I will see if I can get the error a little
later today.

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update interruption recovery

[Hugh E Cruickshank]

From: Hugh E Cruickshank Sent: December 4, 2013 15:09
 From: Frank Cox Sent: December 4, 2013 15:04
  On Wed, 4 Dec 2013 14:55:03 -0800 Hugh E Cruickshank wrote:
   Tried that but it failed. 
  
  Describe failed.
 
 That happened yesterday and I can not recall specifically what it
 said. I am currently in the process of backing up the hard drive
 before proceeding any further. I will see if I can get the error a
 little later today.

Well I am unable to locate the error message as it does not appear to
be logged. In the interim I have done a lot more research and I now
suspect that I have two separate problems:

1. Since the yum update did not complete then it never had a chance
   to update the rpm database,

2. We probably have one or more packages that have been install but
   the predecessor has not be removed.

I have done the following:

a. Rebuilt the rpm database:

rm -f /var/lib/rpm/__db*
rpm --rebuilddb

b. I then retried the yum update this aborted report conflicts in
   systemtap packages.

c. I listed the installed systemtap packages:

   rpm -qa | grep systemtap | sort

   This revealed that there were two systemtap-devel packages
   installed and I removed the newer one.

d. I then retried yum update and this appeared to work fine until it
   got to:

   Cleanup  : 1:xorg-x11-drv-nouveau-1.0.1-3.el6.x86_64  286/513

At this point the system appears to be hung. I can not proceed any
further this evening as I am working on this from home and I do not
have physical access to the server to reboot it. In the morning I
will reboot the server and try again but this time I am going to do
a yum clean all to the rpm database rebuild.

Any thoughts or comments would be appreciated.

That's al for now.

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update --skip-broken failure

[ken]

Though I've used it countless times in the past, yum update 
--skip-broken doesn't work anymore... it doesn't skip over updates 
which have dependency problems.  Is this a known issue?  Is there a 
work-around for it?  Has anyone else experienced this?

tnx.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update --skip-broken failure

[Jim Perrin]

Keep in mind that --skip-broken lets you bypass a problem, but the problem
still exists. If you miss enough updates, you will get breakage.

If you have conflicting repositories enabled that cause --skip-broken to be
needed and you use it regularly, you're asking for problems.


On Mon, Nov 4, 2013 at 8:36 AM, ken geb...@mousecar.com wrote:

 Though I've used it countless times in the past, yum update
 --skip-broken doesn't work anymore... it doesn't skip over updates
 which have dependency problems.  Is this a known issue?  Is there a
 work-around for it?  Has anyone else experienced this?

 tnx.
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos




-- 
During times of universal deceit, telling the truth becomes a revolutionary
act.
George Orwell
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update --skip-broken failure

[m . roth]

ken wrote:
 Though I've used it countless times in the past, yum update
 --skip-broken doesn't work anymore... it doesn't skip over updates
which have dependency problems.  Is this a known issue?  Is there a
work-around for it?  Has anyone else experienced this?

One thing that provokes that, in my experience, is repos from other
repositories, where it's not a dependency on this, but that repo does have
it as a dependency.

   mark



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update after update from 6.3 to 6.4 - problems with epel repository.

[Rafał Radecki]

Hi All.

I've updated my system from 6.3 to 6.4. In my /etc/yum.repos.depel.repo I
have:
[epel]
name=Extra Packages for Enterprise Linux - $basearch
#baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch
mirrorlist=
http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6arch=$basearch
failovermethod=priority
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
#gpgkey=http://download.fedora.redhat.com/pub/epel/RPM-GPG-KEY-EPEL-5
exclude=mongodb*
enabled=1
gpgcheck=0

Yum variables are ok:
# python -c 'import yum, pprint; yb = yum.YumBase();
pprint.pprint(yb.conf.yumvar, width=1)'
Loaded plugins: fastestmirror
{'arch': 'ia32e',
 'basearch': 'x86_64',
 'releasever': '6',
 'uuid': 'd42ce92e-d28b-4637-8365-2cf02892ee58'}

But yum exits with error:
# yum --disablerepo='*' --enablerepo='epel' search iotop
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
Error: Cannot find a valid baseurl for repo: epel

I've tried to open
http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6arch=x86_64
but got

# Bad Request 2960
# {'repo': u'epel-6', 'IP': IP('195.8.99.234'), 'client_ip':
u'195.8.99.234', 'metalink': False, 'arch': u'x86_64'}

Am I doing something wrong? Any clues?
Best regards,
Rafal.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update after update from 6.3 to 6.4 - problems with epel repository.

[Will Public]

Have you tried a `yum clean all`

Also the base arch is your code base, x86_64 etc.

Try commenting out the mirrorlist= and hit the baseurl= directly.

baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch
#mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6arch=$basearch


If you change this you will have to do a `yum clean all`



 From: Rafał Radecki radecki.ra...@gmail.com
To: CentOS mailing list centos@centos.org 
Sent: Friday, August 23, 2013 4:52 AM
Subject: [CentOS] yum update after update from 6.3 to 6.4 - problems with   
epel repository.
 

Hi All.

I've updated my system from 6.3 to 6.4. In my /etc/yum.repos.depel.repo I
have:
[epel]
name=Extra Packages for Enterprise Linux - $basearch
#baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch
mirrorlist=
http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6arch=$basearch
failovermethod=priority
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
#gpgkey=http://download.fedora.redhat.com/pub/epel/RPM-GPG-KEY-EPEL-5
exclude=mongodb*
enabled=1
gpgcheck=0

Yum variables are ok:
# python -c 'import yum, pprint; yb = yum.YumBase();
pprint.pprint(yb.conf.yumvar, width=1)'
Loaded plugins: fastestmirror
{'arch': 'ia32e',
'basearch': 'x86_64',
'releasever': '6',
'uuid': 'd42ce92e-d28b-4637-8365-2cf02892ee58'}

But yum exits with error:
# yum --disablerepo='*' --enablerepo='epel' search iotop
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
Error: Cannot find a valid baseurl for repo: epel

I've tried to open
http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6arch=x86_64
but got

# Bad Request 2960
# {'repo': u'epel-6', 'IP': IP('195.8.99.234'), 'client_ip':
u'195.8.99.234', 'metalink': False, 'arch': u'x86_64'}

Am I doing something wrong? Any clues?
Best regards,
Rafal.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update gone wild? - new base?

[Robert Moskowitz]

I am being hit on a number of my systems with yum update reporting 270+ 
rpms to update, and MOST are coming from the base repo.  I checked a few 
out, and yes, they are of a higher release.

I don't recall ever seeing the base repo change; it is almost like it is 
picking up the the 6.4 base repo instead.

Anyone else seeing this.  I JUST did an install from my local repo copy 
of the 6.3 base and update using a netinstall kickstart, then yum tells 
me that there are 270+ updates...


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update gone wild? - new base?

[Stephen Harris]

On Sun, Mar 10, 2013 at 09:30:40PM -0400, Robert Moskowitz wrote:
 I don't recall ever seeing the base repo change; it is almost like it is 
 picking up the the 6.4 base repo instead.

That's exactly what it's doing.  The /6 base and update repository
always point to the latest version.  6.4 was released this week so
the /6 is now seeing lots of updates as a result.

This is not new.

-- 

rgds
Stephen
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update gone wild? - new base?

[Robert Moskowitz]

On 03/10/2013 09:59 PM, Reindl Harald wrote:

 Am 11.03.2013 02:30, schrieb Robert Moskowitz:
 I am being hit on a number of my systems with yum update reporting 270+
 rpms to update, and MOST are coming from the base repo.  I checked a few
 out, and yes, they are of a higher release.

 I don't recall ever seeing the base repo change; it is almost like it is
 picking up the the 6.4 base repo instead
 maybe you should read this list not only post
 and understand how CentOS works

 6.4 is out - so why do you imagine you stay on 6.3?

Just panicsville.   I am trying to pack up to fly to meetings tomorrow, 
and saw this big update.  It has been too long since I was serious with 
Centos, and forgot that dot releases are major changes to the life of 
your server.  No way to bite off small bits.

So I will download the full current repos to my server over the week 
way, then apply them after I get back.

Just a case of bad timing on my part, resulting in an unnecessary panic.

Sorry all.



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Yum update without internet connection

[Steve Campbell]

I usually use a Desktop option when installing a new machine. This 
gives me all I need for an X session and then I add other packages or 
grouplists on an as-needed basis.

I'm putting together a couple of machines that will not have network 
connectivity until all packages are installed. Is there a way to run yum 
to install packages/groups from the installation disk instead of from 
one of the normal yum repositories? If so, is there a ever a problem 
with packages on the second disk of the 2 disk installation DVDs?

Thanks,

steve campbell
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Yum update without internet connection - realization part

[Steve Campbell]

I'm thinking I found the answer in the Centos-Media repo.

sorry, I overlooked that originally.

steve campbell
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Yum update without internet connection

[Ali Corbin]

On Mon, Nov 19, 2012 at 6:05 AM, Steve Campbell campb...@cnpapers.comwrote:

 I usually use a Desktop option when installing a new machine. This
 gives me all I need for an X session and then I add other packages or
 grouplists on an as-needed basis.

 I'm putting together a couple of machines that will not have network
 connectivity until all packages are installed. Is there a way to run yum
 to install packages/groups from the installation disk instead of from
 one of the normal yum repositories? If so, is there a ever a problem
 with packages on the second disk of the 2 disk installation DVDs?

 Thanks,

 steve campbell


Look at:
 /etc/yum.repos.d/CentOS-Media.repo
and type what it says.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update error

[Michael Simpson]

Hi folks

bit of an odd one
over the last few days i have been getting

[Errno 14] HTTP Error 500: Internal Server error
Could not retrieve mirrorlist
http://mirrorlist.centos.org/?release=5arch=i386repo=updates error
was
[Errno 14] HTTP Error 500: Internal Server Error

(though not just with updates but any mirrorlist from CentOS-Base and
also fasttrack)

this happens when trying to do a yum update

when i try browsing to the mirrorlist address manually i get

Sorry, the requested URL
'http://backend/?ra=:::::::release=5arch=i386repo=os'
caused an error:

the x'd portion represents the boxes network address from my provider
independent ipv6 space which i recently moved to
I am dual-stacked

everything else is working and cached mirrors appear to work ok
using the baseurl instead also works but isn't something i want to do for long

any ideas?

mike
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] 'yum update' rollback or .. ?

[przemolicc]

Hello,

we have several physical servers (CentOS 5.*) with rather critical applications 
where (because of stability)
we don't do regularly 'yum update'. In virtualized environemnts (under Vmware)
we do a snapshot, then 'yum update', reboot and if something is wrong we 
rollback the snapshot.
On physical servers we cannot do that. I have read about rollback option of rpm 
but not sure if
this is reliable solution. What is your best practise regarding rollbacking 
'yum update' on
physical servers ?


Regards
Przemyslaw Bak (przemol)


















































___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 'yum update' rollback or .. ?

[Theo Band]

On 06/22/2012 09:42 AM, przemol...@poczta.fm wrote:
 Hello,

 we have several physical servers (CentOS 5.*) with rather critical 
 applications where (because of stability)
 we don't do regularly 'yum update'. In virtualized environemnts (under Vmware)
 we do a snapshot, then 'yum update', reboot and if something is wrong we 
 rollback the snapshot.
 On physical servers we cannot do that. I have read about rollback option of 
 rpm but not sure if
 this is reliable solution. What is your best practise regarding rollbacking 
 'yum update' on
 physical servers ?

One solution would be to use lvm snapshots. Create a snapshot of the
root volume (lvcreate -s VolGroup00/LogVol00 -n rootsnapshot -L 10G), do
an update and see if it works. If not, boot into rescue mode and copy
the content from the snapshot back to the original.
Make sure the snapshot gets the same size as the original volume. This
is important if you want to copy back all the data.

Theo
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 'yum update' rollback or .. ?

[Nikolaos Milas]

On 22/6/2012 2:06 μμ, Theo Band wrote:

 What is your best practise regarding rollbacking 'yum update' on
 physical servers ?


Assuming that you have problems due to a particular newly-installed 
package, you can downgrade:

rpm -Uvh --oldpackage package-2.4.0-1.el5.x86_64.rpm

or:

yum downgrade package (if it is in the repo)

Since problems are usually introduced by a particular package (and not 
by all), this might be enough in most cases.

Note, however, that dependencies are not resolved automatically with the 
above commands, so they must be handled manually.

Another, more complete solution, of course, would be to have a full 
system backup (regardless whether the system is physical or virtual) and 
in case things go wrong, restore from backup (always a bit risky, I know 
- it makes you feel uneasy). We use mondorescue without problems (see: 
http://www.mondorescue.org/). I have been able to even use the backup to 
restore a KVM guest (using LVM) under VMware (you may see 
http://mondorescue-mailing-list.679749.n3.nabble.com/Mondo-devel-Restore-from-within-a-new-host-without-boot-td2251272.html).

Or - if feasible - you can attempt to virtualize your physical server, 
either using mondorescue or VMware converter (or other commercial tools) 
and be ready to use the virtual machine instead.

I am interested on other solutions too, so your thread is interesting!

Nick
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 'yum update' rollback or .. ?

[Theo Band]

On 06/22/2012 01:58 PM, Nikolaos Milas wrote:
 I am interested on other solutions too, so your thread is interesting!
dump

Assuming some form of ext[n] filesystem is being used. It has the
advantage that is also works with incremental backups. You can dump the
root file system and perhaps also the /boot filesystem.
Instead of the root filesystem, I dump a snaphost that is created each
evening. The snapshot has a frozen filesystem. So databases (mysql)
should just be consistent. If you want to be 100% sure, stop the
database, make a snapshot and start the database again. This is done
within one second, so hardly any impact on the live server.
Disadvantage of this method is that you still need the have a partition
table if you need to fully restore. And LVM and boot sector need to be
recreated. In case of disaster recovery you need this documented
properly (try it out at least once).
Advantage is that you can have daily system backups automatically created.

Theo
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update stuck...

[Mike Burger]

 On 10/02/12 10:50, John Doe wrote:
 Hi,

 Running Transaction
Updating   : selinux-policy
 1/6
Updating   : kmod-r8168
 2/6
 Working. This may take some time ...


 An hour later, still working...


 Wow. These kmods can take quite some time to update/install in yum,
 hence the informational message, but I've not yet seen one take an hour!

 How many kernels do you have installed as time is proportional to the
 number of kernels the module has to install against. Is it a
 particularly slow/old system, maybe short on memory?

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos


I don't recall, now, if I've replied to this thread or not, but...

I ran into a similar issue a few weeks ago...it turned out that I was
having an issue with my /tmp filesystem (at least)...I couldn't even
perform an orderly shutdown -r.

I wound up hard booting, during which /tmp was fsck'd, clearing a fair
number of orphaned inodes, and my yum update ran just fine after that.

Just a thought.

-- 
Mike Burger
http://www.bubbanfriends.org

Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org http://dogpound2.citadel.org
https://dogpound2.citadel.org

To be notified of updates to the web site, visit:

https://www.bubbanfriends.org/mailman/listinfo/site-update

or send a blank email to:

site-update-subscr...@bubbanfriends.org
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update stuck...

[Ned Slider]

On 10/02/12 10:50, John Doe wrote:
 Hi,

 Running Transaction
Updating   : selinux-policy   
 1/6
Updating   : kmod-r8168   
 2/6
 Working. This may take some time ...


 An hour later, still working...


Wow. These kmods can take quite some time to update/install in yum, 
hence the informational message, but I've not yet seen one take an hour!

How many kernels do you have installed as time is proportional to the 
number of kernels the module has to install against. Is it a 
particularly slow/old system, maybe short on memory?

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update stuck...

[John Doe]

Hi,

Running Transaction
  Updating   : selinux-policy   1/6 
  Updating   : kmod-r8168   2/6 
Working. This may take some time ...


An hour later, still working...

S+   10:51   0:08  |   \_ /usr/bin/python /usr/bin/yum update
S+   10:53   0:00  |   \_ /bin/sh /var/tmp/rpm-tmp.9003 2
S+   10:53   0:00  |   \_ /bin/bash /sbin/weak-modules 
--add-modules
S+   10:53   0:00  |   \_ /bin/bash --norc /sbin/mkinitrd 
--allow-missing -f /boot/initrd-2.6.18-274.17.1.el5.tmp 2.6.18-274.17.1.el5
S+   10:53   0:00  |   \_ /bin/bash --norc 
/sbin/mkinitrd --allow-missing -f /boot/initrd-2.6.18-274.17.1.el5.tmp 
2.6.18-274.17.1.el5
D+   10:53   0:00  |   \_ lvm.static lvs 
--ignorelockingfailure --noheadings -o vg_name /dev/md1


I tried an strace but nothing shows up.
Now, it is in: T+and strace showed me it was/is stuck on phantom usb devices 
and doing lvm stuff while I do not use lvm...


Should I wait or can I just ctrl-c, reset the usb_storage module to clean up 
and retry yum update?


Thx,

JD

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update stuck...

[John Doe]

From: John Doe jd...@yahoo.com

 Should I wait or can I just ctrl-c, reset the usb_storage module to clean up 
 and 
 retry yum update?

Never mind, it did end after a while...

JD
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Yum update woes (perl compression)

[Frank M. Ramaekers]

I have had very little problems with yum and it's updates, but this one
has me stumped (CentOS 5.4):

 

Loaded plugins: fastestmirror, priorities

Loading mirror speeds from cached hostfile

 * base: mirrors.loosefoot.com

 * extras: yum.singlehop.com

 * rpmforge: apt.sw.be

 * updates: mirrors.cmich.edu

Setting up Update Process

Resolving Dependencies

-- Running transaction check

-- Processing Dependency: perl(Compress::Raw::Bzip2) = 2.024 for
package: perl-IO-Compress

--- Package perl-Compress-Raw-Bzip2.i386 0:2.037-1.el5.rf set to be
updated

-- Processing Dependency: perl(Compress::Raw::Zlib) = 2.024 for
package: perl-IO-Compress

--- Package perl-Compress-Raw-Zlib.i386 0:2.037-1.el5.rf set to be
updated

-- Finished Dependency Resolution

perl-IO-Compress-2.024-1.el5.rf.noarch from installed has depsolving
problems

  -- Missing Dependency: perl(Compress::Raw::Zlib) = 2.024 is needed by
package perl-IO-Compress-2.024-1.el5.rf.noarch (installed)

perl-IO-Compress-2.024-1.el5.rf.noarch from installed has depsolving
problems

  -- Missing Dependency: perl(Compress::Raw::Bzip2) = 2.024 is needed
by package perl-IO-Compress-2.024-1.el5.rf.noarch (installed)

Error: Missing Dependency: perl(Compress::Raw::Bzip2) = 2.024 is needed
by package perl-IO-Compress-2.024-1.el5.rf.noarch (installed)

Error: Missing Dependency: perl(Compress::Raw::Zlib) = 2.024 is needed
by package perl-IO-Compress-2.024-1.el5.rf.noarch (installed)

 You could try using --skip-broken to work around the problem

 You could try running: package-cleanup --problems

package-cleanup --dupes

rpm -Va --nofiles --nodigest

 

Is this some sort of perl install/update requirement?

Frank M. Ramaekers Jr. | Systems Programmer | Information Technology |
American Income Life Insurance Company | 254-761-6649

 


_
This message contains information which is privileged and confidential and is 
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any 
review, disclosure,
copying, distribution, or use of the contents of this message is strictly 
prohibited. If you have
received this in error, please destroy it immediately and notify us at 
privacy...@ailife.com.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Yum update woes (perl compression)

[Luigi Rosa]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Frank M. Ramaekers said the following on 21/12/11 21:54:


 Error: Missing Dependency: perl(Compress::Raw::Zlib) = 2.024 is needed by
 package perl-IO-Compress-2.024-1.el5.rf.noarch (installed)
 
 You could try using --skip-broken to work around the problem
 
 You could try running: package-cleanup --problems
 
 package-cleanup --dupes
 
 rpm -Va --nofiles --nodigest
 
 
 
 Is this some sort of perl install/update requirement?


Old bug.


Uninstall perl-IO-Compress (and its dependencies, note down the dependencies
you uninstall)

Do the update

Reinstall perl-IO-Compress and anything you unininstalled.





Ciao,
luigi

- -- 
/
+--[Luigi Rosa]--
\

When you have reached the end of the road, then you can decide, whether
to go to the left or to the right, to fire or to water. If you make
those decisions before you have even set foot upon the road, it will
take you no where... except to a bad end.
--Galen, Racing the Night
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7ySEgACgkQ3kWu7Tfl6ZRocgCggithC+8C6YS06OW1ds84PRxV
q74AnAiPFmwZR5HGVOYocnnzA+m2VSe1
=6fNH
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Yum update woes (perl compression)

[Frank M. Ramaekers]

Thanks!   That did the trick.

 
Frank M. Ramaekers Jr.
 
 

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of Luigi Rosa
Sent: Wednesday, December 21, 2011 2:58 PM
To: CentOS mailing list
Subject: Re: [CentOS] Yum update woes (perl compression)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Frank M. Ramaekers said the following on 21/12/11 21:54:


 Error: Missing Dependency: perl(Compress::Raw::Zlib) = 2.024 is needed
by
 package perl-IO-Compress-2.024-1.el5.rf.noarch (installed)
 
 You could try using --skip-broken to work around the problem
 
 You could try running: package-cleanup --problems
 
 package-cleanup --dupes
 
 rpm -Va --nofiles --nodigest
 
 
 
 Is this some sort of perl install/update requirement?


Old bug.


Uninstall perl-IO-Compress (and its dependencies, note down the
dependencies
you uninstall)

Do the update

Reinstall perl-IO-Compress and anything you unininstalled.





Ciao,
luigi

- -- 
/
+--[Luigi Rosa]--
\

When you have reached the end of the road, then you can decide, whether
to go to the left or to the right, to fire or to water. If you make
those decisions before you have even set foot upon the road, it will
take you no where... except to a bad end.
--Galen, Racing the Night
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7ySEgACgkQ3kWu7Tfl6ZRocgCggithC+8C6YS06OW1ds84PRxV
q74AnAiPFmwZR5HGVOYocnnzA+m2VSe1
=6fNH
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

_
This message contains information which is privileged and confidential and is 
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any 
review, disclosure,
copying, distribution, or use of the contents of this message is strictly 
prohibited. If you have
received this in error, please destroy it immediately and notify us at 
privacy...@ailife.com.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] yum update fails on perl dependancy

[Ljubomir Ljubojevic]

I finally started yum upgrade for CentOS 6.0+CR x86_64.

yum reports that I have already installed

perl-5.10.1-119.el6_1.1,

but perl-CGI requests for

perl-5.10.1-119.el6 from ISO/base repo.

Can someone advise on the best course of action? Logical would be to 
downgrade perl to the one from ISO file.


-- 

Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update fails on perl dependancy

[Fabien Archambault]

On 12/20/2011 03:55 PM, Ljubomir Ljubojevic wrote:
 I finally started yum upgrade for CentOS 6.0+CR x86_64.

 yum reports that I have already installed

 perl-5.10.1-119.el6_1.1,

 but perl-CGI requests for

 perl-5.10.1-119.el6 from ISO/base repo.

 Can someone advise on the best course of action? Logical would be to
 downgrade perl to the one from ISO file.


Hi,

perhaps it is the same as: 
http://lists.centos.org/pipermail/centos/2011-December/120923.html
You just need a yum clean all  yum update

Fabien
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos