Update Documentation - Unable to run commands using sudo - Raspberry Pi #513

New Issue

Closed

opened 2022-03-29 04:38:29 +00:00 by R0cketM0nster · 3 comments

R0cketM0nster commented 2022-03-29 04:38:29 +00:00

Copy Link

What I'm trying to do and why

Trying to run sudo borgmatic --version after install to confirm installation completed successfully

Steps to reproduce (if a bug)

run sudo borgmatic --version

Actual behavior (if a bug)

sudo: borgmatic: command not found

Expected behavior (if a bug)

Output version of borgmatic

Other notes / implementation ideas

Environment

borgmatic version: [1.5.24]

Use sudo borgmatic --version or sudo pip show borgmatic | grep ^Version

borgmatic installation method: [Debian - "sudo pip3 install --user --upgrade borgmatic"]

Borg version: [borg 1.1.16]

Use sudo borg --version

Python version: [Python 3.9.2]

Use python3 --version

operating system and version: [Debian GNU/Linux 11 (bullseye)]

The fix for this is to add the path to the sudo path, as per the answer here - https://askubuntu.com/questions/611528/why-cant-sudo-find-a-command-after-i-added-it-to-path

Run the following command - sudo visudo

Add the path "/root/.local/bin" as below:

#### What I'm trying to do and why Trying to run sudo borgmatic --version after install to confirm installation completed successfully #### Steps to reproduce (if a bug) run sudo borgmatic --version #### Actual behavior (if a bug) sudo: borgmatic: command not found #### Expected behavior (if a bug) Output version of borgmatic #### Other notes / implementation ideas #### Environment **borgmatic version:** [1.5.24] Use `sudo borgmatic --version` or `sudo pip show borgmatic | grep ^Version` **borgmatic installation method:** [Debian - "sudo pip3 install --user --upgrade borgmatic"] **Borg version:** [borg 1.1.16] Use `sudo borg --version` **Python version:** [Python 3.9.2] Use `python3 --version` **operating system and version:** [Debian GNU/Linux 11 (bullseye)] The fix for this is to add the path to the sudo path, as per the answer here - https://askubuntu.com/questions/611528/why-cant-sudo-find-a-command-after-i-added-it-to-path Run the following command - sudo visudo Add the path "/root/.local/bin" as below: 

image.png

9.9 KiB

R0cketM0nster changed title from Unable to run commands using sudo - Raspberry Pi to Update Documentation - Unable to run commands using sudo - Raspberry Pi 2022-03-29 04:41:03 +00:00

witten commented 2022-03-29 04:53:13 +00:00

Owner

Copy Link

I've never used sudo's secure_path before, but I'm guessing it only takes effect once you've saved the file (which I assume you've done). And it's probably unrelated to this issue, but it looks like you've got a typo in that value.. /bini should be /bin.

I'm not sure what might be going on with the path though. One thing you could try is the alternate path setting approach documented here, instead of visudo's approach: https://torsion.org/borgmatic/docs/how-to/set-up-backups/#installation

If that still doesn't work, then you are always welcome to switch to the global install option described here: https://torsion.org/borgmatic/docs/how-to/set-up-backups/#global-install-option

That option is much less likely to have path issues because it uses global system paths.

Let me know what you find out!

I've never used sudo's `secure_path` before, but I'm guessing it only takes effect once you've saved the file (which I assume you've done). And it's probably unrelated to this issue, but it looks like you've got a typo in that value.. `/bini` should be `/bin`. I'm not sure what might be going on with the path though. One thing you could try is the alternate path setting approach documented here, instead of visudo's approach: https://torsion.org/borgmatic/docs/how-to/set-up-backups/#installation If that *still* doesn't work, then you are always welcome to switch to the global install option described here: https://torsion.org/borgmatic/docs/how-to/set-up-backups/#global-install-option That option is much less likely to have path issues because it uses global system paths. Let me know what you find out!

witten added the

question / support

label 2022-03-29 04:53:20 +00:00

R0cketM0nster commented 2022-03-29 05:39:32 +00:00

Author

Copy Link

Apologies, yes the typo was just in making the original post, the path is correct in my .bashrc file.

This was just to get a note added to the documentation you have referenced, I followed the documentation to add the path to my $PATH and .bashrc file, but this didn't work.

After adding the path to secure_path I can now run the borgmatic commands using sudo. I thought this method could be added as an alternative to the global install method.

Apologies, yes the typo was just in making the original post, the path is correct in my .bashrc file. This was just to get a note added to the documentation you have referenced, I followed the documentation to add the path to my $PATH and .bashrc file, but this didn't work. After adding the path to secure_path I can now run the borgmatic commands using sudo. I thought this method could be added as an alternative to the global install method.

witten referenced this issue from a commit 2022-04-23 21:30:23 +00:00

Add mention of sudo's "secure_path" option in borgmatic installation documentation (#513).

witten commented 2022-04-23 21:30:34 +00:00

Owner

Copy Link

Added to the documentation! Thanks!

Added to the documentation! Thanks!

witten closed this issue 2022-04-23 21:30:34 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#513

No description provided.