java kills test3 dead?

[Sessoms, Mack]

it was definitely active after i power cycled, i got all sorts of audit 
messages and the box wouldn't completely boot.  had to power cycle again 
and add selinux=0 to the grub command.  it showed as active on the 
SELinux tab again.  rebooted without passing selinux=0 to grub and it 
still shows active.  may have something to do with this from earlier 
today:  btw, i'm using a single p4, no hyperthreading.

>On Thu, 2004-04-29 at 11:26, Jerone Young wrote:
>  
>
>>> Holly crap...It looks like the SELinux LSM module has
>>> been the cause of all my stability issues...I placed
>>> selinux=0 on the kernel command line and rebooted. And
>>> now my issue has just vanished (I never had SELinux,
>>> the kernel module is supposed to do nothing it you
>>> don't have the userspace stuff set, but apparently
>>> this is not true)...Me not likey this SELinux it is
>>> causing problems even when it's supposed to be off. It
>>> looks like you HAVE TO use selinux=0 and fully
>>> (fully!!) cut off SELinux, not just in userspace like
>>> redhat is doing now in Test 3. We need selinux=0 added
>>> to the kernel parms by default on install.
>>    
>>
>
>We recently upstreamed a change to allow complete disabling of SELinux,
>and SysVinit has been updated to use it.  So with the next kernel
>update, /etc/sysconfig/selinux disabled should yield the same behavior
>as selinux=0; SELinux will truly be unregistered as a security module.
>
> -- Stephen Smalley <sds at epoch.ncsc.mil> National Security Agency
>


Keith Irwin wrote:

>On Thu, 2004-04-29 at 10:18, Sessoms, Mack wrote:
>  
>
>>nope, locked up again.  can't even ssh to it.
>>    
>>
>
>Right.  I tried your fix, and it seemed to lock up even sooner than
>usual. ;)  And no ssh.
>
>I wonder why that System Tools setting says "active" even after you set
>it?
>
>And I thought selinux extensions were off by default? If I try to do an
>ls -Z I get a message telling me it's not enabled.
>
>Keith
>
>  
>
>>Sessoms, Mack wrote:
>>
>>    
>>
>>>fixed this by disabling SELinux under System Settings->Security 
>>>Level->SELinux tab.  Set it to disabled and fc2t3 doesn't lockup when 
>>>I start tomcat.  I went back and it showed Active again but the system 
>>>seems to be working.  I'll run my performance tests.
>>>
>>>Sessoms, Mack wrote:
>>>
>>>      
>>>
>>>>just did a fresh install of fc2t3, ibm java 2 sdk 1.4.1 sr2 and 
>>>>tomcat 5.0.19.  started tomcat and fc2t3 is locked, no response from 
>>>>keyboard or mouse.  this stack worked well on fc2t2, performance was 
>>>>awesome.  with fc2t2 and this stack, i had older hardware out running 
>>>>newer hardware which had fc1 (2.4.22) loaded.
>>>>
>>>>Keith Irwin wrote:
>>>>
>>>>        
>>>>
>>>>>Folks--
>>>>>
>>>>>I've installed sun's 1.4.2_4 SDK on my test3 system, then run a big ole
>>>>>"maven" build a few times, and have jboss running, all from within my
>>>>>normal user account (no SELinux).
>>>>>
>>>>>Seems that running java a lot can take down the system. It "feels" like
>>>>>a kernel problem, because it happens whether or not I'm in X.
>>>>>
>>>>>Anyway, I was wondering if ANYONE else around here has had this 
>>>>>problem?
>>>>>
>>>>>I wrote about it here:
>>>>>
>>>>>https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121902
>>>>>
>>>>>I have similar problems with test2, but thought it was just some weird
>>>>>SELinux interaction.
>>>>>
>>>>>Any confirmation?
>>>>>
>>>>>Keith
>>>>>
>>>>>
>>>>> 
>>>>>
>>>>>          
>>>>>
>>>>        
>>>>
>>>      
>>>
>
>
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-test-list/attachments/20040429/7481e6c9/attachment.htm>