Thanks, Gerald, for your response. From the documentation I thought I'd be in good shape. I've set up the test server with OTRS 3.1, stopped services and copied over my config files from the 3.0.11 server: /opt/otrs/Kernel/Config.pm /opt/otrs/Kernel/Config/GenericAgent.pm /opt/otrs/Kernel/Config/Files/ZZZAuto.pm The database from 3.0.11 is restored to a database called otrs3, and although I could use any username I added a user to the otrs3 database with the same name and password as the production server and granted all privileges to otrs3. I've logged onto MySQL using the new credentials and made some table queries to make sure I can see the database properly with the credentials that match the restored Config.pm file. Obviously root works as well. When I ran the command cat scripts/DBUpdate-to-3.1.mysql.sql | mysql -p -f -u root otrs3 The script ran but yielded the following errors: ERROR 1005 (HY000) at line 225: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 226: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 227: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 229: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 230: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 234: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 235: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 237: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 238: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 239: Can't create table 'otrs3.#sql-e40_45' (errno: 150) MySQL documentation says this error (1005 with errno 150) results when a foreign key constraint is not correctly formed. I can see in the script that these line numbers are adding constraints, but I'm afraid I don't understand what's supposed to happen that didn't happen. Can you shed any light on what went awry with the FK constraint creations? Thanks much, Rob in Memphis
This is very much the MyISAM/InnoDB issue.
https://www.google.com/search?q=site:forums.otterhub.org+can%27t+create+tabl...
http://forums.otterhub.org/viewtopic.php?t=15765
http://forums.otterhub.org/viewtopic.php?t=16730
On Tue, Nov 3, 2015 at 12:25 PM, Rob Mitchell
Thanks, Gerald, for your response. From the documentation I thought I'd be in good shape. I've set up the test server with OTRS 3.1, stopped services and copied over my config files from the 3.0.11 server: /opt/otrs/Kernel/Config.pm /opt/otrs/Kernel/Config/GenericAgent.pm /opt/otrs/Kernel/Config/Files/ZZZAuto.pm
The database from 3.0.11 is restored to a database called otrs3, and although I could use any username I added a user to the otrs3 database with the same name and password as the production server and granted all privileges to otrs3. I've logged onto MySQL using the new credentials and made some table queries to make sure I can see the database properly with the credentials that match the restored Config.pm file. Obviously root works as well.
When I ran the command
cat scripts/DBUpdate-to-3.1.mysql.sql | mysql -p -f -u root otrs3
The script ran but yielded the following errors:
ERROR 1005 (HY000) at line 225: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 226: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 227: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 229: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 230: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 234: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 235: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 237: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 238: Can't create table 'otrs3.#sql-e40_45' (errno: 150) ERROR 1005 (HY000) at line 239: Can't create table 'otrs3.#sql-e40_45' (errno: 150)
MySQL documentation says this error (1005 with errno 150) results when a foreign key constraint is not correctly formed. I can see in the script that these line numbers are adding constraints, but I'm afraid I don't understand what's supposed to happen that didn't happen. Can you shed any light on what went awry with the FK constraint creations?
Thanks much, Rob in Memphis
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Gerald - you were correct. After restoring the old database again, I altered the tables from MyISAM to InnoDB. Once that was done the database upgrade SQL script, the perl script, and the database post-upgrade all ran properly with no unexpected errors. After I upgraded the installed packages the server seemed to have full functionality, except for one thing. The scheduler doesn't seem to be running. I ran /opt/otrs/bin/otrs.Scheduler.pl -a start (as user otrs) also ran /opt/otrs/bin/Cron.sh -start (also as user otrs) Nothing appears to happen. As root I run crontab -u otrs -e comes up with an empty crontab. Any idea what I'm missing? The main thing that's not happening is that fetchmail isn't getting the mailed in tickets. Would really like to get this working as it is in production. Thanks again for your help and guidance. I'm pretty sure you'll be hearing from me again as I continue the upgrade process Rob in Memphis OTRS 3.1.21 Ubuntu Server 14.04 LTS x64
Make sure your var/cron isn't full of files only ending in .dist. Check the
docs.
On Nov 4, 2015 7:13 PM, "Rob Mitchell"
Gerald - you were correct.
After restoring the old database again, I altered the tables from MyISAM to InnoDB. Once that was done the database upgrade SQL script, the perl script, and the database post-upgrade all ran properly with no unexpected errors. After I upgraded the installed packages the server seemed to have full functionality, except for one thing.
The scheduler doesn't seem to be running.
I ran /opt/otrs/bin/otrs.Scheduler.pl -a start (as user otrs) also ran /opt/otrs/bin/Cron.sh -start (also as user otrs) Nothing appears to happen.
As root I run crontab -u otrs -e comes up with an empty crontab. Any idea what I'm missing? The main thing that's not happening is that fetchmail isn't getting the mailed in tickets. Would really like to get this working as it is in production. Thanks again for your help and guidance. I'm pretty sure you'll be hearing from me again as I continue the upgrade process
Rob in Memphis
OTRS 3.1.21 Ubuntu Server 14.04 LTS x64
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
participants (2)
-
Gerald Young -
Rob Mitchell