Bug 208773

Summary: yum traceback if /dev/log is not working
Product: [Fedora] Fedora Reporter: Florian La Roche <laroche>
Component: yumAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: mihai.ibanescu
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-04-24 22:01:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 150223    

Description Florian La Roche 2006-10-01 21:06:17 UTC
Description of problem:

Recently a patch was added to yum to have it working even if
/dev/log exists, but is not working (kickstart installs and %post script).

Now yum does work in such a kickstart %post script, but tracebacks with
the following lines after doing a package install:

Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib/python2.4/logging/__init__.py", line 1333, in shutdown
    h.close()
  File "/usr/lib/python2.4/logging/handlers.py", line 642, in close
    if self.unixsocket:
AttributeError: SysLogHandler instance has no attribute 'unixsocket'


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jeremy Katz 2006-10-01 22:41:50 UTC
Hrm, this really looks like a python bug... 

Comment 2 Jeremy Katz 2006-10-13 01:23:22 UTC
Fixed in yum CVS, will be in the next build

Comment 3 Florian La Roche 2006-10-19 08:30:13 UTC
Still not working with current trees, did this get lost?

regards,

Florian La Roche


Comment 4 Jeremy Katz 2006-11-06 20:21:50 UTC
It should have been fixed in 3.0-6 afaik.  Was it not?

Comment 5 Florian La Roche 2006-11-06 20:52:32 UTC
Still happened with the -6 release.

regards,

Florian La Roche


Comment 6 Scott A. Friedman 2007-04-20 22:44:37 UTC
Bump - any update on this problem. Was/is it a python issue?

Comment 7 Jeremy Katz 2007-04-24 22:01:24 UTC
It was a python bug and the fix is included in python 2.5 for F7