Red Hat Bugzilla – Bug 5788
Cannot upgrade if existing /tmp dir is a symlink
Last modified: 2015-01-07 18:38:40 EST
My /tmp dir is a symlink to /var/tmp (space reasons) and the installer does not correctly handle the situation. It gets an exception error because it cannot open the tmp/upgrade.log file for writing. The problem can be solved by removing the symlink and recreating the directory with 1777 permissions. Exception in thread Thread-3: Traceback (innermost last): File "/usr/lib/python1.5/threading.py", line 376, in __bootstrap self.run() File "/mnt/redhat/comps/install/6.1/i386/RedHat/instimage/usr/lib/python1.5/site-packages/iw/progress.py", line 16, in run File "../../../RedHat/instimage/usr/lib/python1.5/site-packages/todo.py", line 1465, in doInstall self.instLog = open(self.instPath + logname, "w+") IOError: [Errno 2] No such file or directory: '/mnt/sysimage/tmp/upgrade.log'
I ran into a similar problem, see bug 6014, with a link for /etc/lilo.conf to /boot/lilo.conf. I fixed it by making the link relative, ../boot/lilo.conf, which allowed the installers remounting of the filesystems to not break the link. alanrb@bigfoot.com
*** Bug 6014 has been marked as a duplicate of this bug. *** While upgrading from 6.0 to 6.1 via FTP I had several errors that the installer did not handle very well. It apparently just crashed the script and displayed a traceback. It took me awhile before I figured out how to deal with this. Clicking OK or DEBUG just seemed to eventually get me to a hung system. Scrolling the traceback and trying to interpret the messages eventually allowed me to get past the problems, which I have listed below: * /etc/lilo.conf was linked to /boot/lilo.conf on my 6.0 system, but that is not valid with the installs mounting setup, so no writtable file existed. The lack of checking on this may be related to the other problems with lilo.conf that have been reported. * Upgrade was done via FTP; transmission errors and login failure due to exceeding user limits lead to script crash and the traceback. This may be tough to deal with, but I think a complete novice user would be stuck if they hit these.
For the installer to be able to follow a symlink, it must be a relative link and not an absolute