PDA

View Full Version : mysql errors?



jvilhuber
2005-07-12, 13:01
Every night, when I have the rescan scheduled, the server crashes
with the following type of message:

DBD::mysql::st execute failed: Cannot delete or update a parent row:
a foreign key constraint fails at /usr/local/slimserver/
SlimServer_v2005-07-06/CPAN/DBIx/ContextualFetch.pm line 51.

Any clues on what the issue might be? I recently switched to mysql
for (hopefully) improved performance (I have over 9000 songs), so
maybe I did something wrong setting up the DB in mysql...

The slimserver has the following privileges: SELECT, INSERT, UPDATE,
DELETE, CREATE, DROP, FILE, INDEX, ALTER, CREATE TEMPORARY TABLES

jan

kdf
2005-07-12, 13:05
Quoting Jan Vilhuber <jan (AT) vilhuber (DOT) com>:

> Every night, when I have the rescan scheduled, the server crashes
> with the following type of message:
>
> DBD::mysql::st execute failed: Cannot delete or update a parent row:
> a foreign key constraint fails at /usr/local/slimserver/
> SlimServer_v2005-07-06/CPAN/DBIx/ContextualFetch.pm line 51.
>
> Any clues on what the issue might be? I recently switched to mysql
> for (hopefully) improved performance (I have over 9000 songs), so
> maybe I did something wrong setting up the DB in mysql...

mysql is not officially supported, and the word on the street is that
performance is usually not as good. The reason for using mysql is primarily
convenience, as some users already have it running for other purposes.

Are you using the latest nightly build?

-kdf

jvilhuber
2005-07-12, 14:28
On Jul 12, 2005, at 1:05 PM, kdf wrote:

> Quoting Jan Vilhuber <jan (AT) vilhuber (DOT) com>:
>
>
>> Every night, when I have the rescan scheduled, the server crashes
>> with the following type of message:
>>
>> DBD::mysql::st execute failed: Cannot delete or update a parent row:
>> a foreign key constraint fails at /usr/local/slimserver/
>> SlimServer_v2005-07-06/CPAN/DBIx/ContextualFetch.pm line 51.
>>
>> Any clues on what the issue might be? I recently switched to mysql
>> for (hopefully) improved performance (I have over 9000 songs), so
>> maybe I did something wrong setting up the DB in mysql...
>>
>
> mysql is not officially supported, and the word on the street is that
> performance is usually not as good.

Interesting. I would have (and did) assumed otherwise.

> The reason for using mysql is primarily
> convenience, as some users already have it running for other purposes.
>
> Are you using the latest nightly build?
>

Just upgraded to it. We'll see if it crashes again tonight at 4am :)

jan


> -kdf
>

kdf
2005-07-12, 14:35
Quoting Jan Vilhuber <jan (AT) vilhuber (DOT) com>:

> > mysql is not officially supported, and the word on the street is that
> > performance is usually not as good.
>
> Interesting. I would have (and did) assumed otherwise.

If you do find it faster, please report back. Its not like there are dozens of
data points so far :)

> > The reason for using mysql is primarily
> > convenience, as some users already have it running for other purposes.
> >
> > Are you using the latest nightly build?
> >
>
> Just upgraded to it. We'll see if it crashes again tonight at 4am :)

There are a couple of reported bugs involving mysql that may apply:

http://bugs.slimdevices.com/show_bug.cgi?id=1799
http://bugs.slimdevices.com/show_bug.cgi?id=947

-kdf