All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Wood <michael.g.wood@intel.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>,
	"toaster@yoctoproject.org" <toaster@yoctoproject.org>
Cc: "Reinhard.Tartler@deshawresearch.com"
	<Reinhard.Tartler@deshawresearch.com>
Subject: Re: Weird migration issue
Date: Thu, 21 Apr 2016 12:13:00 +0100	[thread overview]
Message-ID: <5718B5BC.5010109@intel.com> (raw)
In-Reply-To: <D33D0948.798E8%belen.barros.pena@intel.com>

Yes I briefly looked into this, and I think it has to do with a memory 
mapping issue. If the database is not closed before trying to run 
database migrate we get into a weird state where there is a transaction 
in memory that can't be completed as the database has been deleted.

This then blocks creating the database until it's gone from memory, the 
only way to do this is seemingly to reboot or use a different location 
on the filesystem for Toaster ...which is kind of worrying, we should 
probably open a django bug about this.

To avoid this make sure that toaster/bitbake is fully stopped before 
running migrate/touching the database file.

Michael

On 20/04/16 10:24, Barros Pena, Belen wrote:
> I've been coming across a problem with migrations occasionally (and rather
> randomly) when I start Toaster. At the beginning it seemed I was the only
> one seeing this. But, while at ELC, someone came to me because they were
> having the same problem. His trace is below. Restarting the host seems to
> solve the problem for me. In his case, he tried a different host and
> everything worked.
>
> It doesn't seem distro-related: his was CentOS, mine Ubuntu. That's all I
> know. Michael Wood looked at this briefly, so he might have something to
> add. It was not a problem when it was just me, but if other people are
> seeing this, then I am bit more worried.
>
> Any ideas on what could be causing it?
>
> Cheers
>
> Belén
>
> File
> "/state/partition1/scratch/tartler/yocto-master/poky/bitbake/bin/../lib/toa
> ster/manage.py", line 10, in <module>
>      execute_from_command_line(sys.argv)
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/core/management/__init__.py", line 354, in
> execute_from_command_line
>      utility.execute()
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/core/management/__init__.py", line 346, in execute
>      self.fetch_command(subcommand).run_from_argv(self.argv)
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/core/management/base.py", line 394, in
> run_from_argv
>      self.execute(*args, **cmd_options)
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/core/management/base.py", line 445, in execute
>      output = self.handle(*args, **options)
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/core/management/commands/migrate.py", line 222, in
> handle
>      executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/db/migrations/executor.py", line 110, in migrate
>      self.apply_migration(states[migration], migration, fake=fake,
> fake_initial=fake_initial)
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/db/migrations/executor.py", line 148, in
> apply_migration
>      state = migration.apply(state, schema_editor)
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/db/backends/base/schema.py", line 93, in __exit__
>      self.atomic.__exit__(exc_type, exc_value, traceback)
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/db/transaction.py", line 228, in __exit__
>      connection.rollback()
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/db/backends/base/base.py", line 183, in rollback
>      self._rollback()
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/db/backends/base/base.py", line 147, in _rollback
>      return self.connection.rollback()
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/db/utils.py", line 98, in __exit__
>      six.reraise(dj_exc_type, dj_exc_value, traceback)
>    File
> "/state/partition1/scratch/tartler/yocto-master/poky/build/venv/lib/python2
> .7/site-packages/django/db/backends/base/base.py", line 147, in _rollback
>      return self.connection.rollback()
> django.db.utils.OperationalError: cannot rollback - no transaction is
> active
> Failed migrations, aborting system start
> Failed start.
>
>



      parent reply	other threads:[~2016-04-21 11:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  9:24 Weird migration issue Barros Pena, Belen
2016-04-20 10:03 ` Smith, Elliot
2016-04-20 10:16   ` Barros Pena, Belen
2016-04-21 11:13 ` Michael Wood [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5718B5BC.5010109@intel.com \
    --to=michael.g.wood@intel.com \
    --cc=Reinhard.Tartler@deshawresearch.com \
    --cc=belen.barros.pena@intel.com \
    --cc=toaster@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.