Ask Your Question
0

dnf upgrade fails with curl error

asked 2017-06-22 05:53:34 -0500

PeterDavidCarter gravatar image

I had the

system-python: /builddir/build/BUILD/hawkey-0.6.4/src/python/exception-py.c:101: ret2e: Assertion `0' failed.

issue and ran dnf upgrade --refresh, which did not resolve the issue. I then ran dnf clean all which did remove this particular error. However, now when I run dnf upgrade --refresh I see this error:

[MIRROR] linux-firmware-20170313-72.git695f2d6d.fc25_20170605-74.git37857004.fc25.noarch.drpm: Curl error (23): Failed writing received data to disk/application for https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/25/x86_64/drpms/linux-firmware-20170313-72.git695f2d6d.fc25_20170605-74.git37857004.fc25.noarch.drpm [Failed writing body (8192 != 16384)]
[FAILED] linux-firmware-20170313-72.git695f2d6d.fc25_20170605-74.git37857004.fc25.noarch.drpm: Curl error (23): Failed writing received data to disk/application for https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/25/x86_64/drpms/linux-firmware-20170313-72.git695f2d6d.fc25_20170605-74.git37857004.fc25.noarch.drpm [Failed writing body (8192 != 16384)]
(11-12/33): kernel-m 16% [===                 ]  33 MB/s | 8.8 MB     00:01 ETA
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Error downloading packages:
  Curl error (23): Failed writing received data to disk/application for https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/25/x86_64/drpms/linux-firmware-20170313-72.git695f2d6d.fc25_20170605-74.git37857004.fc25.noarch.drpm [Failed writing body (8192 != 16384)]

Running just dnf update results in this output:

[MIRROR] kernel-core-4.11.5-200.fc25.x86_64.rpm: Curl error (23): Failed writing received data to disk/application for http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/25/x86_64/k/kernel-core-4.11.5-200.fc25.x86_64.rpm [Failed writing body (3241 != 16384)]
[FAILED] kernel-core-4.11.5-200.fc25.x86_64.rpm: Curl error (23): Failed writing received data to disk/application for http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/25/x86_64/k/kernel-core-4.11.5-200.fc25.x86_64.rpm [Failed writing body (3241 != 16384)]
--- Logging error ---46% [=========           ]  42 MB/s |  25 MB     00:00 ETA
Traceback (most recent call last):
  File "/usr/lib64/python3.5/logging/__init__.py", line 985, in emit
    self.flush()
  File "/usr/lib64/python3.5/logging/__init__.py", line 965, in flush
    self.stream.flush()
OSError: [Errno 28] No space left on device
Call stack:
  File "/usr/bin/dnf", line 58, in <module>
    main.user_main(sys.argv[1:], exit_code=True)
  File "/usr/lib/python3.5/site-packages/dnf/cli/main.py", line 174, in user_main
    errcode = main(args)
  File "/usr/lib/python3.5/site-packages/dnf/cli/main.py", line 60, in main
    return _main(base, args)
  File "/usr/lib/python3.5/site-packages/dnf/cli/main.py", line 120, in _main
    ret = resolving(cli, base)
  File "/usr/lib/python3.5/site-packages/dnf/cli/main.py", line 149, in resolving
    base.do_transaction(display=displays)
  File "/usr/lib/python3.5/site-packages/dnf/cli/cli.py", line 212, in do_transaction
    total_cb)
  File "/usr/lib/python3.5/site-packages/dnf/base.py", line 877, in download_packages
    errors = dnf.repo.download_payloads(payloads, drpm)
  File "/usr/lib/python3.5 ...
(more)
edit retag flag offensive close merge delete

Comments

1

OSError: [Errno 28] No space left on device

This tels me that one of your file systems are filled up, That is probably /var/tmp or /var/log or /var/cache.

villykruse gravatar imagevillykruse ( 2017-06-22 12:22:49 -0500 )edit

Ah, cool. I must have overlooked that bit. My bad.

PeterDavidCarter gravatar imagePeterDavidCarter ( 2017-06-22 17:41:27 -0500 )edit

If you haven't already fixed this, please run df -h and add the results to your question. That will tell us which partition is full and help us guide you in cleaning up.

sideburns gravatar imagesideburns ( 2017-06-23 05:45:25 -0500 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2017-06-22 16:49:02 -0500

Aeyoun gravatar image

updated 2017-06-22 16:50:45 -0500

You’re out of disk space. You have to free up disk space before you can put any more data on that drive. Because physics.

edit flag offensive delete link more

Comments

2

Please try to keep sarcasm and other personal remarks out of your answers. It never does any good and only antagonizes people.

sideburns gravatar imagesideburns ( 2017-06-22 17:58:12 -0500 )edit

Agree with @sideburns about the sarcasm. OP admitted he missed the part about the drive being full.

SteveEbey73701 gravatar imageSteveEbey73701 ( 2017-06-23 09:03:04 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2017-06-22 05:50:56 -0500

Seen: 3,532 times

Last updated: Jun 22 '17