Ошибка обновления proxmox 100

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?

gerardsamara

Member

Proxmox 5.4 installed on Debian9 machine

I know there are already a lot of threads on this issue but i was unable to solve this issue.

Tha package repositories have been setup according the «installation-and-configuration» guide
. ://pve.proxmox.com/wiki/Package_Repositories

Here is the log when hitting the «refresh command» in the UPDATE Panel of the Proxmox page ( same in cmd mode in SSH session )
I have removed all the http/https from the log file otherwise posting the thread failed ( No link allowed for new user)

————————————————————-
starting apt-get update
Get:1 ://security.debian.org stretch/updates InRelease [94.3 kB]
Ign:2 ://ftp.debian.org/debian stretch InRelease
Hit:3 ://ftp.debian.org/debian stretch Release
Hit:5 ://download.proxmox.com/debian/pve stretch InRelease
Ign:6 ://enterprise.proxmox.com/debian/pve stretch InRelease
Ign:7 ://enterprise.proxmox.com/debian/pve stretch Release
Ign:8 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:9 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:10 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:8 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:9 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:10 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:8 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:9 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:10 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:8 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:9 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:10 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:8 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:9 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:10 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:8 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Err:9 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
401 Unauthorized
Ign:10 ://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Fetched 94.3 kB in 3s (30.4 kB/s)
Reading package lists.
W: The repository ‘://enterprise.proxmox.com/debian/pve stretch Release’ does not have a Release file.
E: Failed to fetch ://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

Please any advice as the pve-enterprise repository is disabled.
Thgank you

Источник

[SOLVED] command ‘apt-get update’ failed: exit code 100

ca_maer

Active Member

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

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

Alwin

Proxmox Retired Staff

Best regards,
Alwin

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

ca_maer

Active Member

and sometime it works without any issue.

pve n00b

Member

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

Manual update — no roblems!

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

Alwin

Proxmox Retired Staff

Best regards,
Alwin

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

Logan_Rocks

Member

Im also having a issue with the update.

Stoiko Ivanov

Proxmox Staff Member

Best regards,
Stoiko

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

Xeata_James

Member

srslol

New Member

phillip.n

New Member

beumont

New Member

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:

So I have issued the command:

penguin2020

Member

@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)

aciek

New Member

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:

Источник

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

MoxProxxer

Active Member

So I have been greeted today morning with this entry in the task log on the machine. Called apt-get update manually and behold:

..all good before this.
Ign:9 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Err:10 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
401 Unauthorized
Ign:11 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en_US
Ign:12 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Fetched 91.0 kB in 1s (64.6 kB/s)
Reading package lists. Done
W: The repository ‘https://enterprise.proxmox.com/debian/pve stretch Release’ does not have a Release file.
N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
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.

So I just commented out the line in /etc/apt/sources.list.d/pve-enterprise.list

Not sure if this is the right thing to do, though.

Proxmox Retired Staff

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

MoxProxxer

Active Member

I am aware of that, it’s just that it happened by default. I believe there are other threads here that suggest to not include the enterprise repo in the default install.

By the way — today morning:

————
Task viewer: Update package database

Stop
error reading cached package status in /var/lib/pve-manager/pkgupdates

TASK ERROR: fileparse(): need a valid pathname at /usr/share/perl5/PVE/API2/APT.pm line 91.
————-

Not sure what to make of this. Happens in the get_changelog_url anonymous sub, seems $info-> is undefined or malformed.

ceterum censeo: It is next to impossible to paste code — or any text — into this discussion forum.

MoxProxxer

Active Member

Investigating this further, a manual «apt update» revealed:

.
Fetched 185 kB in 0s (259 kB/s)
Reading package lists. Done
Building dependency tree
Reading state information. Done
5 packages can be upgraded. Run ‘apt list —upgradable’ to see them.
W: Problem unlinking the file auxfiles — Clean (21: Is a directory)

I can confirm, that after a rm -rf /var/lib/apt/lists followed by apt update the problem is gone. For apt. Proxmox updater still hangs there

Proxmox Retired Staff

It should go away after a page reload or maybe a service restart (pveproxy).

If you have no subscription, you should switch to the pve-no-subscription repository:
https://pve.proxmox.com/wiki/Package_Repositories

Best regards,
Oguz

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

MoxProxxer

Active Member

Unfortunately neither nor.

pve-enterprise is commented out, there’s only the pve-no-subscription repo.

I restarted the pveproxy service and reloaded the page. That Perl error is still there.

apt update works.

Can it be, that there is a problem/incompatibility with https://wiki.debian.org/AptCacherNg ?

# apt update
Hit:1 http://download.proxmox.com/debian/pve stretch InRelease
Hit:2 http://vmhost:3142/security.debian.org stretch/updates InRelease
Ign:3 http://vmhost:3142/ftp.de.debian.org/debian stretch InRelease
Get:4 http://vmhost:3142/ftp.de.debian.org/debian stretch-updates InRelease [91.0 kB]
Hit:5 http://vmhost:3142/ftp.de.debian.org/debian stretch Release
Fetched 91.0 kB in 0s (97.7 kB/s)
Reading package lists. Done
Building dependency tree
Reading state information. Done
All packages are up to date.

Proxmox Retired Staff

Best regards,
Oguz

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

MoxProxxer

Active Member

Proxmox Retired Staff

pve-manager PVE/API2/APT.pm should be the file.

Take a look at here for information about how to send your patch: https://pve.proxmox.com/wiki/Developer_Documentation

Thanks!

Edit: You can also open a Bug Report on bugzilla.proxmox.com with some extra information after testing this

Best regards,
Oguz

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

MoxProxxer

Active Member

Somehow I read that advice two times already.

You could add to the Developer Documentation the relevant parts. Like e.g. how to debug the stuff.

because neither print/say, nor `cat $xxx > /dev/tmp` nor die «some message» in the source is working when one tries to see what is going on.

After adding a die, restarting pveproxy, having now the same error message + 1 line (line 92) I know the die is there, but it’s simply ignored. Good job.

Looking in /var/log/pveproxy reveals also . nothing, except lots of useless access.log messages «GET /api2/json/nodes/xxxxxx/status HTTP/1.1» 200 every second — seriously?

contains the error I see on the screen and nothing else. Ok, looking up the inheritance hierarchy . Somehow syslog should be used. Yeah I will dig into where you catch the dies and the output. When there’s time.

Sure, I may be new to Proxmox and many things may become clear later on, but please at least consider some of the entry barriers mentioned.

3 days later my die is found.

error reading cached package status in /var/lib/pve-manager/pkgupdates
Use of uninitialized value in die at /usr/share/perl5/PVE/API2/APT.pm line 91.

TASK ERROR: Died at /usr/share/perl5/PVE/API2/APT.pm line 91.

needless to say that I did restart pveproxy.
Seems like the APT upstream package AptPkg has a problem with the AptCacheNg, because PVE::API2::APT is getting a undefined value already. I will try to find out how to rectify that with upstream.

Источник

potetpro

Member

So after upgrading 4 of our Proxmox servers from 6.0 to 6.1, i get this error:

But only on 2 of 4 servers. And all of them have license.

aaron

Proxmox Staff Member

Best regards,
Aaron

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

potetpro

Member

kobruc

New Member

Heere is the same:
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease 401 Unauthorized [IP: xxx.xxx.xxx.xxx]
E: The repository ‘https://enterprise.proxmox.com/debian/pve buster InRelease’ is not signed.
TASK ERROR: command ‘apt-get update’ failed: exit code 100

How should i get to work the update?

Stoiko Ivanov

Proxmox Staff Member

If you have a subscription — go to the node’s Subscription tab and click check — make sure that it is recognized as valid.
If you don’t have a subscription configure a different repository (or get a subscription):
https://pve.proxmox.com/wiki/Package_Repositories

I hope this helps!

Best regards,
Stoiko

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

Источник

Cannot update: apt-get error 100

ChimCham

New Member

I have a very simple set-up, and am trying to get it working. I don’t have an enterprise license. When I try to update in my node, I have this error:

starting apt-get update
Hit:1 http://ftp.us.debian.org/debian bullseye InRelease
Hit:2 http://ftp.us.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org bullseye-security InRelease
Err:4 https://enterprise.proxmox.com/debian/pve bullseye InRelease
401 Unauthorized [IP: 144.217.225.162 443]
Reading package lists.
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 144.217.225.162 443]
E: The repository ‘https://enterprise.proxmox.com/debian/pve bullseye InRelease’ is not signed.
TASK ERROR: command ‘apt-get update’ failed: exit code 100

How can I fix this error? Thank you, in advance.

sterzy

Proxmox Staff Member

since you have no subscription, you will need to configure the no-subscription [1] repository. Otherwise your node will still try to update from the enterprise repo, but won’t be authorized to do so. Hence the error that you see.

Best regards,
Stefan

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

Источник

HOWTO: First Steps After Installation

Add the no subscription repository…

echo "deb http://download.proxmox.com/debian/pve buster pve-no-subscription" >>/etc/apt/sources.list
apt-get update
apt-get check
apt-get --simulate dist-upgrade

Simple Repository Setup for Proxmox

HOWTO: Update PCI and USB IDs

update-pciids
update-usbids

HOWTO: Set System Locale

dpkg-reconfigure locales   (and choose en_GB.utf8)

Thanks — https://wiki.debian.org/Locale

HOWTO: Change To Software RAID and LVM

Do NOT do this if you are using the new 4.x version of Proxmox and have chosen ZFS (RAID) filesystem!

Install Software

aptitude install mdadm

Prepare Disks

sgdisk -R=/dev/sdb /dev/sda
sgdisk -t 2:fd00 /dev/sdb
sgdisk -t 3:fd00 /dev/sdb
sgdisk -R=/dev/sdc /dev/sda
sgdisk -t 2:fd00 /dev/sdc
sgdisk -t 3:fd00 /dev/sdc
parted

GNU Parted 2.3
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print                                                            
Model: ATA WDC WD3000FYYZ-0 (scsi)
Disk /dev/sda: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number  Start   End     Size    File system  Name     Flags
 1      1049kB  2097kB  1049kB               primary  bios_grub
 2      2097kB  537MB   535MB   ext3         primary  boot
 3      537MB   3001GB  3000GB               primary  lvm
(parted)                                                                  
(parted) select /dev/sdb                                                  
Using /dev/sdb
(parted) print                                                  
Model: ATA WDC WD3000FYYZ-0 (scsi)
Disk /dev/sdb: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number  Start   End     Size    File system  Name     Flags
 1      1049kB  2097kB  1049kB               primary  bios_grub
 2      2097kB  537MB   535MB                primary  raid
 3      537MB   3001GB  3000GB               primary  raid

Create RAID Arrays

mdadm --create /dev/md0 --level=1 --raid-disks=2 missing /dev/sdb2
mdadm --create /dev/md1 --level=1 --raid-disks=2 missing /dev/sdb3
cat /proc/partitions /proc/mdstat 

Copy Boot Files To RAID Array

mkfs.ext3 /dev/md0 
mkdir /mnt/tmp
mount /dev/md0 /mnt/tmp
cp -ax /boot/* /mnt/tmp
umount /mnt/tmp
rmdir /mnt/tmp

Change Boot Filesystem Tab

nano /etc/fstab
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
/dev/md0 /boot ext3 defaults 0 1
#UUID=46b4d3d6-fdec-43b6-a4cb-3f8f8a9c6c10 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0

Do not reboot now as per kbDone’s page!

Update GRUB Bootloader

echo 'GRUB_DISABLE_LINUX_UUID=true' >> /etc/default/grub
echo 'GRUB_PRELOAD_MODULES="raid dmraid"' >> /etc/default/grub
echo raid1 >> /etc/modules
echo raid1 >> /etc/initramfs-tools/modules
grub-install /dev/sda
grub-install /dev/sdb
grub-install /dev/sdc   (because we will actually be adding sdc below)
update-grub
update-initramfs -u

Now reboot.

reboot

Prepare First Disk (Part 1)

sgdisk -t 2:fd00 /dev/sda
mdadm --add /dev/md0 /dev/sda2

Move LVM Data

pvcreate /dev/md1
vgextend pve /dev/md1
pvmove /dev/sda3 /dev/md1   <-- this takes a very long time!
vgreduce pve /dev/sda3
pvremove /dev/sda3

Prepare First Disk (Part 2)

sgdisk -t 3:fd00 /dev/sda
mdadm --add /dev/md1 /dev/sda3   <-- this takes a long time as well
cat /proc/mdstat

Wait for RAID to sync.

mdadm --add /dev/md0 /dev/sdc2
mdadm --add /dev/md1 /dev/sdc3

Update GRUB (Again)

grub-install /dev/sda
grub-install /dev/sdb
grub-install /dev/sdc
update-grub
update-initramfs -t -u
sync

Finish

reboot
cat /proc/mdstat

Thanks — http://kbdone.com/proxmox-ve-3-2-software-raid/

HOWTO: Add ISO Files

In the GUI…

Storage View > Datacenter > server > local > content > Upload

Location on disk…

/var/lib/vz/template/iso

HOWTO: Add Virtual Machine (VM)

Server View > Datacenter > server
Create VM

Ubuntu Linux

Copy Existing — Physical To Virtual (P2V)

Physical

• https://help.ubuntu.com/community/BackupYourSystem/TAR
• sudo tar -czvpf /backup.tar.gz —exclude=/backup.tar.gz —one-file-system /

Virtual

STOP PRESS — new method?! — http://www.fsarchiver.org/QuickStart

• Boot with SystemRescueCD iso in virtual cdrom
• either use the proxmox console, or set root password and restart ssh, and ssh in
• Partition and Format virtual hard disk drive (1:swap,2:ext4)
• mkdir /mnt/sda2 and mount -v /dev/sda2 /mnt/sda2/
• scp physical:/backup.tar.gz root@virtual:/mnt/sda2/
• sudo tar -xzvpf /mnt/sda2/backup.tar.gz -C /mnt/sda2/ —numeric-owner (close console window for this)
• mount -t proc none /mnt/sda2/proc
• mount -o bind /dev /mnt/sda2/dev
• mount -t sysfs /sys /mnt/sda2/sys
• chroot /mnt/sda2 /bin/bash
• blkid /dev/sda1 /dev/sda2
• nano /etc/mtab /etc/fstab /etc/hosts /etc/network/interfaces (change IP address to different to physical)
• touch /var/lock/aptitude
• aptitude -y -v purge mdadm lm-sensors hddtemp smartmontools cpufrequtils
• rm -rfv /var/lib/smartmontools/
• grub-install /dev/sda
• update-initramfs -u
• update-grub
• exit
• reboot

Finish

• When you are happy, then shut down the Physical and change the Virtual IP address, then reboot Virtual 

Windows 7

Fresh Installation

• Create an ISO of the Windows 7 DVD

dd if=/dev/sr0 of=/var/lib/vz/template/iso/win7pro-sp1.iso

• Download the VirtIO Drivers ISO (Changelog)
• Create VM according to the Windows 7 Best Practices page
• CDROM #1 = win7pro-sp1.iso
• CDROM #2 = virtio-win-0.1-81.iso
• CDROM #3 = VMware-tools-windows-9.4.11-2400950.iso
• Start VM and read instructions below

Mouse Driver

This gives you much better mouse performance and uses less resources (than the default ‘usb tablet mouse’).

The vmmouse driver need a reboot to get activated but then you can enable/disable the ‘usb device tablet’ on the fly.

• extract setup.exe from iso
• extract datas from setup.exe
• setup.exe /A /P C:Extract
• drivers are in C:extractProgram FilesVMwareVMware ToolsVMwareDriversmouse

Mouse Driver (64 Bit) — http://packages.vmware.com/tools/esx/latest/windows/x64/index.html (e.g. VMware-tools-windows-9.4.11-2400950.iso)

Mouse Driver (32 Bit) — http://packages.vmware.com/tools/esx/latest/windows/x86/index.html (e.g. VMware-tools-windows-9.4.11-2400950.iso)

Qemu Agent

The qemu-guest-agent is a helper daemon, which is installed in the guest. It is used to exchange information between the host and guest, and to execute command in the guest.

This is a must have!

http://pve.proxmox.com/wiki/Qemu-guest-agent

Links

Tweaks — https://pve.proxmox.com/wiki/Performance_Tweaks

Thanks — https://pve.proxmox.com/wiki/Windows_7_guest_best_practices

Thanks — https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Choose_the_right_driver

HOWTO: RUN VIRTUAL MACHINE IN PROXMOX INSIDE VIRTUALBOX

Because VirtualBox does not support KVM Stacking or KVM-in-KVM, you have to use the QEMU option in Proxmox when running inside VirtualBox.

1. Install Proxmox VE inside VirtualBox and start Proxmox
2. Log in to the Proxmox Web Admin and ‘Create VM’
3. VM > Options > KVM Hardware Virtualization = NO, QEMU Agent = YES

HOWTO: RESIZE DISKS

https://pve.proxmox.com/wiki/Resize_disks

Shut Down Stop The Virtual Machine

Shut down and Stop the VM using the GUI or command line.

GUI

Server View > Datacenter > Node > VM > Hardware > Hard Disk > Resize

COMMAND LINE

In this example, we will be increasing the first virtual hard disk sda from 20Gb to 68Gb.

Resize Virtual Hard Disk

Find out the name of the virtual machine and hard disk, using the GUI (shown above), for example 105 and sata0.

Now, you can resize the virtual disk…

qm resize 105 sata0 +48G

Resize Hard Disk Partition

Boot the VM with a live CD such as SystemRescueCD, and then use ‘parted’ to resize the partition (in our case partition #2)…

parted /dev/sda
(parted) print
(parted) resizepart 2 100%
(parted) print
(parted) quit

Check Hard Disk Filesystem (I)

e2fsck -f /dev/sda2

Resize Hard Disk Filesystem

resize2fs /dev/sda2

Check Hard Disk Filesystem (II)

e2fsck -f /dev/sda2

Poweroff The Virtual Machine

Now, you can shutdown the SystemRescueCD…

poweroff

START THE VIRTUAL MACHINE

Start the VM using the GUI or command line, login and check your disk size.

df -H

http://pve.proxmox.com/wiki/Resize_disks

HOWTO: FIX

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

To fix, run the following option to apt-get …

apt-get update --allow-releaseinfo-change

OR

apt-get update

and answer questions manually …

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

apt-get update: server certificate verification failed

https://pve.proxmox.com/wiki/Server_certificate_verification_failed_when_updating

Manually

To check mountpoint of NFS share…

mount

Disable the NFS share (either in web GUI or on the command line)…

pvesm set yournfsharename_inwebgui --disable 1

To unmount (be patient for up to 10 minutes)…

fusermount -uz /path/to/mountpoint

If no success, then…

umount -f -l -vvv /path/to/mountpoint

https://forum.proxmox.com/threads/nfs-share-umount-f-problem-device-is-busy.26777/

Automatically

nano /etc/rc.local.shutdown

#!/bin/sh -e
echo "NFS Shares are unmounting..."
fusermount -uz /mnt/pve/*
exit 0

http://unix.stackexchange.com/questions/98510/run-a-script-at-shutdown-in-debain#98523

Shutdown Error — TASK ERROR: VM quit powerdown failed — got timeout

Install the app ‘acpid’ in each of your Linux virtual machines…

sudo apt install acpid

HOWTO: ENABLE

Add CPU Frequency Scaling

aptitude install cpufrequtils

Thanks — https://wiki.debian.org/HowTo/CpuFrequencyScaling

HOWTO: CONVERT:

From Proxmox RAW Image To VirtualBox Qcow

-rw-r--r-- 1 root root  20G 2015-02-18 12:54 disk-drive-sata0.raw
-rw-r--r-- 1 root root  330 2015-02-18 12:51 qemu-server.conf

qemu-img convert -f raw -O qcow disk-drive-sata0.raw disk-drive-sata0.qcow

-rw-r--r-- 1 root root 9.8G 2015-02-20 11:03 disk-drive-sata0.qcow
-rw-r--r-- 1 root root  20G 2015-02-18 12:54 disk-drive-sata0.raw
-rw-r--r-- 1 root root  330 2015-02-18 12:51 qemu-server.conf

OVA IMAGE TO Qcow

Instructions

This example shows how to convert the ESET Remote Administrator Virtual Appliance to a Proxmox Virtual Machine.

sudo -i
tar -xf era_appliance.ova
qemu-img convert -p -f vmdk ERA_Appliance-disk1.vmdk -O qcow2 ERA_Appliance-disk1.qcow2
qemu-img info ERA_Appliance-disk1.qcow2

image: ERA_Appliance-disk1.qcow2
virtual size: 64G (68719476736 bytes)
disk size: 7.5G
cluster_size: 65536
Format specific information:
    compat: 1.1
    lazy refcounts: false
    corrupt: false

Open up the OVF file in your editor (it’s XML format) and just check what hardware it requires.

Then, create your new VM in the Proxmox web GUI as per hardware requirements.

Then, copy over the new QCOW2 disk image file we converted OVER the one created by Proxmox.

cp -av ERA_Appliance-disk1.qcow2 /var/lib/vz/images/106/vm-106-disk-1.qcow2

Then, edit the Proxmox VM config file to change the disk size to match the figure in bold above.

nano /etc/pve/nodes/proxmox1/qemu-server/106.conf

bootdisk: ide0
cores: 4
ide0: local:106/vm-106-disk-1.qcow2,format=qcow2,size=64G
ide2: none,media=cdrom
memory: 4096
name: eset1
net0: e1000=5E:EF:04:01:CA:45,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
smbios1: uuid=12936a8c-6417-4e5d-9f7d-f6e06730b72a
sockets: 1
startup: order=7,up=70,down=10

Now, you can go back to the Proxmox web GUI and start the new VM in a Console.

Job, done.

Troubleshooting

If your VM will not start because of this error:-

file system may not support O_DIRECT

It is because you are using the new ZFS with Proxmox, which does not support it.

Then change the Cache setting on your VM to Write Through…

cache=writethrough

Thanks — http://www.jamescoyle.net/how-to/471-zfs-and-glusterfs-network-storage

Links

Upload OVA to Proxmox/ KVM

http://forum.proxmox.com/threads/9309-Convert-OVA-to-working-Proxmox-VM

http://opentox.github.io/installation/2012/08/02/converting-ova-images-to-kvm/

http://matthewmidgett.com/virtualization/5-converting-virtualbox-to-proxmox

http://edoceo.com/notabene/ova-to-vmdk-to-qcow2

HOWTO: Command Line Tools

https://pve.proxmox.com/wiki/Command_line_tools

Check Storage

Settings are kept in…

/etc/pve/storage.cfg

Check the current status with…

pvesm status

This also works to fix an unmounted NFS share (say the NFS server rebooted).

Add A User Using Domain Based Authentication

pveum aclmod / -user joebloggs@DOMAIN -role PVEAuditor

Shell Script To List Status Of Virtual Machines

#!/bin/bash
cd /etc/pve/nodes/<nodename>/qemu-server/
for FILE in *.conf
do
  VMID="${FILE%%.*}"
  echo -n "vm $VMID "
  /usr/sbin/qm status $VMID;
done

Backup All VMs

vzdump --quiet 1 --mailto backupnotify@domain.com --mode snapshot --compress lzo --storage nfs1 --node proxmox1 --all 1

Backup 1 VM

vzdump 219 --mode stop --compress lzo --node proxmox2 --remove 0 --storage nfs1 --mailto backupnotify@domain.com

Shutdown VM

qm shutdown VMID

Thanks — https://pve.proxmox.com/wiki/Virtual_Machine_Startup_and_Shutdown_Behavior

List VMs

qm list

Start VM

qm start VMID

Shutdown VM

qm shutdown VMID

Stop VM

qm stop VMID

HOWTO: DHCP For VMs On Different IP Address Range

https://jay.sh/setting-up-dhcp-for-proxmox-vms/

HOWTO: Change Cron Scheduled Backup Time

sudo nano /etc/pve/vzdump.cron

HOWTO: Change Node IP Address

Use the Web GUI…

Server View > Datacenter > Node > Network > vmbr0 > IP Address > OK > Restart

If you are not able to directly access the Web GUI, use SSH to Port Forward to your computer…

ssh root@proxmox-node -L local-port:remote-server-ip:remote-port

ssh root@123.456.789.0 -L 8006:192.168.1.200:8006

Then, point your web browser to the following address, and hey presto, Web GUI!

https://127.0.0.1:8006

OLD

Update the IP address and DNS IP address in these files…

nano /etc/hosts /etc/network/interfaces /etc/resolv.conf

If it’s a cluster, run this command as well…

/etc/init.d/cman restart

Then, reboot…

reboot

HOWTO: Change Node Hostname Name

WARNING: THIS WORKED FOR ME IN A TEST VIRTUALBOX ENVIRONMENT BUT HAS NOT BEEN TRIED IN PRODUCTION

YOU HAVE BEEN WARNED

THESE INSTRUCTIONS ARE A WORK IN PROGRESS

You may also have to edit some VM .conf files.

nano /etc/hostname /etc/hosts /etc/postfix/main.cf
cd /etc/pve/nodes/
cp -av old new
rm -rfv old
cd /var/lib/rrdcached/db/pve2-node/
cp -av old new
rm -rfv old
reboot

HOWTO: System Update

https://pve.proxmox.com/wiki/Downloads

• Change DNS Server to modem

nano /etc/resolv.conf
nameserver 192.168.0.1

• Shut down all running Virtual Machines
• Turn off Start at Boot for each Virtual Machine (using WebGUI) or…

nano /etc/pve/nodes/proxmox1/qemu-server/*.conf
onboot: 1    <-- delete this line

• Update system software…

screen -rd
apt-get update
apt-get check
apt-get --download-only dist-upgrade
apt-get --simulate dist-upgrade
apt-get --quiet dist-upgrade
(answer YES to Continuing Without Installing GRUB)
grub-mkdevicemap -n
grub-install /dev/sda
grub-install /dev/sdb
grub-install /dev/sdc
update-grub
update-initramfs -t -u
sync
touch /root/misc/system_updated
(exit screen)
reboot

HOWTO: Test ZFS With Virtualbox

…

HOWTO: Cluster

https://www.mattwall.co.uk/2019/06/09/new-proxmox-cluster-pt1.html

https://www.howtoforge.com/tutorial/how-to-configure-a-proxmox-ve-4-multi-node-cluster/

Setting up a Cluster With Proxmox

HOWTO: Help

Wiki

https://pve.proxmox.com/wiki/Main_Page

Forum

http://forum.proxmox.com/

[SOLVED] command ‘apt-get update’ failed: exit code 100

ca_maer

Active Member

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

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

Alwin

Proxmox Retired Staff

Best regards,
Alwin

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

ca_maer

Active Member

and sometime it works without any issue.

pve n00b

Member

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

Manual update — no roblems!

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

Alwin

Proxmox Retired Staff

Best regards,
Alwin

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

Logan_Rocks

Member

Im also having a issue with the update.

Stoiko Ivanov

Proxmox Staff Member

Best regards,
Stoiko

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

Xeata_James

Member

srslol

New Member

phillip.n

New Member

beumont

New Member

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:

So I have issued the command:

penguin2020

Member

@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)

aciek

New Member

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:

Источник

Exit code 100 #18

My container is automatically exiting with error code 100 after sudo docker run -d -p 27017:27017 —name=mongo mongo .

The text was updated successfully, but these errors were encountered:

ah, this is resolved via the —smallfiles option

Sadly it didn’t help me. Any other options guys ? I run it via

docker run -p 127.0.0.1:27017:27017 —name mymongo -d mongo:3.1.6 —smallfiles

Doesn’t work for me either. Trying to run mongodb docker container in Windows 10. I’m using:
docker run —name mongodb_svcrm -p 27017:27017 -v C:Usersmatt.moranDocumentsmyprojectdatadb:/data/db -d mongo —smallfiles
docker ps -a shows it exits with code 100. There’s plenty of disk space in the host system for journals.
Any idea why this is happening?

try to make the whole data directory as a volume
instead of

try
volumes:
— ./data:/data

it works for me.

Since the Dockerfile defines a volume on /data/db , if you only mount /data you will not be keeping your data. If you check our data folder on your host, you’ll see that it has a db subdirectory, but it should be empty, because it’s in a separate volume.

@tianon you are right this doesn’t solve the problem.

So are there any solutions to this? Should directory mounting work with mongo:windowsservercore image?

@aorlenko, current solutions are to mount a folder from the VM (#74 (comment)) or use a named volume (#74 (comment)).

Yes, the windowsservercore images work just fine if you are using windows containers:

Источник

Debug: userhomedir = /root
Debug: rootdir = /root/GreatSCT
Debug: trueuser = root
Debug: userprimarygroup = root
Debug: os = kali
Debug: version = «2018.4»
Debug: winedir = /root/.greatsct

[I] Kali Linux «2018.4» x86_64 detected.

I installed kali, did an apt update, did an apt upgrade, and then attempted the «./setup.sh -c»

The text was updated successfully, but these errors were encountered:

Do another apt update -y && apt upgrade -y and run the setup file again.

I am sorry, I have been busy with other projects. I just attempted the update and upgrade and got the same result. I also downloaded a new virtual box kali VM image (2018.4) and I get the same behavior.

Do you think its an issue with the Virtualbox Kali VMs provided by Offsec? I can install from the .iso if you think so.

Thanks for looking into this.

*EDIT: The larger output that I have included in this issue exist within a set of ##############.

Hey @davidblakecoe, I have the same error.

I am currently using a Kali2018.2 but it has been updated and upgraded using the following command:

apt update -y && apt upgrade -y

Current system info:

Linux kali 4.15.0-kali2-amd64 #1 SMP Debian 4.15.11-1kali1 (2018-03-21) x86_64 GNU/Linux

Initial failure:

When attempting to install GreatSCT, this is the error I received before the installation process stopped:

##############
The following packages have unmet dependencies:
libwine:i386 : Depends: libc6:i386 (>= 2.23) but it is not going to be installed
Depends: libfontconfig1:i386 (>= 2.12) but it is not going to be installed
Depends: libfreetype6:i386 (>= 2.2.1) but it is not going to be installed
Depends: libncurses5:i386 (>= 6) but it is not going to be installed
Depends: libtinfo5:i386 (>= 6) but it is not going to be installed
Depends: libasound2:i386 (>= 1.0.16) but it is not going to be installed
Depends: libglib2.0-0:i386 (>= 2.12.0) but it is not going to be installed
Depends: libglu1-mesa:i386 but it is not going to be installed or
libglu1:i386
Depends: libgstreamer-plugins-base1.0-0:i386 (>= 1.0.0) but it is not going to be installed
Depends: libgstreamer1.0-0:i386 (>= 1.4.0) but it is not going to be installed
Depends: liblcms2-2:i386 (>= 2.2+git20110628) but it is not going to be installed
Depends: libldap-2.4-2:i386 (>= 2.4.7) but it is not going to be installed
Depends: libmpg123-0:i386 (>= 1.13.7) but it is not going to be installed
Depends: libopenal1:i386 (>= 1.14) but it is not going to be installed
Depends: libpcap0.8:i386 (>= 0.9.8) but it is not going to be installed
Depends: libpulse0:i386 (>= 0.99.1) but it is not going to be installed
Depends: libudev1:i386 (>= 183) but it is not going to be installed
Depends: libx11-6:i386 but it is not going to be installed
Depends: libxext6:i386 but it is not going to be installed
Depends: libxml2:i386 (>= 2.9.0) but it is not going to be installed
Depends: ocl-icd-libopencl1:i386 but it is not going to be installed or
libopencl1:i386
Depends: ocl-icd-libopencl1:i386 (>= 1.0) but it is not going to be installed or
libopencl-1.1-1:i386
Depends: zlib1g:i386 (>= 1:1.1.4) but it is not going to be installed
Recommends: libcups2:i386 (>= 1.4.0) but it is not going to be installed
Recommends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed
Recommends: libgl1:i386 but it is not going to be installed
Recommends: libgnutls30:i386 (>= 3.5.0) but it is not going to be installed
Recommends: libgsm1:i386 (>= 1.0.13) but it is not going to be installed
Recommends: libjpeg62-turbo:i386 (>= 1.3.1) but it is not going to be installed
Recommends: libodbc1:i386 (>= 2.3.1) but it is not going to be installed
Recommends: libosmesa6:i386 (>= 10.2

) but it is not going to be installed
Recommends: libpng16-16:i386 (>= 1.6.2-1) but it is not going to be installed
Recommends: libtiff5:i386 (>= 4.0.3) but it is not going to be installed
Recommends: libxcomposite1:i386 (>= 1:0.3-1) but it is not going to be installed
Recommends: libxcursor1:i386 (> 1.1.2) but it is not going to be installed
Recommends: libxi6:i386 but it is not going to be installed
Recommends: libxinerama1:i386 but it is not going to be installed
Recommends: libxrandr2:i386 but it is not going to be installed
Recommends: libxrender1:i386 but it is not going to be installed
Recommends: libxslt1.1:i386 (>= 1.1.25) but it is not going to be installed
Recommends: libxxf86vm1:i386 but it is not going to be installed
Recommends: libgl1-mesa-dri:i386 but it is not going to be installed
Recommends: libasound2-plugins:i386 but it is not going to be installed
wine32:i386 : Depends: libc6:i386 (>= 2.17) but it is not going to be installed
E: Unmet dependencies. Try ‘apt —fix-broken install’ with no packages (or specify a solution).
[ERROR] Failed to install dependencies (Metasploit-Framework). Exit code: 100

[*] Updating GreatSCT-Framework configuration.

Great Scott configuration:

[] OPERATING_SYSTEM = Kali
[] TERMINAL_CLEAR = clear
[] WINEPREFIX = /root/.greatsct/
[] TEMP_DIR = /tmp/
[] MSFVENOM_OPTIONS =
[] METASPLOIT_PATH = /usr/share/metasploit-framework/
[] MSFVENOM_PATH = /usr/bin/
[] GREATSCT_BYPASS_PATH = /opt/GreatSCT-master/
[] PAYLOAD_SOURCE_PATH = /usr/share/greatsct-output/source/
[] Path ‘/usr/share/greatsct-output/source/’ Created
[] PAYLOAD_COMPILED_PATH = /usr/share/greatsct-output/compiled/
[] Path ‘/usr/share/greatsct-output/compiled/’ Created
[] Path ‘/usr/share/greatsct-output/handlers/’ Created
[] GENERATE_HANDLER_SCRIPT = True
[] HANDLER_PATH = /usr/share/greatsct-output/handlers/
[] HASH_LIST = /usr/share/greatsct-output/hashes.txt

[*] Path ‘/etc/greatsct/’ Created
Configuration File Written To ‘/etc/greatsct/settings.py’

[] Ensuring this account (root) owns GreatSCT output directory (/usr/share/greatsct-output).
[] Ensuring this account (root) has correct ownership of /root/.greatsct
There was issues installing the following:

Failed to install dependencies (Metasploit-Framework). Exit code: 100

After reviewing the output, it appears that there are newer versions of the required dependencies (wine, libc, libwine and others). If you see something else from the output, please let me know.

I attempted to manually install two of the dependencies mentioned from the default Kali repos, but newer versions of other dependencies are going to be installed resulting in the failure of the original dependency installs. Below is some of the output from my attempt to install two dependencies. Let me know if I am not reading the output correctly.

libc6 install:

##############
apt-get install libc6 -f
Reading package lists. Done
Building dependency tree
Reading state information. Done
You might want to run ‘apt —fix-broken install’ to correct these.
The following packages have unmet dependencies:
libc6-dbg : Depends: libc6 (= 2.27-6) but 2.27-8 is to be installed
libc6-dev : Depends: libc6 (= 2.27-6) but 2.27-8 is to be installed
libc6-i386 : Depends: libc6 (= 2.27-6) but 2.27-8 is to be installed
libwine:i386 : Depends: libc6:i386 (>= 2.23) but it is not going to be installed
Depends: libfontconfig1:i386 (>= 2.12) but it is not going to be installed
Depends: libfreetype6:i386 (>= 2.2.1) but it is not going to be installed
Depends: libncurses5:i386 (>= 6) but it is not going to be installed
Depends: libtinfo5:i386 (>= 6) but it is not going to be installed
Depends: libasound2:i386 (>= 1.0.16) but it is not going to be installed
Depends: libglib2.0-0:i386 (>= 2.12.0) but it is not going to be installed
Depends: libglu1-mesa:i386 but it is not going to be installed or
libglu1:i386
Depends: libgstreamer-plugins-base1.0-0:i386 (>= 1.0.0) but it is not going to be installed
Depends: libgstreamer1.0-0:i386 (>= 1.4.0) but it is not going to be installed
Depends: liblcms2-2:i386 (>= 2.2+git20110628) but it is not going to be installed
Depends: libldap-2.4-2:i386 (>= 2.4.7) but it is not going to be installed
Depends: libmpg123-0:i386 (>= 1.13.7) but it is not going to be installed
Depends: libopenal1:i386 (>= 1.14) but it is not going to be installed
Depends: libpcap0.8:i386 (>= 0.9.8) but it is not going to be installed
Depends: libpulse0:i386 (>= 0.99.1) but it is not going to be installed
Depends: libudev1:i386 (>= 183) but it is not going to be installed
Depends: libx11-6:i386 but it is not going to be installed
Depends: libxext6:i386 but it is not going to be installed
Depends: libxml2:i386 (>= 2.9.0) but it is not going to be installed
Depends: ocl-icd-libopencl1:i386 but it is not going to be installed or
libopencl1:i386
Depends: ocl-icd-libopencl1:i386 (>= 1.0) but it is not going to be installed or
libopencl-1.1-1:i386
Depends: zlib1g:i386 (>= 1:1.1.4) but it is not going to be installed
Recommends: libcups2:i386 (>= 1.4.0) but it is not going to be installed
Recommends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed
Recommends: libgl1:i386 but it is not going to be installed
Recommends: libgnutls30:i386 (>= 3.5.0) but it is not going to be installed
Recommends: libgsm1:i386 (>= 1.0.13) but it is not going to be installed
Recommends: libjpeg62-turbo:i386 (>= 1.3.1) but it is not going to be installed
Recommends: libodbc1:i386 (>= 2.3.1) but it is not going to be installed
Recommends: libosmesa6:i386 (>= 10.2

) but it is not going to be installed
Recommends: libpng16-16:i386 (>= 1.6.2-1) but it is not going to be installed
Recommends: libtiff5:i386 (>= 4.0.3) but it is not going to be installed
Recommends: libxcomposite1:i386 (>= 1:0.3-1) but it is not going to be installed
Recommends: libxcursor1:i386 (> 1.1.2) but it is not going to be installed
Recommends: libxi6:i386 but it is not going to be installed
Recommends: libxinerama1:i386 but it is not going to be installed
Recommends: libxrandr2:i386 but it is not going to be installed
Recommends: libxrender1:i386 but it is not going to be installed
Recommends: libxslt1.1:i386 (>= 1.1.25) but it is not going to be installed
Recommends: libxxf86vm1:i386 but it is not going to be installed
Recommends: libgl1-mesa-dri:i386 but it is not going to be installed
Recommends: libasound2-plugins:i386 but it is not going to be installed
wine32:i386 : Depends: libc6:i386 (>= 2.17) but it is not going to be installed
E: Unmet dependencies. Try ‘apt —fix-broken install’ with no packages (or specify a solution).
##############

libwine install:

##############
apt-get install libwine -f
Reading package lists. Done
Building dependency tree
Reading state information. Done
You might want to run ‘apt —fix-broken install’ to correct these.
The following packages have unmet dependencies:
libwine : Recommends: libsane1 (>= 1.0.24) but it is not installable
Breaks: libwine:i386 (!= 3.0.3-2) but 2.0.4-1 is to be installed
libwine:i386 : Depends: libc6:i386 (>= 2.23) but it is not going to be installed
Depends: libfontconfig1:i386 (>= 2.12) but it is not going to be installed
Depends: libfreetype6:i386 (>= 2.2.1) but it is not going to be installed
Depends: libncurses5:i386 (>= 6) but it is not going to be installed
Depends: libtinfo5:i386 (>= 6) but it is not going to be installed
Depends: libasound2:i386 (>= 1.0.16) but it is not going to be installed
Depends: libglib2.0-0:i386 (>= 2.12.0) but it is not going to be installed
Depends: libglu1-mesa:i386 but it is not going to be installed or
libglu1:i386
Depends: libgstreamer-plugins-base1.0-0:i386 (>= 1.0.0) but it is not going to be installed
Depends: libgstreamer1.0-0:i386 (>= 1.4.0) but it is not going to be installed
Depends: liblcms2-2:i386 (>= 2.2+git20110628) but it is not going to be installed
Depends: libldap-2.4-2:i386 (>= 2.4.7) but it is not going to be installed
Depends: libmpg123-0:i386 (>= 1.13.7) but it is not going to be installed
Depends: libopenal1:i386 (>= 1.14) but it is not going to be installed
Depends: libpcap0.8:i386 (>= 0.9.8) but it is not going to be installed
Depends: libpulse0:i386 (>= 0.99.1) but it is not going to be installed
Depends: libudev1:i386 (>= 183) but it is not going to be installed
Depends: libx11-6:i386 but it is not going to be installed
Depends: libxext6:i386 but it is not going to be installed
Depends: libxml2:i386 (>= 2.9.0) but it is not going to be installed
Depends: ocl-icd-libopencl1:i386 but it is not going to be installed or
libopencl1:i386
Depends: ocl-icd-libopencl1:i386 (>= 1.0) but it is not going to be installed or
libopencl-1.1-1:i386
Depends: zlib1g:i386 (>= 1:1.1.4) but it is not going to be installed
Recommends: libcups2:i386 (>= 1.4.0) but it is not going to be installed
Recommends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed
Recommends: libgl1:i386 but it is not going to be installed
Recommends: libgnutls30:i386 (>= 3.5.0) but it is not going to be installed
Recommends: libgsm1:i386 (>= 1.0.13) but it is not going to be installed
Recommends: libjpeg62-turbo:i386 (>= 1.3.1) but it is not going to be installed
Recommends: libodbc1:i386 (>= 2.3.1) but it is not going to be installed
Recommends: libosmesa6:i386 (>= 10.2

) but it is not going to be installed
Recommends: libpng16-16:i386 (>= 1.6.2-1) but it is not going to be installed
Recommends: libtiff5:i386 (>= 4.0.3) but it is not going to be installed
Recommends: libxcomposite1:i386 (>= 1:0.3-1) but it is not going to be installed
Recommends: libxcursor1:i386 (> 1.1.2) but it is not going to be installed
Recommends: libxi6:i386 but it is not going to be installed
Recommends: libxinerama1:i386 but it is not going to be installed
Recommends: libxrandr2:i386 but it is not going to be installed
Recommends: libxrender1:i386 but it is not going to be installed
Recommends: libxslt1.1:i386 (>= 1.1.25) but it is not going to be installed
Recommends: libxxf86vm1:i386 but it is not going to be installed
Recommends: libgl1-mesa-dri:i386 but it is not going to be installed
Recommends: libasound2-plugins:i386 but it is not going to be installed
Breaks: libwine (!= 2.0.4-1) but 3.0.3-2 is to be installed
wine32:i386 : Depends: libc6:i386 (>= 2.17) but it is not going to be installed
wine64 : Depends: libwine (= 2.0.4-1) but 3.0.3-2 is to be installed
E: Unmet dependencies. Try ‘apt —fix-broken install’ with no packages (or specify a solution).
##############

In conclusion, it appears that the dependencies dependencies are failing because the versions are not correct. One example specifically is the following:

libc6-i386 : Depends: libc6 (= 2.27-6) but 2.27-8 is to be installed

The line above tells me that libc6-i386 depend on libc6 version 2.27-6, but 2.27-8 is going to be installed so libc6-i386 will fail.

Also, when attempting to install wine with «apt-get», I only see wine and wine64. This is because wine is for 32 bit architecture and wine64 is for a 64 bit architecture. I know this has been the case in default Ubuntu repos for sometime. I am not sure when this change took place in Kali’s repo. Hopefully this helps some.

Источник

Original address:https://www.v2ex.cc/224.html

When updating, the console will have the following warning tips:

generalPVE updateserviceThe problem will output the following error log:

starting apt-get update
Ign:1 http://ftp.debian.org/debian stretch InRelease
Get:2 http://ftp.debian.org/debian stretch Release [118 kB]
Get:3 http://ftp.debian.org/debian stretch Release.gpg [2434 B]
Get:4 http://ftp.debian.org/debian stretch/main amd64 Packages [7123 kB]
Get:5 http://security.debian.org stretch/updates InRelease [63.0 kB]
Get:6 http://security.debian.org stretch/updates/main amd64 Packages [264 kB]
Get:7 http://security.debian.org stretch/updates/main Translation-en [116 kB]
Get:8 http://security.debian.org stretch/updates/contrib amd64 Packages [1352 B]
Get:9 http://security.debian.org stretch/updates/contrib Translation-en [1023 B]
Ign:10 https://enterprise.proxmox.com/debian/pve stretch InRelease
Ign:11 https://enterprise.proxmox.com/debian/pve stretch Release
Ign:12 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:13 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:14 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:12 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:13 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:14 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:12 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:13 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:14 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:12 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:13 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:14 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Ign:12 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
Ign:13 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:14 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Get:15 http://ftp.debian.org/debian stretch/main Translation-en [5393 kB]
Err:12 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise amd64 Packages
  401  Unauthorized
Ign:13 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise all Packages
Ign:14 https://enterprise.proxmox.com/debian/pve stretch/pve-enterprise Translation-en
Get:16 http://ftp.debian.org/debian stretch/contrib amd64 Packages [50.9 kB]
Get:17 http://ftp.debian.org/debian stretch/contrib Translation-en [45.9 kB]
Fetched 13.2 MB in 30s (425 kB/s)
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

inPVE appearsTASK ERROR: command ‘apt-get update’ failed: exit code 100This error prompt is due to the need to pay for the enterprise software source (dìngyuè)You can access it, the free version should actually use the most version.
Unsequent user if you need to updateProxmox can be usedProxmox Ve No subscription repository。

PROXMOX VE has no subscription repository, PVE-No-subscription repurchase can be used to test and non-production.

It is not recommended to run on the production server because these packages do not always have strict testing and verification.

As the name suggests, noThe ProxMox VE subscription key needs to access this repository.

2018.2.6 Update: According to the reminder of the Grade, Proxmox Ve from 5.5.x is already stretch. The source also uses Jessie will definitely fail, so this article has made a modification according to the official Wiki documentation. Please read it carefully. .

modify /etc/apt/sources.list

deb http://ftp.debian.org/debian stretch main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT Recommended for Production USE (not recommended for production purposes),

deb http://download.proxmox.com/debian/pve stretch pve-no-subscription

# security updates
deb http://security.debian.org stretch/updates main contrib

Then disable the official toll server:

modify /etc/apt/sources.list.d/pve-enterprise.list

deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise

Add one before this code# . Change to the following

# deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise

Attachment:Proxmox VE Close Up Non-Subscribe pop-up window

in5.1 Verification passReminder: upgrade toAfter the version 5.1-46, the official has changed the pop-up JS path.
According to bloguouuouAfter the exploration, found,Proxmox VE has changed the pop-up JS path after 5.1-46.
Difference in the first step backup and editedJS path
Two different versions of solutions are provided below, please select the corresponding operation according to your own version.
1, back up the original file
5.1-46 before the version operations as follows

[email protected]:~# cd /usr/share/pve-manager/js
[email protected]:/usr/share/pve-manager/js# cp pvemanagerlib.js pvemanagerlib.jsbak
[email protected]:/usr/share/pve-manager/js# vi pvemanagerlib.js

5.1-46 After the version, the operation is as follows

[email protected]:~# cd /usr/share/javascript/proxmox-widget-toolkit
[email protected]:/usr/share/javascript/proxmox-widget-toolkit# cp proxmoxlib.js proxmoxlib.jsbak
[email protected]:/usr/share/javascript/proxmox-widget-toolkit# vi proxmoxlib.js

2、Find this line（5.1 3rd Release is on page 850, 5.1-49 in line 352. The version may not be the same position, it is recommended to search yourself):

if (data.status !== 'Active') {

3、change into

Now I have no annoying pop-up window now!