You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I've got an issue where on the initial database upgrade, ihatemoney exits after having done the upgrade.
I'm expecting gunicorn to "survive" and create new workers after that, and not have the user manually restart ihatemoney, right ?
Here is the syslog :
May 22 19:49:09 salamandar.fr ihatemoney[13368]: [2021-05-22 19:49:09 +0200] [13368] [INFO] Starting gunicorn 20.1.0
May 22 19:49:09 salamandar.fr ihatemoney[13368]: [2021-05-22 19:49:09 +0200] [13368] [INFO] Listening at: unix:/tmp/budget.gunicorn_ihatemoney__2.sock (13368)
May 22 19:49:09 salamandar.fr ihatemoney[13368]: [2021-05-22 19:49:09 +0200] [13368] [INFO] Using worker: sync
May 22 19:49:09 salamandar.fr ihatemoney[13368]: [2021-05-22 19:49:09 +0200] [13375] [INFO] Booting worker with pid: 13375
May 22 19:49:09 salamandar.fr ihatemoney[13368]: [2021-05-22 19:49:09 +0200] [13377] [INFO] Booting worker with pid: 13377
May 22 19:49:09 salamandar.fr ihatemoney[13368]: [2021-05-22 19:49:09 +0200] [13379] [INFO] Booting worker with pid: 13379
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Context impl MySQLImpl.
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Will assume non-transactional DDL.
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Context impl MySQLImpl.
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Will assume non-transactional DDL.
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Running upgrade -> b9a10d5d63ce, Initial migration
May 22 19:49:12 salamandar.fr ihatemoney[13368]: /var/www/ihatemoney__2/venv/lib/python3.7/site-packages/pymysql/cursors.py:170: Warning: (1280, "Name 'alembic_version_pkc' ignored for PRIMARY key.")
May 22 19:49:12 salamandar.fr ihatemoney[13368]: result = self._query(query)
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Running upgrade -> b9a10d5d63ce, Initial migration
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Context impl MySQLImpl.
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Will assume non-transactional DDL.
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Running upgrade -> b9a10d5d63ce, Initial migration
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Running upgrade b9a10d5d63ce -> 26d6a218c329, Add Person.weight column
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Running upgrade 26d6a218c329 -> f629c8ef4ab0, Initialize all members weights to 1
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Running upgrade f629c8ef4ab0 -> b78f8a8bdb16, hash project passwords
May 22 19:49:12 salamandar.fr ihatemoney[13368]: [2021-05-22 19:49:12 +0200] [13368] [WARNING] Worker with pid 13375 was terminated due to signal 15
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Running upgrade b78f8a8bdb16 -> afbf27e6ef20, add bill.import_date field
May 22 19:49:12 salamandar.fr ihatemoney[13368]: INFO [alembic.runtime.migration] Running upgrade afbf27e6ef20 -> a67119aa3ee5, Migrate negative weights
May 22 19:49:13 salamandar.fr ihatemoney[13368]: [2021-05-22 19:49:13 +0200] [13368] [INFO] Shutting down: Master
May 22 19:49:13 salamandar.fr ihatemoney[13368]: [2021-05-22 19:49:13 +0200] [13368] [INFO] Reason: Worker failed to boot.
May 22 19:49:13 salamandar.fr systemd[1]: ihatemoney__2.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
The text was updated successfully, but these errors were encountered:
Hi,
I've got an issue where on the initial database upgrade, ihatemoney exits after having done the upgrade.
I'm expecting gunicorn to "survive" and create new workers after that, and not have the user manually restart ihatemoney, right ?
Here is the syslog :
The text was updated successfully, but these errors were encountered: