Bug 699259

Summary: [abrt] anaconda-15.28-1.fc15: __init__.py:912:_open:IOError: [Errno 13] Permission denied: '/tmp/anaconda.log'
Product: [Fedora] Fedora Reporter: Jirka Daněk <juraad>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5ab65257c64f5a4ebdea5e1b4119fb30405149a6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-28 18:10:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Jirka Daněk 2011-04-24 17:52:13 UTC
abrt version: 2.0.1
comment: Started anaconda from terminal as normal user
executable: /usr/sbin/anaconda
component: anaconda
kernel: 2.6.38.2-9.fc15.x86_64
reason: __init__.py:912:_open:IOError: [Errno 13] Permission denied: '/tmp/anaconda.log'
architecture: x86_64
uid: 500
username: liveuser
package: anaconda-15.28-1.fc15
os_release: Fedora release 15 (Lovelock)
time: 1303667461

backtrace
-----
__init__.py:912:_open:IOError: [Errno 13] Permission denied: '/tmp/anaconda.log'

Traceback (most recent call last):
  File "/usr/sbin/anaconda", line 491, in <module>
    anaconda_log.init()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/anaconda_log.py", line 213, in init
    logger = AnacondaLog()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/anaconda_log.py", line 125, in __init__
    minLevel=logging.DEBUG)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/anaconda_log.py", line 170, in addFileHandler
    logfileHandler = logging.FileHandler(file)
  File "/usr/lib64/python2.7/logging/__init__.py", line 893, in __init__
    StreamHandler.__init__(self, self._open())
  File "/usr/lib64/python2.7/logging/__init__.py", line 912, in _open
    stream = open(self.baseFilename, self.mode)
IOError: [Errno 13] Permission denied: '/tmp/anaconda.log'

Local variables in innermost frame:
self: <logging.FileHandler object at 0x1bd1f90>

Comment 1 Jirka Daněk 2011-04-24 17:52:17 UTC
Created attachment 494548 [details]
File: backtrace

Comment 2 Brian Lane 2011-04-25 19:32:17 UTC
Does anaconda.log already exist? What do the permissions on /tmp and /tmp/anaconda.log look like (if it exists). Was there anything different you did for this install?

Comment 3 Jirka Daněk 2011-04-28 18:10:29 UTC
This bug can probably be safely closed. I did the install from an USB whith enabled overlay and I tried this install several times, was updating the image with yum upgrade and so on. I still have a byte copy of the drive from the time when it was broken, but I don't think I'll have the parience to mess around it more. The live system was completely broken. On my second try then, anaconda worked, but crashed when it tried to open password databaze (to check the strength of root password), after that, anaconda refused to run completely with yet different error. (I reported that, but my bug got closed with comment that "anaconda is not supposed to be stared from command line", which is complete misunderstanding of my bugreport, I was running it from menu in GNOME 3 first, I resulted to the command line only after to see what is it writing on the std out) But anyway, I think there is nothing to fix.

I managed to do the install by creating a new live USB without overlays and separate /home and installing right away, without updates. So it is now all OK.

Comment 4 Brian Lane 2011-04-28 18:29:46 UTC
Thanks. FYI, running yum update on a live USB isn't recommended.

Comment 5 Jirka Daněk 2011-04-28 19:17:05 UTC
> running yum update on a live USB isn't recommended

I know, that is why I am closing this bug. But I think that should be advertised more. Like some message in yum when live user tries to update, note in wiki... I did not find anything discouraging me from doing that.