Description of problem: When haproxy is running, sudo -u haproxy killall -0 haproxy outputs (incorrectly): haproxy: no process found and exists with exit code 1 On Rawhide (Fedora 32), it returns (correctly): haproxy(15849): Operation not permitted and exists with exit code 0. Version-Release number of selected component (if applicable): psmisc-23.1-7 (on Fedora 31) psmisc-23.2-3 (on Rawhide) How reproducible: Always Steps to Reproduce: 1.See description 2. 3. Actual results: See desciption Expected results: See description Additional info: Upstream commit 38829585 resolved the problem. Please could either that patch be included in Fedora, or else could psmisc be upgraded to version 23.2 (or even 23.3). The functionality was broken by upstream commit 6a2d61173 and the first version of psmisc that was in was v23.0
FEDORA-2019-71bf085842 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-71bf085842
FEDORA-2019-9de0094801 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-9de0094801
psmisc-23.2-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-71bf085842
psmisc-23.2-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-9de0094801
psmisc-23.2-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
psmisc-23.2-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
This update broke killall for me in a similar way. psmisc-23.1-7.fc31.x86_64 successfully kills some processes where psmisc-23.2-1.fc31.x86_64 gives "XXXXXXXXXXXXXXXX: no process found". The new killall works if I use the short/truncated process name (second column of /proc/PID/stat), but not the long process name. The older psmisc works with the long process name but does not work with the short process name found in /proc/PID/stat.
Created attachment 1639934 [details] psmisc.spec 23.3-1 Built psmisc version 23.3 with attached spec file and updated source tarball (sha256sum 41750e1a5abf7ed2647b094f58127c73dbce6876f77ba4e0a7e0995ae5c7279a). The resulting killall binary works for me with both the short and long process names.
FEDORA-2019-01d54af2ee has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-01d54af2ee
FEDORA-2019-9487833604 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-9487833604
psmisc-23.3-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-9487833604
psmisc-23.3-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-01d54af2ee
psmisc-23.3-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
psmisc-23.3-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
not fixed.. bug got introduced by the update itself. Was working correctly before.
new bug filed BZ#1869413
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days