[issue34028] Python 3.7.0 wont compile with SSL Support 1.1.0 > alledged missing X509_VERIFY_PARAM_set1_host() support
Change by Frank Thommen : -- nosy: -fthommen ___ Python tracker <https://bugs.python.org/issue34028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32627] Header dependent _uuid build failure on Fedora 27
Change by Frank Thommen : -- nosy: +fthommen ___ Python tracker <https://bugs.python.org/issue32627> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34028] Python 3.7.0 wont compile with SSL Support 1.1.0 > alledged missing X509_VERIFY_PARAM_set1_host() support
Frank Thommen added the comment: The configure script doesn't work with a proper openssl installation either. Even though there is a "lib" directory in the directory given to --with-openssl=, libssl.so.1.1 isn't found, because there is still a "-L/lib" missing in some of the compiler calls. LDFLAGS="-L/lib" ./configure --with-openssl= is required, which seems somehow redundant. Bug? -- nosy: +fthommen ___ Python tracker <https://bugs.python.org/issue34028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22326] tempfile.TemporaryFile fails on NFS v4 filesystems
Frank Thommen added the comment: strace gives me the error: unlink(/mnt/tmpu817xz) = -1 EIO (Input/output error) But after escalating the issue to our server vendor it turned out that the problem lies in the filesystem option nbmand. If this option is set to on - which it seems to be by default on our zfs filesystems - and the filesystem is exported and mounted with NFS v4, then tempfile.TemporaryFile fails: [...] V4 Call (Reply In 167) RENAME From: tmpr0OaMb To: .nfs0027af65 V4 Reply (Call In 166) RENAME Status: NFS4ERR_FILE_OPEN [...] I assume that this is nothing Python can check for and therefore not a Python problem. Not sure what the policy is: Can I set the ticket to solved myself? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22326 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22326] tempfile.TemporaryFile fails on NFS v4 filesystems
Frank Thommen added the comment: It might be an issue of strict ACL mapping (http://wiki.linux-nfs.org/wiki/index.php/ACLs) is implemented. On our ZFS based NFS v4 server this is the case, on CentOS based NFS v4 servers this doesn't seem to be implemented/enforced. It becomes then still a Python problem, as tempfile.TemporaryFile is not generally usable any more. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22326 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22326] tempfile.TemporaryFile fails on NFS v4 filesystems
New submission from Frank Thommen:
Hi,
tempfile.TemporaryFile fails on NFS v4 filesystems.
Assume the following mounts:
$ mount
[...]
psi:/volumes/vol1 on /mnt/nfsv4 type nfs4 (rw,addr=xx.xx.xx.xx)
psi:/volumes/vol1 on /mnt/nfsv3 type nfs (rw,addr=xx.xx.xx.xx)
[...]
$
and the following script testtmpfile.py:
---
#! env python
import tempfile
def _is_writable_dir_unnamed(p):
try:
t = tempfile.TemporaryFile(dir=p)
t.write('1')
t.close()
except OSError: return False
else: return True
def _is_writable_dir_named(p):
try:
t = tempfile.NamedTemporaryFile(dir=p)
t.write('1')
t.close()
except OSError: return False
else: return True
if not _is_writable_dir_unnamed(.):
print (unnamed) . is not writable
else:
print (unnamed) OK
if not _is_writable_dir_named(.):
print (named) . is not writable
else:
print (named) OK
---
Then you'll find the following behaviour:
$ pwd
/mnt/nfsv4
$ /g/software/bin/python-2.7 /tmp/testtmpfile.py
(unnamed) . is not writable
(named) OK
$
$ pwd
/mnt/nfsv3
$ /g/software/bin/python-2.7 /tmp/testtmpfile.py
(unnamed) OK
(named) OK
$
Additionally in the failing case, a - writable - temporary file named tmp* is
left in the directory.
Observed on CentOS 5.10 with kernel 2.6.18-371.11.1.el5 and on CentOS 6.5 with
kernel 2.6.32-431.23.3.el6.x86_64.
The problem appears with Python 2.4, 2.6 and 2.7.
Cheers
frank
--
messages: 226271
nosy: drosera
priority: normal
severity: normal
status: open
title: tempfile.TemporaryFile fails on NFS v4 filesystems
versions: Python 2.7
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22326
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22326] tempfile.TemporaryFile fails on NFS v4 filesystems
Frank Thommen added the comment: errno:5 strerror: Input/output error -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22326 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22326] tempfile.TemporaryFile fails on NFS v4 filesystems
Frank Thommen added the comment: Agreed. If I export from CentOS and mount on CentOS (local or remote) it seems to work. So this is probably due to our specific fileserver setup or a problem of the underlying filesystem (zfs). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22326 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
