Yum update corrupted something badly - can only get access through SSH terminal or Webmin
Hey there -
This morning I ran the yum updater through Webmin as I do every month or so - after about two hours I realized that I still had the same updating screen going - and no response. Seemed strange.
Simple attempts to kill it didn't work so I sent a command to reboot the system - that seemed to work, till I turned on the monitor directly connected to the server -
I saw this error go by - and then only a spinning cursor - never get to a login screen. (I power cycled again and saw it go by again - and recognized it when I tried again at Webmin and through a terminal connection).
Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
I deleted the yum cash and no improvement. I tried the yum clean and no imporvement [root@trailrunner yum]# yum clean all Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n [root@trailrunner yum]#
Not at all sure what happened or why, or where I even start trying to straighten this mess out.
How do I blow away the apparent yum junk in the hope of getting a local login capability back?
How or what should I do to reset yum - seems reinstalling the latest version is probably the route. What is the version that CentOS uses? Should I go the RPM route or try something more specific?
Totally unexpected problem and leaving me feeling very uncertain about things.
On Wed, Apr 22, 2009 at 11:47 AM, Dan Roberts dan@jlazyh.com wrote:
This morning I ran the yum updater through Webmin as I do every month or so - after about two hours I realized that I still had the same updating screen going - and no response. Seemed strange.
No idea why you are getting this problem or using Webmin to update your box, but I suggest you rethink the idea of only doing updates "every month or so". You could have the box exposed to an exploit for a long time, with that schedule. Hopefully someone else on the list will have a solution for your immediate problem. GL
On Wed, Apr 22, 2009 at 12:47 PM, Dan Roberts dan@jlazyh.com wrote:
Hey there -
This morning I ran the yum updater through Webmin as I do every month or so - after about two hours I realized that I still had the same updating screen going - and no response. Seemed strange.
So you probably missed the notes and announcements about the 5.3 release, as well as the release notes about upgrade hiccups. There are also quite a few updates here, so the update will take some time to run.
Simple attempts to kill it didn't work so I sent a command to reboot the system - that seemed to work, till I turned on the monitor directly connected to the server -
Updating via webmin may not be the best approach, as some things may update which could impact webmin.
I saw this error go by - and then only a spinning cursor - never get to a login screen. (I power cycled again and saw it go by again - and recognized it when I tried again at Webmin and through a terminal connection).
Power cycling a system should be considered a last-resort option, not a method for troubleshooting.
Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
I deleted the yum cash and no improvement. I tried the yum clean and no imporvement [root@trailrunner yum]# yum clean all Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n [root@trailrunner yum]#
Not at all sure what happened or why, or where I even start trying to straighten this mess out.
For systems which experienced issues moving from 5.2 to 5.3, a 'yum clean all' resolved the majority of issues.
How do I blow away the apparent yum junk in the hope of getting a local login capability back?
Yum doesn't have anything to do with logging into the system at all. I'm not sure why you think this would help. However as previously stated a 'yum clean all' should 'blow away' the yum bits. Further nuking yum transactions is not to be done lightly, and requires the yum-utils package to be installed. We'll go over that command later if we have to.
How or what should I do to reset yum - seems reinstalling the latest version is probably the route. What is the version that CentOS uses? Should I go the RPM route or try something more specific?
Totally unexpected problem and leaving me feeling very uncertain about things.
Please subscribe to the Centos-Announce list. You got blind-sided by a very public release because you only update every month or so, and don't generally follow updates in a manner most admins would consider 'good practice'. I believe that had you been aware of the 5.3 release, you would have been a bit more careful in things.
thanks for the details - As the server lives in a closet without a monitor on it or even easy access I opted for Webmin so as to have the ability to get in and work with it.
I will resubscribe and get back into a better habit - I had been checking every day a year ago, and then life got busy.
Things were fine, and I had no trouble the in January when i put a monitor on it for some other reasons - but after the hang today it now is stuck.
As my cut and past below indicates, the "yum clean all" results in a consistent set of errors - any yum command seems to return the same errors.
Regardless of how or why they were caused, the issue now is how to clear them out so that I can actually get yum to work -
[root@trailrunner yum]# yum clean all Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n [root@trailrunner yum]#
On Apr 22, 2009, at 11:15 AM, Jim Perrin wrote:
On Wed, Apr 22, 2009 at 12:47 PM, Dan Roberts dan@jlazyh.com wrote:
Hey there -
This morning I ran the yum updater through Webmin as I do every month or so - after about two hours I realized that I still had the same updating screen going - and no response. Seemed strange.
So you probably missed the notes and announcements about the 5.3 release, as well as the release notes about upgrade hiccups. There are also quite a few updates here, so the update will take some time to run.
Simple attempts to kill it didn't work so I sent a command to reboot the system - that seemed to work, till I turned on the monitor directly connected to the server -
Updating via webmin may not be the best approach, as some things may update which could impact webmin.
I saw this error go by - and then only a spinning cursor - never get to a login screen. (I power cycled again and saw it go by again - and recognized it when I tried again at Webmin and through a terminal connection).
Power cycling a system should be considered a last-resort option, not a method for troubleshooting.
Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
I deleted the yum cash and no improvement. I tried the yum clean and no imporvement [root@trailrunner yum]# yum clean all Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n [root@trailrunner yum]#
Not at all sure what happened or why, or where I even start trying to straighten this mess out.
For systems which experienced issues moving from 5.2 to 5.3, a 'yum clean all' resolved the majority of issues.
How do I blow away the apparent yum junk in the hope of getting a local login capability back?
Yum doesn't have anything to do with logging into the system at all. I'm not sure why you think this would help. However as previously stated a 'yum clean all' should 'blow away' the yum bits. Further nuking yum transactions is not to be done lightly, and requires the yum-utils package to be installed. We'll go over that command later if we have to.
How or what should I do to reset yum - seems reinstalling the latest version is probably the route. What is the version that CentOS uses? Should I go the RPM route or try something more specific?
Totally unexpected problem and leaving me feeling very uncertain about things.
Please subscribe to the Centos-Announce list. You got blind-sided by a very public release because you only update every month or so, and don't generally follow updates in a manner most admins would consider 'good practice'. I believe that had you been aware of the 5.3 release, you would have been a bit more careful in things.
-- 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
Dan Roberts wrote:
thanks for the details - As the server lives in a closet without a monitor on it or even easy access I opted for Webmin so as to have the ability to get in and work with it.
I will resubscribe and get back into a better habit - I had been checking every day a year ago, and then life got busy.
Things were fine, and I had no trouble the in January when i put a monitor on it for some other reasons - but after the hang today it now is stuck.
As my cut and past below indicates, the "yum clean all" results in a consistent set of errors - any yum command seems to return the same errors.
Regardless of how or why they were caused, the issue now is how to clear them out so that I can actually get yum to work -
[root@trailrunner yum]# yum clean all Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n [root@trailrunner yum]#
there was an issue with the update to 5.3 in that the glibc libraries needed to be updated prior to the remainder otherwise rpm had issues - this is probably what yum is choking on try #>rpm -uv glibc* after that try yum clean all and then see what happens HTH
On Apr 22, 2009, at 11:15 AM, Jim Perrin wrote:
<snip>
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hmmm -
# rpm -uv glibc* -uv: unknown option
Ok - so I go with -Uv instead # rpm -Uv glibc* error: File not found by glob: glibc*
But this is strange because I know that glib-2.0 is there - fairly easy to confirm - is something missing? # locate glibc /usr/lib/glib-2.0/include/glibconfig.h /usr/lib/valgrind/glibc-2.2.supp /usr/lib/valgrind/glibc-2.3.supp /usr/lib/valgrind/glibc-2.4.supp /usr/sbin/glibc_post_upgrade.i686 /usr/share/doc/glibc-2.5 /usr/share/doc/glibc-common-2.5 /usr/share/doc/glibc-2.5/BUGS /usr/share/doc/glibc-2.5/CONFORMANCE /usr/share/doc/glibc-2.5/COPYING /usr/share/doc/glibc-2.5/COPYING.LIB /usr/share/doc/glibc-2.5/FAQ /usr/share/doc/glibc-2.5/INSTALL /usr/share/doc/glibc-2.5/LICENSES /usr/share/doc/glibc-2.5/NEWS /usr/share/doc/glibc-2.5/NOTES /usr/share/doc/glibc-2.5/PROJECTS /usr/share/doc/glibc-2.5/README /usr/share/doc/glibc-2.5/README.hesiod /usr/share/doc/glibc-2.5/README.libm /usr/share/doc/glibc-common-2.5/ChangeLog.15.bz2 /usr/share/doc/glibc-common-2.5/ChangeLog.16.bz2 /usr/share/doc/glibc-common-2.5/ChangeLog.bz2 /usr/share/doc/glibc-common-2.5/README.timezone /usr/share/doc/glibc-common-2.5/README.ufc-crypt /usr/share/doc/glibc-common-2.5/gai.conf
On Apr 22, 2009, at 12:08 PM, Rob Kampen wrote:
Dan Roberts wrote:
thanks for the details - As the server lives in a closet without a monitor on it or even easy access I opted for Webmin so as to have the ability to get in and work with it.
I will resubscribe and get back into a better habit - I had been checking every day a year ago, and then life got busy.
Things were fine, and I had no trouble the in January when i put a monitor on it for some other reasons - but after the hang today it now is stuck.
As my cut and past below indicates, the "yum clean all" results in a consistent set of errors - any yum command seems to return the same errors.
Regardless of how or why they were caused, the issue now is how to clear them out so that I can actually get yum to work -
[root@trailrunner yum]# yum clean all Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n [root@trailrunner yum]#
there was an issue with the update to 5.3 in that the glibc libraries needed to be updated prior to the remainder otherwise rpm had issues - this is probably what yum is choking on try #>rpm -uv glibc* after that try yum clean all and then see what happens HTH
On Apr 22, 2009, at 11:15 AM, Jim Perrin wrote:
<snip> _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
<rkampen.vcf>_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
on 4-22-2009 11:18 AM Dan Roberts spake the following:
Hmmm -
# rpm -uv glibc* -uv: unknown option
Ok - so I go with -Uv instead # rpm -Uv glibc* error: File not found by glob: glibc*
But this is strange because I know that glib-2.0 is there - fairly easy to confirm - is something missing?
You might have to manually download glibc and yum rpm's and install them since you cleaned the cache.
Rob Kampen wrote:
there was an issue with the update to 5.3 in that the glibc libraries needed to be updated prior to the remainder otherwise rpm had issues - this is probably what yum is choking on
No. Completely different beast.
Ralph
Dan Roberts wrote:
thanks for the details - As the server lives in a closet without a monitor on it or even easy access I opted for Webmin so as to have the ability to get in and work with it.
I think most people on this list would recommend using ssh + screen for remote administration, not webmin.
Even if your connection is lost you can log into the remote screen session with screen -r from the local console and see what went wrong.
2009/4/22 Dan Roberts dan@jlazyh.com:
thanks for the details - As the server lives in a closet without a monitor on it or even easy access I opted for Webmin so as to have the ability to get in and work with it.
I will resubscribe and get back into a better habit - I had been checking every day a year ago, and then life got busy.
Things were fine, and I had no trouble the in January when i put a monitor on it for some other reasons - but after the hang today it now is stuck.
As my cut and past below indicates, the "yum clean all" results in a consistent set of errors - any yum command seems to return the same errors.
Regardless of how or why they were caused, the issue now is how to clear them out so that I can actually get yum to work -
[root@trailrunner yum]# yum clean all Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n [root@trailrunner yum]#
This looks like a problem with python to me. Try removing the python RPM and reinstalling, perhaps?
Given the mess that I have already got, would you care to provide a clear list of the steps to do that - I certainly don't want to blow a hole in something else by mistake.
On Apr 22, 2009, at 12:37 PM, Michael Holmes wrote:
2009/4/22 Dan Roberts dan@jlazyh.com:
thanks for the details - As the server lives in a closet without a monitor on it or even easy access I opted for Webmin so as to have the ability to get in and work with it.
I will resubscribe and get back into a better habit - I had been checking every day a year ago, and then life got busy.
Things were fine, and I had no trouble the in January when i put a monitor on it for some other reasons - but after the hang today it now is stuck.
As my cut and past below indicates, the "yum clean all" results in a consistent set of errors - any yum command seems to return the same errors.
Regardless of how or why they were caused, the issue now is how to clear them out so that I can actually get yum to work -
[root@trailrunner yum]# yum clean all Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n [root@trailrunner yum]#
This looks like a problem with python to me. Try removing the python RPM and reinstalling, perhaps? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
2009/4/22 Dan Roberts dan@jlazyh.com:
Given the mess that I have already got, would you care to provide a clear list of the steps to do that - I certainly don't want to blow a hole in something else by mistake.
Can you tell me what version Python is? A simple "python -v" (without quotes of course) should work.
On Wed, Apr 22, 2009 at 12:48 PM, Dan Roberts dan@jlazyh.com wrote:
thanks for the details - As the server lives in a closet without a monitor on it or even easy access I opted for Webmin so as to have the ability to get in and work with it.
There are other ways you can get into a headless server or a server that is remote to your location. SSH for example.
I will resubscribe and get back into a better habit - I had been checking every day a year ago, and then life got busy.
If you subscribe to this mailing list and read the messages, you will learn a lot. I have.
As someone pointed out, there was an issue with glibc. From the CentOS 5.3 Release Notes: http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.3
4. Known Issues
* When updating from 5.2 to 5.3 you can run into a problem with rpm: "rpmdb: unable to lock mutex: Invalid argument". To avoid this please update glibc before updating the rest of the installation:
yum clean all && yum update glibc* && yum update
After you solve the issue(s) you have with the server at this moment, I suggest that you do some reading on the CentOS Wiki, about how to begin securing your server. http://wiki.centos.org/
Thanks -
I will start reading again and striving to improve things. I have previously taken steps to secure the server, and was under the impression that it was so.
that aside - I can't run the command you suggest because any yum operation results in the same error message.
# yum clean all && yum update glibc* && yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
On Apr 22, 2009, at 12:41 PM, Lanny Marcus wrote:
On Wed, Apr 22, 2009 at 12:48 PM, Dan Roberts dan@jlazyh.com wrote:
thanks for the details - As the server lives in a closet without a monitor on it or even easy access I opted for Webmin so as to have the ability to get in and work with it.
There are other ways you can get into a headless server or a server that is remote to your location. SSH for example.
I will resubscribe and get back into a better habit - I had been checking every day a year ago, and then life got busy.
If you subscribe to this mailing list and read the messages, you will learn a lot. I have.
As someone pointed out, there was an issue with glibc. From the CentOS 5.3 Release Notes: http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.3
Known Issues
- When updating from 5.2 to 5.3 you can run into a problem with
rpm: "rpmdb: unable to lock mutex: Invalid argument". To avoid this please update glibc before updating the rest of the installation:
yum clean all && yum update glibc\* && yum updateAfter you solve the issue(s) you have with the server at this moment, I suggest that you do some reading on the CentOS Wiki, about how to begin securing your server. http://wiki.centos.org/ _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Wed, Apr 22, 2009 at 1:46 PM, Dan Roberts dan@jlazyh.com wrote:
I will start reading again and striving to improve things. I have previously taken steps to secure the server, and was under the impression that it was so.
I hope so. If not, you have a tiger by the tail.
that aside - I can't run the command you suggest because any yum operation results in the same error message.
# yum clean all && yum update glibc* && yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s2-sysconfig-i18n.html
Have you tried yum install i18n ?
2009/4/22 Lanny Marcus lmmailinglists@gmail.com:
On Wed, Apr 22, 2009 at 1:46 PM, Dan Roberts dan@jlazyh.com wrote:
I will start reading again and striving to improve things. I have previously taken steps to secure the server, and was under the impression that it was so.
I hope so. If not, you have a tiger by the tail.
that aside - I can't run the command you suggest because any yum operation results in the same error message.
# yum clean all && yum update glibc* && yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s2-sysconfig-i18n.html
Have you tried yum install i18n ? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
That wouldn't work because yum is broken?
Just my two cents.
On 4/22/09, Michael Holmes holmesmich@googlemail.com wrote:
2009/4/22 Lanny Marcus lmmailinglists@gmail.com:
On Wed, Apr 22, 2009 at 1:46 PM, Dan Roberts dan@jlazyh.com wrote:
I will start reading again and striving to improve things. I have previously taken steps to secure the server, and was under the impression that it was so.
I hope so. If not, you have a tiger by the tail.
that aside - I can't run the command you suggest because any yum operation results in the same error message.
<snip>
File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s2-sysconfig-i18n.html
Have you tried yum install i18n ?
<snip>
That wouldn't work because yum is broken? Just my two cents.
Michael: 2 cents well spent. You are correct. Looks like he needs to install or update i18n, but not with yum..... Lanny
Michael Holmes wrote:
On Wed, Apr 22, 2009 at 1:46 PM, Dan Roberts dan@jlazyh.com wrote:
I will start reading again and striving to improve things. I have previously taken steps to secure the server, and was under the impression that it was so.
I hope so. If not, you have a tiger by the tail.
that aside - I can't run the command you suggest because any yum operation results in the same error message.
# yum clean all && yum update glibc* && yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s2-sysconfig-i18n.html
Have you tried yum install i18n ? _______________________________________________
That wouldn't work because yum is broken?
Just my two cents.
I have always wondered about the sanity of using python for system administration tools, but this should be a yum file in /usr/share/yum-cli/.
On 4/22/09, Les Mikesell lesmikesell@gmail.com wrote:
On Wed, Apr 22, 2009 at 1:46 PM, Dan Roberts dan@jlazyh.com wrote:
<snip>
that aside - I can't run the command you suggest because any yum operation results in the same error message.
# yum clean all && yum update glibc* && yum update Traceback (most recent call last):
<snip>
File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s2-sysconfig-i18n.html
Have you tried yum install i18n ?
That wouldn't work because yum is broken?
Just my two cents.
I have always wondered about the sanity of using python for system administration tools, but this should be a yum file in /usr/share/yum-cli/.
Les: Is i18n installed by Webmin during the Webmin installation? Possibly he needs to add another yum repository? Lanny
On 4/22/09, Les Mikesell lesmikesell@gmail.com wrote:
Michael Holmes wrote:
<snip>
I have always wondered about the sanity of using python for system administration tools, but this should be a yum file in /usr/share/yum-cli/.
I found i18n on my CentOS 5.3 Desktop. It's in /etc/sysconfig/
Yes - I have it in that location too - but clearly it is not getting found by yum
On Apr 22, 2009, at 1:23 PM, Lanny Marcus wrote:
On 4/22/09, Les Mikesell lesmikesell@gmail.com wrote:
Michael Holmes wrote:
<snip> > I have always wondered about the sanity of using python for system > administration tools, but this should be a yum file in /usr/share/ > yum-cli/.
I found i18n on my CentOS 5.3 Desktop. It's in /etc/sysconfig/ _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Wed, Apr 22, 2009 at 15:23, Lanny Marcus lmmailinglists@gmail.com wrote:
I have always wondered about the sanity of using python for system administration tools, but this should be a yum file in /usr/share/yum-cli/.
I found i18n on my CentOS 5.3 Desktop. It's in /etc/sysconfig/
The /etc/sysconfig/i18n file has nothing to do with Python. Just because it's named i18n does not mean it's the file you are looking for. It definitely is not.
HTH, Filipe
Lanny Marcus wrote:
On 4/22/09, Les Mikesell lesmikesell@gmail.com wrote:
Michael Holmes wrote:
<snip> > I have always wondered about the sanity of using python for system > administration tools, but this should be a yum file in /usr/share/yum-cli/.
I found i18n on my CentOS 5.3 Desktop. It's in /etc/sysconfig/
ARGH.
Ralph
Dan Roberts wrote:
that aside - I can't run the command you suggest because any yum operation results in the same error message.
# yum clean all && yum update glibc* && yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
I think this is your immediate problem. Do you have a /usr/share/yum-cli/i18n.py file?
My current version of python appears to be python 2.4.3
python - v (without quotes returned a slue of lines, but near the bottom it said Python 2.4.3 (#1, Jan 21 2009, 01:10:13) [GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
As to the question below - I have that directory, but not that file.
On Apr 22, 2009, at 1:04 PM, Les Mikesell wrote:
Dan Roberts wrote:
that aside - I can't run the command you suggest because any yum operation results in the same error message.
# yum clean all && yum update glibc* && yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
I think this is your immediate problem. Do you have a /usr/share/yum-cli/i18n.py file?
-- Les Mikesell lesmikesell@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Dan Roberts wrote:
My current version of python appears to be python 2.4.3
python - v (without quotes returned a slue of lines, but near the bottom it said Python 2.4.3 (#1, Jan 21 2009, 01:10:13) [GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
As to the question below - I have that directory, but not that file.
Does 'rpm -Vv yum' say it was installed by is now missing?
Hi,
On Wed, Apr 22, 2009 at 15:17, Dan Roberts dan@jlazyh.com wrote:
As to the question below - I have that directory, but not that file.
yum-3.2.8-9.el5.centos.2.1 (from CentOS 5.2) has /usr/share/yum-cli/i18n.py
yum-3.2.19-18.el5.centos (from CentOS 5.3) no longer has that file.
Probably you broke your update in the middle so you got things in an inconsistent state.
Try this command to see which yum you have installed: # rpm -q yum
And then you can verify if the package's integrity is compromised with: # rpm -V yum
I believe to solve your problem you will have to reinstall the RPM for "yum" manually.
To do that, download this RPM: http://mirror.centos.org/centos/5/os/i386/CentOS/yum-3.2.19-18.el5.centos.no...
And then run: # rpm -Uvh --force yum-3.2.19-18.el5.centos.noarch.rpm
After that is done, your yum should start working again.
If it does not, report any issues you have, together with the output of "rpm -q yum" and "rpm -V yum" after reinstalling the package.
HTH, Filipe
Hi Filipe -
Clearly I have indeed got things broken - # rpm -q yum package yum is not installed
So I downloaded the rpm for a reinstall as you suggested - but clearly I have more to get and install -
I downloaded to my home directory and ran the rpm -Uvh from there
# rpm -Uvh --force yum-3.2.19-18.el5.centos.noarch.rpm error: Failed dependencies: rpm >= 0:4.4.2 is needed by yum-3.2.19-18.el5.centos.noarch rpm-python is needed by yum-3.2.19-18.el5.centos.noarch yum-fastestmirror is needed by yum-3.2.19-18.el5.centos.noarch
Either I am running this in the wrong location, or there is a lot of other stuff out of whack.
On Apr 22, 2009, at 1:29 PM, Filipe Brandenburger wrote:
Hi,
On Wed, Apr 22, 2009 at 15:17, Dan Roberts dan@jlazyh.com wrote:
As to the question below - I have that directory, but not that file.
yum-3.2.8-9.el5.centos.2.1 (from CentOS 5.2) has /usr/share/yum-cli/ i18n.py
yum-3.2.19-18.el5.centos (from CentOS 5.3) no longer has that file.
Probably you broke your update in the middle so you got things in an inconsistent state.
Try this command to see which yum you have installed: # rpm -q yum
And then you can verify if the package's integrity is compromised with: # rpm -V yum
I believe to solve your problem you will have to reinstall the RPM for "yum" manually.
To do that, download this RPM: http://mirror.centos.org/centos/5/os/i386/CentOS/yum-3.2.19-18.el5.centos.no...
And then run: # rpm -Uvh --force yum-3.2.19-18.el5.centos.noarch.rpm
After that is done, your yum should start working again.
If it does not, report any issues you have, together with the output of "rpm -q yum" and "rpm -V yum" after reinstalling the package.
HTH, Filipe _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi,
On Wed, Apr 22, 2009 at 15:40, Dan Roberts dan@jlazyh.com wrote:
# rpm -Uvh --force yum-3.2.19-18.el5.centos.noarch.rpm error: Failed dependencies: rpm >= 0:4.4.2 is needed by yum-3.2.19-18.el5.centos.noarch rpm-python is needed by yum-3.2.19-18.el5.centos.noarch yum-fastestmirror is needed by yum-3.2.19-18.el5.centos.noarch Either I am running this in the wrong location, or there is a lot of other stuff out of whack.
It looks like your system is closer to 5.2 than 5.3.
In that case, I suggest you try to install this RPM of yum instead: http://mirror.centos.org/centos/5.2/updates/i386/RPMS/yum-3.2.8-9.el5.centos...
If it still asks about dependencies, you will have to download them and install/upgrade them manually using RPM.
Look for them here: http://mirror.centos.org/centos/5.2/os/i386/CentOS/ And here: http://mirror.centos.org/centos/5.2/updates/i386/RPMS/
Once you get to install yum-3.2.8-9.el5.centos.2.1, yum should start working again.
When you got that done, you can try to use it to upgrade again, but this time I advise you to do it on a screen session from an SSH connection, and not through Webmin. And do not reboot the server in the middle of the upgrade, since that is probably what started your problems in this case.
HTH, Filipe
Filipe Brandenburger wrote:
Hi,
On Wed, Apr 22, 2009 at 15:40, Dan Roberts dan@jlazyh.com wrote:
# rpm -Uvh --force yum-3.2.19-18.el5.centos.noarch.rpm error: Failed dependencies: rpm >= 0:4.4.2 is needed by yum-3.2.19-18.el5.centos.noarch rpm-python is needed by yum-3.2.19-18.el5.centos.noarch yum-fastestmirror is needed by yum-3.2.19-18.el5.centos.noarch Either I am running this in the wrong location, or there is a lot of other stuff out of whack.
It looks like your system is closer to 5.2 than 5.3.
In that case, I suggest you try to install this RPM of yum instead: http://mirror.centos.org/centos/5.2/updates/i386/RPMS/yum-3.2.8-9.el5.centos...
If it still asks about dependencies, you will have to download them and install/upgrade them manually using RPM.
Look for them here: http://mirror.centos.org/centos/5.2/os/i386/CentOS/ And here: http://mirror.centos.org/centos/5.2/updates/i386/RPMS/
Once you get to install yum-3.2.8-9.el5.centos.2.1, yum should start working again.
When you got that done, you can try to use it to upgrade again, but this time I advise you to do it on a screen session from an SSH connection, and not through Webmin. And do not reboot the server in the middle of the upgrade, since that is probably what started your problems in this case.
Once yum is basically working you might be able to yum install yum-utils and yum-complete-transaction to pick up where you left off. I had to do this on one box where the update process kicked me off and died with a bunch of duplicate packages still in the rpm database.
On Wed, 2009-04-22 at 15:05 -0500, Les Mikesell wrote:
Once yum is basically working you might be able to yum install yum-utils and yum-complete-transaction to pick up where you left off. I had to do this on one box where the update process kicked me off and died with a bunch of duplicate packages still in the rpm database.
---- me too...punished for not using screen to update.
yum-complete-transaction actually required a leap of faith because there were hundreds of packages it wanted to remove ;-)
Craig
Craig White wrote:
On Wed, 2009-04-22 at 15:05 -0500, Les Mikesell wrote:
Once yum is basically working you might be able to yum install yum-utils and yum-complete-transaction to pick up where you left off. I had to do this on one box where the update process kicked me off and died with a bunch of duplicate packages still in the rpm database.
me too...punished for not using screen to update.
I sort-of expected yum to be smart enough to trap sighup's during transactions. And I think the connection broke because the process underneath died - so screen would probably have croaked too.
yum-complete-transaction actually required a leap of faith because there were hundreds of packages it wanted to remove ;-)
Same here... I did do a sanity check with rpm -q package for some of them to see that two versions were actually there (or rpm thought there were).
On Wed, 2009-04-22 at 15:37 -0500, Les Mikesell wrote:
Craig White wrote:
On Wed, 2009-04-22 at 15:05 -0500, Les Mikesell wrote:
Once yum is basically working you might be able to yum install yum-utils and yum-complete-transaction to pick up where you left off. I had to do this on one box where the update process kicked me off and died with a bunch of duplicate packages still in the rpm database.
me too...punished for not using screen to update.
I sort-of expected yum to be smart enough to trap sighup's during transactions. And I think the connection broke because the process underneath died - so screen would probably have croaked too.
yum-complete-transaction actually required a leap of faith because there were hundreds of packages it wanted to remove ;-)
Same here... I did do a sanity check with rpm -q package for some of them to see that two versions were actually there (or rpm thought there were).
---- well interesting...so it probably wouldn't have mattered if I had used screen. This only happened on one of the servers that I updated and it is possible that I didn't update glibc first...it was one of the last systems I updated so I may have been too cavalier about the process. The first few I carefully updated glibc first, then yum and then finally the rest.
And yes, when yum-complete-transaction is telling you it is removing like 500 packages, you do a double and triple take, start checking the packages it intends to remove to make certain that it will leave a new version but still, I wasn't going to check everything so I eventually had to make the leap.
While the updates don't always go perfectly, especially when one gets lackadaisical, the yum-tools seem to clean up behind you pretty well.
Craig
Ok - something truly bad appears to have happened. Yes, I will concede that cycling the system was a bad thing - but after two hours it should have returned from the update, still I was bad.
There are indeed updates that it wants - and I went back to the site to get them, but then things continue to show up as missing. # rpm -Uvh --force rpm-4.4.2-48.el5.i386.rpm error: Failed dependencies: librpm-4.4.so is needed by rpm-4.4.2-48.el5.i386 librpmbuild-4.4.so is needed by rpm-4.4.2-48.el5.i386 librpmdb-4.4.so is needed by rpm-4.4.2-48.el5.i386 librpmio-4.4.so is needed by rpm-4.4.2-48.el5.i386 popt = 1.10.2 is needed by rpm-4.4.2-48.el5.i386
Clearly I have a pretty big hole here. Yes I have been spoiled by yum and rpm. Years ago I use to command line build, make and install everything - but dropped that habit in favor of the ease of yum.
Are there are set of core files that seem reasonable to pull and install -
It is beginning to seem that I may be ahead of the curve to download the new Centos 5.3 i386 images and install a fresh system on another hard drive and then move my mail, websites and other relevant files over.
On Apr 22, 2009, at 1:48 PM, Filipe Brandenburger wrote:
Hi,
On Wed, Apr 22, 2009 at 15:40, Dan Roberts dan@jlazyh.com wrote:
# rpm -Uvh --force yum-3.2.19-18.el5.centos.noarch.rpm error: Failed dependencies: rpm >= 0:4.4.2 is needed by yum-3.2.19-18.el5.centos.noarch rpm-python is needed by yum-3.2.19-18.el5.centos.noarch yum-fastestmirror is needed by yum-3.2.19-18.el5.centos.noarch Either I am running this in the wrong location, or there is a lot of other stuff out of whack.
It looks like your system is closer to 5.2 than 5.3.
In that case, I suggest you try to install this RPM of yum instead: http://mirror.centos.org/centos/5.2/updates/i386/RPMS/yum-3.2.8-9.el5.centos...
If it still asks about dependencies, you will have to download them and install/upgrade them manually using RPM.
Look for them here: http://mirror.centos.org/centos/5.2/os/i386/CentOS/ And here: http://mirror.centos.org/centos/5.2/updates/i386/RPMS/
Once you get to install yum-3.2.8-9.el5.centos.2.1, yum should start working again.
When you got that done, you can try to use it to upgrade again, but this time I advise you to do it on a screen session from an SSH connection, and not through Webmin. And do not reboot the server in the middle of the upgrade, since that is probably what started your problems in this case.
HTH, Filipe _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Wed, 2009-04-22 at 14:06 -0600, Dan Roberts wrote:
<snip>
I know very little about this, but maybe Felipe et al can fill in the holes.
I recall times that folks on the list indicated an rpm rebuild db be done. Is that possibly needed here?
Did the glibc get updated? If so/not what should be done.
Just hoping this sparks knowledgeable folks to hit the right path for you.
HTH
Hi,
On Wed, Apr 22, 2009 at 16:06, Dan Roberts dan@jlazyh.com wrote:
There are indeed updates that it wants - and I went back to the site to get them, but then things continue to show up as missing. # rpm -Uvh --force rpm-4.4.2-48.el5.i386.rpm error: Failed dependencies: librpm-4.4.so is needed by rpm-4.4.2-48.el5.i386 librpmbuild-4.4.so is needed by rpm-4.4.2-48.el5.i386 librpmdb-4.4.so is needed by rpm-4.4.2-48.el5.i386 librpmio-4.4.so is needed by rpm-4.4.2-48.el5.i386 popt = 1.10.2 is needed by rpm-4.4.2-48.el5.i386
See my previous e-mail, try with the previous version of yum from CentOS 5.2 first.
Once you get yum running, you can use it to update your whole system to 5.3 (in screen and SSH).
HTH, Filipe
Dan Roberts wrote:
Ok - something truly bad appears to have happened. Yes, I will concede that cycling the system was a bad thing - but after two hours it should have returned from the update, still I was bad.
There are indeed updates that it wants - and I went back to the site to get them, but then things continue to show up as missing. # rpm -Uvh --force rpm-4.4.2-48.el5.i386.rpm error: Failed dependencies: librpm-4.4.so is needed by rpm-4.4.2-48.el5.i386 librpmbuild-4.4.so is needed by rpm-4.4.2-48.el5.i386 librpmdb-4.4.so is needed by rpm-4.4.2-48.el5.i386 librpmio-4.4.so is needed by rpm-4.4.2-48.el5.i386 popt = 1.10.2 is needed by rpm-4.4.2-48.el5.i386
Clearly I have a pretty big hole here. Yes I have been spoiled by yum and rpm. Years ago I use to command line build, make and install everything - but dropped that habit in favor of the ease of yum.
Are there are set of core files that seem reasonable to pull and install -
You could try using rpm2cpio to get the package files back down on disk.
Download all rpms you need to the machine. Probably the 5.2 versions as others have said.
Boot rescue media, let it find & mount your partitions. run cd /mnt/sysimage rpm2cpio package.rpm > package.rpm.cpio cpio -idmv < package.rpm.cpio
Do that with rpm, rpm-libs, rpm-python, popt, whatever else seems hammered.
May not hurt much if you're at your last solution - rebuild.
On Wed, 2009-04-22 at 13:40 -0600, Dan Roberts wrote:
Hi Filipe -
Clearly I have indeed got things broken - # rpm -q yum package yum is not installed
So I downloaded the rpm for a reinstall as you suggested - but clearly I have more to get and install -
I downloaded to my home directory and ran the rpm -Uvh from there
# rpm -Uvh --force yum-3.2.19-18.el5.centos.noarch.rpm error: Failed dependencies: rpm >= 0:4.4.2 is needed by yum-3.2.19-18.el5.centos.noarch rpm-python is needed by yum-3.2.19-18.el5.centos.noarch yum-fastestmirror is needed by yum-3.2.19-18.el5.centos.noarch
Either I am running this in the wrong location, or there is a lot of other stuff out of whack.
---- you've been spoiled by the dependency resolution by yum which doesn't exist with rpm so in order to get yum installed, you going to need to do some manual downloading and installation of dependencies.
I wouldn't recommend that you use '--force' for any rpm commands unless you know what you're doing.
Open a web browser and depending upon your installation (I am using i386 here)...
http://mirror.centos.org/centos/5/os/i386/CentOS/
(it's possible that you may need something from updates) http://mirror.centos.org/centos/5/updates/i386/RPMS/
and you will undoubtedly need to download rpm-4.4.2.3-9.el5.i386.rpm rpm-libs-4.4.2.3-9.el5.i386.rpm rpm-python-4.4.2.3-9.el5.i386.rpm
possibly popt and maybe some python stuff - and install locally like...
rpm -Uvh *rpm
and you will probably have to also do that for yum and yum-fastest-mirror packages as well. Once yum is installed, you can then update the rest.
rpm
Hi,
On Wed, Apr 22, 2009 at 16:00, Craig White craigwhite@azapple.com wrote:
I wouldn't recommend that you use '--force' for any rpm commands unless you know what you're doing.
I suggested the --force just in case the RPM database already had the yum package registered, but the package was corrupt.
I agree with your statement that --force should be only used if you know what you're doing.
Open a web browser and depending upon your installation (I am using i386 here)... http://mirror.centos.org/centos/5/os/i386/CentOS/
I suggested that the OP gets the packages for 5.2, since his install seems to be closer to a 5.2 than a 5.3. That way he may end up getting yum to work again quicker, and then he can use yum to update his system to the latest packages.
Using /5/ (CentOS 5.3) is also doable, but the number of packages he will have to download and install manually will certainly be larger.
HTH, Filipe
On Wed, 2009-04-22 at 16:06 -0400, Filipe Brandenburger wrote:
Hi,
On Wed, Apr 22, 2009 at 16:00, Craig White craigwhite@azapple.com wrote:
I wouldn't recommend that you use '--force' for any rpm commands unless you know what you're doing.
I suggested the --force just in case the RPM database already had the yum package registered, but the package was corrupt.
I agree with your statement that --force should be only used if you know what you're doing.
Open a web browser and depending upon your installation (I am using i386 here)... http://mirror.centos.org/centos/5/os/i386/CentOS/
I suggested that the OP gets the packages for 5.2, since his install seems to be closer to a 5.2 than a 5.3. That way he may end up getting yum to work again quicker, and then he can use yum to update his system to the latest packages.
Using /5/ (CentOS 5.3) is also doable, but the number of packages he will have to download and install manually will certainly be larger.
---- you could be correct on using 5.2 version of yum might be easier
Craig
Les Mikesell wrote:
Dan Roberts wrote:
that aside - I can't run the command you suggest because any yum operation results in the same error message.
# yum clean all && yum update glibc* && yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
I think this is your immediate problem. Do you have a /usr/share/yum-cli/i18n.py file?
Run on my four C5.3 systems here
yum provides "/usr/share/yum-cli/i18n.py" rpm -q --whatprovides /usr/share/yum-cli/i18n.py ls -las /usr/share/yum-cli/i18n.py
I got zip.
On 4/22/09, Dan Roberts dan@jlazyh.com wrote:
I will start reading again and striving to improve things. I have previously taken steps to secure the server, and was under the impression that it was so.
If you were only updating every month or so, impossible for the server to have been secure or anything approaching that. In addition to keeping the server up to date, there are many things you can do, to try to make it more secure. If it is connected to the Internet, many people would like to take it over, so it is their server, not yours. Try to make it harder for them.
On Wed, Apr 22, 2009 at 1:46 PM, Dan Roberts dan@jlazyh.com wrote:
I will start reading again and striving to improve things. I have previously taken steps to secure the server, and was under the impression that it was so.
Dan: After you get the server running properly again, you might go to this URL: http://www.nsa.gov and search for "Guide to the Secure Configuration of Red Hat Enterprise Linux 5 Revision 2 December 20, 2007"
it's a .pdf file you can download. They also have a 2 page pamphlet, which gives you an overview of how to harden your CentOS 5 server. HTH, Lanny
Jim Perrin wrote:
So you probably missed the notes and announcements about the 5.3 release, as well as the release notes about upgrade hiccups.
You guys just have to screw up more often to keep everyone on their toes.
On Wed, 2009-04-22 at 13:28 -0500, Les Mikesell wrote:
Jim Perrin wrote:
So you probably missed the notes and announcements about the 5.3 release, as well as the release notes about upgrade hiccups.
You guys just have to screw up more often to keep everyone on their toes.
---- that ignores the fact that the problem was noted in upstream release notes as well.
Craig
Craig White wrote:
On Wed, 2009-04-22 at 13:28 -0500, Les Mikesell wrote:
Jim Perrin wrote:
So you probably missed the notes and announcements about the 5.3 release, as well as the release notes about upgrade hiccups.
You guys just have to screw up more often to keep everyone on their toes.
that ignores the fact that the problem was noted in upstream release notes as well.
Yes, but we've all gotten used to things "just working", so nobody reads that stuff.
On Wed, Apr 22, 2009 at 12:47 PM, Dan Roberts dan@jlazyh.com wrote:
Hey there -
This morning I ran the yum updater through Webmin as I do every month or so - after about two hours I realized that I still had the same updating screen going - and no response. Seemed strange.
Simple attempts to kill it didn't work so I sent a command to reboot the system - that seemed to work, till I turned on the monitor directly connected to the server -
My first approach would be to use the lower level rpm to determine what packages may be in error. Start with yum:
rpm -qV yum
It will list files that have changed from the initial package installation: [u108752@linbox ~]$ rpm -qV yum S.5....T c /etc/yum.conf
If you see any files besides the user editable ones (such as the yum.conf, for example) it could mean you have a corrupted binary. If so, re-install the package:
rpm -ivh yum-x.x.x..rpm
You may need to use the --oldpackage flag or even --force.
If you don't see anything that jumps out as wrong, try running the rpm verify against all packages;
rpm -qaV
Ignore things like conf files and logs and look for packages with a S (checksum change) in the results colums..
Once you can get yum reinstalled, update glibc first, then the rest of the system.
I saw this error go by - and then only a spinning cursor - never get to a login screen. (I power cycled again and saw it go by again - and recognized it when I tried again at Webmin and through a terminal connection).
Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n
I deleted the yum cash and no improvement. I tried the yum clean and no imporvement [root@trailrunner yum]# yum clean all Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 29, in ? import cli File "/usr/share/yum-cli/cli.py", line 30, in ? import output File "/usr/share/yum-cli/output.py", line 26, in ? from i18n import _ ImportError: No module named i18n [root@trailrunner yum]#
Not at all sure what happened or why, or where I even start trying to straighten this mess out.
How do I blow away the apparent yum junk in the hope of getting a local login capability back?
How or what should I do to reset yum - seems reinstalling the latest version is probably the route. What is the version that CentOS uses? Should I go the RPM route or try something more specific?
Totally unexpected problem and leaving me feeling very uncertain about things.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Craig White -
Dan Roberts -
Filipe Brandenburger -
Jim Perrin -
Kwan Lowe -
Lanny Marcus -
Les Mikesell -
Michael Holmes -
Ralph Angenendt -
Richard Foltyn -
Rob Kampen -
Scott Silva -
Toby Bluhm -
William L. Maltby