The DietPi software update had trouble getting an ipV4 connection. Now when I try to run I get this & rebooting does not fix the problem. How to I kill these processes? Also, the RaspberryPi no longer is able to connect to the internet. Tried rebooting everything. I am no Pi-less and my Roku is laughing at me - dialing home several times per minute.
│ WARNING: Concurrent execution of DietPi-Update detected │
│ │
│ Please check if one of the following applies: │
│ - This script already runs on another terminal/SSH session. │
│ - Currently a cron or systemd background job executes the script. │
│ - You started this script from within another DietPi program, causing a │
│ loop. │
│ │
│ Please assure that the concurrent execution has finished, before retrying, │
│ otherwise cancel this instance. │
│ │
│ The following info might help: │
│ 680 root pts/0 \_ /bin/bash /boot/dietpi/dietpi-update │
│ 689 root pts/0 \_ /bin/bash /boot/dietpi/dietpi-update │
│ 691 root pts/0 \_ grep -i dietpi │
│ 532 root ? /bin/bash /boot/dietpi/dietpi-update 2 │
│ │
│ <Retry> <Cancel> │
│
I have searched the existing open and closed issues
Linux XXXX 6.12.34+rpt-rpi-v7 #1 SMP Raspbian 1:6.12.34-1+rpt1 (2025-06-26) armv7l GNU/Linux
EDIT: The Raspberry Pi is no longer able to communicate with the internet. It just times out. I have tried 9.9.9.9 & 8.8.8.8 - same result.
root@JacoPi:~# dietpi-update
[ INFO ] DietPi-Update | Concurrent execution of DietPi-Update detected, retrying... (1/5)
[ INFO ] DietPi-Update | Concurrent execution of DietPi-Update detected, retrying... (2/5)
[ INFO ] DietPi-Update | Concurrent execution of DietPi-Update detected, retrying... (3/5)
[ INFO ] DietPi-Update | Concurrent execution of DietPi-Update detected, retrying... (4/5)
[ INFO ] DietPi-Update | Concurrent execution of DietPi-Update detected, retrying... (5/5)
[FAILED] DietPi-Update | Cancelled DietPi-Update due to concurrent execution
root@JacoPi:~# echo $g_hw-model-name
-model-name
root@JacoPi:~# echo $g
root@JacoPi:~# echo $g
root@JacoPi:~# uname --all
Linux JacoPi 6.12.34+rpt-rpi-v7 #1 SMP Raspbian 1:6.12.34-1+rpt1 (2025-06-26) armv7l GNU/Linux
root@JacoPi:~# ^C
root@JacoPi:~# dietpi-update
DietPi-Update
─────────────────────────────────────────────────────
Phase: Checking for available DietPi update
[ ..]PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.ctivity (2/2)
From 192.168.227.5 icmp_seq=1 Destination Host Unreachable
--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
[FAILED] DietPi-Update | Checking IPv4 network connectivity
- Command: ping -4nc 1 -W 10 8.8.8.8
[ OK ] DietPi-Config | Setting in /boot/dietpi.txt adjusted: CONFIG_CHECK_CONNECTION_IP=9.9.9.9
[ ..]PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.ctivity (2/2)
From 192.168.227.5 icmp_seq=1 Destination Host Unreachable
--- 9.9.9.9 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
[FAILED] DietPi-Update | Checking IPv4 network connectivity
- Command: ping -4nc 1 -W 20 9.9.9.9
[FAILED] DietPi-Update | Unable to continue, DietPi-Update will now terminate.
If I were looking for help, I might provide a little more information. For example, what is no longer working. Or an error message. Maybe even a log. And if I’m feeling particularly nice, I might even fill out the provided troubleshooting template.
But I don’t have to, because the others will already know what’s wrong with my system.
But we don’t know what system it is. And after rebooting it can take a while for dietpi-update to finish (depending on system) as it is executed during boot automatically.
It’s communicating to the net again. But when I run the software update it gets hung up on a missing key.
Err:3 https://archive.raspberrypi.com/debian trixie InRelease
Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key CF8A1AF502A2AA2D763BAE7E82B129927FA3303E, which is needed to verify signature.
Fetched 54.7 kB in 1s (37.6 kB/s)
Reading package lists...
Do you remember what you did? Do you have another Linux computer where you could insert the SD card as an external storage drive? That way, you could try changing the network settings.
So I am back in & followed your advice but this is what happened:
root@JacoPi:~# apt install --reinstall raspberrypi-archive-keyring
Installing:
raspberrypi-archive-keyring
Summary:
Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 15
Download size: 7,372 B
Space needed: 28.7 kB / 10.3 GB available
Ign:1 https://archive.raspberrypi.com/debian trixie/main armhf raspberrypi-archive-keyring all 2025.1+rpt1
Ign:1 https://archive.raspberrypi.com/debian trixie/main armhf raspberrypi-archive-keyring all 2025.1+rpt1
Ign:1 https://archive.raspberrypi.com/debian trixie/main armhf raspberrypi-archive-keyring all 2025.1+rpt1
Err:1 https://archive.raspberrypi.com/debian trixie/main armhf raspberrypi-archive-keyring all 2025.1+rpt1
Temporary failure resolving 'archive.raspberrypi.com'
Error: Failed to fetch https://archive.raspberrypi.com/debian/pool/main/r/raspberrypi-archive-keyring/raspberrypi-archive-keyring_2025.1%2brpt1_all.deb Temporary failure resolving 'archive.raspberrypi.com'
Error: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
root@JacoPi:~# apt-get update --fix-missing
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 630 (apt-get)
N: Be aware that removing the lock file is not a solution and may break your system.
E: Unable to lock directory /var/lib/apt/lists/
OK… I was able to restart the net settings and it connected & finished the DietPi update as well as the Raspberry Pi software.
root@JacoPi:~# cat /etc/resolv.conf
# Generated by dhcpcd from eth0.dhcp
# /etc/resolv.conf.head can replace this line
nameserver 1.1.1.1
nameserver 1.0.0.1
# /etc/resolv.conf.tail can replace this line
Now for reasons unknown it’s offline again. But now this seems to be a RaspberryPi software issue rather than a DietPi OS thing.
It was on DHCP on OS side (this had been an issue before) but I switched it back to STATIC with no effect. Unfortunately I am unable to generate a log as it times out when it tries to upload to Tricorder.
There’s a second IP address assigned to my ethernet - I am not sure what is causing it. Switching to STATIC in DietPi OS fixed it last time. But it’s back.