Lasso 9.2.3 64Bit CentOS 6.3

Today I decided to swap from using the internal SQLite DB to an external MySQL DB.

Our SQL Server is a separate machine, that Lasso (this instance) talks to all the time without issue.. It is the main DB server for our site.. currently 99% idle.

I went into Lasso Admin - > Sessions and changed from SQLite to MySQL, Selected our DB name and clicked the 'Create Sessions Table' button, then the 'Select as Default Driver' button.

It then changed the wording of each pulldown menu to have (Default) next to each of my selected items.

I then rebooted the server completely (Lasso) and tested.. within 3 mins Lasso was at 100% CPU and stopped service requests under normal load. MySQL Server was still mostly idle (97%).

Rebooting resulted in the same thing happening.. and after 4 reboots over an hour I have reverted back to SQLite and havent seen the problem since.

I do notice that this same sort of thing has been mentioned in another previous thread (Moving sessions to external server - Jim Sheffer) "So now I have sessions running externally but now have a problem with Lasso eating 190%+ CPU. This happens quickly after restart (A matter of a few minutes)"

I used to run an external sessions DB with LP8.5.6 with no issues.. So far I dont have a clue what the problem is here. MySQL is responsive to queries etc when lasso is not responding.

Simple fix in the meantime is not to use external sessions, but thats not a real fix. Is anyone successfully using external sessions using Lassos session management and auto built database?

Daniel Parker
#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso
Lasso@lists.lassosoft.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>