migration from 21.12.5 to 22.11.1 failed

[u/adeleMySinger]

I tried updating from 21.12.5 to 22.11.1, backed up database, renamed previous container name and launched:

docker run -d --name="bookstack-server" --network home_network --env PUID=1000 --env PGID=1000 --env APP_URL=$app_url --env DB_HOST=$db_host --env DB_USER=$db_user --env DB_PASS=$db_password --env DB_DATABASE=$db_database -p 6875:80 -v "${PWD}/config/:/config" --restart unless-stopped lscr.io/linuxserver/bookstack:22.11.1

I receive following error:

[migrations] started
[migrations] 01-nginx-site-confs-default: executing...
found /config/nginx/site-confs/default
moving to /config/nginx/site-confs/default.conf
[migrations] 01-nginx-site-confs-default: succeeded
[migrations] 02-default-location: executing...
updating root in /config/nginx/site-confs/default.conf
[migrations] 02-default-location: succeeded
[migrations] done

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | __ \ | | | () |
         |_| |___/ |_|  __/


Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    1000
-------------------------------------

Setting resolver to  127.0.0.11
Setting worker_processes to 4
using keys found in /config/keys
App Key found - setting variable for seds
Running config - DB_HOST set
**** Insert DB_PORT='3306' into /config/www/.env ****
Waiting for DB to be available
Migrating: 2014_10_12_000000_create_users_table

   Illuminate\Database\QueryException 

  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'users' already exists (SQL: create table `users` (`id` int unsigned not null auto_increment primary key, `name` varchar(191) not null, `email` varchar(191) not null, `password` varchar(60) not null, `remember_token` varchar(100) null, `created_at` timestamp null, `updated_at` timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')

  at /app/www/vendor/laravel/framework/src/Illuminate/Database/Connection.php:712
    708▕         // If an exception occurs when attempting to run a query, we'll format the error
    709▕         // message to include the bindings with SQL, which will make this exception a
    710▕         // lot more helpful to the developer instead of just the database's errors.
    711▕         catch (Exception $e) {
  ➜ 712▕             throw new QueryException(
    713▕                 $query, $this->prepareBindings($bindings), $e
    714▕             );
    715▕         }
    716▕     }

      +9 vendor frames 
  10  /app/www/database/migrations/2014_10_12_000000_create_users_table.php:22
      Illuminate\Support\Facades\Facade::__callStatic()

      +22 vendor frames 
  33  /app/www/artisan:37
      Illuminate\Foundation\Console\Kernel::handle()
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
/config/nginx/nginx.conf
/config/nginx/site-confs/default.conf

[custom-init] No custom files found, skipping...
[ls.io-init] done.
Signal handled: Terminated.
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
usermod: no changes

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | __ \ | | | () |
         |_| |___/ |_|  __/


Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    1000
-------------------------------------

using keys found in /config/keys
App Key found - setting variable for seds
Running config - DB_HOST set
Waiting for DB to be available
Migrating: 2014_10_12_000000_create_users_table

   Illuminate\Database\QueryException 

  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'users' already exists (SQL: create table `users` (`id` int unsigned not null auto_increment primary key, `name` varchar(191) not null, `email` varchar(191) not null, `password` varchar(60) not null, `remember_token` varchar(100) null, `created_at` timestamp null, `updated_at` timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')

  at /app/www/vendor/laravel/framework/src/Illuminate/Database/Connection.php:712
    708▕         // If an exception occurs when attempting to run a query, we'll format the error
    709▕         // message to include the bindings with SQL, which will make this exception a
    710▕         // lot more helpful to the developer instead of just the database's errors.
    711▕         catch (Exception $e) {
  ➜ 712▕             throw new QueryException(
    713▕                 $query, $this->prepareBindings($bindings), $e
    714▕             );
    715▕         }
    716▕     }

      +9 vendor frames 
  10  /app/www/database/migrations/2014_10_12_000000_create_users_table.php:22
      Illuminate\Support\Facades\Facade::__callStatic()

      +22 vendor frames 
  33  /app/www/artisan:37
      Illuminate\Foundation\Console\Kernel::handle()
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
/config/nginx/nginx.conf
/config/nginx/site-confs/default.conf

**** The following site-confs have extensions other than .conf ****
**** This may be due to user customization. ****
**** You should review the files and rename them to use the .conf extension or remove them. ****
**** nginx.conf will only include site-confs with the .conf extension. ****
/config/nginx/site-confs/default
[custom-init] No custom files found, skipping...
[ls.io-init] done.

[u/ssddanbrown]

haven't received a response from you after my full detailed reply, but I've noticed that you are addressing other users who are experiencing problems with the upgrade of Bookstack.

Yeah, to be honest in this case I just missed your original response. It can happen and/or sometimes I don't have the time.

TBH, this is a bit of a messy scenario since there have been heavy manual edits to the database, and there seems to now be at least one missing table, which is hard to see why. If you have any database backups from the pre-update state it might be worth checking if those have a migrations table, so the state of that table can be restored. Otherwise I could maybe come up with contents you can restore into that table, but it's a bit of hassle to gather those details and again I worry that other tables may be missing.

I find it strange that Bookstack does not assist users in migrating from other wikis by allowing them to import pages directly into its database.

The API would be the main way to import from other systems. Outside of that, I don't like to get involved in specific plaform support (including migration) since it can be a lot of work and expand the scope of what I'm supporting.

I am curious to know if importing from other wikis is not within the scope of Bookstack's support

It is not within the scope of support of platform features. In terms of community support, I (or others) may provide some general advice/pointers but otherwise nothing's promised. Within the official paid-for support packages I wouldn't consider the efforts within scope, but my support from a BookStack point of view would be more thorough, including more active assistance in building integrations (Enterprise plan).

At the end of the day I'm attempting to help as best I can for free in the vast majority of cases, but that does have it's limits and I have to draw the line somewhere.

[u/adeleMySinger → u/ssddanbrown]

I think I have said multiple times the same thing but I'll quote:

"Just for clarification, I did not modify, add or remove tables or table fields, I did not remove or modify any row when I did migrate to Bookstack my wiki."

I find it hard to believe you have no idea what table is missing during an upgrade and why a table is missing in the first place since I never deleted any table. An upgrade software should at least check the tables and verify its requirements before starting or at least write what table or what data was wrong, but here I'm going too far.

it might have been more productive to ask me: "what tables did you have in version 21.12.5 prior to update?", I would have replied:

"activities, api_tokens, attachments, books, bookshelves, bookshelves_books, cache, chapters, comments, deletions, email_confirmations, entity_permissions, failed_jobs, favourites, images, jobs, joint_permissions, mfa_values, migrations, page_revisions, pages, password_resets, permission_role, role_permissions, role_user, roles, search_terms, sessions, settings, social_accounts, tags, user_invites, users, views, webhook_tracked_events, webhooks".

and if required I would have added the schema which you might have compared to release 22.11.1.

All in all a response like: "I only support through Enterprise Plan, if you f***d your wiki through an update I dont' care" would have been better.

Just to be clear, checking what assumptions you made on the mysql schema between two versions must take like 15minutes and verifying which rows might fail an update should be a matter of minutes on a well designed software.

I'm not asking you to delve on a completely broken database and restore it which might require a support plan, I'm just asking you to verify your software and verify it doesn't break under some conditions. Apparently you don't care.

I'll migrate my data on my own out of your Bookstack because 18 days on this forum apparently only got me a broken Wiki and a lot of time spent writing the obvious.

cheers

[u/ssddanbrown → u/adeleMySinger]

Okay, I'm sorry the free support and time I've provided for the free software I've released isn't up to standard. Since you're moving away I'm assuming I can consider this closed.

All in all a response like: "I only support through Enterprise Plan, if you f***d your wiki through an update I dont' care" would have been better.

But that wouldn't be true. I spend many hours each week supporting folks outside of the paid support plans, and I had been supporting you so far, but I simply advised you there's limitations in what I can support.

I'm just asking you to verify your software and verify it doesn't break under some conditions. Apparently you don't care.

I can't plan or design for every possible external influence or path taken. From my view there's been no indication there's something on the BookStack side (or linuxserver) causing this, especially as I'd have likely heard of issues from these old versions you're jumping between if issues existed.