Red Hat Bugzilla – Bug 199558
Last modified: 2014-01-21 17:54:55 EST
Description of problem:
This happens if yum is called todo updates right in the %post section of
an install. Maybe if /dev/log is not available, this could stay left out
Florian La Roche
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in ?
File "/usr/share/yum-cli/yummain.py", line 85, in main
File "/usr/share/yum-cli/cli.py", line 201, in getOptionsConfig
File "/usr/lib/python2.4/site-packages/yum/logginglevels.py", line 110, in
syslog = logging.handlers.SysLogHandler('/dev/log')
File "/usr/lib/python2.4/logging/handlers.py", line 589, in __init__
File "/usr/lib/python2.4/logging/handlers.py", line 605, in _connect_unixsocket
File "<string>", line 1, in connect
socket.error: (2, 'No such file or directory')
Error in atexit._run_exitfuncs:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 132758 [details]
Check for the log device first
This patch checks to see if the log device exists first, before trying to make
a syslog handler that speaks to it.
I first tried just catching the exception that is thrown, but it seems that the
SysLogHandler code ended up in a state after this exception that caused other
problems upon garbage collection.
Patch looked sensible so I checked it in.
*** Bug 199712 has been marked as a duplicate of this bug. ***