Failing to install on CentOS 7 or Ubuntu 14.04.03

[H R]

Hi,

I've tried to install on VM CentOS 7 minimal following this link:

https://groups.google.com/forum/#!topic/ratticdb/OvTqGAGQuHU

Also tried on a different VM with Ubuntu 14.04.03 using the following link:

http://www.fishley.co.za/2015/08/rattic-password-database-on-ubuntu-14-04-with-apache/

But on both systems, I'm getting the following error when running ./manage.py syncdb --noinput:

[root@passvault RatticWeb]# ./manage.py syncdb --noinput

Traceback (most recent call last):

  File "./manage.py", line 10, in <module>

    execute_from_command_line(sys.argv)

  File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line

    utility.execute()

  File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute

    self.fetch_command(subcommand).run_from_argv(self.argv)

  File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv

    self.execute(*args, **options.__dict__)

  File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute

    output = self.handle(*args, **options)

  File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 415, in handle

    return self.handle_noargs(**options)

  File "/usr/lib/python2.7/site-packages/south/management/commands/syncdb.py", line 68, in handle_noargs

    migrations = migration.Migrations(app_label)

  File "/usr/lib/python2.7/site-packages/south/migration/base.py", line 64, in __call__

    self.instances[app_label] = super(MigrationsMetaclass, self).__call__(app_label_to_app_module(app_label), **kwds)

  File "/usr/lib/python2.7/site-packages/south/migration/base.py", line 90, in __init__

    self.set_application(application, force_creation, verbose_creation)

  File "/usr/lib/python2.7/site-packages/south/migration/base.py", line 154, in set_application

    module = importlib.import_module(self.migrations_module())

  File "/usr/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module

    __import__(name)

  File "/usr/lib/python2.7/site-packages/kombu/transport/django/migrations/__init__.py", line 16, in <module>

    raise ImproperlyConfigured(SOUTH_ERROR_MESSAGE)

django.core.exceptions.ImproperlyConfigured:

For South support, customize the SOUTH_MIGRATION_MODULES setting

to point to the correct migrations module:

    SOUTH_MIGRATION_MODULES = {

        'kombu_transport_django': 'kombu.transport.django.south_migrations',

    }

Anyone know what might be the issue? 

Thanks,

H

[Arie Koppelaar]

Hi,

I've been struggling with this installation for days now as well. Tried to install using this CenOS manual and this Ubuntu Manual. It's been a  couple of late nights, and now I'm doubting my sanity. I checked and re-checked the installation manuals, on GitHub as well, but it always goes wrong as pointed out, when starting ./manage.py syncdb --noinput and ending with ./manage.py demosetup.

I would really like to use this great password management solution.

Regards, and many thanks for any help and response.

Arie

Op zaterdag 17 oktober 2015 16:43:01 UTC schreef H R:

[H R]

Might be related to this:

https://github.com/celery/kombu/pull/510

[Paul Tötterman]

Anyone know what might be the issue?

I've never written any web services using Django, so take the following with a grain of salt:

Django 1.7+ features built-in migrations

With django < 1.7, one had to use south for migrations

Rattic specifies (in requirements.txt) django < 1.7 and south < 0.9

Both django 1.7+ migrations and south look for migrations in a python package (i.e a directory) called 'migrations'. In order to avoid collisions, south 1.0+ (compatible with django 1.7+ ?) recommends that the old south-specific content of the 'migrations' directory be moved to a directory called 'south_migrations' so that django 1.7+ can have the 'migrations' directory. Now, I'm not sure how to properly tell south < 1.0 to look for its migrations in 'south_migrations' in the modules (apps?) kombu and djcelery. But I did use force and got it running:

cd /usr/local/lib/python2.7/dist-packages # this path probably varies from system to system

rm -rf kombu/transport/django/migrations djcelery/migrations

mv kombu/transport/django/south_migrations kombu/transport/django/migrations

mv djcelery/south_migrations djcelery/migrations

I'd appreciate it if someone educated me in the proper way of going about his.

Cheers,

Paul

[Leonardo Cunil]

Sadly, that doesn't worked for me :(

It did the import and I can see the data on mysql and didn't get thrown all those python migration errors. Issue now is, http://i.imgur.com/bClQ4ex.png

[Arie Koppelaar]

Would be nice if someone could post an installation howto for non-python people. I'm used to install all sorts of software on (Ubuntu) Linux servers, but this seems to be too complex because of it's Python dependencies. In my opinion it is a good starting point to use apt/yum package management where possible. 

Op zaterdag 17 oktober 2015 18:43:01 UTC+2 schreef H R:

[Andre Stefanovic]

For me on Centos 7 this helped  https://github.com/groventure/docker-ratticdb-uwsgi/issues/1
Took requirements-base.txt from https://github.com/csakoda/RatticWeb

[Paul Tötterman]

Would be nice if someone could post an installation howto for non-python people. I'm used to install all sorts of software on (Ubuntu) Linux servers, but this seems to be too complex because of it's Python dependencies. In my opinion it is a good starting point to use apt/yum package management where possible. 

May I suggest (like Andre) that you look at available rattic dockerfiles. Those should contain a set of repeatable steps. So if you can build a functioning docker image using a dockerfile, you should be able to examine the dockerfile to figure out what you need to do. I just happened to have time to finish my own Docker packaging of Rattic (<https://github.com/ptman/rattic-docker>) which is ubuntu 14.04 based and avoids running both the wsgi processes and a web server in the same container. But it is just one of many available (<https://hub.docker.com/search/?q=rattic&isAutomated=0>) dockerfiles that can provide the answers you seek.

Cheers,

Paul

[Andrew Meyer]

I got it working.  But i'm building it at home and having trouble setting up Apache to proxy the request or redirect it.  I can share what I have...

[Andrew Meyer]

Ok maybe one of you can help me get my apache config to work.

I have confluence, gitlab and 1 other application running on my web server.  Confluence is proxied to a back-end tomcat app running on another port.  But how would I setup RatticDB to work in this situation.

<VirtualHost 10.150.1.65>

LoadModule wsgi_module modules/mod_wsgi.so

ServerName rattic.borg.local

ServerAlias rattic

Alias / /opt/apps/RatticWeb/ratticweb/

Options +Multiviews +FollowSymLinks

Redirect permanent / http://rattic.borg.local/

DocumentRoot /opt/apps/RatticWeb/ratticweb/

#Once you have the redirect setup, configure Apache to serve RatticDB and its static assets as follows:

Alias /robots.txt /opt/apps/RatticWeb/static/robots.txt

Alias /favicon.ico /opt/apps/RatticWeb/static/favicon.ico

AliasMatch ^/([^/]*\.css) /opt/apps/RatticWeb/static/styles/$1

Alias /media/ /opt/apps/RatticWeb/media/

Alias /static/ /opt/apps/RatticWeb/static/

<Directory /opt/apps/RatticWeb/static>

Order deny,allow

Allow from all

<RequireAny>

       Require ip 10.0.0.0/8 192.168.0.0/16 172.16.0.0/16

       Require ip ::1

</RequireAny>

</Directory>

<Directory /opt/apps/RatticWeb/media>

Order deny,allow

Allow from all

<RequireAny>

       Require ip 10.0.0.0/8 192.168.0.0/16 172.16.0.0/16

       Require ip ::1

</RequireAny>

</Directory>

WSGIScriptAlias / /opt/apps/RatticWeb/ratticweb/wsgi.py

WSGIPassAuthorization On

WSGIDaemonProcess rattic processes=2 threads=25 home=/opt/apps/RatticWeb/ python-path=/opt/apps/RatticWeb display-name=%{GROUP}

WSGIProcessGroup rattic

<Directory /opt/apps/RatticWeb/ratticweb>

  <Files wsgi.py>

    Order deny,allow

    Allow from all

        <RequireAny>

        Require ip 10.0.0.0/8 192.168.0.0/16 172.16.0.0/16

        Require ip ::1

        </RequireAny>

  </Files>

</Directory>

</VirtualHost>