Hi Torben,
I havent seen the DB error since I updated to Snapshot 5026 last week.
I will continue to monitor the logfile and keep you informed
Hi Torben,
I did not have any DB errors registered in 5026.
I have updated to 5027 this morning, and will continue to monitor.
1 Like
Hi Torben,
I got this error in Build 5028 today, when generating a new playlist.
Would you like to get the bugreport?
{“Timestamp”:“2022-05-21T07:47:35.680”,“Message”:“Error creating playlist cache file C:\ProgramData\mAirList\7.x\PlaylistCache\{05549F0C-40C4-42C7-878E-9602C3EEAF38}\1\2022-05-21-23.mlp: [FireDAC][Phys][SQLite] ERROR: database is locked”,“Level”:“Error”}
Yes, please send me the report. I want to fix this for good.
Thanks. I have uploaded the bugreport.
I just got the same error again after creating a new playlist. I have uploaded the bugreport.
What is that?
A bugreport have been uploaded.
Thank you. Torben will have a look on the report when he is back in the office.
I dont know if this error has been reported… This one occurs when an MLDB is being fully cloned / exported to MySQL/MariaDB using old AND new version (doenst matter which one chosen.
SQL Error: FireDAC Phys MySQL Specified key was too long; max key length is 3072 bytes. Query CREATE INDEX auth_tokens_scopedid_token_idx ON auth_tokens (scope_id, token).
I guess it could be relative easily debugged , since the referred command is being displayed. 
Kind regards
Vincent
Thank you, please try again in upcoming snapshot 5030 and report back.
Not related to the DB but rather something in the image processing library (we switched all internal icons to SVG). I’ll look into it.
Made yet another small change in snapshot 5030. Please report back.
I have installed 5030 yesterday. I will be monitoreing for errors.
1 Like
It continues, but further in the cloning process it gives another error:
FireDAC Phys Mysql Data too long for column value’ at row 1. I also send a bug report through the builti-in system.
Hi Torben,
I have uploaded a bugreport to you, besed on this error.
{“Timestamp”:“2022-06-04T10:00:00.144”,“Message”:“Error writing log entry into database Database: [FireDAC][Phys][SQLite] ERROR: database is locked”,“Level”:“Error”}
I am running release 5032.
Apparently some data is too large for a table column in MySQL. Can you tell from the progress dialog which table it is?
Do you have any album art stored as icons? Does it also happen when you omit the icons in the cloning process?
Yes I omit the icons. I can’t see which table it is. It display;s only x records out of maximum of y records. Is there a way to debug log this?
Sorry to dig up an old topic but I encounter a lot of this “database locked” error during mairlist execution with my version (the latest release update).
And the real problem is that, sometimes, this error generates a silent on air between two tracks…
Here is an extract of the today log :
|2024-07-28 17:45:20|Playlist|Start: D:\HABILLAGE\HABILLAGE 02\JINGLE COURT 13.mp3|
|---|---|---|
|2024-07-28 17:45:23|Playlist|Stop: D:\SONGS\HEAVEN-ORIGINAL\Avril Lavigne - When You-'re Gone.flac (233 seconds)|
|2024-07-28 17:45:27|Playlist|Start: D:\SONGS\HEAVEN-ORIGINAL\Jean-Jacques Goldman - Quand la musique est bonne.flac|
|2024-07-28 17:45:28|Playlist|Stop: D:\HABILLAGE\HABILLAGE 02\JINGLE COURT 13.mp3 (8 seconds)|
|2024-07-28 17:49:04|Debug|Caching playlists for Heaven REWIND / REPLAY|
|2024-07-28 17:49:04|Playlist|Start: D:\HABILLAGE\HABILLAGE 01\JINGLE COURT 4.WAV|
|2024-07-28 17:49:06|Playlist|Stop: D:\SONGS\HEAVEN-ORIGINAL\Jean-Jacques Goldman - Quand la musique est bonne.flac (219 seconds)|
|2024-07-28 17:49:14|Error|Error writing log entry into database Heaven REWIND / REPLAY: [FireDAC][Phys][SQLite] ERROR: database is locked|
|2024-07-28 17:49:15|Playlist|Stop: D:\HABILLAGE\HABILLAGE 01\JINGLE COURT 4.WAV (10 seconds)|
|2024-07-28 17:49:24|Error|Error writing log entry into database Heaven REWIND / REPLAY: [FireDAC][Phys][SQLite] ERROR: database is locked|
|2024-07-28 17:49:24|Playlist|Start: D:\SONGS\HEAVEN-ORIGINAL\Hoobastank - If I Were You.flac|
As you can see at the end, there are 2 “database is locked” errors. The problem is that at this moment, the track “Hoobastank - If I Ware You” took 9 seconds to start (at 17:49:24) after the previous track ended (jingle that ended at 17:49:15). I had a silent on air, that is not very good !!!
This kind of error occured at other moment of the day, but if I check the log time, it seems there was no silent on air…
I use Mairlist 7.3.6 build 5650.
Any idea to fix it ?
(One more question: if I upgrade to mairlist advanced server with mairlistDB server, will this issue occur again ? or will it be better ?)
Regards,
Sylvain
If you’re using the “local db” function your database is only stored in a plain text file for sqlite.
When more than one instance (e.g. playout and separate database app, two playout instances on different PC or playout on PC and database app on a second one) are trying to access this file at the same time via windows only one of them can and then the file is then blocked for all others.
This will not happen when you’re using the db server because it will bundle the requests of all instances and only one connection is used to access the text file.
2 Likes