sqlalchemy.exc.OperationalError

sqlalchemy.exc.OperationalError: (MySQLdb._exceptions.OperationalError) (2006, 'MySQL server has gone away') [SQL: SELECT author.id AS author_id, author.name AS author_name, author.surname AS author_surname FROM author WHERE author.id = %s] [parameters: (82,)] (Background on this error at: http://sqlalche.me/e/e3q8)

Traceback (most recent call last)

sqlalchemy.exc.OperationalError: (MySQLdb._exceptions.OperationalError) (2006, 'MySQL server has gone away') [SQL: SELECT author.id AS author_id, author.name AS author_name, author.surname AS author_surname FROM author WHERE author.id = %s] [parameters: (82,)] (Background on this error at: http://sqlalche.me/e/e3q8)

This is the Copy/Paste friendly version of the traceback. You can also paste this traceback into a gist:

The debugger caught an exception in your WSGI application. You can now look at the traceback which led to the error. If you enable JavaScript you can also use additional features such as code execution (if the evalex feature is enabled), automatic pasting of the exceptions and much more.

Console Locked

The console is locked and needs to be unlocked by entering the PIN. You can find the PIN printed out on the standard output of your shell that runs the server.

PIN: