Problem Opening ECCE Builder

From NWChem

Viewed 2754 times, With a total of 7 Posts
Jump to: navigation, search

Clicked A Few Times
Threads 6
Posts 8
I have installed ECCE v-7.0 in Debian Testing/Jessie RC1. There were no warning or error messages and the system started without any errors or warnings.

However, when I attepted opening Builder, after creating a j0b I got the following (in fact this is the entire run low):

comp@inga:~$ ecce
Starting ECCE server ...
/home/comp/Apps/ecce-v7.0/server/httpd/bin/apachectl start: httpd started
[1] 1450
INFO BrokerService - ActiveMQ 5.1.0 JMS Message Broker (localhost) is starting
INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:inga-41936-1426273887689-0:0) started

Starting ECCE ... please wait
The program 'builder' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
 (Details: serial 1966 error_code 2 request_code 156 minor_code 24)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

The application runs in Debian v-7.8 (on another computer) without any problems. Not being a programmer I have no idea as to what might be the problem.

Stephen P. Molnar, Ph.D. Life is a fuzzy set
Foundation for Chemistry Stochastic and Multivariate
www.FoundationForChemistry.com
(614)312-7528(c)
Skype: smolnar1

Gets Around
Threads 14
Posts 110
See other posts. Are you running this natively or in a VM?

Make sure that it's not down to you using
1) a VM
2) a testing release rather than a stable one

What does glxgears do?
Edited On 12:42:31 AM PDT - Tue, Apr 28th 2015 by Ohlincha

Clicked A Few Times
Threads 6
Posts 8
I am reasonably sure that the problem is not due to the VMware Player. I have run ecce n the same vm in other Linux distributions without any problems.

Glxgrears runs without any problem.

I have just changed from Debian Testing to Debian Jessie (stable) and get the same error messsage.

I do not have this problem on my production tower running natiivee Debian Wheezy.

Clicked A Few Times
Threads 6
Posts 8
ECCE runs perfectly in Debian Wheezy/Stable in a VM n the same version of VMware Player.

Gets Around
Threads 14
Posts 110
Confirmed on Debian Jessie
I'm finally getting around to testing ECCE on debian jessie (remember that I'm just a user who posts to this forum and am in no way affiliated with PNNL, NWChem or ECCE), and I can confirm that
  • on one debian jessie system with onboard intel graphics (dell laptop) a fresh binary install of ECCE starts, generates the floating menu from which the organizer can be opened. A new job can be created, but the builder won't open
  • on another debian jessie system, with onboard nvidia graphics (homebuilt desktop), a fresh binary install of ECCE starts, generates the floating menu, but nothing can be started -- the mouse icon just churns as if waiting for something to happen. Not even the periodic table will open.
  • on the second system, a functioning ECCE version had been compiled and installed under wheezy. This version behaves the same as a fresh binary install i.e. doesn't open any viewer, builder, organizer etc.

Both systems were upgraded from debian wheezy, but the second system only had a desktop installed under jessie.



I've also built ECCE on debian jessie (http://verahill.blogspot.com.au/2015/06/611-building-ecce-on-debian-jessie.html). I've confirmed that it works perfectly on a thinkpad sl410 with intel graphics. I still need to confirm that it works on machines with nvidia.
Edited On 3:35:29 PM PDT - Fri, Jun 5th 2015 by Ohlincha

Clicked A Few Times
Threads 13
Posts 35
I'm posting so that I can follow this thread, but I'll contribute what I can.

I have two machines that I installed Debian Jessie on when that was the testing version along with both GNU and KDE desktop (I actually use i3wm for my window manager). I installed ECCE on both machines and it more or less worked correctly. The machines are:

An HP Probook 4530s with an Intel HD Graphics 3000.
A homebuilt desktop with an Nvidia GeForce GTX660.

After Jessie moved from testing to stable I can no longer open the builder/viewer on the laptop version, but everything still works correctly on the desktop.

I use a third machine with a Matrox MGA G200eW WPCM450 that recently moved from Ubuntu 14.04.1 to 14.04.2 and sometime around that time the viewer/builder quit opening.

On a possibly unrelated note, both the laptop and the Ubuntu system also had the issue I mentioned here: http://www.nwchem-sw.org/index.php/Special:AWCforum/st/id1648/ECCE_gives_no_properties_wit... where the input parser misidentifies the ECCE output for normal NWChem runs as an NWChem Metadynamics runs and thus fails to give any properties.
Edited On 12:56:14 PM PDT - Fri, Jun 26th 2015 by WillEverett

Clicked A Few Times
Threads 13
Posts 35
As suggested by ochlinda, I tried recompiling ecce using the patch referenced in this post and the builder and viewer windows now open as expected.

Gets Around
Threads 14
Posts 110
Quote:WillEverett Jun 27th 6:55 am

On a possibly unrelated note, both the laptop and the Ubuntu system also had the issue I mentioned here: http://www.nwchem-sw.org/index.php/Special:AWCforum/st/id1648/ECCE_gives_no_properties_wit... where the input parser misidentifies the ECCE output for normal NWChem runs as an NWChem Metadynamics runs and thus fails to give any properties.


Both apps/data/client/cap/MetaDyn.edml and apps/data/client/cap/NWChem.edml look for the same patterns:
me@beryllium:/media/highio/ecce-v7.0g/apps/data/client/cap$ grep verifypattern NWChem.edml 
  <Output type="parse" verifypattern="%begin%input" mimetype="chemical/x-ecce-parse">ecce.out</Output>
  <Output type="parse" verifypattern="%begin%input" mimetype="chemistry/x-ecce-parse">ecce.out</Output>
me@beryllium:/media/highio/ecce-v7.0g/apps/data/client/cap$ grep verifypattern MetaDyn.edml 
  <Output type="parse" verifypattern="%begin%input" mimetype="chemical/x-ecce-parse">ecce.out</Output>
  <Output type="parse" verifypattern="%begin%input" mimetype="chemistry/x-ecce-parse">ecce.out</Output>

so I suspect that the file is first checked to see if it's standard nwchem output, and only after that is it checked to see if it's a metadyn file.

I had issues on one workstation when it came to opening output files. The remedy was to edit the .edml file(s) and add the full path to the importer script
  <Importer>${ECCE_HOME}/scripts/parsers/Gaussian-03.expt </Importer>

On the other hand, on all the other systems things worked fine 'out of the box' and making the above change caused the import to fail.


Logging (ECCE_RCOM_LOGMODE true in site_runtime and RemoteServer/site_runtime) will be key to sorting this out.


Forum >> ECCE: Extensible Computational Chemistry Environment >> General ECCE Topics



Who's here now Members 0 Guests 0 Bots/Crawler 1


AWC's: 2.5.10 MediaWiki - Stand Alone Forum Extension
Forum theme style by: AWC