unable to update dietpi to latest version

[hcr2020]

Details:

• Date | Fri Jul 12 19:40:13 BST 2024
• Bug report | 6dbbd6b4-823d-4de3-b099-33ee20fb991d
• DietPi version | v9.5.1 (MichaIng/master)
• Image creator |
• Pre-image |
• Hardware | ROCK64 (aarch64) (ID=43)
• Kernel version | Linux DietPi 6.1.63-current-rockchip64 #1 SMP PREEMPT Mon Nov 20 10:52:19 UTC 2023 aarch64 GNU/Linux
• Distro | bullseye (ID=6)
• Command | apt-get -y --with-new-pkgs upgrade
• Exit code | 100
• Software title | DietPi-Update

  Steps to reproduce:

  1. ...
  2. ...

     Expected behaviour:

• ...

  Actual behaviour:

• ...

  Extra details:

• ...

  Additional logs:

  
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Calculating upgrade...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  3 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up exim4-config (4.94.2-7+deb11u3) ...
  /usr/sbin/update-exim4.conf: 467: cannot create /dev/null: File exists
  Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not installing 
  /var/lib/exim4/config.autogenerated.tmp to /var/lib/exim4/config.autogenerated
  dpkg: error processing package exim4-config (--configure):
  installed exim4-config package post-installation script subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of exim4-base:
  exim4-base depends on exim4-config (>= 4.94) | exim4-config-2; however:
  Package exim4-config is not configured yet.
  Package exim4-config-2 is not installed.
  Package exim4-config which provides exim4-config-2 is not configured yet.

dpkg: error processing package exim4-base (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of exim4-daemon-light: exim4-daemon-light depends on exim4-base (>= 4.94.2); however: Package exim4-base is not configured yet.

dpkg: error processing package exim4-daemon-light (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: exim4-config exim4-base exim4-daemon-light E: Sub-process /usr/bin/dpkg returned an error code (1)

I am unable to update dietpi to latest version, due to exim4-config; exim4-base; exim-daemon-light upgrade error and 
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied

Thank you in advance

[MichaIng]

This is not a solution. We need to find out what exactly is removing/replacing the node, and fix it.

I btw found the reason for the issue on my servers: https://github.com/MichaIng/hacks/blob/main/rootfs/etc/mysql/mariadb.conf.d/99-micha.cnf#L3 pid_file=/dev/null in MariaDB now leads to the removal of the node, when the service is stopped. I tried to find a way to disable the unnecessary PID file with a drop-in config, and this worked, but obviously broke with the latest MariaDB update on Debian Trixie. However this is not the reason in your case: You do not use MariaDB, service stops/restarts do not trigger the issue, reboots do (in my case not), and this config was never built into DietPi, but just my personal one.

This however means it really is a individual problem, not a general one, and it was a coincidence that we both have it, with a very different culprit.

I have one idea how to probably find out what is causing it:

cat << '_EOF_' > /var/lib/dietpi/postboot.d/devnull.sh
#!/bin/bash
while [[ $(stat -c '%a' /dev/null) == '666' ]]; do :; done
lsof /dev/null > /root/devnull.log
_EOF_

I hope postboot scripts run early enough and lsof runs fast enough to catch it. This is causing a constant CPU load of ~15% (on two of my systems) since the mode of the node is checked very frequently, but I currently have no better idea. Check the log after reboot:

cat /root/devnull.log