Bug 643201

Summary: [abrt] umit-1.0-0.3.RC.fc13: __init__.py:754:flush:ValueError: I/O operation on closed file
Product: [Fedora] Fedora Reporter: Adam Daman Nicholson <adam>
Component: umitAssignee: Mykola Ulianytskyi <lystor>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: lystor
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:8b49e855
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-28 11:35:15 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:
Attachments:
Description Flags
File: backtrace none

Description Adam Daman Nicholson 2010-10-14 21:48:42 UTC
abrt version: 1.1.13
architecture: i686
cmdline: /usr/bin/python /usr/bin/umit_scheduler.py start
component: umit
executable: /usr/bin/umit_scheduler.py
kernel: 2.6.34.7-56.fc13.i686
package: umit-1.0-0.3.RC.fc13
reason: __init__.py:754:flush:ValueError: I/O operation on closed file
release: Fedora release 13 (Goddard)
time: 1287092887
uid: 500

backtrace
-----
__init__.py:754:flush:ValueError: I/O operation on closed file

Traceback (most recent call last):
  File "/usr/lib/python2.6/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib/python2.6/logging/__init__.py", line 1508, in shutdown
    h.flush()
  File "/usr/lib/python2.6/logging/__init__.py", line 754, in flush
    self.stream.flush()
ValueError: I/O operation on closed file

Local variables in innermost frame:
self: <logging.StreamHandler instance at 0x841098c>

Comment 1 Adam Daman Nicholson 2010-10-14 21:48:44 UTC
Created attachment 453586 [details]
File: backtrace

Comment 2 Mykola Ulianytskyi 2010-10-15 06:06:21 UTC
Sorry, I can't reproduce the error.

1) Install umit-1.0-0.3.RC.fc13.noarch on fully updated Fedora 13 x86_64 with the 2.6.34.7-56.fc13.x86_64 kernel.
2) Run umit from root.
3) Tools > Scheduler > Editor:
* Shema Name: s1;
* Scan Profile: Operation System Detection;
* Command: nmap -O -v 127.0.0.1
* Scheduling Profile: 8:00 to 17:00 hourle, Mon thru Fri
* Save output to: /tmp/
* OK
4) Close umit
5) # /usr/bin/python /usr/bin/umit_scheduler.py start
6) # ps aux | grep umit
root      4785  0.0  0.9 185416  9728 ?        S    08:57   0:00 /usr/bin/python /usr/bin/umit_scheduler.py start 

SELinux is disabled.

Comment 3 Bug Zapper 2011-05-31 11:18:42 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2011-06-28 11:35:15 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.