[SOLVED] rpm command and yum command not found

Joaquin · 04-03-2013, 02:16 AM

Hello,

after typing, this command:

Code:

rpm -e --nodeps xulrunner

does not work the command rpm and yum command

Glennzo · 04-03-2013, 02:49 AM

What is the specific error output from both commands?

Joaquin · 04-03-2013, 02:50 AM

Quote:

Originally Posted by Glennzo

What is the specific error output from both commands?

rpm:command not found

John VV · 04-03-2013, 02:54 AM

we will need a lot more information
like:

What is the operating system you are using ?
The version of the OS ?
And the full error you are getting .

I take it you want to install "xulrunner"
from the normal user account become "root" in the terminal
for CentOS 6.4

Code:

su -
------- then type in your root password when asked -----
yum search xulrunner
--- then from that list install it ----
yum install xulrunner

for the rpm command --- It is NOT recommended to use
unless as a very last resort
to manually install xulrunner AND all the needed dependencies FIRST before installing "xulrunner"

Joaquin · 04-03-2013, 03:02 AM

Quote:

Originally Posted by John VV

we will need a lot more information
like:

What is the operating system you are using ?
The version of the OS ?
And the full error you are getting .

I take it you want to install "xulrunner"
from the normal user account become "root" in the terminal
for CentOS 6.4

Code:

su -
------- then type in your root password when asked -----
yum search xulrunner
--- then from that list install it ----
yum install xulrunner

for the rpm command --- It is NOT recommended to use
unless as a very last resort
to manually install xulrunner AND all the needed dependencies FIRST before installing "xulrunner"

The O.S. is RedHat 5.

The error is

Quote:

rpm:command not found

and this

Quote:

error:Unable to opem /usr/lib/rpm/rpmrc for reading:No such file or directory

John VV · 04-03-2013, 03:10 AM

well the current RHEL5 is 5.9

and you did buy the required support contract ? right ?

can you post the output of

Code:

cat /etc/redhat-release

if "yum" and "rpm" are not installed , then you have a very big problem .
the fastest fix will be to reinstall

Joaquin · 04-03-2013, 03:22 AM

Quote:

Originally Posted by John VV

well the current RHEL5 is 5.9

and you did buy the required support contract ? right ?

can you post the output of

Code:

cat /etc/redhat-release

if "yum" and "rpm" are not installed , then you have a very big problem .
the fastest fix will be to reinstall

How does it happen that running the command I wrote in the first post, it happened prevents this problem?

If, for example

Code:

yum update

launch, the result is in the attached image.

John VV · 04-03-2013, 03:32 AM

man that is hard to read
please "copy/paste" the text into the forum

with this RHEL5 install you do have the support contract you bought

have you contacted red hat tech support
-- you are paying for it , so you might want to use it

you will likely need to manually extract files from the rpm's that you will need to download from RHN ( ftp or in the web browser)
and for that you will need there help

chrism01 · 04-03-2013, 10:28 PM

This

Code:

rpm -e --nodeps xulrunner

would only erase xulrunner.

Its likely some other cmd has been used to remove bits of rpm/yum.
You could check the root user's history; might show something.

In any case, you could ask RH or try to force re-install rpm (& possibly yum) from the install media, but if its been upgraded one or more point releases since the install it might still have issues.
You could try downloading the rpm/yum rpms (from RH)for the exact version you have (eg say 5.6) and force installing those.
As above, the latest v5 is 5.9.
Please post the output of the 'cat /etc/redhat-release' cmd, as requested by JohnVV & check if the install media is the same or not.

Joaquin · 04-05-2013, 03:08 AM

Quote:

Originally Posted by chrism01

This

Code:

rpm -e --nodeps xulrunner

would only erase xulrunner.

Its likely some other cmd has been used to remove bits of rpm/yum.
You could check the root user's history; might show something.

In any case, you could ask RH or try to force re-install rpm (& possibly yum) from the install media, but if its been upgraded one or more point releases since the install it might still have issues.
You could try downloading the rpm/yum rpms (from RH)for the exact version you have (eg say 5.6) and force installing those.
As above, the latest v5 is 5.9.
Please post the output of the 'cat /etc/redhat-release' cmd, as requested by JohnVV & check if the install media is the same or not.

The release is:

Code:

Red Hat Enterprise Linux Server release 5.9 (Tikanga)

chrism01 · 04-07-2013, 09:49 PM

As per my above '...& check if the install media is the same or not.'

Joaquin · 04-08-2013, 02:22 AM

Quote:

Originally Posted by chrism01

As per my above '...& check if the install media is the same or not.'

I do not know what to ask. RedHat is duly registered support is working but are now many days that I do not give a solution.

knudfl · 04-08-2013, 03:30 AM

# 12.

Quote:

I do not know what to ask. RedHat is duly registered support

Please call your Redhat support to ask for help.
They will most likely advise you to reinstall the OS.

Possible workarounds : Use another OS to unpack the rpm package(s)
That's $ rpm2cpio <package.rpm> | cpio -idmv
... and then copy the missing files into their locations.

I.e. you cannot force install anything with no rpm command.

-

Joaquin · 04-08-2013, 03:34 AM

Quote:

Originally Posted by knudfl

# 12.

Please call your Redhat support to ask for help.
They will most likely advise you to reinstall the OS.

Possible workarounds : Use another OS to unpack the rpm package(s)
That's $ rpm2cpio <package.rpm> | cpio -idmv
... and then copy the missing files into their locations.

I.e. you cannot force install anything with no rpm command.

-

Do you think there is a way to recover the OS without having to reinstall? Also because I have already installed a lot of software that kept me ilmpegnato long time to configure it.

knudfl · 04-08-2013, 04:11 AM

# 14.

1) Never use 'rpm -e --nodeps ', unless you know what will happen.

2) Use another rpm based Linux OS to unpack the missing files : See #13.