Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

weblate migrate terminated by signal SIGSEGV (Address boundary error) #6328

Closed
Real-Gecko opened this issue Jul 23, 2021 · 5 comments
Closed
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.

Comments

@Real-Gecko
Copy link

Trying to install Weblate 4.7.2 following this instruction leads to aforementioned error on Filling up the database step.

Tried to clone the repo and run project from there, get the same error with manage.py migrate

Describe the steps you tried to solve the problem yourself.

To Reproduce the issue

Steps to reproduce the behavior:

  1. clone the repo
  2. install dependencies
  3. create postgresql db for the project
  4. configure settings.py accordingly
  5. run python manage.py migrate

Expected behavior

Database structure required for project is created.

Screenshots
image

Exception traceback

None, see screenshot.

Server configuration and status

Weblate installation: local from GitHub source code

./manage.py list_versions

  • Weblate: weblate-4.7.2-57-gec27d923ea
  • Django: 3.2.5
  • siphashc: 2.1
  • translate-toolkit: 3.3.6
  • lxml: 4.6.3
  • Pillow: 8.3.1
  • bleach: 3.3.1
  • python-dateutil: 2.8.2
  • social-auth-core: 4.1.0
  • social-auth-app-django: 4.0.0
  • django-crispy-forms: 1.12.0
  • oauthlib: 3.1.1
  • django-compressor: 2.4.1
  • djangorestframework: 3.12.4
  • django-filter: 2.4.0
  • django-appconf: 1.0.4
  • user-agents: 2.2.0
  • filelock: 3.0.12
  • setuptools: 56.0.0
  • jellyfish: 0.8.2
  • openpyxl: 3.0.7
  • celery: 5.1.2
  • kombu: 5.1.0
  • translation-finder: 2.9
  • weblate-language-data: 2021.5
  • html2text: 2020.1.16
  • pycairo: 1.20.1
  • pygobject: 3.40.1
  • diff-match-patch: 20200713
  • requests: 2.26.0
  • django-redis: 5.0.0
  • hiredis: 2.0.0
  • sentry_sdk: 1.3.0
  • Cython: 0.29.24
  • misaka: 2.1.1
  • GitPython: 3.1.19
  • borgbackup: 1.1.17
  • pyparsing: 2.4.7
  • pyahocorasick: 1.4.2
  • python-redis-lock: 3.7.0
  • Python: 3.7.11
  • Git: 2.32.0
  • psycopg2-binary: 2.9.1
  • ruamel.yaml: 0.17.10
  • Redis server: 6.2.5
  • PostgreSQL server: 13.3
  • Database backends: django.db.backends.postgresql
  • Cache backends: default:RedisCache, avatar:FileBasedCache
  • Email setup: django.core.mail.backends.smtp.EmailBackend: localhost
  • OS encoding: filesystem=utf-8, default=utf-8
  • Celery: redis://localhost:6379, redis://localhost:6379, regular
  • Platform: Linux 5.13.4-arch1-1 (x86_64)

PC: Arch Linux, Core i7 7700, 32 GB RAM.

@Real-Gecko Real-Gecko added the question This is more a question for the support than an issue. label Jul 23, 2021
@github-actions
Copy link

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.

In case your question is already answered, making a donation is the right way to say thank you!

@nijel
Copy link
Member

nijel commented Jul 23, 2021

Seems like something is wrong with your hardware (eg. RAM), Python (maybe compiled for different CPU) or some of the Python modules. I'm not sure what is the best approach to debug this, though...

@Real-Gecko
Copy link
Author

Any ideas where to dig? Other Django+PostgreSQL projects work flawlessly. My whole job is built around Django.

@nijel
Copy link
Member

nijel commented Jul 26, 2021

Getting a core dump and looking where it crashes would be a good starting point. See https://wiki.archlinux.org/title/Core_dump

@github-actions
Copy link

github-actions bot commented Aug 6, 2021

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

@github-actions github-actions bot added the wontfix Nobody will work on this. label Aug 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.
Projects
None yet
Development

No branches or pull requests

2 participants