Bug 16393

Summary: mysql error 1171 in Web installer Step 3
Product: Koha Reporter: g.meyer
Component: Installation and upgrade (web-based installer)Assignee: Bugs List <koha-bugs>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: major    
Priority: P2 CC: flittle, gmcharlt, jonathan.druart, katrin.fischer
Version: 3.22   
Hardware: PC   
OS: Linux   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16402
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description g.meyer 2016-04-29 08:07:52 UTC
Web installer Step 3 displays the following mysql error:

"The following error occurred while importing the database structure:

mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 1171 (42000) at line 1385: All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead "

These are the informations from Step 2
"Database settings:

    database type : mysql
    database name : koha_library
    database host : localhost
    database port : 3306 (probably OK if blank)
    database user : koha_library

Connection established.

Database koha_library exists.

User koha_library has all required privileges on database koha_library."
Comment 1 flittle 2016-05-04 09:23:03 UTC
Hi, I have this issue also, trying to install koha on a fresh ubuntu 16.04 install, MySQL 5.7.12.

Same message in the web installer:

mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 1171 (42000) at line 1385: All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead
Comment 2 Katrin Fischer 2016-05-04 19:35:22 UTC
Can you continue the web installer after this warning?
Comment 3 flittle 2016-05-05 10:16:00 UTC
(In reply to Katrin Fischer from comment #2)
> Can you continue the web installer after this warning?

Hi, no it will not continue.
Comment 4 g.meyer 2016-05-05 11:09:09 UTC
For me it is exactly the same.
Comment 5 Katrin Fischer 2016-05-06 06:07:03 UTC
Please take a look at bug 16402 for a possible fix!
Comment 6 Jonathan Druart 2016-05-06 13:29:36 UTC

*** This bug has been marked as a duplicate of bug 16402 ***