Traceback attempted server start

[Adam Sechrest]

Hello, folks.

My setup:  Linux Mint 17.1, completely fresh install of Evennia.

I get the following traceback when attempting a server start:

Traceback (most recent call last):
  File "/usr/local/bin/evennia", line 10, in <module>
    execfile(__file__)
  File "/home/adam/Development/evennia/bin/unix/evennia", line 10, in <module>
    main()
  File "/home/adam/Development/evennia/evennia/server/evennia_launcher.py", line 999, in main
    init_game_directory(CURRENT_DIR, check_db=True)
  File "/home/adam/Development/evennia/evennia/server/evennia_launcher.py", line 678, in init_game_directory
    check_database()
  File "/home/adam/Development/evennia/evennia/server/evennia_launcher.py", line 499, in check_database
    create_superuser()
  File "/home/adam/Development/evennia/evennia/server/evennia_launcher.py", line 447, in create_superuser
    django.core.management.call_command("createsuperuser", interactive=True)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 120, in call_command
    return command.execute(*args, **defaults)
  File "/usr/local/lib/python2.7/dist-packages/django/contrib/auth/management/commands/createsuperuser.py", line 50, in execute
    return super(Command, self).execute(*args, **options)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 441, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python2.7/dist-packages/django/contrib/auth/management/commands/createsuperuser.py", line 149, in handle
    self.UserModel._default_manager.db_manager(database).create_superuser(**user_data)
  File "/usr/local/lib/python2.7/dist-packages/django/contrib/auth/models.py", line 191, in create_superuser
    **extra_fields)
  File "/usr/local/lib/python2.7/dist-packages/django/contrib/auth/models.py", line 182, in _create_user
    user.save(using=self._db)
  File "/home/adam/Development/evennia/evennia/utils/idmapper/models.py", line 369, in save
    super(SharedMemoryModel, self).save(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/base.py", line 710, in save
    force_update=force_update, update_fields=update_fields)
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/base.py", line 738, in save_base
    updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/base.py", line 822, in _save_table
    result = self._do_insert(cls._base_manager, using, fields, update_pk, raw)
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/base.py", line 861, in _do_insert
    using=using, raw=raw)
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/manager.py", line 127, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py", line 920, in _insert
    return query.get_compiler(using=using).execute_sql(return_id)
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/sql/compiler.py", line 963, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/utils.py", line 97, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/sqlite3/base.py", line 318, in execute
    return Database.Cursor.execute(self, query, params)
django.db.utils.IntegrityError: NOT NULL constraint failed: players_playerdb.last_login

There is a fragment in the Getting Started, "Setting Up Your Game" section.  My database file exists in mygame/server, but I don't know if this might be the issue, because it directs to enter a command to set up the DB file but then doesn't specify the command:

You will see the game database being created. If you are converting from an existing Evennia database you might get questions about removing certain models - answer "yes" to those questions. Next, enter the following command in a terminal or shell to create the database file (in the case of SQLite3) 

Any ideas?  Thank you in advance.

-Adam 

[Brian Petty]

I actually had this same error tonight when loading up the server that I'm working on.  (I'm in a Windows environment, just so you know.  Don't think it matters in this case.)  I had forgotten to fire up the virtual environment, and so it was running with Django 1.8, which apparently doesn't like anything being NoneType.  I fired up vienv, and it ran using 1.7, and I didn't have any more problems.

[Griatch Art]

Django 1.8 was released yesterday and Evennia is not yet tested with it. Use 1.7 for now until we get around to upgrade, that should work normally.
.
Griatch

[Adam Sechrest]

Aha, thus the 1.8 warning.

Thank you both. Will try tonight.

--
--
You received this message because you are subscribed to the "Evennia" MU* server mailing list.
To post to this group, send email to eve...@googlegroups.com (or use the web interface).
To unsubscribe from this group, send email to evennia+u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/evennia?hl=en

---
You received this message because you are subscribed to a topic in the Google Groups "Evennia" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/evennia/5ZIFMb2cwwY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to evennia+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.