Issue2025

Hi,

Version Jython 2.5.4

./jython -V
Jython 2.5.4rc1


OS: Solaris 10 (x86)

uname -a
SunOS atrcxb1809 5.10 Generic_147441-19 i86pc i386 i86pc


We are experiencing the exact same issue that was reported in  http://bugs.jython.org/issue1885 even though we have upgraded from Jython 2.5.2 to Jython 2.5.4:


FAILED: Message: [Errno 20000] Unknown error: 20000: '/var/opt/ericsson/nms_smo_srv/smo_file_store/Software/EXTREME/10_CXC_132_9107_R2C05/firmware/v784b1-patch1-4.SBxtr'
Error traceback:
Traceback (most recent call last):
File "/var/opt/ericsson/nms_smo_srv/smo_file_store/Software/EXTREME/10_CXC_132_9107_R2C05/bin/main.py", line 486, in <module>
mashost.copyFirmwareFile(LAN_SWITCH_PARAMS,file)
File "/var/opt/ericsson/nms_smo_srv/smo_file_store/Software/EXTREME/10_CXC_132_9107_R2C05/bin/OssUtils.py", line 439, in copyFirmwareFile
shutil.copy2(os.path.join(params['SSH_EW_PATH'], file), self.firmwarePath)
File "/var/opt/ericsson/nms_smo_srv/smo_file_store/Software/EXTREME/10_CXC_132_9107_R2C05/bin/OssUtils.py", line 439, in copyFirmwareFile
shutil.copy2(os.path.join(params['SSH_EW_PATH'], file), self.firmwarePath)
File "/opt/python/jpython/Lib/shutil.py", line 97, in copy2
copystat(src, dst)
File "/opt/python/jpython/Lib/shutil.py", line 74, in copystat
os.chmod(dst, mode) 


I have done a checksum comparison between the 2.5.2 shutil.py and the 2.5.4 version - and they are identical - not sure if that is relevent, but just in case:

cksum /opt/python/jpython/Lib/shutil.py
633590336       6103    /opt/python/jpython/Lib/shutil.py

vs

cksum /opt/python/jpython/Lib/shutil.py
633590336       6103    /opt/python/jpython/Lib/shutil.py



thank you,

Regards,
Dónal

What is the exact code that is failing?

Did this work on a previous version of Jython? Or did you get a different error message? What happens if you try the call from Jython as (something like):

os.system("chmod 0600 /path/to/file")

the following (suggested by you) works:

from os import system
system('chmod 660 file.txt')

We get the same error message on 2.5.2 and 2.5.4.

Have you tried this on 2.7b1? The libraries we use to hit posix are more recent in 2.7 - they can't be upgraded as far in 2.5.4 because of dependencies that can't in turn be upgraded in the 2.5 series for backwards compatibility reasons.

No -is 2.7b1 a stable release? Is it safe to deploy?

Regards 
Donal

No 2.7b1 is a beta, so it is not ready for production. I'm just trying to see if the upgraded posix libraries solve your problem to give a clue as to what to do. Hopefully it won't be a really long time before 2.7 is final, but I don't have a concrete date yet.

Hi frank -thanks. Is there any hope that we could back port the fix to 2.5.4?

Hi Frank,

Just wondering you saw my below query?

Did you check if the posix libraries are fixed in 2.7? 

If so - Is there any way that we could port back the posix libraries from  2.7 to 2.5.4?

Regards,
Dónal

Hi Donal,

I don't have access to a Solaris machine, so I can't actually check myself. 2.7b1 is available if you want to give it a try and let us know.

Hi Frank,

Yes, we plan to try it - but if it DOES work - what about the liftback - is that supported?

You mentioned some issue with the new posix libraries and dependencies in 2.5.4?

Regards,
Dónal

Ah I see - it sort of depends on why it works if it does. If it does turn out to be the jffi library updates, it probably can't be backported because the new jffi libs have dependencies that can't be backported. On the other hand, if it is broken in 2.7b1 or if it isn't the libraries that are the problem we might be able to find a back-portable solution.

Hi Frank,

Bad (or good?) news - 2.7 does NOT fix the issue.
So - do you know what the fix for this is?

Maybe we should look @ fixing it locally?

Is the problem with the OS chmod, or, in the Jython code?

Regards,
Dónal

Sorry for the slow response - I got the flu and just started to recover. Since this is almost certainly a bug in the posix library we use - the library authors are more closely associated with the JRuby project - I bet if you reproduce this on JRuby and log a bug with them you could get an expert to look into it. Another way to get their attention is to poke them  on irc on #jruby - they're very responsive there.

Please try with 2.7.0 beta 4, which has a significantly upgraded JNR Posix support in 3.0.9

No response, so assuming upgrade to 2.7 will be successful for this issue