Dpkg error 1 expected program not found in path or not executable

Я установил сервер LAMP с помощью команды sudo apt-get install lamp-server^. После этого всякий раз, когда я открывал терминал, начинала появляться следующая ошибка:

 bash: /home/gaja/.bashrccu: No such file or directory 
 bash: /home/gaja/.bashrc: line 4: syntax error near unexpected token (' 
 bash: /home/gaja/.bashrc: line 4: see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)'

Я мог избавиться от этой проблемы , используя ответ, приведенный здесь .

Однако теперь проблема в том, что я не могу установить что-либо с помощью команды sudo apt-get.

Я пытаюсь стать root, а затем повторно запустить команду sudo apt-get install lamp-server^, которая выдает следующую ошибку:

dpkg: warning: 'tar' not found in PATH or not executable
dpkg: error: 1 expected program not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)

Ниже приведен полный вывод выполнения команд:

gaja@gaja-System-Product-Name:~$ sudo su
[sudo] password for gaja:

root@gaja-System-Product-Name:/home/gaja# sudo apt-get install lamp-server^
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'libdbi-perl' for task 'lamp-server'
Note, selecting 'perl-modules' for task 'lamp-server'
Note, selecting 'libaprutil1-dbd-sqlite3' for task 'lamp-server'
Note, selecting 'perl' for task 'lamp-server'
Note, selecting 'apache2-bin' for task 'lamp-server'
Note, selecting 'libapache2-mod-php5' for task 'lamp-server'
Note, selecting 'ssl-cert' for task 'lamp-server'
Note, selecting 'mysql-server-5.5' for task 'lamp-server'
Note, selecting 'mysql-client-core-5.5' for task 'lamp-server'
Note, selecting 'libclass-isa-perl' for task 'lamp-server'
Note, selecting 'mysql-server' for task 'lamp-server'
Note, selecting 'libapr1' for task 'lamp-server'
Note, selecting 'php5-readline' for task 'lamp-server'
Note, selecting 'libaprutil1' for task 'lamp-server'
Note, selecting 'libwrap0' for task 'lamp-server'
Note, selecting 'libdbd-mysql-perl' for task 'lamp-server'
Note, selecting 'apache2-mpm-prefork' for task 'lamp-server'
Note, selecting 'libhtml-template-perl' for task 'lamp-server'
Note, selecting 'mysql-client-5.5' for task 'lamp-server'
Note, selecting 'libaio1' for task 'lamp-server'
Note, selecting 'mysql-common' for task 'lamp-server'
Note, selecting 'libmysqlclient18' for task 'lamp-server'
Note, selecting 'mysql-server-core-5.5' for task 'lamp-server'
Note, selecting 'libterm-readkey-perl' for task 'lamp-server'
Note, selecting 'php5-mysql' for task 'lamp-server'
Note, selecting 'apache2-data' for task 'lamp-server'
Note, selecting 'apache2' for task 'lamp-server'
Note, selecting 'php5-common' for task 'lamp-server'
Note, selecting 'php5-cli' for task 'lamp-server'
Note, selecting 'libswitch-perl' for task 'lamp-server'
Note, selecting 'libaprutil1-ldap' for task 'lamp-server'
Note, selecting 'tcpd' for task 'lamp-server'
libaio1 is already the newest version.
libapr1 is already the newest version.
libaprutil1 is already the newest version.
libaprutil1-dbd-sqlite3 is already the newest version.
libaprutil1-ldap is already the newest version.
libclass-isa-perl is already the newest version.
libdbd-mysql-perl is already the newest version.
libdbi-perl is already the newest version.
libhtml-template-perl is already the newest version.
libswitch-perl is already the newest version.
libterm-readkey-perl is already the newest version.
libwrap0 is already the newest version.
perl is already the newest version.
perl-modules is already the newest version.
ssl-cert is already the newest version.
tcpd is already the newest version.
apache2 is already the newest version.
apache2-bin is already the newest version.
apache2-data is already the newest version.
apache2-mpm-prefork is already the newest version.
libapache2-mod-php5 is already the newest version.
libmysqlclient18 is already the newest version.
mysql-client-5.5 is already the newest version.
mysql-client-core-5.5 is already the newest version.
mysql-common is already the newest version.
mysql-server is already the newest version.
mysql-server-5.5 is already the newest version.
mysql-server-core-5.5 is already the newest version.
php5-cli is already the newest version.
php5-common is already the newest version.
php5-mysql is already the newest version.
php5-readline is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 230 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
dpkg: warning: 'tar' not found in PATH or not executable
dpkg: error: 1 expected program not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)

root@gaja-System-Product-Name:/home/gaja# sudo apt-get install apache2
Reading package lists... Done
Building dependency tree       
Reading state information... Done
apache2 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 230 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
dpkg: warning: 'tar' not found in PATH or not executable
dpkg: error: 1 expected program not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)
root@gaja-System-Product-Name:/home/gaja# 

Некоторые из шагов по устранению неполадок, которые я предпринял по предложению других участников:

$ ls -l /bin/tar
ls: cannot access /bin/tar: No such file or directory

$ apt-cache policy tar
tar: Installed: 1.26+dfsg-8 Candidate: 1.26+dfsg-8 Version table: *** 1.26+dfsg-8 0 500 in.archive.ubuntu.com/ubuntu saucy/main i386 Packages 100 /var/lib/dpkg/status

Я также попытался выполнить следующую команду после переключения на root, но это не либо помогите:

export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

ответ дан chaos
13 April 2017 в 15:25

поделиться

ls -l /etc/rmt
ls -l /usr/lib/mime/packages/tar
ls -l /usr/sbin/rmt-tar
ls -l /usr/sbin/tarcat

sudo cp tar /bin/
sudo chmod 755 /bin/tar

-rwxr-xr-x 1 root root ...

ответ дан souravc
13 April 2017 в 15:25

поделиться

sudo apt-get dist-upgrade

dpkg: 3 expected programs not found in PATH or not executable.

su root
apt-get dist-upgrade

ответ дан thohl
13 April 2017 в 15:25

поделиться

export PATH=$PATH:/sbin

ответ дан
7 May 2021 в 20:58

поделиться

Problem description
Steps to reproduce

pkg install busybox
Hit:1 https://termux.net stable InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
28 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
busybox is already the newest version (1.30.1-4).
0 upgraded, 0 newly installed, 0 to remove and 28 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
dpkg: warning: 'tar' not found in PATH or not executable
dpkg: error: 1 expected program not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /data/data/com.termux/files/usr/bin/dpkg returned an error code (2)

echo $PATH
/data/data/com.termux/files/usr/bin:/data/data/com.termux/files/usr/bin/applets

Expected behavior

Additional information
I did not expect apt-get -qq upgrade to break everything

/data/data/com.termux/files/usr/bin/busybox  tar
BusyBox v1.30.1 (2019-07-28 21:51:06 UTC) multi-call b.   inary.

Usage: tar c|x|t [-ZzJjahmvokO] [-f TARFILE] [-C DIR] [-T FILE] [-X FILE] [--exclude PATTERN]... [FILE]...

Create, extract, or list files from a tar file

    c       Create
    x       Extract
    t       List
    -f FILE Name of TARFILE ('-' for stdin/out)
    -C DIR  Change to DIR before operation
    -v      Verbose
    -O      Extract to stdout
    -m      Don't restore mtime
    -o      Don't restore user:group
    -k      Don't replace existing files
    -Z      (De)compress using compress
    -z      (De)compress using gzip
    -J      (De)compress using xz
    -j      (De)compress using bzip2
    -a      (De)compress using lzma
    -h      Follow symlinks
    -T FILE File with names to include
    -X FILE File with glob patterns to exclude
    --exclude PATTERN       Glob pattern to exclude

cd /data/data/com.termux/files/usr/bin/
ln -s busybox tar

Ok that let me finish the busybox config but now

pkg install wget
Hit:1 https://termux.net stable InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
28 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  pcre
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  bzip2 diffutils dpkg gzip libandroid-support
  libbz2 libiconv liblzma pcre2 tar xz-utils
  zlib
The following NEW packages will be installed:
  bzip2 diffutils gzip libiconv pcre2 tar
  xz-utils zlib
The following packages will be upgraded:
  dpkg libandroid-support libbz2 liblzma wget
5 upgraded, 8 newly installed, 0 to remove and 23 not upgraded.
Need to get 0 B/2071 kB of archives.
After this operation, 4923 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
E.: This installation run will require temporarily removing the essential package libandroid-
support:aarch64 due to a Conflicts/Pre-Depends loop. This is often bad, but if you really want to do it,     activate the APT::Force-LoopBreak option.
E: Internal Error, Could not early remove libandroid-support:aarch64 (2)

Which I assume is the origonal issue

Another apt-get -qq upgrade fixed things though I lost a few of my package selections (grep findutils).

Bad repo? Temp bug?

Hello,

When trying to install local .deb package, on Debian 10, I get the following errors.

dpkg: warning: ‘ldconfig’ not found in PATH or not executable
dpkg: warning: ‘start-stop-daemon’ not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable

The package can’t be installed.

If you use su to become root, you have to enter

If you just use su on its own, you keep the user’s path, which does not include ldconfig etc.

EDIT: . Roseway responded faster than I did. My observation is the same, but with a longer explanation.

questlinq wrote:

Code: Select all

dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable

/sbin/ldconfig is provided by the libc-bin package and /sbin/start-stop-daemon is provided by the dpkg package. Both are «essential» packages. They must have been installed at installation.

So assuming that they’re installed … How did you become root? On Debian Buster, you now have to add a dash («-«) after the su command:

$ su -
Password:
# dpkg -i <debfile>

When you add the dash, your $PATH will contain the /sbin/ directories:

$ su -
Password: 
# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

If you forget to add the dash, your $PATH will not:

$ su
Password: 
# echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

Thank you to both of you — it worked!

Usually, I sign in as user and then I do «su» + «password» and then «apt install .. «

Do I always need to use «su -» in Buster?

questlinq wrote:Do I always need to use «su -» in Buster?

As explained by Soul Singin’ and roseway, if you need to run anything which is not in your user PATH, yes.
I sometimes run apt install (which is in /usr/bin/ therefore in user’s PATH) without the dash after su, , to install a locally downloaded package. apt install is better than dpkg -i as it will also resolve and download dependencies if there are any. eg. —

apt install ./<downloaded-package>

Don’t forget the ./ (or give the full path) so apt knows it’s installing locally and not from repository.
Of course you’d still need su — if the installer calls ldconfig or anything else in /usr/sbin/ .

See also — http://forums.debian.net/viewtopic.php?f=16&t=142973

sunrat wrote:to install a locally downloaded package. apt install is better than dpkg -i as it will also resolve and download dependencies if there are any. eg. —

Code: Select all

apt install ./<downloaded-package>

Don’t forget the ./ (or give the full path) so apt knows it’s installing locally and not from repository.

Thank you for sharing this tip. I was unaware of it.

But my experiments with that command downloaded the package from the repository. They did not install from the local file. (See below).

So suppose that I built a backport. Under what conditions would the «dot-slash» installation method install my backport? and under what conditions would it install from the repository?

——— ——— ——— ———

Below are the results of my experiment with the (trivial) hello package:

# apt install ./hello_2.10-2_amd64.deb 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'hello' instead of './hello_2.10-2_amd64.deb'
The following NEW packages will be installed:
  hello
0 upgraded, 1 newly installed, 0 to remove and 30 not upgraded.
Need to get 56.1 kB of archives.
After this operation, 287 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main amd64 hello amd64 2.10-2 [56.1 kB]
Fetched 56.1 kB in 0s (444 kB/s)
Selecting previously unselected package hello.
(Reading database ... 311442 files and directories currently installed.)
Preparing to unpack .../hello_2.10-2_amd64.deb ...
Unpacking hello (2.10-2) ...
Setting up hello (2.10-2) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...

I also tried with apt-get and obtained the same result:

# apt-get install ./hello_2.10-2_amd64.deb 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'hello' instead of './hello_2.10-2_amd64.deb'
The following NEW packages will be installed:
  hello
0 upgraded, 1 newly installed, 0 to remove and 30 not upgraded.
Need to get 56.1 kB of archives.
After this operation, 287 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main amd64 hello amd64 2.10-2 [56.1 kB]
Fetched 56.1 kB in 0s (276 kB/s)
Selecting previously unselected package hello.
(Reading database ... 311442 files and directories currently installed.)
Preparing to unpack .../hello_2.10-2_amd64.deb ...
Unpacking hello (2.10-2) ...
Setting up hello (2.10-2) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...

Soul Singin’ wrote:Under what conditions would the «dot-slash» installation method install my backport?

If your backport was versioned correctly to indicate that it was newer than the package in the repositories.

stevepusser wrote:After becoming root with «su -«, you moved to your /root directory, and apt could not find the local deb in that directory. If you have enabled sudo, you can use that instead with apt to avoid that problem.

Exactly. The command needs to be run with the terminal opened in the same directory as the file. su — switches you to root user’s environment, which means it also switches the terminal to root user’s home directory. That’s why I said «Don’t forget the ./ (or give the full path)». If you use su — , you could cd back to where the file resides. the «./» applies to when your terminal is open at the directory containing the file, «(or give the full path)» for when it is anywhere else.

Head_on_a_Stick wrote:

Soul Singin’ wrote:Under what conditions would the «dot-slash» installation method install my backport?

If your backport was versioned correctly to indicate that it was newer than the package in the repositories.

Thanks! .

stevepusser wrote:After becoming root with «su -«, you moved to your /root directory, and apt could not find the local deb in that directory. If you have enabled sudo, you can use that instead with apt to avoid that problem.

Not in this case. Being in the wrong directory generates a different error message. See below — where I am intentionally in the wrong directory.

# apt install ./hello_2.10-2_amd64.deb 
Reading package lists... Done
E: Unsupported file ./hello_2.10-2_amd64.deb given on commandline

# apt-get install ./hello_2.10-2_amd64.deb 
Reading package lists... Done
E: Unsupported file ./hello_2.10-2_amd64.deb given on commandline

Deb-fan wrote:Lol … or in the grandest of gnu/Nix noobishness style. While in da directory (folder thingy) containing said .deb(s), right click xyz-filemanager, select «Open terminal here» ? Then go from there ! Sorry, sleep deprived and irritable I still do that often enough myself anyway, when not in the cli nav(cd) kind of mood.

Look at the date that I joined this forum. Read some of the HowTo guides in my signature. Do you really think I’m a noob?

Answer: Yes! That’s the way I do it every time. It’s so much more convenient that way. .

^LMAO !

Hey … true, whatever works. Was on the verge of having a meltdown, so was joshing the OP but do that approach often enough too. Got a few hrs sleep and another cup of coffee am ready to go for awhile longer again.