Actual Budget Update command causes an issue #318

Closed
opened 2026-02-04 17:56:18 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @danluckner on GitHub (Jan 11, 2025).

Have you read and understood the above guidelines?

yes

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

Actual Budget

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

update

📝 Provide a clear and concise description of the issue.

I had Actual Budget installed and with a new update, I decided to use the update command inside the LXC container to have the latest features available.

By doing that I got an error that is better described by the picture further below.

I went throug the same routine a couple of months ago, without any issues then. But we have this issue now.

image

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Step 1: Install an instance of Actual Budget LXC

Step 2: Login into the LXC and use the update command

Paste the full error output (if available).

 ⠧mv: target '/opt/actualbudget/': No such file or directory

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

🖼️ Additional context (optional).

I was able to recover by doing the following:

Step 1: Login into the Actual Budget LXC
Step 2: Go to /opt directory
Step 3: Copy the actualbudget_bak directory with: cp -R /opt/actualbudget_bak/ /opt/actualbudget/
Step 4: Modify the file /usr/bin/update as the following:

#bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/actualbudget.sh)"
bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/actualbudget.sh)"

Step 5: Use update command again.

This will cause the Actual Budget instance to be updated with tteck's original script, which does not present issues.

Originally created by @danluckner on GitHub (Jan 11, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Actual Budget ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. I had Actual Budget installed and with a new update, I decided to use the `update` command inside the LXC container to have the latest features available. By doing that I got an error that is better described by the picture further below. I went throug the same routine a couple of months ago, without any issues then. But we have this issue now. ![image](https://github.com/user-attachments/assets/5c6cfa10-e8a7-4146-a6fe-42af20b54c76) ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Step 1: Install an instance of Actual Budget LXC Step 2: Login into the LXC and use the `update` command ### ❌ Paste the full error output (if available). ``` ⠧mv: target '/opt/actualbudget/': No such file or directory [ERROR] in line 48: exit code 0: while executing command mv actualbudget-actual-server-*/* /opt/actualbudget/ ``` ### 🖼️ Additional context (optional). I was able to recover by doing the following: Step 1: Login into the Actual Budget LXC Step 2: Go to `/opt` directory Step 3: Copy the `actualbudget_bak` directory with: `cp -R /opt/actualbudget_bak/ /opt/actualbudget/` Step 4: Modify the file `/usr/bin/update` as the following: ``` #bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/actualbudget.sh)" bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/actualbudget.sh)" ``` Step 5: Use `update` command again. This will cause the Actual Budget instance to be updated with tteck's original script, which does not present issues.
Author
Owner

@Telesphoreo commented on GitHub (Jan 12, 2025):

What worked for me is to ignore the update script altogether and just run git pull and then yarn install inside of the /opt/actualbudget directory

@Telesphoreo commented on GitHub (Jan 12, 2025): What worked for me is to ignore the update script altogether and just run git pull and then yarn install inside of the /opt/actualbudget directory
Author
Owner

@dosten commented on GitHub (Jan 13, 2025):

The issue is related to 5170056078

This commit added a mv command which moves /opt/actualbudget to /opt/actualbudget_bak but after that another mv command tries to move to /opt/actualbudget/ but this dir does not exists. Maybe we just need to cp /opt/actualbudget to /opt/actualbudget_bak. CC @MickLesk

@dosten commented on GitHub (Jan 13, 2025): The issue is related to https://github.com/community-scripts/ProxmoxVE/commit/5170056078b3a1e11c8d872c720e3014530752c9 This commit added a `mv` command which moves `/opt/actualbudget` to `/opt/actualbudget_bak` but after that another `mv` command tries to move to `/opt/actualbudget/` but this dir does not exists. Maybe we just need to `cp` `/opt/actualbudget` to `/opt/actualbudget_bak`. CC @MickLesk
Author
Owner

@michelroegl-brunner commented on GitHub (Jan 13, 2025):

Merged.

@michelroegl-brunner commented on GitHub (Jan 13, 2025): Merged.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#318