search for: cleandup

Author: mvgr Repository: /hg/zfs-crypto/gate Revision: eea51c04b2438fc6efd8793d2daa95f347e52ce8 Log message: 6298924 stale data on virtual channels should be cleandup when channel end-user points dies Files: update: usr/src/lib/libpcp/common/libpcp.c update: usr/src/lib/libpcp/common/libpcp.h

...proceed. HOwever it then hung for over 30 minutes. I stopped the update and tried again. It complained about problems with the update, so I tried yum --skip-broken -y update which then hung at a different place. After some Googling I tried yum-complete-transaction and package-cleanup --cleandupes both of which failed. I then using my "Microsoft" head I thought I'd try rebooting to see if that fixes it. This of course was a big mistake as my server now crashes on bootup. I have managed to get it back up and running by selecting a version of the kernel that is 3 version...

...te-transaction. When I ran yum-complete-transaction I got screen after screen of "x is a duplicate with x" where x consists of a huge list of packages. "package-cleanup --dupes" gives me a huge list of packages. I think that my next step here should be "package-cleanup --cleandupes" but when I do that it tells me that it will remove 800-plus mb of files. I suppose it's the the same list that I get with "package-cleanup --dupes". Do I want to do this or will that nuke the operating system? If not, what should I be doing? -- MELVILLE THEATRE ~ Real D 3...

...t;> conflicts with file from package zlib-1.2.7-17.el7.x86_64 > > You have to cleanup duplicate packages. package-cleanup from yum-utils > will do this job. > > Basically: > > package-cleanup --dupes > > will list the duplicate packages > > package-cleanup --cleandupes > > will remove the dupes. If I remember correctly, you have to add > --removenewestdupes to the second command. > > Best regards > Ulf > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman...

Hello All, I have this Centos7 machine that"s dualbooted with Win7. It's Centos7 with Mate desktop. The upgrade to Centos7.1 was interrupted. I ssh-d into the machine and finished it manualy, by issuing the command package-cleanup --cleandupes and yum update Now I' missing some packages, after some re?nstalling, I can boot again. However, I can not log in. EM:apr 02 13:58:25 jvanbaekel lightdm[1596]: ** (process:2903): WARNING **: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org....

Hello All, the update to Centos6.6 got interrupted on a laptop. I then did this: package-cleanup --cleandupes yum-complete-transaction and remove and reinstall the latest kernel. I now get an error message when booting: /dev/mapper/vg_jvermeulen-lv_home does not exist. I can boot into single user mode and run all commands. in fdisk -l .....lv_home is not listed. How can I re-add this? I do have a bac...

...complete. Finishing the most > Any idea to go back to a normal situation before a full re-install ? restoring the old state before the broken 'yum update' can be done by package-cleanup. package-cleanup --dupes will give you a long list of duplicate packages. package-cleanup --cleandupes --removenewestdupes will try to remove the duplicate rpms from the update. after that you should run 'package-cleanup --dupes' and clean the remaining dupes manually. if this is done, you can try to run the 'yum update' again. HTH and best regards Ulf ___________________...

I've launch a "yum update" while I was going to lunch. 1 hour later the system was completely freezed (no mouse, no keyboard, screen black, no network). I try a hard reboot => kernel panic on the new kernel I boot on the old kernel => boot hangs with gnome-shell failure. SSH was OK so I remove the new kernel and re-install gnome shell. Reboot is ok but now the computer

When I attempted to update a remote server via SSH last night the UPS on my local workstations failed, causing the SSH session to get dropped in the middle of the upgrade process. This morning I am not able to complete the update. When it failed when I tried to run it again thins morning I did the suggested things like "dnf clean all" and "rpm -rebuilddb", and I still get

...that close to just re-installing. > > For glibc problem, can you do > > yum erase glibc-2.17-222.el7.i686 > > there shouldn't be any serious dependencies on the .i686 version. If > there are, just make a note and reinstall them later. > > "package-cleanup --cleandupes" helped sort out some of the issues and > with the remaining few it was a case of manually removing the specific > versions and reinstalling what dependencies there were. > > Once most of the issues were done, I then did a 'yum distrosync" (or > whatever it's call...

...you can debug what failed there later by taking a note of the rpm that's being updated, and looking at the script later. > 2) How do I go about fixing the problems listed above? Don't kill yum in the middle of a run if you can possibly avoid it. I always favour "package-cleanup --cleandupes --removenewestdupes" But right now, the problem is you're part way between updated and not. You can be more brutal than package-cleanup or yum are willing to be. You can fix this with yum shell, telling it what you're going to remove and what you're going to add to put it back...

...ns to complete. Finishing the most > Any idea to go back to a normal situation before a full re-install ? restoring the old state before the broken 'yum update' can be done by package-cleanup. package-cleanup --dupes will give you a long list of duplicate packages. package-cleanup --cleandupes --removenewestdupes will try to remove the duplicate rpms from the update. after that you should run 'package-cleanup --dupes' and clean the remaining dupes manually. if this is done, you can try to run the 'yum update' again. HTH and best regards Ulf

...out 12 hours in total to sort out - I was that close to just re-installing. For glibc problem, can you do yum erase glibc-2.17-222.el7.i686 there shouldn't be any serious dependencies on the .i686 version. If there are, just make a note and reinstall them later. "package-cleanup --cleandupes" helped sort out some of the issues and with the remaining few it was a case of manually removing the specific versions and reinstalling what dependencies there were. Once most of the issues were done, I then did a 'yum distrosync" (or whatever it's called) to make sure package...

...4/libz.so.1.2.7 from install of zlib-1.2.7-18.el7.x86_64 > conflicts with file from package zlib-1.2.7-17.el7.x86_64 You have to cleanup duplicate packages. package-cleanup from yum-utils will do this job. Basically: package-cleanup --dupes will list the duplicate packages package-cleanup --cleandupes will remove the dupes. If I remember correctly, you have to add --removenewestdupes to the second command. Best regards Ulf

On 22.04.19 18:12, Emmett Culley via CentOS wrote: > On 4/21/19 10:15 AM, Ulf Volmer wrote: >> package-cleanup --dupes >> >> will list the duplicate packages >> >> package-cleanup --cleandupes >> >> will remove the dupes. If I remember correctly, you have to add >> --removenewestdupes to the second command. > That didn't seem to work. It did remove duplicates, however, I get the > same error when running dnf update. Should I try it without the > --remov...

On 4/22/19 10:45 AM, Ulf Volmer wrote: > On 22.04.19 18:12, Emmett Culley via CentOS wrote: >> On 4/21/19 10:15 AM, Ulf Volmer wrote: > >>> package-cleanup --dupes >>> >>> will list the duplicate packages >>> >>> package-cleanup --cleandupes >>> >>> will remove the dupes. If I remember correctly, you have to add >>> --removenewestdupes to the second command. > >> That didn't seem to work. It did remove duplicates, however, I get the >> same error when running dnf update. Should I try it...

Hi! I have a small problem with some packages : i was doing an update over ssh and my connection was interrupted .. now i have a lots of duplicates and if i try to remove them, yum tries to uninstall all system (447 packages 1.4 gb)!! Any idea how can i clean this mess? would be pretty bad if the machine needs to be re-installed only because the connection went bad during the process... Thanks

I was in the middle of a yum update on physical box over teh weekend and power died. Ssytem came pack up. But now when I run yum-complete-transaction I get all kinds of errors (these are just the last 4, there are many) systemtap-runtime-4.0-10.el7_7.x86_64 has installed conflicts systemtap-devel < ('0', '4.0', '10.el7_7'): systemtap-devel-4.0-9.el7.x86_64

...6_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: <snip> 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 ha...

I was doing an update to 7.4 and somewhere in middle the machine died. If I drop back to a previous kernel the machine is alive. So how do I say "forget the previous yum update" and start all over and do it again. Booting into the new kernel I get a kernel fault. So going back one level on teh boot screen solves that - I just need to start the update again. How is that? Thanks, Jerry