FS#29320 - [sudo] Sometimes fails with error 143

Attached to Project: Arch Linux
Opened by Tim (tes) - Saturday, 07 April 2012, 10:24 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 29 April 2012, 14:12 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Allan McRae (Allan)
Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When running sudo, the process *sometimes* exits with return status 143. No further error messages or any indication of what went wrong. This has been going on for at least a few weeks.

Additional info:
sudo 1.8.4.p4-1

/etc/sudoers:
root ALL=(ALL) ALL
nt ALL=(ALL) ALL

No changes to the sudo pam configuration.

Similar problem on the debian bugtracker (not by me): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667814

Steps to reproduce:

[root@server: ~]# echo ok > /tmp/test

[root@server: ~]# sudo cat /tmp/test; echo $?
143

[root@server: ~]# sudo cat /tmp/test; echo $?
143

[root@server: ~]# sudo cat /tmp/test; echo $?
ok
0

[root@server: ~]# sudo cat /tmp/test; echo $?
ok
143

[root@server: ~]# sudo cat /tmp/test; echo $?
143

[root@server: ~]# sudo cat /tmp/test; echo $?
143

[root@server: ~]# sudo cat /tmp/test; echo $?
ok
0

(Never mind root, it does the same for my user account)
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 29 April 2012, 14:12 GMT
Reason for closing:  Fixed
Comment by Dave Reisner (falconindy) - Monday, 09 April 2012, 12:42 GMT
What version of systemd?
Comment by Tim (tes) - Monday, 09 April 2012, 15:21 GMT
Currently 44-1
Comment by Dave Reisner (falconindy) - Monday, 09 April 2012, 15:36 GMT Comment by Tim (tes) - Wednesday, 11 April 2012, 11:32 GMT
Oops, can't afford to upgrade now, but I will do so in two weeks. Assuming this is fixed in the meantime.
Comment by Tim (tes) - Wednesday, 25 April 2012, 05:02 GMT
Upgraded my system, but the problem is still there.
Comment by Dave Reisner (falconindy) - Sunday, 29 April 2012, 03:30 GMT
Running version of systemd is? I'm assuming you rebooted or re-exec'd logind/systemd before reporting that this still doesn't work...
Comment by Tim (tes) - Sunday, 29 April 2012, 07:36 GMT
I'm now using 44-5.

I've followed the trail of bugreports to the systemd bugtracker: https://bugs.freedesktop.org/show_bug.cgi?id=45670

In the meantime, I've added "session required pam_loginuid.so" to the sshd pam configuration, and now sudo works again.
Comment by Dave Reisner (falconindy) - Sunday, 29 April 2012, 14:12 GMT
Cool, thanks for following up. This is fixed in testing/openssh.

Loading...