Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Unable to parse Unattended-Upgrade::Allowed-Origins

  1. #11
    Join Date
    Oct 2021
    Beans
    7

    Re: Unable to parse Unattended-Upgrade::Allowed-Origins

    This happened

    Code:
    Purging configuration files for linux-modules-5.4.0-77-generic (5.4.0-77.86) ...
    dpkg: warning: while removing linux-modules-5.4.0-77-generic, directory '/lib/modules/5.4.0-77-generic' not empty so not removed
    Purging configuration files for linux-image-5.4.0-77-generic (5.4.0-77.86) ...
    I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-88-generic
    I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-89-generic
    Purging configuration files for linux-modules-extra-5.4.0-80-generic (5.4.0-80.90) ...
    Purging configuration files for linux-modules-extra-5.4.0-74-generic (5.4.0-74.83) ...
    Purging configuration files for linux-modules-extra-5.4.0-73-generic (5.4.0-73.82) ...
    Purging configuration files for linux-image-5.4.0-80-generic (5.4.0-80.90) ...
    Purging configuration files for linux-modules-5.4.0-81-generic (5.4.0-81.91) ...
    dpkg: warning: while removing linux-modules-5.4.0-81-generic, directory '/lib/modules/5.4.0-81-generic' not empty so not removed
    Purging configuration files for linux-modules-5.4.0-80-generic (5.4.0-80.90) ...
    Purging configuration files for linux-image-5.4.0-73-generic (5.4.0-73.82) ...
    Purging configuration files for linux-image-5.4.0-72-generic (5.4.0-72.80) ...
    Purging configuration files for linux-modules-5.4.0-74-generic (5.4.0-74.83) ...
    dpkg: warning: while removing linux-modules-5.4.0-74-generic, directory '/lib/modules/5.4.0-74-generic' not empty so not removed
    Purging configuration files for linux-image-5.4.0-74-generic (5.4.0-74.83) ...
    Purging configuration files for linux-modules-5.4.0-73-generic (5.4.0-73.82) ...
    Purging configuration files for linux-image-5.4.0-81-generic (5.4.0-81.91) ...
    rmdir: failed to remove '/lib/modules/5.4.0-81-generic': Directory not empty
    Purging configuration files for linux-modules-extra-5.4.0-72-generic (5.4.0-72.80) ...
    Purging configuration files for linux-modules-5.4.0-72-generic (5.4.0-72.80) ...
    Purging configuration files for linux-modules-extra-5.4.0-77-generic (5.4.0-77.86) ...
    Purging configuration files for linux-modules-extra-5.4.0-81-generic (5.4.0-81.91) ...
    No I have this
    Code:
    dpkg -l | grep linux-image
    rc  linux-image-5.4.0-65-generic         5.4.0-65.73                           amd64        Signed kernel image generic
    rc  linux-image-5.4.0-66-generic         5.4.0-66.74                           amd64        Signed kernel image generic
    rc  linux-image-5.4.0-67-generic         5.4.0-67.75                           amd64        Signed kernel image generic
    rc  linux-image-5.4.0-70-generic         5.4.0-70.78                           amd64        Signed kernel image generic
    rc  linux-image-5.4.0-71-generic         5.4.0-71.79                           amd64        Signed kernel image generic
    ii  linux-image-5.4.0-84-generic         5.4.0-84.94                           amd64        Signed kernel image generic
    ii  linux-image-5.4.0-88-generic         5.4.0-88.99                           amd64        Signed kernel image generic
    ii  linux-image-5.4.0-89-generic         5.4.0-89.100                          amd64        Signed kernel image generic
    ii  linux-image-generic                  5.4.0.89.93                           amd64        Generic Linux kernel image
    Now Boot has 208MB free space. Would it be enough? Can I delete more older packages?
    Code:
    df -Th -x squashfs -x tmpfs
    Filesystem                        Type      Size  Used Avail Use% Mounted on
    udev                              devtmpfs  950M     0  950M   0% /dev
    /dev/mapper/ubuntu--vg-ubuntu--lv ext4       15G  8.6G  5.4G  62% /
    /dev/sda2                         ext4      976M  702M  208M  78% /boot
    //200.200.26.3/backdrive          cifs      6.8T  6.5T  283G  96% /media/backdrive
    //200.200.26.3/projekty           cifs      6.8T  6.5T  283G  96% /media/data
    Last edited by deadflowr; October 24th, 2021 at 05:26 AM. Reason: code tags

  2. #12
    Join Date
    Apr 2011
    Location
    Mystletainn Kick!
    Beans
    12,398
    Distro
    Ubuntu

    Re: Unable to parse Unattended-Upgrade::Allowed-Origins

    Would it be enough?
    You should now have enough wiggle room to work with.
    It might be possible to get more space.
    A reboot should boot into the newer 5.4.0-89 kernel as it's now shown as properly installed.
    Running autoremove again should then remove the 5.4.0-84 kernel, and leave you with just 2.
    That should help clear up another 50MB or more.
    Splat Double Splat Triple Splat
    Earn Your Keep
    Don't mind me, I'm only passing through.
    Once in a blue moon, I'm actually helpful
    .

  3. #13
    Join Date
    Oct 2021
    Beans
    7

    Re: Unable to parse Unattended-Upgrade::Allowed-Origins

    As you said, after reboot there is more free space

    I runned this

    sudo rm /etc/apt/apt.conf.d/50unattended-upgrades
    sudo apt purge unattended-upgrades
    sudo apt clean
    sudo apt update
    sudo apt full-upgrade
    sudo apt install unattended-upgrades
    sudo unattended-upgrades --debug --dry-run

    and got this after dry run. I googled little bit and found there are some type in Ubuntu. But I am not able to find where. It does not look in conf file. It looks like conf file on my another Ubuntu machine where everything works perfect.


    Running on the development release
    Starting unattended upgrades script
    Unable to parse Unattended-Upgrade::Allowed-Origins.
    An error occurred: not enough values to unpack (expected 2, got 0)
    Traceback (most recent call last):
    File "/usr/bin/unattended-upgrades", line 1985, in main
    res = run(options, rootdir, mem_log, logfile_dpkg,
    File "/usr/bin/unattended-upgrades", line 2126, in run
    cache = UnattendedUpgradesCache(rootdir=rootdir)
    File "/usr/bin/unattended-upgrades", line 156, in __init__
    self.allowed_origins = get_allowed_origins()
    File "/usr/bin/unattended-upgrades", line 785, in get_allowed_origins
    allowed_origins = get_allowed_origins_legacy()
    File "/usr/bin/unattended-upgrades", line 764, in get_allowed_origins_legacy
    (distro_id, distro_codename) = s.split()
    ValueError: not enough values to unpack (expected 2, got 0)
    Extracting content from /var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2021-10-24 12:02:07
    Traceback (most recent call last):
    File "/usr/bin/unattended-upgrades", line 2514, in <module>
    sys.exit(main(options))
    File "/usr/bin/unattended-upgrades", line 1985, in main
    res = run(options, rootdir, mem_log, logfile_dpkg,
    File "/usr/bin/unattended-upgrades", line 2126, in run
    cache = UnattendedUpgradesCache(rootdir=rootdir)
    File "/usr/bin/unattended-upgrades", line 156, in __init__
    self.allowed_origins = get_allowed_origins()
    File "/usr/bin/unattended-upgrades", line 785, in get_allowed_origins
    allowed_origins = get_allowed_origins_legacy()
    File "/usr/bin/unattended-upgrades", line 764, in get_allowed_origins_legacy
    (distro_id, distro_codename) = s.split()
    ValueError: not enough values to unpack (expected 2, got 0)

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •