Hello,
I would like to ask for a hint in order to be able to eliminate the following error:
root@DietPi:~# apt upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete werden aktualisiert (Upgrade):
apt libapt-pkg5.0 wpasupplicant
3 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 3.433 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 9.216 B Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n]
Holen:1 https://deb.debian.org/debian buster-updates/main arm64 libapt-pkg5.0 arm64 1.8.2.3 [897 kB]
Holen:2 https://deb.debian.org/debian buster-updates/main arm64 apt arm64 1.8.2.3 [1.370 kB]
Holen:3 https://deb.debian.org/debian-security buster/updates/main arm64 wpasupplicant arm64 2:2.7+git20190128+0c1e29f-6+deb10u3 [1.165 kB]
Es wurden 3.433 kB in 1 s geholt (3.607 kB/s).
debconf: delaying package configuration, since apt-utils is not installed
dpkg: nicht behebbarer fataler Fehler, Abbruch:
Abschließender Zeilenvorschub fehlt in Dateilisten-Datei des Paketes »libtevent0:arm64«
E: Sub-process /usr/bin/dpkg returned an error code (2)
root@DietPi:~#
Thank you and many friendly greetings.
This is not an issue of the DietPi update, it more a challenge of apt upgrade that is invoke before.
could you try following and post entire output
/boot/dietpi/func/dietpi-set_software apt-cache clean
apt update
apt upgrade
Hello,
unfortunately, the proposed solution was not effective:
Mode: apt-cache (clean)
[ OK ] apt-cache clean | Completed
root@DietPi:~# apt update
Holen:1 https://downloads.plex.tv/repo/deb public InRelease [6.685 B]
Holen:2 https://deb.debian.org/debian buster InRelease [121 kB]
Holen:3 https://deb.debian.org/debian buster-updates InRelease [51,9 kB]
Holen:4 https://deb.debian.org/debian-security buster/updates InRelease [65,4 kB]
Holen:5 https://deb.debian.org/debian buster-backports InRelease [46,7 kB]
Holen:6 https://downloads.plex.tv/repo/deb public/main armhf Packages [1.724 B]
Holen:7 https://downloads.plex.tv/repo/deb public/main arm64 Packages [1.728 B]
Holen:8 https://deb.debian.org/debian buster/main armhf Packages [7.698 kB]
Holen:9 https://deb.debian.org/debian buster/non-free arm64 Packages [53,8 kB]
Holen:10 https://deb.debian.org/debian buster/contrib arm64 Packages [38,4 kB]
Holen:11 https://deb.debian.org/debian buster/non-free armhf Packages [62,0 kB]
Holen:12 https://deb.debian.org/debian buster/contrib armhf Packages [40,1 kB]
Holen:13 https://deb.debian.org/debian buster/main arm64 Packages [7.736 kB]
Holen:14 https://deb.debian.org/debian buster-updates/main arm64 Packages [10,8 kB]
Holen:15 https://deb.debian.org/debian buster-updates/main armhf Packages [10,9 kB]
Holen:16 https://deb.debian.org/debian buster-updates/non-free armhf Packages [604 B]
Holen:17 https://deb.debian.org/debian buster-updates/non-free arm64 Packages [600 B]
Holen:18 https://deb.debian.org/debian buster-backports/contrib armhf Packages [8.320 B]
Holen:19 https://deb.debian.org/debian buster-backports/contrib arm64 Packages [9.020 B]
Holen:20 https://deb.debian.org/debian buster-backports/main armhf Packages [456 kB]
Holen:21 https://deb.debian.org/debian buster-backports/non-free arm64 Packages [22,1 kB]
Holen:22 https://deb.debian.org/debian buster-backports/non-free armhf Packages [13,0 kB]
Holen:23 https://deb.debian.org/debian buster-backports/main arm64 Packages [461 kB]
Holen:24 https://archive.raspberrypi.org/debian buster InRelease [32,9 kB]
Holen:25 https://archive.raspberrypi.org/debian buster/main armhf Packages [372 kB]
Holen:26 https://archive.raspberrypi.org/debian buster/main arm64 Packages [283 kB]
Paketlisten werden gelesen... Fertig
E: Release file for https://deb.debian.org/debian-security/dists/buster/updates/InRelease is not valid yet (invalid for another 53 min 46 s). Updates for this repository will not be applied.
root@DietPi:~# apt update
OK:1 https://downloads.plex.tv/repo/deb public InRelease
OK:2 https://deb.debian.org/debian buster InRelease
OK:3 https://deb.debian.org/debian buster-updates InRelease
Holen:4 https://deb.debian.org/debian-security buster/updates InRelease [65,4 kB]
OK:5 https://archive.raspberrypi.org/debian buster InRelease
OK:6 https://deb.debian.org/debian buster-backports InRelease
Paketlisten werden gelesen... Fertig
E: Release file for https://deb.debian.org/debian-security/dists/buster/updates/InRelease is not valid yet (invalid for another 1 h 5 min 42 s). Updates for this repository will not be applied.
root@DietPi:~# apt update
OK:1 https://downloads.plex.tv/repo/deb public InRelease
OK:2 https://deb.debian.org/debian buster InRelease
OK:3 https://deb.debian.org/debian buster-updates InRelease
Holen:4 https://deb.debian.org/debian-security buster/updates InRelease [65,4 kB]
OK:5 https://archive.raspberrypi.org/debian buster InRelease
OK:6 https://deb.debian.org/debian buster-backports InRelease
Paketlisten werden gelesen... Fertig
E: Release file for https://deb.debian.org/debian-security/dists/buster/updates/InRelease is not valid yet (invalid for another 1 h 27 min 39 s). Updates for this repository will not be applied.
root@DietPi:~# apt upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden NEUEN Pakete werden installiert:
libbrotli1
Die folgenden Pakete werden aktualisiert (Upgrade):
apt curl libapt-pkg5.0 libcurl3-gnutls libcurl4
5 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 3.430 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 809 kB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n]
Holen:1 https://deb.debian.org/debian buster-updates/main arm64 libapt-pkg5.0 arm64 1.8.2.3 [897 kB]
Holen:2 https://deb.debian.org/debian buster-updates/main arm64 apt arm64 1.8.2.3 [1.370 kB]
Holen:3 https://deb.debian.org/debian buster/main arm64 libbrotli1 arm64 1.0.7-2+deb10u1 [262 kB]
Holen:4 https://deb.debian.org/debian buster-backports/main arm64 curl arm64 7.74.0-1.2~bpo10+1 [261 kB]
Holen:5 https://deb.debian.org/debian buster-backports/main arm64 libcurl4 arm64 7.74.0-1.2~bpo10+1 [321 kB]
Holen:6 https://deb.debian.org/debian buster-backports/main arm64 libcurl3-gnutls arm64 7.74.0-1.2~bpo10+1 [318 kB]
Es wurden 3.430 kB in 1 s geholt (4.111 kB/s).
debconf: delaying package configuration, since apt-utils is not installed
dpkg: nicht behebbarer fataler Fehler, Abbruch:
Abschließender Zeilenvorschub fehlt in Dateilisten-Datei des Paketes »libtevent0:arm64«
E: Sub-process /usr/bin/dpkg returned an error code (2)
root@DietPi:~#
Are there any further clues, please?
Thank you very much.
pls update your local system time. It dosn’t seems to be correct
E: Release file for https://deb.debian.org/debian-security/ ... /InRelease is not valid yet (invalid for another 53 min 46 s). Updates for this
@Joulinar:
Thank you, the faulty system time was the cause of the error. apt update now ran without errors. I should have noticed it myself, sorry.
Kind regards and stay healthy!
Edit:
After only a few minutes of operation, the system time is already slowing down again, what can be done?
root@DietPi:~# timedatectl status
Failed to create bus connection: Datei oder Verzeichnis nicht gefunden
root@DietPi:~# sudo nano /etc/systemd/timesyncd.conf
root@DietPi:~# date
Fr 23. Apr 15:39:37 CEST 2021
root@DietPi:~# sudo ntpd -qg
sudo: ntpd: Befehl nicht gefunden
root@DietPi:~# cat /etc/fake-hwclock.data
2021-04-23 13:17:01
root@DietPi:~#
/etc/ntp.conf does not exist.
Now I studied this thread:
https://dietpi.com/forum/t/wrong-time-after-power-off/3181/1
and changed the NTP server from pool.ntp.org to Gateway, the problem isn’t be solved.
root@DietPi:~# date
Fr 23. Apr 16:22:18 CEST 2021
root@DietPi:~# systemctl status fake-hwclock
● fake-hwclock.service - Restore / save the current clock
Loaded: loaded (/lib/systemd/system/fake-hwclock.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2021-04-23 15:49:37 CEST; 32min ago
Docs: man:fake-hwclock(8)
Main PID: 113 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/fake-hwclock.service
Apr 23 15:49:37 DietPi fake-hwclock[113]: Fri Apr 23 13:49:37 UTC 2021
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
root@DietPi:~#
Any ideas here? Thank you.
hi,
pls don’t mix up thinks. Using date should always display current system time
timedatectl is not working because dbus is not active/installed by default
/etc/ntp.conf is not present because DietPi did not use NTP tool
fake-hwclock is not displaying current time, it’s updated on hourly basis to generate a time stamp that can be used on reboot until time sync has been done. Usually the update is done at the 17 minute of a hour as you can see on your output
root@DietPi:~# cat /etc/fake-hwclock.data
2021-04-23 13:17:01
on DietPi, by default time sync is done on daily basis using systemd-timesyncd.service. It’s triggered by a daily cron job and status can be checked like this
systemctl status systemd-timesyncd.service
if needed time sync interval could be changed to hourly using dietpi-config
Usually the service is in status inactive. As well you could run a manual sync by restarting the service or run /boot/dietpi/func/run_ntpd. A full log is available using journalctl -u systemd-timesyncd
Hello @Joulinar,
DietPi 7.1.0 beta 64bit on RasPi4 says here:
root@DietPi:~# date
Fr 23. Apr 22:57:01 CEST 2021
root@DietPi:~#
root@DietPi:~# systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
└─disable-with-time-daemon.conf
Active: inactive (dead)
Docs: man:systemd-timesyncd.service(8)
Apr 23 20:45:06 DietPi systemd[1]: Started Network Time Synchronization.
Apr 23 20:45:07 DietPi systemd[1]: Stopping Network Time Synchronization…
Apr 23 20:45:07 DietPi systemd[1]: systemd-timesyncd.service: Succeeded.
Apr 23 20:45:07 DietPi systemd[1]: Stopped Network Time Synchronization.
Apr 23 20:45:07 DietPi systemd[1]: Starting Network Time Synchronization…
Apr 23 20:45:07 DietPi systemd[1]: Started Network Time Synchronization.
Apr 23 20:46:08 DietPi systemd-timesyncd[483]: Synchronized to time server for the first time 162.159.200.1:123 (0.debian.pool.ntp.org).
Apr 23 20:46:08 DietPi systemd[1]: Stopping Network Time Synchronization…
Apr 23 20:46:08 DietPi systemd[1]: systemd-timesyncd.service: Succeeded.
Apr 23 20:46:08 DietPi systemd[1]: Stopped Network Time Synchronization.
root@DietPi:~#
What do I have to do to restart the time synchronisation?
The system time from dietpi is 10 seconds per minute real time to slow . . .
Thank you very much.
It does not work, the log file is not updated, the windows system time is currently 23.37 CEST, the Raspi time is
date:
Fr. 23. Apr 23:15:30 CEST 2021
root@DietPi:~# /boot/dietpi/func/run_ntpd
[ OK ] Network time sync | Completed
root@DietPi:~# journalctl -u systemd-timesyncd
-- Logs begin at Fri 2021-04-23 20:44:54 CEST, end at Fri 2021-04-23 23:12:10 CEST. --
Apr 23 20:45:06 DietPi systemd[1]: Starting Network Time Synchronization...
Apr 23 20:45:06 DietPi systemd[1]: Started Network Time Synchronization.
Apr 23 20:45:07 DietPi systemd[1]: Stopping Network Time Synchronization...
Apr 23 20:45:07 DietPi systemd[1]: systemd-timesyncd.service: Succeeded.
Apr 23 20:45:07 DietPi systemd[1]: Stopped Network Time Synchronization.
Apr 23 20:45:07 DietPi systemd[1]: Starting Network Time Synchronization...
Apr 23 20:45:07 DietPi systemd[1]: Started Network Time Synchronization.
Apr 23 20:46:08 DietPi systemd-timesyncd[483]: Synchronized to time server for the first time 162.159.200.1:123 (0.debian.pool.ntp.org).
Apr 23 20:46:08 DietPi systemd[1]: Stopping Network Time Synchronization...
Apr 23 20:46:08 DietPi systemd[1]: systemd-timesyncd.service: Succeeded.
Apr 23 20:46:08 DietPi systemd[1]: Stopped Network Time Synchronization.
root@DietPi:~#
The log file has been at Apr 23 20:45:06 for hours.
Now I changed time sync interval could be changed to hourly and this log file changed to 23:xx:xx, nevertheless, the time is much too slow, about 20 seconds too slow per minute.
I run a RaspiZero, a Raspi1, a Raspi2 and a Raspi3 with Dietpi 7.1.0 beta 32bit, with none of them the problem occurs, only with my Raspi4 with the 64bit dietpi. Could there be a hardware error?
I’d like to continue to be a beta tester and reset the system; after that I’ll report back.
Could be that you need to call it with option 1
/boot/dietpi/func/run_ntpd 1
this way you will force the time sync
Joulinar thank you for your hints.
The update now went without a hitch, only the system time is lagging behind by about 4 minutes per hour.
Many greetings.
if you switch to hourly update, it shouldn’t be an issue. But still strange that your time is not synchron. On my RPi3B+ running dev branch it is still in sync after hours. Are you running some CPU intensiv operation on that board?