Bug 208773 - yum traceback if /dev/log is not working
yum traceback if /dev/log is not working
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
: Reopened
Depends On:
Blocks: FC6Target
  Show dependency treegraph
 
Reported: 2006-10-01 17:06 EDT by Florian La Roche
Modified: 2014-01-21 17:55 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-04-24 18:01:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Florian La Roche 2006-10-01 17:06:17 EDT
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 18:41:50 EDT
Hrm, this really looks like a python bug... 
Comment 2 Jeremy Katz 2006-10-12 21:23:22 EDT
Fixed in yum CVS, will be in the next build
Comment 3 Florian La Roche 2006-10-19 04:30:13 EDT
Still not working with current trees, did this get lost?

regards,

Florian La Roche
Comment 4 Jeremy Katz 2006-11-06 15:21:50 EST
It should have been fixed in 3.0-6 afaik.  Was it not?
Comment 5 Florian La Roche 2006-11-06 15:52:32 EST
Still happened with the -6 release.

regards,

Florian La Roche
Comment 6 Scott A. Friedman 2007-04-20 18:44:37 EDT
Bump - any update on this problem. Was/is it a python issue?
Comment 7 Jeremy Katz 2007-04-24 18:01:24 EDT
It was a python bug and the fix is included in python 2.5 for F7

Note You need to log in before you can comment on or make changes to this bug.