Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
systemd maintainers: Please add an exclusion equivalent to attachment #867073[details] to tmpfiles.d , which has replaced the tmpwatch cron.daily script in RHEL-7.
(For #678161 you wanted to move this to a more specific package, but every installation includes Python due to yum/dnf, so adding an extra file to the Python interpreter instead of adding it to the main tmp.conf would be pointless overhead IMHO; if you disagree, feel free to reassign.)
+++ This bug was initially created as a clone of Bug #1058310 +++
Description of problem:
The Python multiprocessing library (http://docs.python.org/2/library/multiprocessing.html) can open an ephemeral socket for interprocess communication based on a temporary file. It creates these temp files in /tmp/pymp-XXXXXX. However, the atomic temp file creation does not ever list the directory, so its atime is not updated. However, the pymp-* directory is only generated once, when the program is started.
As a result, if a Python program runs for more than ten days (the default cleanup time for /tmp in /etc/cron.d/tmpwatch), creates sockets (e.g., with multiprocessing.connnection.Listener()), and has no open sockets when tmpwatch runs, the pymp-* directory will be removed, and the next time the Python program attempts to open a socket it will fail spectacularly.
Version-Release number of selected component (if applicable):
tmpwatch-2.9.16-4.el6.x86_64
python-2.6.6-51.el6.x86_64
python-libs-2.6.6-51.el6.x86_64
How reproducible:
Always.
Steps to Reproduce:
create-socket-and-sleep.py is attached. Run:
./create-socket-and-sleep.py 864010 & sleep 864005; bash /etc/cron.daily/tmpwatch
This takes ten days to run, so if you want something quicker, you can run:
./create-socket-and-sleep.py 70 & sleep 65;/usr/sbin/tmpwatch -x /tmp/.X11-unix -x /tmp/.XIM-unix -x /tmp/.font-unix -x /tmp/.ICE-unix -x /tmp/.Test-unix 1m /tmp
The tmpwatch command there is taken directly from the stock /etc/cron.daily/tmpwatch, with '240' (hours) changed to '1m' so that this can be run in a timely fashion.
Actual results:
% ./create-socket-and-sleep.py 70 & sleep 65;/usr/sbin/tmpwatch -x /tmp/.X11-unix -x /tmp/.XIM-unix -x /tmp/.font-unix -x /tmp/.ICE-unix -x /tmp/.Test-unix 1m /tmp
[1] 7361
/tmp/pymp-oki8QE/listener-AA8c0N
Traceback (most recent call last):
File "./create-socket-and-sleep.py", line 19, in <module>
sys.exit(main())
File "./create-socket-and-sleep.py", line 15, in main
l = Listener()
File "/usr/lib64/python2.6/multiprocessing/connection.py", line 106, in __init__
self._listener = SocketListener(address, family, backlog)
File "/usr/lib64/python2.6/multiprocessing/connection.py", line 227, in __init__
self._socket.bind(address)
File "<string>", line 1, in bind
socket.error: [Errno 2] No such file or directory
Traceback (most recent call last):
File "/usr/lib64/python2.6/multiprocessing/util.py", line 235, in _run_finalizers
finalizer()
File "/usr/lib64/python2.6/multiprocessing/util.py", line 174, in __call__
res = self._callback(*self._args, **self._kwargs)
File "/usr/lib64/python2.6/shutil.py", line 204, in rmtree
onerror(os.listdir, path, sys.exc_info())
File "/usr/lib64/python2.6/shutil.py", line 202, in rmtree
names = os.listdir(path)
OSError: [Errno 2] No such file or directory: '/tmp/pymp-oki8QE'
Expected results:
The file names of two temp files should be printed.
Additional info:
--- Additional comment from Chris St. Pierre on 2014-01-27 08:50:35 EST ---
A patch for /etc/cron.d/tmpwatch that fixes the issue is attached.
--- Additional comment from Miloslav Trmač on 2014-01-27 16:17:10 EST ---
Thanks for your report and the patch.
I'm not... thrilled... about the way multiprocessing uses the temporary directory, but we have a precedent in doing the same for bug #527425 .
Needs to be fixed for RHEL 7 first, though, to avoid a regression on update,
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-2101.html