The other thing to try is to go to /var/lib/rpm and delete the __db* files:
cd /var/lib/rpm
rm __db*
Then try the up2date again.
Alfred Hovdestad, RHCE
University of Saskatchewan
Jeff wrote:
Did that, it just says that the system is already up to date.
Jeff
-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of chockalingam
Sent: Wednesday, October 05, 2005 01:01
To: General Red Hat Linux discussion list
Subject: Re: Up2date crash
Hi Jeff,
As instructed, delete all the rpm files in the
/var/spool/up2date folder and reboot the server to normal and
oce again try the up2date -u command for a complete update......
regards,
Chockalingam.S
On 10/5/05, Jeff <jsmforum@xxxxxxxxxxxxx> wrote:
-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Andrew Bacchi
Sent: Tuesday, October 04, 2005 16:25
To: General Red Hat Linux discussion list
Subject: Re: Up2date crash
Reboot to single user mode, look to see if /var/spool/up2date is
full. Try 'df -h' or 'du -h /var/spool/'. Find the full directory,
clean it out and reboot to normal. You should be able to
save this from a full install.
Look here for howto on booting to single user.
http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/custom
-guide/s1-rescuemode-booting-single.html
On Tue, 2005-10-04 at 16:02, Jeff wrote:
Hey all,
Running RHES3 and did an up2date. The / partition was full and
because of this up2date crashed during the install phase.
Now the server won't boot correctly, I've lost X windows
and have to
boot to runlevel 3. Non of my daemons start automatically
so I have
to run /etc/init/network and every thing else in
/etc/init.d/ manually
to get things going.
If I run up2date -u again, I get the following.
[root@mis02tc07927 root]# up2date -u
Traceback (most recent call last):
File "/usr/sbin/up2date", line 1174, in ?
sys.exit(main() or 0)
File "/usr/sbin/up2date", line 668, in main
up2dateAuth.updateLoginInfo()
File "up2dateAuth.py", line 151, in updateLoginInfo
File "up2dateAuth.py", line 105, in login
File "up2dateAuth.py", line 49, in maybeUpdateVersion File
"/usr/share/rhn/up2date_client/up2dateUtils.py",
line 228, in
getVersion
release, version = getOSVersionAndRelease()
File "/usr/share/rhn/up2date_client/up2dateUtils.py",
line 221, in
getOSVersionAndRelease
raise up2dateErrors.RpmError(
up2date_client.up2dateErrors.RpmError: RPM error. The
message was:
Could not determine what version of Red Hat Linux you are
running. If
you get this error, try running
rpm --rebuilddb
Although running rpm --rebuilddb does't help.
Any ideas how I can unscrew this without a total re-install?
Thanks,
Jeff
--
redhat-list mailing list
unsubscribe
mailto:redhat-list-request@xxxxxxxxxx?> subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
No need for single user mode, I can get logged in running RL3.
The full directory was /mnt/USBDrive. The problem was the was no
external USB drive mounted and a backup script ran. This filled up /
That's since been cleaned out.
[root@mis02tc07927 up2date]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda7 11G 252M 9.9G 3% /
/dev/sda3 122M 31M 85M 27% /boot
/dev/sda2 2.5G 209M 2.2G 9% /home
none 1004M 0 1004M 0% /dev/shm
/dev/sda8 1012M 33M 928M 4% /tmp
/dev/sda5 108G 63G 40G 62% /usr
/dev/sda6 79G 35G 40G 47% /var
That being said, /var/spool/up2date contains a lot of rpm files.
Should I delete these?
Jeff
--
redhat-list mailing list
unsubscribe
mailto:redhat-list-request@xxxxxxxxxx?> subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjectunsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
