Broken after Trying to Update/Upgrade

Hi All.
I’m trying to put my station back online after a few months of absence (1920) and having pulled the Pi out of it’s hiding place it went ONLINE just fine. Then me being me tried to apt update & apt upgrade and low and behold it now defunked.
Please see all the listed below and i need all the help i can get.

Thanks
Karl

Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following additional packages will be installed:
libuhd3.15.0
The following packages will be upgraded:
libuhd3.15.0 uhd-host
2 upgraded, 0 newly installed, 0 to remove and 60 not upgraded.
Need to get 9,043 kB/11.4 MB of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://download.opensuse.org/repositories/home:/librespace:/satnogs/Raspbi an_11 ./ uhd-host 3.15.0.0-4+b1satnogs1 [9,043 kB]
Err:1 http://download.opensuse.org/repositories/home:/librespace:/satnogs/Raspbi an_11 ./ uhd-host 3.15.0.0-4+b1satnogs1
File has unexpected size (9043200 != 9043268). Mirror sync in progress? [IP: 9 1.193.113.70 80]
Hashes of expected file:

  • SHA256:e5c7220f38c049cce979dae8034c144b97042605000301520135c3ec7adf7645
  • SHA1:7c9a7aba86a4773970a9c2dc12c6affa1af98064 [weak]
  • MD5Sum:77a39e3061f8e6df9c32678e811ae647 [weak]
  • Filesize:9043268 [weak]
    apt-listchanges: Reading changelogs…
    (Reading database … 135741 files and directories currently installed.)
    Preparing to unpack …/libuhd3.15.0_3.15.0.0-4+b1satnogs1_armhf.deb …
    Unpacking libuhd3.15.0:armhf (3.15.0.0-4+b1satnogs1) over (3.15.0.0-4satnogs1) . …
    Setting up libuhd3.15.0:armhf (3.15.0.0-4+b1satnogs1) …
    Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u7) …
    E: Failed to fetch http://provo-mirror.opensuse.org/repositories/home%3A/libresp ace%3A/satnogs/Raspbian_11/armhf/uhd-host_3.15.0.0-4%2Bb1satnogs1_armhf.deb Fil e has unexpected size (9043200 != 9043268). Mirror sync in progress? [IP: 91.193 .113.70 80]
    Hashes of expected file:
    - SHA256:e5c7220f38c049cce979dae8034c144b97042605000301520135c3ec7adf7645
    - SHA1:7c9a7aba86a4773970a9c2dc12c6affa1af98064 [weak]
    - MD5Sum:77a39e3061f8e6df9c32678e811ae647 [weak]
    - Filesize:9043268 [weak]

I’m able to Log Into it just fine and it shows active on the Pi.

pi@raspberrypi:~ $ systemctl status satnogs-client
● satnogs-client.service - SatNOGS client

  • Loaded: loaded (/etc/systemd/system/satnogs-client.service; enabled; vendor preset: enabled)*
    
  • Active: active (running) since Sun 2024-06-16 14:35:06 MDT; 285ms ago*
    
  • Main PID: 1522 (satnogs-client)*
  •  Tasks: 1 (limit: 1595)*
    
  •    CPU: 269ms*
    
  • CGroup: /system.slice/satnogs-client.service*
    
  •         └─1522 /var/lib/satnogs/bin/python /var/lib/satnogs/bin/satnogs-client*
    

Jun 16 14:35:06 raspberrypi systemd[1]: Started SatNOGS client.

My SatNogs Support Report…
------------[ copy here ]------------
{
“versions”: {
“satnogs-client”: “1.8.1”,
“satnogs-client-ansible”: “202209101521”,
“satnogs-flowgraphs”: “1.5-1”,
“gr-satnogs”: “2.3.5.0-1”,
“gr-soapy”: “2.1.3.1-1”,
“gnuradio”: “3.8.2.0-14”,
“satnogs-config”: “0.13.2”
},
“state”: {
“is-applied”: true,
“pending-tags”: null
},
“system”: {
“date”: “2024-06-16T20:37:36.185330+00:00”,
“distribution”: {
“DESCRIPTION”: “Raspbian GNU/Linux 11 (bullseye)”,
“RELEASE”: “11”,
“CODENAME”: “bullseye”,
“ID”: “Raspbian”
},
“pending-updates”: true,
“platform”: {
“system”: “Linux”,
“node”: “raspberrypi”,
“release”: “6.1.21-v7+”,
“version”: “#1642 SMP Mon Apr 3 17:20:52 BST 2023”,
“machine”: “armv7l”
},
“memory”: {
“total”: 966750208,
“available”: 818925568,
“percent”: 15.3,
“used”: 91803648,
“free”: 526241792,
“active”: 221499392,
“inactive”: 155856896,
“buffers”: 27852800,
“cached”: 320851968,
“shared”: 724992,
“slab”: 33615872
},
“disk”: {
“total”: 30431997952,
“used”: 4842483712,
“free”: 24298078208,
“percent”: 16.6
}
},
“configuration”: {
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_rf_gain”: “42.1”,
“satnogs_rot_baud”: “0”,
“satnogs_rot_enabled”: true,
“satnogs_rot_model”: “ROT_MODEL_NETROTCTL”,
“satnogs_rot_port”: “192.168.1.97:4553”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “driver=rtlsdr”,
“satnogs_station_elev”: “550”,
“satnogs_station_id”: “1920”,
“satnogs_station_lat”: “54.892”,
“satnogs_station_lon”: “-112.298”
}
}
------------[ copy end ]-------------

1 Like

So it turns out a FULL reinstall fixed the issue… At least for now anyway… Happy Monday folks and Step On… :smiley:

2 Likes