Ticket #294 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

Umit Crash - 'no such table: scan'

Reported by: luis Owned by: boltrix
Priority: medium Milestone: Umit 1.0RC
Component: CrashReport Version: current svn
Keywords: user crash Cc:

Description (last modified by ignotus) (diff)

Crash Report
==========

sys.platform linux2
os.name posix
Gtk version 2.14.4
Umit version 1.0beta3

Description


Versions:
---
GTK: 2.14.4
PyGTK: 2.15.3
HIGWidgets: 1.0beta1
Python: 2.5.2 (r252:60911, Oct  5 2008, 19:24:49) 
[GCC 4.3.2]
Nmap: Nmap version 4.62 ( http://nmap.org )
Operating System: Linux bastiao-desktop 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686
Umit: 1.0beta3
UmitCore: 1.0beta3
UmitGUI: 1.0beta3
---
<class 'sqlite3.OperationalError'>
Python 2.5.2: /usr/bin/python
Sat Apr 11 16:14:41 2009

A problem occurred in a Python script.  Here is the sequence of
function calls leading up to the error, in the order they occurred.

 /home/bastiao/Projects/umit/umit-svn/trunk/umit/gui/MainWindow.py in _exit_cb(self=<MainWindow object at 0xa8423ec (GtkWindow at 0xa00e168)>, widget=<MainWindow object at 0xa8423ec (GtkWindow at 0xa00e168)>, extra=<GdkEvent at 0xaf5d9a8>)
 1243 
 1244             # Remove old data from database
 1245             remove_old_data()
 1246 
 1247             gtk.main_quit()
global remove_old_data = <function remove_old_data at 0xa7bda74>

 /home/bastiao/Projects/umit/umit-svn/trunk/umit/core/DataDecay.py in remove_old_data()
   79 
   80     remover = ScanRemover(umitdb)
   81     remover.remove_old_umit_scans(umit_decay)
   82     remover.remove_old_inventory_scans(inventory_decay)
   83 
remover = <umit.db.Remove.ScanRemover instance at 0xb50a78c>
remover.remove_old_umit_scans = <bound method ScanRemover.remove_old_umit_scans ...mit.db.Remove.ScanRemover instance at 0xb50a78c>>
umit_decay = 60

 /home/bastiao/Projects/umit/umit-svn/trunk/umit/db/Remove.py in remove_old_umit_scans(self=<umit.db.Remove.ScanRemover instance at 0xb50a78c>, older_than=60)
   77         # get scans from table scan older than especified days
   78         scans_ids = self.cursor.execute("SELECT pk FROM scan WHERE finish <= ?",
   79                                         (old_data_date, )).fetchall()
   80         scans_ids = set([s_id[0] for s_id in scans_ids])
   81 
old_data_date = datetime.datetime(2009, 2, 10, 16, 14, 41, 588033)
).fetchall undefined
<class 'sqlite3.OperationalError'>: no such table: scan
    __class__ = <class 'sqlite3.OperationalError'>
    __delattr__ = <method-wrapper '__delattr__' of OperationalError object at 0xa1f3c84>
    __dict__ = {}
    __doc__ = None
    __getattribute__ = <method-wrapper '__getattribute__' of OperationalError object at 0xa1f3c84>
    __getitem__ = <method-wrapper '__getitem__' of OperationalError object at 0xa1f3c84>
    __getslice__ = <method-wrapper '__getslice__' of OperationalError object at 0xa1f3c84>
    __hash__ = <method-wrapper '__hash__' of OperationalError object at 0xa1f3c84>
    __init__ = <method-wrapper '__init__' of OperationalError object at 0xa1f3c84>
    __module__ = 'sqlite3'
    __new__ = <built-in method __new__ of type object at 0x8145f60>
    __reduce__ = <built-in method __reduce__ of OperationalError object at 0xa1f3c84>
    __reduce_ex__ = <built-in method __reduce_ex__ of OperationalError object at 0xa1f3c84>
    __repr__ = <method-wrapper '__repr__' of OperationalError object at 0xa1f3c84>
    __setattr__ = <method-wrapper '__setattr__' of OperationalError object at 0xa1f3c84>
    __setstate__ = <built-in method __setstate__ of OperationalError object at 0xa1f3c84>
    __str__ = <method-wrapper '__str__' of OperationalError object at 0xa1f3c84>
    __weakref__ = None
    args = ('no such table: scan',)
    message = 'no such table: scan'

The above is a description of an error in a Python program.  Here is
the original traceback:

Traceback (most recent call last):
  File "/home/bastiao/Projects/umit/umit-svn/trunk/umit/gui/MainWindow.py", line 1245, in _exit_cb
    remove_old_data()
  File "/home/bastiao/Projects/umit/umit-svn/trunk/umit/core/DataDecay.py", line 81, in remove_old_data
    remover.remove_old_umit_scans(umit_decay)
  File "/home/bastiao/Projects/umit/umit-svn/trunk/umit/db/Remove.py", line 79, in remove_old_umit_scans
    (old_data_date, )).fetchall()
OperationalError: no such table: scan


Change History

follow-up: ↓ 2   Changed 4 years ago by ignotus

  • description modified (diff)

Luis. Can you describe how to produce the bug?

in reply to: ↑ 1   Changed 4 years ago by luis

  • status changed from new to closed
  • resolution set to invalid

Replying to ignotus:

Luis. Can you describe how to produce the bug?

Hello.

It easy to reproduce, but it is not exactly a bug. Probably I was using umit and developing for it at the same time, then I removed umitng.db and I closed Umit.

I could provide a workaround to solve this issue, then I'll need to provide others to solve all others issues that can be happened by remove files in runtime. It is the reason I'm closing it. By you guys have different opinion, reopen it.

Note: See TracTickets for help on using tickets.