Got the following traceback a couple of times while testing on EC2:
File "/usr/lib/python2.5/site-packages/landscape/plugin.py", line 82, in dispatch_message
return handler(message)
File "/usr/lib/python2.5/site-packages/landscape/manager/packagemanager.py", line 39, in _enqueue_message_as_changer_task
self._package_store.add_task("changer", message)
File "/usr/lib/python2.5/site-packages/landscape/package/store.py", line 34, in inner
result = method(self, cursor, *args, **kwargs)
File "/usr/lib/python2.5/site-packages/landscape/package/store.py", line 280, in add_task
"VALUES (?,?,?)", (queue, time.time(), buffer(data)))
OperationalError: no such table: task
It only happens when scheduling a package activity shortly after startup. The package activity related stays in "Delivered" forever.
Got the error in another place. I used an initial script and the hardy large ami.
==> /var/log/ landscape/ monitor. log <== monitor. packagemonitor. PackageMonitor. _resynchronize( ) for event type 'resynchronize' with args () {}. python2. 5/site- packages/ landscape/ reactor. py", line 78, in fire append( handler( *args, **kwargs)) python2. 5/site- packages/ landscape/ monitor/ packagemonitor. py", line 85, in _resynchronize python2. 5/site- packages/ landscape/ package/ store.py" , line 34, in inner python2. 5/site- packages/ landscape/ package/ store.py" , line 280, in add_task
2009-08-20 21:17:00,864 ERROR [MainThread] Error running event handler landscape.
Traceback (most recent call last):
File "/usr/lib/
results.
File "/usr/lib/
{"type" : "resynchronize"})
File "/usr/lib/
result = method(self, cursor, *args, **kwargs)
File "/usr/lib/
"VALUES (?,?,?)", (queue, time.time(), buffer(data)))
OperationalError: no such table: task