Appion

Does anybody else get this when making a new stack from selected particles from an alignment?
... Assembling database insertion command
... Inserting particle information into database
Traceback (most recent call last):
File "/panfs/storage.local/imb/stagg/software/myami-3.2/appion/bin/alignSubStack.py", line 314, in <module>
subStack.start()
File "/panfs/storage.local/imb/stagg/software/myami-3.2/appion/bin/alignSubStack.py", line 306, in start
apStack.commitSubStack(self.params,included=includeParticle)
File "/panfs/storage.local/imb/stagg/software/myami-3.2/appion/appionlib/apStack.py", line 569, in commitSubStack
sinedon.directq.complexMysqlQuery('appiondata',sqlcmd)
File "/panfs/storage.local/imb/stagg/software/myami-3.2/sinedon/directq.py", line 24, in complexMysqlQuery
results = cur.selectall(query)
File "/panfs/storage.local/imb/stagg/software/myami-3.2/sinedon/sqldb.py", line 42, in selectall
self.c.execute(strSQL, param)
File "/usr/lib64/python2.7/site-packages/MySQLdb/cursors.py", line 174, in execute
self.errorhandler(self, exc, value)
File "/usr/lib64/python2.7/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
raise errorclass, errorvalue
_mysql_exceptions.OperationalError: (2006, 'MySQL server has gone away')>

If I revert to myami-3.1, there is no problem because it does the inserts one at a time instead of making one big MySQL insert statement. This only seems to happen for bigger stacks.