"procps" error caused by recent update to Ubuntu 12.04 (12.04.3)

Bug #1240332 reported by David Jones
This bug report is a duplicate of:  Bug #1157643: procps fail to start. Edit Remove
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
procps (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Recent updates on a typical Ubuntu 12.04 (12.04.3) LAMP server has errors relating to updates to the "procps" package.

Apparently, /proc/sys/kernel/kptr_restrict is no longer editable, even by root,
and is always set to "1", as confirmed by: cat /proc/sys/kernel/kptr_restrict

Therefore, attempts to change it in /etc/sysctl.d/10-kernel-hardening.conf will fail.

As a consequence of this, apt-get will complain with errors and the "procps" package will never finish being installed.

- - - - -

An effective workaround is to comment out this line: (in the file: /etc/sysctl.d/10-kernel-hardening.conf )
# kernel.kptr_restrict = 1

And then run this command: service procps restart

-- David

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in procps (Ubuntu):
status: New → Confirmed
Revision history for this message
Andreas Gutlederer (5ndreas) wrote :

Workaround doesn't work for me but I'm able to change /proc/sys/kernel/kptr_restrict:

# cat /proc/sys/kernel/kptr_restrict
1

# echo 2 > /proc/sys/kernel/kptr_restrict
# cat /proc/sys/kernel/kptr_restrict
2

Revision history for this message
Filip Dorosz (fihufil) wrote :

This workaround worked for me. However iptables now seem to work quite strange. Valid config (it used to worked well in same containers) block outgoing connections but not incomming etc.
This happen on updated 12.04.3 on OpenVZ.
greetings.
~Filip

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.