| Summary: | LinuxIA32 AC - Security fails with SIGSEGV or unable to connect | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Bob Duncan <duncan> | ||||||
| Component: | TPTP | Assignee: | Igor Alelekov <igor.alelekov> | ||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | P1 | CC: | karla.callaghan, paulslau, samwai | ||||||
| Version: | unspecified | Keywords: | plan | ||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | closed460 | ||||||||
| Bug Depends on: | |||||||||
| Bug Blocks: | 125103 | ||||||||
| Attachments: |
|
||||||||
|
Description
Bob Duncan
These failures only occur with security enabled for the AC. The details (uname -a and java -version) for the machines mentioned in comment #1 are as follows: RedHat AS 2.1: Linux .... 2.4.9-e.49 #1 Fri Aug 6 11:56:52 EDT 2004 i686 unknown Java HotSpot(TM) Client VM (build 1.5.0_05-b05, mixed mode) Suse SLES9: 2.6.5-7.97-default #1 Fri Jul 2 14:21:59 UTC 2004 i686 i686 i386 GNU/Linux IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20060504
Debugging this on suse 9.0 I am seeing the following in the servicelog.log file
Exception in init() from fileServer.c (line 309)
The code is written so it tries to continue and I am not seeing any more errors in the the servicelog.log file.
I am seeing an error on the AC's console
java.lang.NullPointerException
KeyStoremanagerImpl.java (50)
SecureServer.java (48)
This test was using the IBM 1.5 jvm.
I was not seeing this error running on suse 10.0
I think this error is due to running on an NFS mounted file system and not being able to setuid on the necessary executable. I discussed this with Samson and we agreed to add a bugzilla and put in a release note. I am seeing some slightly different symptoms. I am still encountering the same problems in 4.3.0 with the TPTP-4.3.0-200610090100 driver. Some further info for each follows:
For the Sigsegv on RedHat (during AC start), I am getting a dump (attached) with the key info being the following failing call stack:
Stack: [0x4ed90000,0x4f58f000), sp=0x4f58c94c, free space=8178k
Native frames: (J=compiled Java code, ... , Vv=VM code, C=native code)
V [libjvm.so+0x4b18fa]
V [libjvm.so+0x3ede78]
V [libjvm.so+0x256876]
V [libjvm.so+0x2721d1]
C [libtptpCCTL.so+0xe4f5] getnewstrutf+0x21
C [libtptpCCTL.so+0xdcd1] createSecuredFileServer+0x201
C [libtptpCCTL.so+0xe57d] JavaJob+0x81
C [libpthread.so.0+0x6c6f]
For the "Unable to connect" condition on SUSE SLES9 (attempting to connect after the AC starts), the following message appears in the AC servicelog (attached):
msg="Security is enabled. Notify client to authenticate and drop this
connection and reconnect to port 0" severity="10"
Created attachment 52170 [details]
Dump from SigSegv on RedHat
Created attachment 52171 [details]
Servicelog (with level=DEBUG) from "unable to connect" on Suse SLES9
Retarget to 4.4. This is a blocker to the adoption of the new AC's backwards compatibility on Linux (125103). Assigning new AC Linux bugs to Igor, consider for 4.4. Added effort estimate: 5 days Marked as resolved since testing of AC 4.4i1 (build TPTP-4.4.0-200702211545) at RedHat AS 2.1, RHEL 4 upd 3, SLES-9 and SLES-10 with Sun (1.4, 1.5) and IBM (1.5) JVM was successfull. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |