Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Actual Budget Update command causes an issue #1424

Closed
1 of 2 tasks
danluckner opened this issue Jan 11, 2025 · 3 comments
Closed
1 of 2 tasks

Actual Budget Update command causes an issue #1424

danluckner opened this issue Jan 11, 2025 · 3 comments

Comments

@danluckner
Copy link

danluckner commented 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.

@Telesphoreo
Copy link

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

@dosten
Copy link
Contributor

dosten commented Jan 13, 2025

The issue is related to 5170056

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

@michelroegl-brunner
Copy link
Member

Merged.

@community-scripts community-scripts locked as resolved and limited conversation to collaborators Jan 13, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants