OperationalError: database is locked

[Joe]

Hello,

We periodically get this lock error. Im running review board 1.7.22. 

Best regards,  

Joe.

--

Traceback (most recent call last):

  File "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/core/handlers/base.py", line 111, in get_response
    response = callback(request, *callback_args, **callback_kwargs)

  File "/usr/local/lib/python2.6/dist-packages/Djblets-0.7.28-py2.6.egg/djblets/auth/util.py", line 47, in _checklogin
    return view_func(request, *args, **kwargs)

  File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/site/decorators.py", line 35, in _check
    return view_func(request, local_site=local_site, *args, **kwargs)

  File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/accounts/decorators.py", line 53, in _check_valid_prefs
    return view_func(request, *args, **kwargs)

  File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/reviews/views.py", line 828, in dashboard
    'sidebar_counts': get_sidebar_counts(request.user, local_site),

  File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.22-py2.6.egg/reviewboard/reviews/datagrids.py", line 803, in get_sidebar_counts
    profile=profile)

  File "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/fields/related.py", line 493, in get_or_create
    return super(RelatedManager, self.db_manager(db)).get_or_create(**kwargs)

  File "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/manager.py", line 134, in get_or_create
    return self.get_query_set().get_or_create(**kwargs)

  File "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/query.py", line 452, in get_or_create
    obj.save(force_insert=True, using=self.db)

  File "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/base.py", line 463, in save
    self.save_base(using=using, force_insert=force_insert, force_update=force_update)

  File "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/models/base.py", line 555, in save_base
    transaction.commit_unless_managed(using=using)

  File "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/transaction.py", line 135, in commit_unless_managed
    connection.commit_unless_managed()

  File "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/backends/__init__.py", line 214, in commit_unless_managed
    self._commit()

  File "/usr/local/lib/python2.6/dist-packages/Django-1.4.10-py2.6.egg/django/db/backends/__init__.py", line 50, in _commit
    return self.connection.commit()

OperationalError: database is locked


<ModPythonRequest
path:/reviews/dashboard/,
GET:<QueryDict: {}>,
POST:<QueryDict: {}>,
COOKIES:{'collapsediffs': 'True',
 'csrftoken': '5a764b26f0910188c3e86cf96567dea7',
 'rbsessionid': '6880c2e09e0002d305c304b9282eb587'},
META:{'AUTH_TYPE': None,
 'CONTENT_LENGTH': 0,
 'CONTENT_TYPE': None,
 'GATEWAY_INTERFACE': 'CGI/1.1',
 'HTTP_ACCEPT': 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
 'HTTP_ACCEPT_ENCODING': 'gzip, deflate',
 'HTTP_ACCEPT_LANGUAGE': 'en-US,en;q=0.5',
 'HTTP_CONNECTION': 'keep-alive',
 'HTTP_COOKIE': 'rbsessionid=6880c2e09e0002d305c304b9282eb587; csrftoken=5a764b26f0910188c3e86cf96567dea7; collapsediffs=True',
 'HTTP_HOST': 'daytona',
 'HTTP_REFERER': 'http://daytona/reviews/account/preferences/',
 'HTTP_USER_AGENT': 'Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0',
 'PATH_INFO': u'/reviews/dashboard/',
 'PATH_TRANSLATED': None,
 'QUERY_STRING': None,
 'REMOTE_ADDR': '172.16.56.188',
 'REMOTE_HOST': None,
 'REMOTE_IDENT': None,
 'REMOTE_USER': None,
 'REQUEST_METHOD': 'GET',
 'SCRIPT_NAME': '',
 'SERVER_NAME': 'daytona.us.megatrends.com',
 'SERVER_PORT': 80,
 'SERVER_PROTOCOL': 'HTTP/1.1',
 'SERVER_SOFTWARE': 'mod_python'}>

[Adam Collard]

Hi Joe,

What database are you using for this? I would guess SQLite from the error. That's not advisable for anything but a test/dev setup (you should use PostgreSQL or MySQL in production)

Regards, Adam

--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
---
You received this message because you are subscribed to the Google Groups "reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jothiram Selvam]

Hi Adam,

Thanks for the tip.

I am just searching for steps to do the migration. Any pointers there would be helpful. And which would be a better option for linux system - PostgreSQL or MySQL.

Best regards,  

Joe.

You received this message because you are subscribed to a topic in the Google Groups "reviewboard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/reviewboard/XB0GmcmSH2k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to reviewboard...@googlegroups.com.