ottomeister a écrit :
On Wed, Sep 23, 2009 at 2:31 PM, Bob Doolittle <[email protected]> wrote:So if I follow, it's the CentOS session that's terminating? It sounds like the X server is crashing. gdm might have logged some clues in /var/log/gdm or wherever it stores its logs (sorry, my RHEL system is down at the moment). I'm less familiar with Linux than Solaris, is there an equivalent of coreadm so that you can force core dumps to some particular location? If so, I'd do that and see if you can find a core dump for Xnewt.The Sun Ray X server, and therefore its error messages (in /var/dt/Xerrors) and possible core dumps, will be on the Solaris machine that is running SRSS. So 'coreadm' can be used to gather core dumps in a specific location. If core dumps are being generated then 'pstack' on those files will tell us whether this is the same issue as the Matlab crash. OttoM.
Thank you for your replies. I did a bit of digging from what you suggested. - on the linux box, nothing to declare - on the solaris server:- /var/dt/Xerrors contains many errors regarding keyboard configuration (but they're explicitely noted as non-fatal). However, I have the following message: "FreeFontPath: FPE "/usr/X11/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing." sometimes (but not always) directly followed by "Xserver exiting (desktop RESET)". As there is no timestamp in this file, I cannot say if that corresponds to the crashes I'm encountering - /core is created every time the Xserver crashes, and pstack /core returns (hopping the formatting won't be lost in the email):
________________________________________________________________core '/core' of 20747: /opt/SUNWut/lib/Xnewt :2 -nobanner -auth /var/dt/A:2-NRaOuk -query pis 0826f457 xmesa_check_and_update_buffer_size (0, 98b9ed0, 8047518, 8125d52, 0) + 27 08270199 XMesaResizeBuffers (98b9ed0, 84d50b0, 8047538, 8213ece, 8c8d1a0, 26) + 29 0826c270 __glXMesaDrawableResize (8c8d1a0, 26, 4d, 84d50b0, 86b97b8, 8bea588) + 20
08213ece PositionWindow (8bea588, a3, 4d, 84d50b0, 2e203fb, 88b9188) + 7e 0812da20 ResizeChildrenWinSize (8be9440, 9e, 0, ffffff62, 0, 88a98c8) + a0 081e9ddb miSlideAndSizeWindow (8be9440, 9e, 0, ffffff62, 0, 88b92a0) + 19b 0812ea80 ConfigureWindow (8be9440, 5, 9d3adf0, 889cbc0, 2a8, 0) + b9008106d54 ProcConfigureWindow (889cbc0, 889cbc0, 84edf60, 84d50b0, 889cbc0, 86b5ac0) + 94
081a9bbd XaceCatchDispatchProc (889cbc0, 889cbc0, 5, 15, 9d3ade4, 0) + 8d 0810e287 Dispatch (2, 0, 8047e58, 8121af1, fec9d788, 80a1a7c) + 4b7 08121f71 main (9, 8047e58, 8047e80) + 491 080a369a _start (9, 8047f00, 8047f16, 8047f19, 8047f23, 8047f29) + 7a ____________________________________________________________________I'm completely lost here, but there are some keywords (namely Mesa) that sound similar to the bug Tom Crummey described.
I suppose my only option now is to contact sun to have more information regarding this bug, because if it is a bug, and if it is not fixed, then I'm afraid the sun rays won't be of any use to us (which would be a shame, I quite like this system!)
Thank you for your help Regards Cyril
<<attachment: cyril_buttay.vcf>>
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
