Page 1 of 1
SOLVED: no yum, rpm after fedora re-installation
Posted: Sun Aug 16, 2015 2:52 am
by justright
gday guys, i have posted in this portion of the forum due to very low knowledge of linux. My problem does not lie with amahi as i have had it installed and working seamlessly previously but had a OS HDD failure and the server would only boot into emergency mode. My problem lies with fedora now as i pulled the greyhole storage drives out and attempted a fresh install on the OS drive which went smoothly until i came to install amahi from the instructions on the amahi 7 full installation wiki page. Installing by hand has been my only option aswell due to my NIC not allowing me to take the express path **not eth0**. The very first line from the guide (installing amahi repo) is met with error: /var/tmp/rpm/-tmp.xxxxxx: not an rpm package (or package manifest). I have also tried to see if yum is working by attempting to install nano and i am met with **nano error: cannot retrieve metalink for repository: fedora/19/x86_64. please verify its path and try again**. This was all working yesterday but i cannot seem to get it to work now and have tried re-installing fedora one to many times haha. any help with this will be very much appreciated as i was enjoying the whole process up until this road block. I was hoping at the time a simple fedora re-install and re-mounting of the data disks would have sufficed up until i couldn't even get past installing amahi.
thanks in advance.
Re: no yum, rpm after fedora re-installation
Posted: Sun Aug 16, 2015 2:58 am
by cpg
This is new. Are you SURE you are on Fedora 19?
About the
Code: Select all
error: /var/tmp/rpm/-tmp.xxxxx not an rpm package ...
it's also a little strange (not enough free space?). also, you do not say what you did exactly to get this output.
what command was it what *exactly* showed on on screen?
Re: no yum, rpm after fedora re-installation
Posted: Sun Aug 16, 2015 3:21 am
by justright
sorry, what caused all this turmoil in the first place was me attempting to add outgoing emails by use of
https://wiki.amahi.org/index.php/Enable_Outgoing_Emails . Something went wrong along the way
Code: Select all
su -
yum -y install sendmail-cf mailx
cp /etc/mail/sendmail.mc /etc/mail/sendmail.mc.orig
vi /etc/mail/sendmail.mc
adding the lines before MAILER was met with struggle and i ended up restarting the server. This was met with emergency mode
*Thus resulting in me attempting a fedora re-installation. install of fedora looks to go well until i have to install amahi by hand. and anything else for that matter.
the command that gives me the error and the error is:
Code: Select all
rpm -Uvh http://f19.amahi.org/noarch/hda-release-6.9.0-1.noarch.rpm
Retrieving http://f19.amahi.org/noarch/hda-release-6.9.0-1.noarch.rpm
error: /var/tmp/rpm-tmp.xxxxxx: not an rpm package (or package manifest):
cheers.
Re: no yum, rpm after fedora re-installation
Posted: Sun Aug 16, 2015 3:25 am
by justright
Also i see you have mentioned enough free space.
All instructions were followed on
https://wiki.amahi.org/index.php/Hard_D ... ion_Scheme
and yes i am positive i have installed fedora 19 as i have have seen the install fedora 19 page one to many times.
cheers.
Re: no yum, rpm after fedora re-installation
Posted: Sun Aug 16, 2015 3:37 am
by cpg
What's in /etc/issue ?
Re: no yum, rpm after fedora re-installation
Posted: Sun Aug 16, 2015 3:44 am
by justright
thanks for your reply. this is interesting as i have been given a permission denied bash
Code: Select all
/etc/issue
bash: /etc/issue: permission denied
this was done in root access too.
Re: no yum, rpm after fedora re-installation
Posted: Sun Aug 16, 2015 4:50 am
by cpg
Re: no yum, rpm after fedora re-installation
Posted: Sun Aug 16, 2015 6:03 am
by justright
Code: Select all
Fedora release 19 (Schrödinger's Cat)
Kernel \r on an \m (\l)
definitely 19
Re: no yum, rpm after fedora re-installation
Posted: Sun Aug 16, 2015 6:56 am
by bigfoot65
Try downloading the RPM local first, then run the command to install it.
Re: no yum, rpm after fedora re-installation
Posted: Sun Aug 16, 2015 10:15 pm
by justright
Just thought i would follow up on this and elaborate on my findings. Rookie error really, I did a ping test through console and it failed. Which reminded me of when I disabled dhcp on my router to accommodate my server running the dhcp. Enabling my router as dhcp has done the trick and I am now back on track. Thanks for your assistance guys. Much appreciated.