![]() ![]() ![]() Is there anything I can do to ensure the SQL will work? I'm running MySQL 8.0.31 on Ubuntu Server 20.04.5 LTS. I found only very old mentions of this error. Certainly no other processes are running that affect this database. I can't imagine why there would be a deadlock on that that table at that time of night. I tried changing that to:ĭELETE FROM playlist_track where id in (select id from playlist_track) īut that turned up the same error the next day. The failing statement is one of the first in /usr/share/squeezeboxserver/SQL/mysql/schema_clear.sql. Sessions will typically run globally with each page load, so the Session class should either be initialized in your controller constructors, or it can be auto-loaded by the system. restarting transaction nested exception is .jdbc4. ![]() I then need to do a manual rescan, which always succeeds. MySQLTransactionRollbackException: Deadlock found when trying to get lock. However, more often than not, te rescan fails with:Įrror: Couldn't execute SQL statement: : at /usr/share/perl5/Slim/Schema/Storage.pm line 125]Īnd my music collection appears completely empty. A while ago I switched from SQLite to MySQL. : : Deadlock found when trying to get lock try restarting transaction at .convert (AbstractEntityManagerImpl.java:1377) at .convert (AbstractEntityManagerImpl.java:1300) a. Both will burn lots of AUTOINCREMENT ids, but the latter is probably less prone to deadlock. I do a full automatic wipe and rescan at 5:00 daily. 1 Answer 1 Instead of IODKU, use INSERT IGNORE. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |