NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
It is likely that this is still an issue (unless IDV 2.7 takes care of the problem). --------------------------------------- | Case Information | --------------------------------------- Case Title : [SEG] RHEL5 Xvfb Segmentation fault Case Number : 1841218 Case Open Date : 09-JUL-2008 Problem Type : Last Update Comment as of 25-JUN-2009 04:51:47 : Hello, I just wanted to provide with an update that engineering is still making progress on this issue. They have isolated the area of code in which the problem occurs and are working towards implementing a solution. I will keep you posted of any further progress or changes. Regards, John Ruemker, RHCA --------------------------------------- Thank you for your latest interaction with Red Hat Support. If you wish to reach Red Hat, please go to http://support.redhat.com/ for phone and web contact information appropriate to your region and support contract. Red Hat Global Support Services is working a case associated to this email address as the primary point of contact. For tracking purposes, the case has been assigned a number of "1841218" and has the title "[SEG] RHEL5 Xvfb Segmentation fault". More information related to this specific case is attached to this message. If any of this is in error, please notify us immediately by calling our support line at the number specific to your region see https://www.redhat.com/support/service/GSS_phone.html The purpose of this email is to notify you that a Red Hat associate is presently working on this case and has updated the case with the following information.You may continue to follow the progress and read any notes logged to the case at http://support.redhat.com. If you update the case via the web portal (such as adding a note or adding an attachment), the case status will stay in the "Waiting on Red Hat" status, or you may change it to "Closed". If left in "Waiting on Red Hat", the case will stay in this status while it is worked until changed by Red Hat to "Waiting on Customer", If more information is needed from you, or "Pending Closure" or "Closed" depending on the situation. Note: Please do not reply to this email. If you wish to reach Red Hat, please go to http://support.redhat.com for phone and web contact information appropriate to your region and support contract. Thank you so much and have a great day. Red Hat Global Support Services ________________________________________ From: idvusers-bounces@xxxxxxxxxxxxxxxx [idvusers-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Zehel, Samuel [zehel@xxxxxxx] Sent: Monday, June 08, 2009 2:49 PM To: Matt Alonso Cc: idvusers@xxxxxxxxxxxxxxxx Subject: Re: [idvusers] IDV/Xvfb behavior If you have the kernel 2.6.18-128.1.10, or later (you can check by typing "uname -a" in a terminal window.), you have 5.3 already. It was released in January, and comes with the normal RHEL 5 update process. I looked in the release notes for 5.3, and it doesn't seem to mention Xvfb at all. I suspect there still may be a bug in Xvfb. If you have already tried 5.3, and still have this problem, you may want to try a POSSIBLE solution that Evan Lowery(elowery@xxxxxxxxxxxx) has found - using IDV2.7b2 on a 32 bit system with Java 3D 1.3 (compatibility mode) You may want to check with Evan and/or Unidata first, since I said before - I have not been able to find a solution to the Xvfb problem (other than running IDV scripts thru the Console) ________________________________________ From: Matt Alonso [matt.alonso@xxxxxxxxx] Sent: Sunday, June 07, 2009 2:53 PM To: Zehel, Samuel Cc: Tom Whittaker; idvusers@xxxxxxxxxxxxxxxx Subject: Re: [idvusers] IDV/Xvfb behavior Hi Samuel, Thanks very much for the reply. I will definitely look into upgrading to 5.3 and will report back what happens. I agree, setting up virtual machine is not really something that I believe is possible for us at the moment. The weird thing is that it runs fine on CentOS5 which seems a little odd. Ultimately, the Xvfb is a temporary solution until I can identify what is causing ISL scripts to fail when offscreen is set to true. Thanks again for the help Samuel and I will keep the list updated w/any progress I have. Cheers, Matt On Fri, Jun 5, 2009 at 11:40 AM, Zehel, Samuel <zehel@xxxxxxx<mailto:zehel@xxxxxxx>> wrote: The situation I ran into was not a hardware issue, because I could run the .isl script at the console with no problem. Only Xvfb would fail(with a segment fault). My belief was that RedHat introduced a bug to xvfb when moving to RHEL5, since RHEL3 seemed to work fine. I submitted this issue to RedHat, and was told that this would be fixed in RHEL 5.3. I have not been able to test the 5.3 fix, however Matt makes it sounds as though it may still be an issue. If you haven't upgraded to 5.3, please do so, and let us know how it goes. RedHat technical support also suggested using a Virtual(XEN) machine to run IDV with the .isl script, until RHEL 5.3 was released. Unfortunately the amount of time/effort required to convert our server to XEN is prohibitive. It also seems like using and elephant gun to kill a flea. I was going to wait until 5.3 came out, but the xvfb problem has now become a low priority at our site. _______________________________________________ idvusers mailing list idvusers@xxxxxxxxxxxxxxxx For list information, to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
idvusers archives: