Ubuntu 24.04.3 Improvements #45

sumdev commented 2025年09月22日 18:14:20 +02:00

I attempted to install Bookstack on a brand new Ubuntu Server 24.04.3 and the installation fails. I made some adjustments to the installation script to work with Ubuntu Server 24.04.3.

Changed these sections
#Get the domain from the arguments (Requested later if not set)
if [ -z "${1-}" ]; then
read -rp "Enter your domain (or press Enter to use IP $CURRENT_IP): " DOMAIN
DOMAIN=${DOMAIN:-$CURRENT_IP}
else
DOMAIN=1ドル
fi

#Install core system packages
function run_package_installs() {
apt update
apt install -y git unzip apache2 curl mysql-server php8.3
php8.3-fpm php8.3-curl php8.3-mbstring php8.3-ldap php8.3-xml php8.3-zip php8.3-gd php8.3-mysql
}

#Set up database
function run_database_setup() {
#Ensure database service has started
systemctl start mysql.service
systemctl enable mysql.service
sleep 3

I attempted to install Bookstack on a brand new Ubuntu Server 24.04.3 and the installation fails. I made some adjustments to the installation script to work with Ubuntu Server 24.04.3. **Changed these sections** #Get the domain from the arguments (Requested later if not set) if [ -z "${1-}" ]; then read -rp "Enter your domain (or press Enter to use IP $CURRENT_IP): " DOMAIN DOMAIN=${DOMAIN:-$CURRENT_IP} else DOMAIN=1ドル fi #Install core system packages function run_package_installs() { apt update apt install -y git unzip apache2 curl mysql-server php8.3 \ php8.3-fpm php8.3-curl php8.3-mbstring php8.3-ldap php8.3-xml php8.3-zip php8.3-gd php8.3-mysql } #Set up database function run_database_setup() { #Ensure database service has started systemctl start mysql.service systemctl enable mysql.service sleep 3

danb commented 2025年09月23日 00:06:21 +02:00

Hi @sumdev,
Can you describe the exact environment used to run the script where it failed (service used if any, if VM: host OS and VM software used, Exact Ubuntu download link used if any etc...).

Also, if you still have it, please share the install log from the original failed attempt (Should be in the same directory as where you originally ran the script from).

I don't think changes in Ubuntu should need those changes, but there could environmental elements which lead to differences, so it would be good to know those to properly plan for them in future.

Hi @sumdev, Can you describe the exact environment used to run the script where it failed (service used if any, if VM: host OS and VM software used, Exact Ubuntu download link used if any etc...). Also, if you still have it, please share the install log from the original failed attempt (Should be in the same directory as where you originally ran the script from). I don't think changes in Ubuntu should need those changes, but there could environmental elements which lead to differences, so it would be good to know those to properly plan for them in future.

sumdev commented 2025年09月26日 18:46:19 +02:00

Hi Dan,
The failure occurred when installing on Ubuntu Server 24.04.3 VM. It failed starting the mysql service and the script stopped. It complained the mysql.service did not exist. I tried to recreate it to get you an install log, but for some reason in the new VM the script ran correctly, so I am not sure what the original issue was.

I also had issues with DOMAIN=1ドル which also caused it to error out. I cannot remember what the error was though.

Hi Dan, The failure occurred when installing on Ubuntu Server 24.04.3 VM. It failed starting the mysql service and the script stopped. It complained the mysql.service did not exist. I tried to recreate it to get you an install log, but for some reason in the new VM the script ran correctly, so I am not sure what the original issue was. I also had issues with DOMAIN=1ドル which also caused it to error out. I cannot remember what the error was though.

danb commented 2025年09月27日 16:12:01 +02:00

Okay, thanks for responding.

I'll therefore close this off since re-running the script worked okay, but I'll keep this in mind if I get further reports, or if there's specific errors to address.

Okay, thanks for responding. I'll therefore close this off since re-running the script worked okay, but I'll keep this in mind if I get further reports, or if there's specific errors to address.