Changes between Initial Version and Version 2 of Ticket #749


Ignore:
Timestamp:
01/11/10 15:55:39 (8 years ago)
Author:
admin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #749

    • Property Status changed from new to closed
    • Property Resolution changed from to duplicate
    • Property Severity changed from to minor
  • Ticket #749 – Description

    initial v2  
    276276   ------- Additional comments from megware Mon Feb 8 07:45:08 -0700 2010 -------
    277277do you need any further information or tests?
     278------- Additional comments from megware Wed Sep 22 04:56:42 -0700 2010 -------
     279
     280observations found on the ge-users list just now:
     281
     282===
     283Date: Wed, 22 Sep 2010 13:39:04 +0200                                                                                         
     284From: juanjo <juanjo.gutierrez@jeppesen.com>                                                                                   
     285To: users@gridengine.sunsource.net                                                                                             
     286Subject: Re: [GE users] anyone running GE 6.2u{5,6} on openSUSE 11.3                                                           
     287
     288On Fri, 6 Aug 2010 14:06:46 +0200 reuti wrote:
     289
     290> > the issue 3194 "sge_shepherd segfault on OpenSuSE 11.2 (x86_64)" is                                                       
     291> > still open. Has anyone managed to run GE 6.2u{5,6} on openSUSE 11.2                                                       
     292> > or the recently released openSUSE 11.3 ?                                                                                   
     293>                                                                                                                             
     294> my experience with this issue is a little bit weird: on some systems                                                         
     295> with 11.2 it's working w/o any problems, on others it's crashing. As                                                         
     296> these are desktop machines  with different mainboards (where we run                                                         
     297> SGE local) my observations are further, that systems with the same                                                           
     298> mainboards share the behavior. So it could be a side effect of one of                                                       
     299> the kernel modules in interaction with SGE.                                                                                 
     300
     301We were testing SGE 6.2u5 on SuSE 11 and run into this same issue.
     302After some fiddling around we've found out that starting the nscd
     303daemon makes sge_shepherd behave correctly. It might also serve as an
     304indication of what is wrong with the source.
     305
     306According to the strace present on the issue, nscd was also not
     307started. I don't seem to be able to update the issue on the issue
     308tracker, so someone that does, please do :)
     309
     310/juanjo
     311===
     312
     313I'll see whether nscd is/was running on that system.
     314
     315stephan
     316
    278317}}}