Can't start via systemd

To me this looks like a path / environment issue.

Okay but why should django try to use SQLite? Or isn’t it trying to use it? But why shouldn’t it find the tables then?

Because it’s the default.

Because no database has been initialised.

Wouldn’t that mean seahub_settings.py is ingored? What could be a solution?

Anything to watch out for when upgrading to Debian Stretch?

Keep in mind that they switched from MySQL to MariaDB as the default MySQL server. In theory, the upgrade should work without problems but you can’t be 100% sure before noticing the changes. See https://mariadb.com/kb/en/mariadb/moving-from-mysql-to-mariadb-in-debian-9/

I use MariaDB since it’s stable already, so nothing to change here. :slight_smile:

No issues upgrading to Stretch, including switch to systemd, Docker LE etc…