[danomac]

Probably shouldn't resurrect an old post like this one, but it's the only one Google turns up.

I finally upgraded to 13.2, and got the dreaded:

Code:

ERROR: SQL: Undefined MySQL error: Code (1419)

There's a really easy way to fix this without granting SUPER privileges. I read into the SUPER privilege and it allows for things like killing mysql threads to accounts other than your own, as well as modifying global settings in mysql. This really shouldn't be enabled on a user account, especially since I also use mysql for mythtv and I don't want them to be able to trash each other's databases.

I'm using mariadb, I tried going to mysql and it made no difference (despite what the bugtracker says.)

That error is telling you binary logging is enabled on the server. It is generally used for replication, so on most XBMC installs you don't need it.

Anyway, a quicker way is to check the status. In the mysql client check this parameter (you'll need to be root most likely):

Code:

mysql> show global variables like 'log_bin_trust_function_creators';
+---------------------------------+-------+
| Variable_name                   | Value |
+---------------------------------+-------+
| log_bin_trust_function_creators | OFF   |
+---------------------------------+-------+
1 row in set (0.00 sec)

As you can see it's set to off.

BEFORE running xbmc, go to the mysql backend and set it with the client:

Code:

mysql> SET GLOBAL log_bin_trust_function_creators = 1;
Query OK, 0 rows affected (0.00 sec)

Then check it:

Code:

mysql> show global variables like 'log_bin_trust_function_creators';
+---------------------------------+-------+
| Variable_name                   | Value |
+---------------------------------+-------+
| log_bin_trust_function_creators | ON    |
+---------------------------------+-------+
1 row in set (0.00 sec)

Make sure the incomplete tables are dropped, then run XBMC and let it do its upgrade. When it's done, set it back the way it was:

Code:

mysql> SET GLOBAL log_bin_trust_function_creators = 0;
Query OK, 0 rows affected (0.00 sec)

Hopefully this will help someone else.