After another unattended update of procps has failed this morning I figured out that "net.ipv4.tcp_mem in 30-iscsitarget.conf" causes an error and prevents procps from starting - like Ryan already said. Commenting out that line is a workaround.
After another unattended update of procps has failed this morning I figured out that "net.ipv4.tcp_mem in 30-iscsitarget. conf" causes an error and prevents procps from starting - like Ryan already said. Commenting out that line is a workaround.