Actual Budget Update Failing

[chmsant]

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

actualbudget.sh

📂 What was the exact command used to execute the script?

update

📝 Provide a clear and concise description of the issue.

The Actual Budget 'update' command is failing. This was occurring on my LXC that I've been running for quite a while from the ttech days (RIP ttech), so I spun up a new LXC last week and the issue is still happening in the new LXC.

Current Actual Budget version is 25.1.0

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

open LXC console
run 'update' command

❌ Paste the full error output (if available).

.:mv: cannot stat 'actual-server-*': No such file or directory

[ERROR] in line 54: exit code 0: while executing command mv acutal-server-* /opt/actualbudget

🖼️ Additional context (optional).

Commit history leads me to believe that this issue may have been recently introduced as the corresponding lines have recent changes.

[infinitytec]

Same issue here. I was coming across this in #1623 which got closed without full resolution.

[chmsant]

Looks like some of the codebase has been playing leapfrog.

Commit 5c1954c added the following on line 41

mv actualbudget-actual-server-*/* /opt/actualbudget/

Then in commit dd0cdf5 it became:
mv actual-server-* /opt/actualbudget
on line 54

there's an extra "/*" missing from the folder path from the latest commits?

EDIT: Tried forking and messing around with it and doesn't seem to have fixed. Lost again.

[MickLesk]

The biggest problem with this script is the Git retrieval. I worked on it for 2 days, at most 1 of 10 calls worked.
I can then look again to see if there is anything left, but in the end it worked several times for me.

I have already considered removing it, as it only causes problems and they maintain their projects in a very peculiar way.

[MickLesk]

i found an little bug in the curl and jq dep in update function, i fixed it.

Checkout following guide:

1. Set a specific version (not the current one)

Run the following command to set a specific version, e.g., v24.12.0:

echo "v24.12.0" > /opt/actualbudget_version.txt

2. Perform the update

Execute the update process on your LXC after setting the version.

3. Provide feedback

Once the update is complete, please test the changes and share your feedback.

Otherwise: Create an new LXC

[infinitytec]

Thanks, I'll try that later today.

[chmsant]

@MickLesk followed your instructions both in existing LXC and new LXC. While the mv issue seems to be fixed in the new LXC, I'm now seeing the following error:

[ERROR] in line 53: exit code 0: while executing command yarn install &> /dev/null

which seems to be what @infinitytec was seeing in #1623

[MickLesk]

Can you create an new one? The shit script has a lot of build bugs after Update

[chmsant]

My apologies, I should have clarified my terminology. "Existing LXC" is now the one I created last week. "New LXC" was instantiated a few hours ago after your response earlier today, and after your latest commit.

[MickLesk]

on an new lxc you get an yarn install issue? wtf, im not. ActualBudget Script is fck annoying

[chmsant]

Yep. When I then try to do the corepack update to solve the yarn install issue, as suggested on infinitytec's issue report, I now get a different move error:

mv cannot stat '/opt/actualbudget_bak/.env': no such file or directory
[ERROR] in line 50: exit code 0: while executing command mv /opt/actualbudget_bak.env /opt/actualbudget

Might I request the issue be re-opened to increase visibility so that other devs/users can take a look?

[devdecrux]

I get the following error when executing update or executing the script:

⠇mv: cannot move '/opt/actualbudget' to '/opt/actualbudget_bak/actualbudget': Directory not empty [ERROR] in line 46: exit code 0: while executing command mv /opt/actualbudget /opt/actualbudget_bak

[infinitytec]

Yep. When I then try to do the corepack update to solve the yarn install issue, as suggested on infinitytec's issue report, I now get a different move error:

mv cannot stat '/opt/actualbudget_bak/.env': no such file or directory
[ERROR] in line 50: exit code 0: while executing command mv /opt/actualbudget_bak.env /opt/actualbudget

Might I request the issue be re-opened to increase visibility so that other devs/users can take a look?

@MickLesk can we get this issue re-opened?

[infinitytec]

I have an almost working solution!

Of course, make a backup first. This is also really a breaking change because it changes the path the application runs out of.

This also breaks the application starting at boot (probably due to systemctl and the path change)!

systemctl stop actualbudget
apt update && apt upgrade -y
npm install -g npm
mv /opt/actualbudget /opt/actualbudget_bak
cd /opt
git clone https://github.com/actualbudget/actual-server.git
cd /opt/actual-server
corepack enable
corepack prepare yarn@4.3.1 --activate
yarn add @babel/core -D
yarn add typescript -D
yarn add ipaddr.js
yarn add proxy-addr
yarn add axios
yarn rebuild
npm rebuild bcrypt
npm rebuild better-sqlite3
yarn install
yarn start

The application should start. Now, ctrl+c to close it, then run the following to copy your data:

mv /opt/actualbudget_bak/server-files/* /opt/actual-server/server-files
mv /opt/actualbudget_bak/user-files/* /opt/actual-server/user-files
yarn start

The application should start and your data should be intact.

If you copy the data before running the application once it gives and SQL error.

This melted my brain.

Now if someone can get this to work seamlessly and update the main script, that would be awesome. For now, I'm just going to run the old version until this gets figured out.

[MickLesk]

We dont use git clone and add unnessecarry deps like babel, this should be done by the maintainer of actual Budget. Ive checked the Changelog and there are not Breaking changes declared, sad for everyone.

I take a look next week