[Maia-users] MySQL error under Xenial

[Ian R. Justman]

Hi, all.

I am in the process of building up a server which is running Xenial
Xerus, coming from Trusty Tahr. However, I'm running into a bit of a snag.

I'm trying to test the server and I'm running into trouble. Everything
else works up until it goes to insert the message received into the
database, whereupon it errors out with the following:

DBD::mysql::st execute failed: Column 'autolearn_status' cannot be null
at /usr/sbin/amavisd-new line 4410, <GEN64> line 53.

I tried the exact same thing on my current production server and it
worked just fine.

Any ideas? I'd like to be able to get what the values of the row that's
about to be inserted.

For some additional reference, the versions of Perl are as follows:

Trusty: 5.18.2-2ubuntu1.1
Xenial: 5.22.1-9

Versions of MySQL (which may also be an issue) are:

Trusty: 5.5.52-0ubuntu0.14.04.1
Xenial: 5.7.16-0ubuntu0.16.04.1

Thanks for any ideas out there!

--Ian.

[Ian R. Justman]

Hi, all.

I found a solution to my issues with MySQL in my installation:

Don't use MySQL at all.

Instead, use MariaDB if you need MySQL compatibility. I don't use PgSQL
in my inventory just yet, so I can't say how well it works.

Hope this helps.

--Ian.

Post by Ian R. Justman
Hi, all.
I am in the process of building up a server which is running Xenial
Xerus, coming from Trusty Tahr. However, I'm running into a bit of a snag.
I'm trying to test the server and I'm running into trouble. Everything
else works up until it goes to insert the message received into the
DBD::mysql::st execute failed: Column 'autolearn_status' cannot be null
at /usr/sbin/amavisd-new line 4410, <GEN64> line 53.
I tried the exact same thing on my current production server and it
worked just fine.
Any ideas? I'd like to be able to get what the values of the row that's
about to be inserted.
Trusty: 5.18.2-2ubuntu1.1
Xenial: 5.22.1-9
Trusty: 5.5.52-0ubuntu0.14.04.1
Xenial: 5.7.16-0ubuntu0.16.04.1
Thanks for any ideas out there!
--Ian.

[Janky Jay, III]

Hi Ian,

Post by Ian R. Justman
Hi, all.
Don't use MySQL at all.
run
Instead, use MariaDB if you need MySQL compatibility. I don't use PgSQL
in my inventory just yet, so I can't say how well it works.
Hope this helps.

Was this a fresh install? The maia db creation file (even the update
file) should set these values to non-NULL (or perhaps "NULL" which is
considered non-null). Was this an update? If so, update from what
version and did you run any upgrade scripts to update the database?

Regards,
Janky Jay, III

[Ian R. Justman]

Post by Janky Jay, III
Hi Ian,

Post by Ian R. Justman
Hi, all.
Don't use MySQL at all.
run
Instead, use MariaDB if you need MySQL compatibility. I don't use PgSQL
in my inventory just yet, so I can't say how well it works.
Hope this helps.

Was this a fresh install? The maia db creation file (even the update
file) should set these values to non-NULL (or perhaps "NULL" which is
considered non-null). Was this an update? If so, update from what
version and did you run any upgrade scripts to update the database?
Regards,
Janky Jay, III

No, this was from an existing setup which worked fine on an older
version of MySQL under Trusty Tahr. And that setup was transplanted
from another, older-yet system running Saucy Salamander(? will have to
verify my old backups).

Besides, I'm thinking of going MariaDB anyway, since we have no idea
what Oracle is going to do with MySQL as I understand that its covenant
to keep it in the GPL may be expiring soon.

As for MySQL and new installations, I can test it by building up another
server to see how that works. More as I get that.

Semi-related, and as one other user said, there's also the issue of
newer versions of PHP, e.g. 7.0 and 7.1, which I can confirm that it
won't work.

Thanks for the followup.

--Ian.