Apt get ошибка 100

I was installing Xfec desktop environment in the Debian 8 OS. I logged in as root and command tasksel in the shell. Among the other chooses, I selected the Xfce

enter image description here

At the time the installation is few seconds left, I get the message tasksel: apt-get failed (100).

enter image description here

I did an sudo apt-get update but the issue seems stayed as it is after the next try. What to do now?

asked Dec 28, 2017 at 6:38

Arefe's user avatar

1

1.Check your /etc/resolv.conf.

This means checking your DNS settings for visiting website correctly. You can Google Public DNS address on internet :)

2.Check your /etc/apt/sources.list

This means checking your «Ubuntu Update Servers» list for using «apt-update» command.

3.Run apt-get update && apt-get install vim(or whatever the app is) for testing to see if it works.

4.Reboot and try it again…

Thanks for guys who given any suggestions :)

answered Jan 24, 2018 at 10:01

welrod's user avatar

welrodwelrod

1411 silver badge6 bronze badges

4

This just happened to me. In my case the problem was caused by an previously interrupted package transaction. The solution was to run:

dpkg --configure -a

After that, tasksel worked as expected.

(short quick answer, just in case it helps someone out!)

answered Sep 18, 2018 at 9:52

starfry's user avatar

starfrystarfry

1,58715 silver badges30 bronze badges

2

I had this problem and both answers above helped me, I restarted it a couple of times and final time this worked

sudo apt-get update 
dpkg --configure -a

and finally

sudo tasksel

answered Jul 27, 2019 at 9:25

TheErminK's user avatar

TheErminKTheErminK

1011 silver badge3 bronze badges

1

I had the same problem — the error code given by tasksel (100) is rather non-descriptive; I found out the actual reason why it failed in my case when running the tasksel command from the cli:

apt-get install kde-plasma-desktop

Gives the following error message:

0 upgraded, 904 newly installed, 0 to remove and 0 not upgraded.
Need to get 680 MB of archives.
After this operation, 2,279 MB of additional disk space will be used.
E: You don't have enough free space in /var/cache/apt/archives/.

After extending the root partition, the command completes without problems.

answered Oct 7, 2020 at 13:44

Fabien H. Dumay's user avatar

Try this:

sudo apt-get purge
sudo apt-get update
sudo tasksel

G-Man Says 'Reinstate Monica''s user avatar

answered Dec 8, 2019 at 3:37

manchester's user avatar

I experienced this error after installing the gnome-shell package on raspbian with apt, subsequently uninstalling it, then trying to install GNOME again with tasksel.

I solved the problem by running sudo apt install gnome-software, which resolved a dependency conflict, and allowed tasksel to continue.

answered Jul 25, 2022 at 20:05

Benny Powers's user avatar

1

You must log in to answer this question.

Not the answer you’re looking for? Browse other questions tagged

.

Источник

Whenever I am trying to install anything using apt-get, it shows:

Could not exec dpkg
Returned with error code (100)

Same result when I execute 

apt-get upgrade

When I type 

dpkg --configure -a

It tells me dpkg is not installed and when I run:

apt-get install dpkg

it tells it is the newest version, but when I run:

apt-get install --reinstall dpkg

it again returns error code (100)

Even system updates are failing to occur, no software is getting downloaded even from the Software Download Center.

I use Ubuntu 14.04 LTS

Fabby's user avatar

Fabby

34.4k38 gold badges97 silver badges191 bronze badges

asked Apr 8, 2017 at 9:14

Diganta Dutta's user avatar

0

Check if dpkg is missing some libraries:

ldd /usr/bin/dpkg

If any library is missing, try to install it. If that’s not the issue, then try the following:

sudo -i
mkdir /tmp/dpkg

cd /tmp/dpkg

If you are running a 32 bit version of ubuntu

wget http://security.ubuntu.com/ubuntu/pool/main/d/dpkg/dpkg_1.17.5ubuntu5.2_i386.deb

For 64 bit

wget http://security.ubuntu.com/ubuntu/pool/main/d/dpkg/dpkg_1.17.5ubuntu5.2_amd64.deb
ar x dpkg*.deb data.tar.gz
tar xfvz data.tar.gz ./usr/bin/dpkg
sudo cp ./usr/bin/dpkg /usr/bin/
sudo apt-get update
sudo apt-get install --reinstall dpkg

Zanna's user avatar

Zanna♦

69.3k56 gold badges217 silver badges327 bronze badges

answered Apr 8, 2017 at 13:50

Noisy_Botnet's user avatar

Noisy_BotnetNoisy_Botnet

1,59911 silver badges15 bronze badges

Not the answer you’re looking for? Browse other questions tagged

.

Источник

  • #1

Hello,

Since yesterday, we are getting the following error on multiple servers when running pveupdate:

Code: 

command 'apt-get update' failed: exit code 100

Manually running apt-get update works fine. We always used apt-get dist-upgrade when upgrading.
We are using the paid entreprise repo.

Any idea what might cause this ?

Here’s our pveversion

Code: 

proxmox-ve: 5.1-41 (running kernel: 4.13.13-5-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13.13-6-pve: 4.13.13-41
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve3
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-3
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-22
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.6-pve1~bpo9

Last edited:

Alwin

Alwin

Proxmox Retired Staff


  • #2

What is the output of ‘apt-get update’?

  • #3

What is the output of ‘apt-get update’?

I think it might be related to the debian repo because it gets stuck at

Code: 

0% [Connecting to ftp.ca.debian.org (192.175.120.168)]

and sometime it works without any issue.

Code: 

Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 https://enterprise.proxmox.com/debian/pve stretch InRelease
Ign:3 http://linux.dell.com/repo/community/debian jessie InRelease
Hit:4 http://linux.dell.com/repo/community/debian jessie Release
Ign:6 http://ftp.ca.debian.org/debian stretch InRelease
Hit:7 http://ftp.ca.debian.org/debian stretch Release
Reading package lists... Done

EDIT:
Using an online ping tool confirms the debian ca repo is having issue

Code: 

packets transmitted     9
received     0
packet loss     100 %
time     8238 ms

  • #4

Hi!

Having the issue and its not the ca repo of Debian.
I am using the de repo.

Manual update — no roblems!

Any suggestions?

Regards

Oh, here is the output of «apt-get update»:

Code: 

Ign:1 http://mirror.hetzner.de/debian/packages stretch InRelease
Hit:2 http://mirror.hetzner.de/debian/security stretch/updates InRelease
Hit:3 http://mirror.hetzner.de/debian/packages stretch-updates InRelease
Hit:4 http://mirror.hetzner.de/debian/packages stretch Release
Get:5 http://download.proxmox.com/debian/pve stretch InRelease [3,052 B]
Ign:6 http://ftp.debian.org/debian stretch InRelease
Ign:7 http://ftp.de.debian.org/debian stretch InRelease
Hit:8 http://ftp.debian.org/debian stretch Release
Hit:9 http://ftp.de.debian.org/debian stretch-updates InRelease
Hit:10 http://ftp.de.debian.org/debian stretch Release
Hit:11 http://security.debian.org/debian-security stretch/updates InRelease
Hit:12 http://security.debian.org stretch/updates InRelease
Err:5 http://download.proxmox.com/debian/pve stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0D9A1950E2EF0603
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.proxmox.com/debian/pve stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0D9A1950E2EF0603
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/stretch/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0D9A1950E2EF0603
W: Some index files failed to download. They have been ignored, or old ones used instead.

Alwin

Alwin

Proxmox Retired Staff


  • #6

Im also having a issue with the update.

Code: 

starting apt-get update
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 https://enterprise.proxmox.com/debian/pve stretch InRelease
Ign:3 https://enterprise.proxmox.com/debian/pve stretch Release
Ign:4 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:5 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:6 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:4 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:5 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:6 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:4 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:5 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:6 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:4 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:5 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:6 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:4 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:5 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:6 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:4 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Err:5 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
  401  Unauthorized
Ign:6 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:7 http://ftp.us.debian.org/debian stretch InRelease
Hit:8 http://ftp.us.debian.org/debian stretch-updates InRelease
Hit:9 http://ftp.us.debian.org/debian stretch Release
Reading package lists...
W: The repository 'https://enterprise.proxmox.com/debian/pve stretch Release' does not have a Release file.
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/stretch/pve-enterprise/binary-amd64/Packages  401  Unauthorized
E: Some index files failed to download. They have been ignored, or old ones used instead.
TASK ERROR: command 'apt-get update' failed: exit code 100

Stoiko Ivanov


  • #8

Another cause: After upgrading my cluster to Proxmox 6 I got the apt-get error 100 on all nodes. Turns out I forgot to disable the /etc/apt/sources.list.d/corosync3.list.
Anything that breaks apt is usually pretty simple to troubleshoot; run apt-get update manually and read the error.

  • #9

I went to each node and did this: mv /etc/apt/sources.list.d/pve-enterprise.list /tmp

  • #10

TASK ERROR: command ‘apt-get update’ failed: exit code 100

  • #11

If you encounter the error TASK ERROR: command ‘apt-get update’ failed: exit code 100 you double-click the log information to see the full output of apt-get. I have the issue:

Code: 

starting apt-get update
Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Hit:2 https://enterprise.proxmox.com/debian/pve buster InRelease
Get:3 http://ftp.pl.debian.org/debian buster InRelease [122 kB]
Get:4 http://ftp.pl.debian.org/debian buster-updates InRelease [51.9 kB]
Reading package lists...
E: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://ftp.pl.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://ftp.pl.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
TASK ERROR: command 'apt-get update' failed: exit code 100

So I have issued the command:

Code: 

apt-get update --allow-releaseinfo-change

This has fixed the problem for me.

Last edited:

  • #12

@beumont , make this does not generate problems in the future?.
I don’t think to upgrade to Debian 11. I prefer clean installs when there are major version available ( For E. pve6.4 to 7.X)

there I saw a problem, when doing this, old updates were listed and they conflicted
(I’m not 100% sure about this, I just read it)

  • #13

If you encounter the error TASK ERROR: command ‘apt-get update’ failed: exit code 100 you double-click the log information to see the full output of apt-get. I have the issue:

Code: 

starting apt-get update
Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Hit:2 https://enterprise.proxmox.com/debian/pve buster InRelease
Get:3 http://ftp.pl.debian.org/debian buster InRelease [122 kB]
Get:4 http://ftp.pl.debian.org/debian buster-updates InRelease [51.9 kB]
Reading package lists...
E: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://ftp.pl.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://ftp.pl.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
TASK ERROR: command 'apt-get update' failed: exit code 100

So I have issued the command:

Code: 

apt-get update --allow-releaseinfo-change

This has fixed the problem for me.

There is also another simple solution for this case.
You can manually run apt update and confirm questions

Code: 

Get:1 http://ftp.pl.debian.org/debian buster InRelease [122 kB]
Get:2 http://ftp.pl.debian.org/debian buster-updates InRelease [51.9 kB]                                                                             
Get:3 http://security.debian.org buster/updates InRelease [65.4 kB]           
Hit:4 https://enterprise.proxmox.com/debian/pve buster InRelease               
E: Repository 'http://ftp.pl.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
E: Repository 'http://ftp.pl.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
E: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
Get:5 http://security.debian.org buster/updates/main amd64 Packages [302 kB]                                                                                           
Get:6 http://security.debian.org buster/updates/main Translation-en [159 kB]                                                                                           
Fetched 635 kB in 7s (96.9 kB/s)                                                                                                                                       
Reading package lists... Done
Building dependency tree       
Reading state information... Done

Next apt update will run without any problems

Источник

Linux is the operating system of choice for anyone who wants to tinker around with their computer without worrying about breaking too many things. That said, Linux also has its fair share of bugs and problems that can come up at any given time. 

Apt-get is one of the most important tools in Linux as it allows you to install tools and upgrade your existing Linux distribution. This means that if Apt-get stops working on your system, you can run into a host of problems.

In this article, we’re taking a look at how to fix the “Task error: command apt-get update failed: exit code 100” in Linux as well as the major causes behind the error.

What causes this error?

The main cause behind this error is that the tool is unable to access the repositories you’re using to fetch the required tool or update. This can in turn be caused by either the repository being offline or if you’re trying to access a paid repository that you aren’t subscribed to yet. 

Also read: Valorant freezes PC on startup: 13 Fixes

How to fix this?

Here are three fixes you can try out. 

Check internet connection

Now’s a good time to check whether or not you have an active internet connection. If you’re on WiFi, make sure you’ve got an active link and that there are no signal issues. On cellular data, ensure that it’s enabled and that you’re getting good network coverage. 

Restarting your router can help get rid of a bunch of seemingly random internet and connectivity issues that may be hindering your connection to the Linux servers. 

Comment out the Proxmox instance

The error also commonly occurs when trying to install or update the Proxmox instance from web GUI or through the terminal by using apt-get update. The fix is to just remove the repository from the repo list. 

All you have to do is run the following command in your terminal.

cp /etc/apt/sources.list.d/pve-enterprise.list /etc/apt/sources.list.d/pve-enterprise.list.backup && echo -e "#$(cat /etc/apt/sources.list.d/pve-enterprise.list)" > /etc/apt/sources.list.d/pve-enterprise.list

Manually update the repo list

Last but not least, you can also manually update your repo list to remove any domains that might be causing issues.

Step 1: Change the active working directory to one where your repo list is saved. Usually, it’s located at the path given below. 

cd /etc/apt/sources.list.d

Step 2: As a precaution, we’re backing up the repo file so we can go back in case of some irreversible changes. 

cp pve-enterprise.list pve-enterprise.list.backup

Step 3: Use Nano to open the file and edit it as required. 

nano pve-enterprise.list

Step 4: Find the line given below and add a ‘#’ at the starting of the line to comment it and effectively remove it from the repo list. Additionally, check for any other domains that may be causing issues and comment them out too. 

https://enterprise.proxmox.com/debian/pve%20buster%20pve-enterprise

Now try running the update again and it should work just fine.

Also read: How to unfreeze Venmo account?

Источник
Proxmox ошибка обновления
  • Добавил Win32
  • Добавлен в 28.12.2022
  • Просмотров 1,489
  • Смотреть другие уроки в категории Linux сервер

HMARA.IO VPS

Если у вас нету подписки, то в панели проксмокс будет ругаться с ошибкой обновления TASK ERROR: command ‘apt-get update’ failed: exit code 100
или
E: The repository ‘https://enterprise.proxmox.com/debian/pve bullseye InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.

Чтобы устранить это, нужно подключить некоммерческий репозиторий для обновления бесплатной системы Proxmox.
Удаляем файл коммерческого репозитория 

 rm -f /etc/apt/sources.list.d/pve-enterprise.list

Создаем новый 

cat > /etc/apt/sources.list.d/pve-no-subscription.list <<EOF 
deb http://download.proxmox.com/debian/pve buster pve-no-subscription
EOF

после чего обновляем apt-get update и ошибки об отсутствии подписки больше не будет.

Поделись с друзьями:

proxmox, ошибка обновления, update

0 комментарии

Пожалуйста, авторизуйтесь для добавления комментария.

Пока нет комментариев.

Источник

Понравилась статья? Поделить с друзьями:
  • Apt get исправление ошибок
  • Aqsd 129 ошибка f01
  • Apt get update ошибка сегментирования
  • Apu контур 3 неисправен мерседес актрос ошибка
  • Aptdaemon программная ошибка