Hi, The stack is nginx + uwsgi + pylons. Whenever we restart our app, the first request to each uwsgi worker process returns an error. Now this is an easy thing to work around as we are into the habit of hitting the app after a restart (something you would naturally do anyway,) however, curiosity is getting the better of us.
Here are some of the typical errors: - *OperationalError: (OperationalError) (2006, 'MySQL server has gone away')* - *ProgrammingError: (ProgrammingError) (2014, "Commands out of sync; you can't run this command now") * - *ResourceClosedError: This result object does not return rows. It has been closed automatically.* The actual errors are all MySQL but we are guessing it has something to do with the mysterious SQLAlchemy Session, the combination of uwsgi, timeouts while everything spins up or some combination of all of the above. We were wondering if any other pylons developers have experienced a similar behaviour? Cheers -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
