starred/BookStack
1
0
Fork 0
mirror of https://github.com/BookStackApp/BookStack.git synced 2026-02-11 03:13:15 +03:00
Code Issues 784 Packages Projects Releases 10 Wiki Activity

SQLSTATE Connection Refused #3731

New Issue
Closed
opened 2026-02-05 07:16:48 +03:00 by OVERLORD · 14 comments
OVERLORD commented 2026-02-05 07:16:48 +03:00
Owner
Copy Link

Originally created by @samundo on GitHub (Apr 4, 2023).

Attempted Debugging

  • I have read the debugging page

Searched GitHub Issues

  • I have searched GitHub for the issue.

Describe the Scenario

I tried to load Bookstack web interface via IP and I got a site not reachable. I use watchtower to update Bookstack. I noticed on the container log files it said new config files. I loaded the new config files and those errors disappeared. Now when I load the web interface via IP I get a white page. In the container log I now get this error saying Connect Refused as you can see from error in container logs below. Any suggestions on what/how to fix this?

Exact BookStack Version

Not Sure cannot load interface

Log Content

Details 

using keys found in /config/keys
App Key found - setting variable for seds
Running config - DB_HOST set
Waiting for DB to be available
   Illuminate\Database\QueryException 
  SQLSTATE[HY000] [2002] Connection refused (SQL: select * from information_schema.tables where table_schema = bookstackapp and table_name = migrations and table_type = 'BASE TABLE')
  at /app/www/vendor/laravel/framework/src/Illuminate/Database/Connection.php:760
    756▕         // If an exception occurs when attempting to run a query, we'll format the error
    757▕         // message to include the bindings with SQL, which will make this exception a
    758▕         // lot more helpful to the developer instead of just the database's errors.
    759▕         catch (Exception $e) {
  ➜ 760▕             throw new QueryException(
    761▕                 $query, $this->prepareBindings($bindings), $e
    762▕             );
    763▕         }
    764▕     }
      +39 vendor frames 
  40  /app/www/artisan:37
      Illuminate\Foundation\Console\Kernel::handle()
[custom-init] No custom files found, skipping...
[ls.io-init] done.

PHP Version

??

Hosting Environment

Ubuntu 20.04.2, VPS.
Installed by docker compose script

Originally created by @samundo on GitHub (Apr 4, 2023). ### Attempted Debugging - [X] I have read the debugging page ### Searched GitHub Issues - [X] I have searched GitHub for the issue. ### Describe the Scenario I tried to load Bookstack web interface via IP and I got a site not reachable. I use watchtower to update Bookstack. I noticed on the container log files it said new config files. I loaded the new config files and those errors disappeared. Now when I load the web interface via IP I get a white page. In the container log I now get this error saying Connect Refused as you can see from error in container logs below. Any suggestions on what/how to fix this? ### Exact BookStack Version Not Sure cannot load interface ### Log Content <details><summary>Details</summary> <p> ``` using keys found in /config/keys App Key found - setting variable for seds Running config - DB_HOST set Waiting for DB to be available Illuminate\Database\QueryException SQLSTATE[HY000] [2002] Connection refused (SQL: select * from information_schema.tables where table_schema = bookstackapp and table_name = migrations and table_type = 'BASE TABLE') at /app/www/vendor/laravel/framework/src/Illuminate/Database/Connection.php:760 756▕ // If an exception occurs when attempting to run a query, we'll format the error 757▕ // message to include the bindings with SQL, which will make this exception a 758▕ // lot more helpful to the developer instead of just the database's errors. 759▕ catch (Exception $e) { ➜ 760▕ throw new QueryException( 761▕ $query, $this->prepareBindings($bindings), $e 762▕ ); 763▕ } 764▕ } +39 vendor frames 40 /app/www/artisan:37 Illuminate\Foundation\Console\Kernel::handle() [custom-init] No custom files found, skipping... [ls.io-init] done. ``` </p> </details> ### PHP Version ?? ### Hosting Environment Ubuntu 20.04.2, VPS. Installed by docker compose script
OVERLORD added the 🐕 Support label 2026-02-05 07:16:48 +03:00
OVERLORD commented 2026-02-05 07:16:52 +03:00
Author
Owner
Copy Link

@ssddanbrown commented on GitHub (Apr 4, 2023):

Hi @samundo,
Generally an error of SQLSTATE[HY000] [2002] Connection refused means the app simply can't connect to the database at all. Might just not have network visibility.

Could be due to wrong DB_* options used in BookStack. Could be networking issue.
If you could provide a copy of your docker-compose file (With any secrets redacted) that would be helpful.

I loaded the new config files

What do you exactly mean by this? What exact steps/files did you touch?

@ssddanbrown commented on GitHub (Apr 4, 2023): Hi @samundo, Generally an error of `SQLSTATE[HY000] [2002] Connection refused` means the app simply can't connect to the database at all. Might just not have network visibility. Could be due to wrong `DB_*` options used in BookStack. Could be networking issue. If you could provide a copy of your docker-compose file (With any secrets redacted) that would be helpful. > I loaded the new config files What do you exactly mean by this? What exact steps/files did you touch?
OVERLORD commented 2026-02-05 07:16:56 +03:00
Author
Owner
Copy Link

@samundo commented on GitHub (Apr 4, 2023):

Hi @ssddanbrown, Thanks for the quick reply.

Docker-compose file below. I have customised it and was working for the paste year and stopped working in the last month. Not sure when as I have been overseas. I just got back and went to access my wiki and would not load.

---
version: "2"
services:
  bookstack:
    image: lscr.io/linuxserver/bookstack
    container_name: bookstack
    #networks:
    #  - bookstack
    environment:
      - PUID=1000
      - PGID=1000
      #- APP_URL=[redacted]
      - APP_URL=https://wiki.samundo.com.au
      - DB_HOST=bookstack_db
      - DB_USER=bookstack
      - DB_PASS=[redacted]
      - DB_DATABASE=bookstackapp
      - MAIL_DRIVER=smtp
      # Host, Port & Encryption mechanism to use
      - MAIL_HOST=[redacted]
      - MAIL_PORT=25
      #- MAIL_ENCRYPTION=tls
      # Authentication details for your SMTP service
      #- MAIL_USERNAME=user@provider.tld
      #- MAIL_PASSWORD=onlyifneeded
      # The "from" email address for outgoing email
      - MAIL_FROM=wiki@samundo.com.au  
      # The "from" name used for outgoing email
      - MAIL_FROM_NAME=BookStack
    volumes:
      - /opt/bookstack:/config
    ports:
      #- 6875:80
      - 80:80
    restart: unless-stopped
    depends_on:
      - bookstack_db
  bookstack_db:
    image: lscr.io/linuxserver/mariadb
    container_name: bookstack_db
    #networks:
    #  - bookstack
    environment:
      - PUID=1000
      - PGID=1000
      - MYSQL_ROOT_PASSWORD=[redacted]
      - TZ=Australia/Perth
      - MYSQL_DATABASE=bookstackapp
      - MYSQL_USER=bookstack
      - MYSQL_PASSWORD=[redacted]
    volumes:
      - /opt/database:/config
    restart: unless-stopped
    
networks:
  default:
    external:
      name: bookstack

I have checked the containers and they are on the same network. 172.18.0.xx
I have checked the .env file and made sure details matched.

With this message

I loaded the new config files

In the container console it came up with a message that the following files are old and there is new files. Not sure how to replicate the error as it has now gone since I loaded the new files.

Files that were old were
default.conf
nginx.conf
ssl.conf

I went in and renamed these files as old.xxx.conf moved the files to an archives folder. In the folder there was a new sample file. I copied that and then rename it to the above. Regenerated the container and the error disappeared. Then I was left with the SQL error only. If you need I could put the archive files back to generate the error. When the old files are there the web interface does not load. Once I changed the files to the new files the web interface loads but with white screen. Not sure if this is relevant.

@samundo commented on GitHub (Apr 4, 2023): Hi @ssddanbrown, Thanks for the quick reply. Docker-compose file below. I have customised it and was working for the paste year and stopped working in the last month. Not sure when as I have been overseas. I just got back and went to access my wiki and would not load. <details> ``` --- version: "2" services: bookstack: image: lscr.io/linuxserver/bookstack container_name: bookstack #networks: # - bookstack environment: - PUID=1000 - PGID=1000 #- APP_URL=[redacted] - APP_URL=https://wiki.samundo.com.au - DB_HOST=bookstack_db - DB_USER=bookstack - DB_PASS=[redacted] - DB_DATABASE=bookstackapp - MAIL_DRIVER=smtp # Host, Port & Encryption mechanism to use - MAIL_HOST=[redacted] - MAIL_PORT=25 #- MAIL_ENCRYPTION=tls # Authentication details for your SMTP service #- MAIL_USERNAME=user@provider.tld #- MAIL_PASSWORD=onlyifneeded # The "from" email address for outgoing email - MAIL_FROM=wiki@samundo.com.au # The "from" name used for outgoing email - MAIL_FROM_NAME=BookStack volumes: - /opt/bookstack:/config ports: #- 6875:80 - 80:80 restart: unless-stopped depends_on: - bookstack_db bookstack_db: image: lscr.io/linuxserver/mariadb container_name: bookstack_db #networks: # - bookstack environment: - PUID=1000 - PGID=1000 - MYSQL_ROOT_PASSWORD=[redacted] - TZ=Australia/Perth - MYSQL_DATABASE=bookstackapp - MYSQL_USER=bookstack - MYSQL_PASSWORD=[redacted] volumes: - /opt/database:/config restart: unless-stopped networks: default: external: name: bookstack ``` </details> I have checked the containers and they are on the same network. 172.18.0.xx I have checked the .env file and made sure details matched. With this message _I loaded the new config files_ In the container console it came up with a message that the following files are old and there is new files. Not sure how to replicate the error as it has now gone since I loaded the new files. Files that were old were default.conf nginx.conf ssl.conf I went in and renamed these files as old.xxx.conf moved the files to an archives folder. In the folder there was a new sample file. I copied that and then rename it to the above. Regenerated the container and the error disappeared. Then I was left with the SQL error only. If you need I could put the archive files back to generate the error. When the old files are there the web interface does not load. Once I changed the files to the new files the web interface loads but with white screen. Not sure if this is relevant.
OVERLORD commented 2026-02-05 07:17:06 +03:00
Author
Owner
Copy Link

@ssddanbrown commented on GitHub (Apr 6, 2023):

@samundo Ah, okay, those files changes are part of linuxserver changes. Should not affect the reported error at play so don't think we need to consider them as a cause at all.

You've probably already done this, but can you confirm that the database container is starting up and running without error? Should be able to watch the logs for the database container to ensure it's not actually in a constantly restarting/error state.

If that's okay could you access the running BookStack container, and test connection via ping bookstack_db? Just to ensure that returns on ping as expected.
If that works, you could try to connect to the database using the mysql command line from the BookStack container:

mysql -h bookstack_db -u bookstack -p<password_here> bookstackapp
@ssddanbrown commented on GitHub (Apr 6, 2023): @samundo Ah, okay, those files changes are part of linuxserver changes. Should not affect the reported error at play so don't think we need to consider them as a cause at all. You've probably already done this, but can you confirm that the database container is starting up and running without error? Should be able to watch the logs for the database container to ensure it's not actually in a constantly restarting/error state. If that's okay could you access the running BookStack container, and test connection via `ping bookstack_db`? Just to ensure that returns on ping as expected. If that works, you could try to connect to the database using the `mysql` command line from the BookStack container: ```bash mysql -h bookstack_db -u bookstack -p<password_here> bookstackapp ```
OVERLORD commented 2026-02-05 07:17:18 +03:00
Author
Owner
Copy Link

@samundo commented on GitHub (Apr 7, 2023):

@ssddanbrown I am using portainer and connected to the BookStack container and was able to ping the bookstack_db. It replied with

64 bytes from 172.18.0.3: seq=0 ttl=64 time=0.143 ms

I then tried the next section to enter mysql but in the BookStack container it says

bash: mysql: command not found

I have then gone into the bookstack_db container and tried connecting to mysql and I get this error

ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)

If there is something I am doing wrong please advise.

@samundo commented on GitHub (Apr 7, 2023): @ssddanbrown I am using portainer and connected to the BookStack container and was able to ping the bookstack_db. It replied with 64 bytes from 172.18.0.3: seq=0 ttl=64 time=0.143 ms I then tried the next section to enter mysql but in the BookStack container it says bash: mysql: command not found I have then gone into the bookstack_db container and tried connecting to mysql and I get this error ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2) If there is something I am doing wrong please advise.
OVERLORD commented 2026-02-05 07:17:19 +03:00
Author
Owner
Copy Link

@samundo commented on GitHub (Apr 7, 2023):

@ssddanbrown forgot to add the logs from the bookstack_db

Caught SIGTERM signal!
cat: /var/run/mysqld/mysqld.pid: No such file or directory
230407 20:44:43 mysqld_safe Logging to '/config/databases/a28276778c36.err'.
230407 20:44:43 mysqld_safe Starting mariadbd daemon with databases from /config/databases

This message is appearing every 3 seconds.

@samundo commented on GitHub (Apr 7, 2023): @ssddanbrown forgot to add the logs from the bookstack_db Caught SIGTERM signal! cat: /var/run/mysqld/mysqld.pid: No such file or directory 230407 20:44:43 mysqld_safe Logging to '/config/databases/a28276778c36.err'. 230407 20:44:43 mysqld_safe Starting mariadbd daemon with databases from /config/databases This message is appearing every 3 seconds.
OVERLORD commented 2026-02-05 07:17:26 +03:00
Author
Owner
Copy Link

@ssddanbrown commented on GitHub (Apr 7, 2023):

@samundo Can you check that databases/a28276778c36.err file within the mounted folder for the database container to get more information?

@ssddanbrown commented on GitHub (Apr 7, 2023): @samundo Can you check that `databases/a28276778c36.err` file within the mounted folder for the database container to get more information?
OVERLORD commented 2026-02-05 07:17:28 +03:00
Author
Owner
Copy Link

@samundo commented on GitHub (Apr 9, 2023):

@ssddanbrown the file is 515mb, so I have copied the last logs from the file.

230404 21:53:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
230404 21:53:04 mysqld_safe Starting mariadbd daemon with databases from /config/databases
2023-04-04 21:53:04 0 [Note] Starting MariaDB 10.6.12-MariaDB-log source revision 4c79e15cc3716f69c044d4287ad2160da8101cdc as process 50025
Cannot find checkpoint record at LSN (1,0x7fee)
2023-04-04 21:53:04 0 [ERROR] mariadbd: Aria recovery failed. Please run aria_chk -r on all Aria tables (.MAI) and delete all aria_log.######## files
2023-04-04 21:53:04 0 [ERROR] Plugin 'Aria' init function returned error.
2023-04-04 21:53:04 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2023-04-04 21:53:04 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2023-04-04 21:53:04 0 [Note] InnoDB: Number of pools: 1
2023-04-04 21:53:04 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-04-04 21:53:04 0 [Note] mariadbd: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2023-04-04 21:53:04 0 [Note] InnoDB: Using Linux native AIO
2023-04-04 21:53:04 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728
2023-04-04 21:53:04 0 [Note] InnoDB: Completed initialization of buffer pool
2023-04-04 21:53:04 0 [Note] InnoDB: 128 rollback segments are active.
2023-04-04 21:53:04 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-04-04 21:53:04 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-04-04 21:53:04 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2023-04-04 21:53:04 0 [Note] InnoDB: 10.6.12 started; log sequence number 14625851; transaction id 7248
2023-04-04 21:53:04 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-04-04 21:53:04 0 [Note] InnoDB: Loading buffer pool(s) from /config/databases/ib_buffer_pool
2023-04-04 21:53:04 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded
2023-04-04 21:53:04 0 [Note] InnoDB: Buffer pool(s) load completed at 230404 21:53:04
2023-04-04 21:53:04 0 [ERROR] Failed to initialize plugins.
2023-04-04 21:53:04 0 [ERROR] Aborting
230404 21:53:04 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
230404 21:53:05 mysqld_safe Starting mariadbd daemon with databases from /config/databases
2023-04-04 21:53:05 0 [Note] Starting MariaDB 10.6.12-MariaDB-log source revision 4c79e15cc3716f69c044d4287ad2160da8101cdc as process 50232
Cannot find checkpoint record at LSN (1,0x7fee)
2023-04-04 21:53:05 0 [ERROR] mariadbd: Aria recovery failed. Please run aria_chk -r on all Aria tables (.MAI) and delete all aria_log.######## files
2023-04-04 21:53:05 0 [ERROR] Plugin 'Aria' init function returned error.
2023-04-04 21:53:05 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2023-04-04 21:53:05 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2023-04-04 21:53:05 0 [Note] InnoDB: Number of pools: 1
2023-04-04 21:53:05 0 [Note] InnoDB: U

@samundo commented on GitHub (Apr 9, 2023): @ssddanbrown the file is 515mb, so I have copied the last logs from the file. 230404 21:53:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 230404 21:53:04 mysqld_safe Starting mariadbd daemon with databases from /config/databases 2023-04-04 21:53:04 0 [Note] Starting MariaDB 10.6.12-MariaDB-log source revision 4c79e15cc3716f69c044d4287ad2160da8101cdc as process 50025 Cannot find checkpoint record at LSN (1,0x7fee) 2023-04-04 21:53:04 0 [ERROR] mariadbd: Aria recovery failed. Please run aria_chk -r on all Aria tables (*.MAI) and delete all aria_log.######## files 2023-04-04 21:53:04 0 [ERROR] Plugin 'Aria' init function returned error. 2023-04-04 21:53:04 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 2023-04-04 21:53:04 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 2023-04-04 21:53:04 0 [Note] InnoDB: Number of pools: 1 2023-04-04 21:53:04 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2023-04-04 21:53:04 0 [Note] mariadbd: O_TMPFILE is not supported on /var/tmp (disabling future attempts) 2023-04-04 21:53:04 0 [Note] InnoDB: Using Linux native AIO 2023-04-04 21:53:04 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728 2023-04-04 21:53:04 0 [Note] InnoDB: Completed initialization of buffer pool 2023-04-04 21:53:04 0 [Note] InnoDB: 128 rollback segments are active. 2023-04-04 21:53:04 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2023-04-04 21:53:04 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2023-04-04 21:53:04 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2023-04-04 21:53:04 0 [Note] InnoDB: 10.6.12 started; log sequence number 14625851; transaction id 7248 2023-04-04 21:53:04 0 [Note] Plugin 'FEEDBACK' is disabled. 2023-04-04 21:53:04 0 [Note] InnoDB: Loading buffer pool(s) from /config/databases/ib_buffer_pool 2023-04-04 21:53:04 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded 2023-04-04 21:53:04 0 [Note] InnoDB: Buffer pool(s) load completed at 230404 21:53:04 2023-04-04 21:53:04 0 [ERROR] Failed to initialize plugins. 2023-04-04 21:53:04 0 [ERROR] Aborting 230404 21:53:04 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 230404 21:53:05 mysqld_safe Starting mariadbd daemon with databases from /config/databases 2023-04-04 21:53:05 0 [Note] Starting MariaDB 10.6.12-MariaDB-log source revision 4c79e15cc3716f69c044d4287ad2160da8101cdc as process 50232 Cannot find checkpoint record at LSN (1,0x7fee) 2023-04-04 21:53:05 0 [ERROR] mariadbd: Aria recovery failed. Please run aria_chk -r on all Aria tables (*.MAI) and delete all aria_log.######## files 2023-04-04 21:53:05 0 [ERROR] Plugin 'Aria' init function returned error. 2023-04-04 21:53:05 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 2023-04-04 21:53:05 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 2023-04-04 21:53:05 0 [Note] InnoDB: Number of pools: 1 2023-04-04 21:53:05 0 [Note] InnoDB: U
OVERLORD commented 2026-02-05 07:17:32 +03:00
Author
Owner
Copy Link

@ssddanbrown commented on GitHub (Apr 9, 2023):

Hi @samundo,

Looks like your MariaDB container system has somewhat gone wrong. I can only advise stopping all containers, ensure you have a secure off-machine backup of all container data, then follow the guidance in the error log, specifically:

2023-04-04 21:53:04 0 [ERROR] mariadbd: Aria recovery failed. Please run aria_chk -r on all Aria tables (.MAI) and delete all aria_log.######## files

Would probably be a case of accessing bash shell in the database container, then find any *.MAI files within the /config directory and run that aria_chk -r <file> command on them. Docs for that command here. Then find and delete any aria_log.* files within that directory as suggested. Then restart the database container and see if the logs show it coming back up safely.

@ssddanbrown commented on GitHub (Apr 9, 2023): Hi @samundo, Looks like your MariaDB container system has somewhat gone wrong. I can only advise stopping all containers, ensure you have a secure off-machine backup of all container data, then follow the guidance in the error log, specifically: > 2023-04-04 21:53:04 0 [ERROR] mariadbd: Aria recovery failed. Please run aria_chk -r on all Aria tables (.MAI) and delete all aria_log.######## files Would probably be a case of accessing bash shell in the database container, then find any `*.MAI` files within the `/config` directory and run that `aria_chk -r <file>` command on them. [Docs for that command here](https://mariadb.com/kb/en/aria_chk/). Then find and delete any `aria_log.*` files within that directory as suggested. Then restart the database container and see if the logs show it coming back up safely.
OVERLORD commented 2026-02-05 07:17:36 +03:00
Author
Owner
Copy Link

@ssddanbrown commented on GitHub (Apr 17, 2023):

Since there's been no follow-up I'm going to close this. If the issue remains and is something you still require to be fixed respond to my previous comment and this can then be re-opened.

@ssddanbrown commented on GitHub (Apr 17, 2023): Since there's been no follow-up I'm going to close this. If the issue remains and is something you still require to be fixed respond to my previous comment and this can then be re-opened.
OVERLORD commented 2026-02-05 07:17:38 +03:00
Author
Owner
Copy Link

@samundo commented on GitHub (Apr 25, 2023):

Hi @ssddanbrown,
Sorry have been away for work. Just an update did the fix from above and now all working. Does not work in Safari but works in all other browsers. Thanks for all your help.

@samundo commented on GitHub (Apr 25, 2023): Hi @ssddanbrown, Sorry have been away for work. Just an update did the fix from above and now all working. Does not work in Safari but works in all other browsers. Thanks for all your help.
OVERLORD commented 2026-02-05 07:17:43 +03:00
Author
Owner
Copy Link

@samundo commented on GitHub (Apr 25, 2023):

Hi @ssddanbrown,
The database is now saying it needs upgrade. Should I run the upgrade?
So far BookStack is working and all data is there.

@samundo commented on GitHub (Apr 25, 2023): Hi @ssddanbrown, The database is now saying it needs upgrade. Should I run the upgrade? So far BookStack is working and all data is there.
OVERLORD commented 2026-02-05 07:17:48 +03:00
Author
Owner
Copy Link

@ssddanbrown commented on GitHub (Apr 25, 2023):

@samundo I'm not sure what that's referring to. I'd need to see the message to understand where that's coming from and to advise.

@ssddanbrown commented on GitHub (Apr 25, 2023): @samundo I'm not sure what that's referring to. I'd need to see the message to understand where that's coming from and to advise.
OVERLORD commented 2026-02-05 07:17:51 +03:00
Author
Owner
Copy Link

@samundo commented on GitHub (Apr 25, 2023):

Hi @ssddanbrown,
When I check the logs under the bookstack database it shows the following message.

#################################################################
#                                                               #
#           An upgrade is required on your databases.           #
#                                                               #
#         Stop any services that are accessing databases        #
#          in this container, and then run the command          #
#                                                               #
#             mariadb-upgrade -u root -p<PASSWORD>              #
#                                                               #
#################################################################
[ls.io-init] done.
@samundo commented on GitHub (Apr 25, 2023): Hi @ssddanbrown, When I check the logs under the bookstack database it shows the following message. ``` ################################################################# # # # An upgrade is required on your databases. # # # # Stop any services that are accessing databases # # in this container, and then run the command # # # # mariadb-upgrade -u root -p<PASSWORD> # # # ################################################################# [ls.io-init] done. ```
OVERLORD commented 2026-02-05 07:17:51 +03:00
Author
Owner
Copy Link

@ssddanbrown commented on GitHub (Apr 25, 2023):

@samundo

Okay, so that's all on the database side.
I'd probably follow what it advises but first stop all containers then backup all volumes just in case things go wrong.

@ssddanbrown commented on GitHub (Apr 25, 2023): @samundo Okay, so that's all on the database side. I'd probably follow what it advises but first stop all containers then backup all volumes just in case things go wrong.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
pull-request
Mirrored from GitHub Pull Request
No Label 🐕 Support
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#3731
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?