On Mon, 2011-07-18 at 10:39 -0400, James Laska wrote: > On Mon, 2011-07-18 at 08:38 -0400, James Laska wrote: > > On Mon, 2011-07-18 at 09:11 -0300, Lucas Meneghel Rodrigues wrote: > > > On Mon, Jul 18, 2011 at 9:01 AM, James Laska <[email protected]> wrote: > > > > Greetings, > > > > > > > > While running autotest-0.13.0, I've come across the following error as > > > > reported in the scheduler.log. Before I start digging in, I thought > > > > I'd ask if anyone has already seen this issue? I'm wondering if this > > > > is related to the stream file handle that is removed when running the > > > > scheduler forks from the SysV initscript. > > > > > > Well, need to check, but I've noticed you are using py 2.6 there. The > > > guys at the chrome OS team @google uncovered a bug that is a python > > > 2.6 bug: > > > > > > http://autotest.kernel.org/changeset/5489 > > > > > > This bugfix didn't get into autotest 0.13.0, so would you check if > > > this solves your problem? you can easily download this patch to try it > > > out: > > > > > > http://patchwork.test.kernel.org/patch/3542/mbox/ > > > > > > Thanks and let me know how it goes, > > > > I saw the original bug, and the above patch on the list when packaging > > +testing autotest-0.13.0 for Fedora. The autotest RPM's I created for > > Fedora [1] include that patch. > > > > One thing I noticed that's different with the current upstream RH-style > > initscript included in autotest, the scheduler/babysitter stdout > > handling after forking doesn't seem correct. Meaning, output still is > > sent to the tty after starting the scheduler. I'm not sure if if this > > is at all related. Also, I'm seeing that the babysitter seems to be > > dead, while monitor_db.py continues. Still poking around ... > > Found another crash instance while monitoring the scheduler logs ... > > 07:38:08 ERROR| monitor_db exception > EXCEPTION: Uncaught exception; terminating monitor_db > Traceback (most recent call last): > File "/usr/share/autotest/scheduler/monitor_db.py", line 158, in > main_without_exception_handling > dispatcher.tick() > File "/usr/share/autotest/scheduler/monitor_db.py", line 289, in tick > self._run_cleanup() > File "/usr/share/autotest/scheduler/monitor_db.py", line 305, in > _run_cleanup > self._periodic_cleanup.run_cleanup_maybe() > File "/usr/share/autotest/scheduler/monitor_db_cleanup.py", line 32, > in run_cleanup_maybe > self._cleanup() > File "/usr/share/autotest/scheduler/monitor_db_cleanup.py", line 57, > in _cleanup > self._check_for_db_inconsistencies() > File "/usr/share/autotest/scheduler/monitor_db_cleanup.py", line 91, > in _check_for_db_inconsistencies > self._check_all_invalid_related_objects() > File "/usr/share/autotest/scheduler/monitor_db_cleanup.py", line 133, > in _check_all_invalid_related_objects > first_model, first_field, second_model, second_field)) > File "/usr/share/autotest/scheduler/monitor_db_cleanup.py", line 120, > in _check_invalid_related_objects > second_model, second_field, first_model)) > File "/usr/share/autotest/scheduler/monitor_db_cleanup.py", line 111, > in _check_invalid_related_objects_one_way > related_manager.clear() > File > "/usr/lib/python2.6/site-packages/django/db/models/fields/related.py", > line 519, in clear > self._clear_items(self.source_field_name) > File > "/usr/lib/python2.6/site-packages/django/db/models/fields/related.py", > line 641, in _clear_items > source_field_name: self._pk_val > File "/usr/lib/python2.6/site-packages/django/db/models/query.py", > line 444, in delete > collector.collect(del_query) > File "/usr/lib/python2.6/site-packages/django/db/models/deletion.py", > line 146, in collect > reverse_dependency=reverse_dependency) > File "/usr/lib/python2.6/site-packages/django/db/models/deletion.py", > line 91, in add > if not objs: > File "/usr/lib/python2.6/site-packages/django/db/models/query.py", > line 113, in __nonzero__ > iter(self).next() > File "/usr/lib/python2.6/site-packages/django/db/models/query.py", > line 107, in _result_iter > self._fill_cache() > File "/usr/lib/python2.6/site-packages/django/db/models/query.py", > line 772, in _fill_cache > self._result_cache.append(self._iter.next()) > File "/usr/lib/python2.6/site-packages/django/db/models/query.py", > line 273, in iterator > for row in compiler.results_iter(): > File > "/usr/lib/python2.6/site-packages/django/db/models/sql/compiler.py", > line 680, in results_iter > for rows in self.execute_sql(MULTI): > File > "/usr/lib/python2.6/site-packages/django/db/models/sql/compiler.py", > line 735, in execute_sql > cursor.execute(sql, params) > File > "/usr/lib/python2.6/site-packages/django/db/backends/mysql/base.py", > line 86, in execute > return self.cursor.execute(query, args) > File "/usr/lib64/python2.6/site-packages/MySQLdb/cursors.py", line > 173, in execute > self.errorhandler(self, exc, value) > File "/usr/lib64/python2.6/site-packages/MySQLdb/connections.py", line > 36, in defaulterrorhandler > raise errorclass, errorvalue > OperationalError: (1054, "Unknown column 'afe_acl_groups_hosts.id' in > 'field list'")
Update ... Lucas directed me to http://autotest.kernel.org/changeset/5483. I'm applying that change and will be testing shortly. Thanks, James
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
