AlterTable Error During Database Setup

[DisposableHero]

Hi,

 

Just want to test PhpVms v7 beta on a subdomain (with vmsAcars enabled), downloaded latest version (beta4 from github) created a new database and assigned my dbuser to it with all rights ... Uploaded the file to server, unzipped and head on to the installing phase.

 

All checks are ok (php extensions and requirements), put in my new database and user info, db test is ok too but then I get the below error during install ;

 

  #sql: "alter table `v7_airlines` drop index `airlines_iata_unique`"
  #bindings: []
  #message: "SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP INDEX `airlines_iata_unique`; check that it exists (SQL: alter table `v7_airlines` drop index `airlines_iata_unique`)"
 

 

If I close the page and head on the subdomain root, PhpVms seems like installed but the database is empty ... I checked it from phpMyAdmin , see that all the tables are generated but nothing more as expected (like basic data, indexes etc).

 

Any ideas or solutions.

 

PS : I have another copy installed on the main domain (so my server setup must be good to run it) , do not want to use it on main domain and can not take the risk to delete it now either  During the install on the main domain, got a timeout error at the last phase but it seems working ok (with all required data in the tables, indexes etc). Do not want to activate vmsAcars on the main domain, 'cause i need v7 beta working on the subdomain.

 

Best wishes

[Nabeel]

Try the latest dev version. Also, for acars, the latest dev is required - https://docs.phpvms.net/acars/install-server

Also, need the Laravel logs

[DisposableHero]

Thanks for the reply Nabeel , I used the docs but did not gone that far and was following the first installation section (the one at the top, for phpvms install)  Anyway, dev is downloaded ... Will try to install now, hope it goes well.

 

Will supply you with any logs needed if things go worse.

 

Best wishes

[DisposableHero]

Hi again @Nabeel 

 

Laravel log is below

 

[2020-11-05 09:09:25] dev.INFO: Testing Connection: mysql::u9681834_vadba:<hidden>@127.0.0.1:3306;u9681834_turksimva  
[2020-11-05 09:09:25] dev.INFO: Connection string: mysql:host=127.0.0.1;port=3306;dbname=u9681834_turksimva  
[2020-11-05 09:09:31] dev.INFO: Testing Connection: mysql::u9681834_vadba:<hidden>@127.0.0.1:3306;u9681834_turksimva  
[2020-11-05 09:09:31] dev.INFO: Connection string: mysql:host=127.0.0.1;port=3306;dbname=u9681834_turksimva  
[2020-11-05 09:09:47] dev.INFO: ENV setup {"_token":"2YqcX9DSe82no2IrQcVbDiWkUnUczLrxpRXQiMho","site_name":"TurkSim","site_url":"http://vms7.turksim.org","db_conn":"mysql","db_host":"127.0.0.1","db_port":"3306","db_name":"u9681834_turksimva","db_user":"u9681834_vadba","db_pass":"","db_prefix":"v7_"} 
[2020-11-05 09:09:47] dev.INFO: Testing Connection: mysql::u9681834_vadba:<hidden>@127.0.0.1:3306;u9681834_turksimva  
[2020-11-05 09:09:47] dev.INFO: Connection string: mysql:host=127.0.0.1;port=3306;dbname=u9681834_turksimva  
[2020-11-05 09:09:47] dev.INFO: Connection string: mysql:host=127.0.0.1;port=3306;  
[2020-11-05 09:09:47] dev.INFO: Detected DB Version: 10.3.24-mariadb-cll-lve  
[2020-11-05 09:09:47] dev.INFO: Detected MariaDB, setting DB_EMULATE_PREPARES to true  
[2020-11-05 09:09:47] dev.INFO: No extension detected, using file cache  
[2020-11-05 09:09:47] dev.INFO: Redirecting to database setup  
[2020-11-05 09:09:48] prod.ERROR: Error on db setup: SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP INDEX `airlines_iata_unique`; check that it exists (SQL: alter table `v7_airlines` drop index `airlines_iata_unique`)  

 

Still stuck at same position  But with the latest dev, installer reverts back to database setup screen beta4 was just displaying the error and stopping. As it happened I checked the logs and saw the same syntax error about the airline table index.

 

Best wishes

laravel-2020-11-05 (1).zip

Edited November 5, 2020 by FatihKoz

[DisposableHero]

Well ... Just gaved up and tried another approach to continue working on v7.

 

As I had another working install on the main domain, I used its database ... Had to configure some files manually of course but it seems ok right now. Will delete the files from main domain and continue using that database with the latest dev + acars on the subdomain.

 

If there are no acars license activation restrictions for subdomains , I can easily create another one for installation testing and transfer my data manually (via sql or csv imports) if required.

 

Best wishes

 

 

[Nabeel]

There's no restriction for subdomains. If you get an error, send in a support ticket. Is your database completely empty? Delete the database and then start over. Do you also have multiple installs in a single database? It could be a bug where an index doesn't have a proper prefix on it... I can hunt that down if that's the case.

[DisposableHero]

The database was empty and it was for PhpVms7 only , at least I wanted to use a new database ... I also have v5.5 installed at a different subdomain but it uses a different database . Anyway after couple of tries, I decided to use the already built database ,which was also another test install but that db was shared with a different application, I moved that apps data to another database and achieved my goal with a different approach.

 

I am all ok now, but still wondering why I did got those errors in a completely new db and in a fresh install, same server same settings same rights for users/directories/databases etc. I can install v7 on main domain but can not complete it on subdomain somehow.

 

Thanks for your time and suggestions, if you want me to do another test with a new dev build just let me know.

 

Best wishes

[Nabeel]

Strange... I haven't seen that before. Is it possible it wasn't completely empty? I need to do some research to see if there is something I'm missing in regards to naming of those links

[DisposableHero]

It was a brand new database, so yes it was empty ... I have no doubts about that, also after getting the error and before my next attempt I dropped all the tables, so it was again clear of tables/data.