Peacock aborted (core dumped)

283 views
Skip to first unread message

Yuki Maehashi

unread,
Feb 6, 2018, 7:10:06 PM2/6/18
to moose-users
I`m trying to install peacock by the procedure written by the following page.


However, when I entered "peacock" command, "Aborted (core dumped)" message is displayed.
Could you please tell me what is wrong?

Bests,
Yuki

Cody Permann

unread,
Feb 7, 2018, 3:23:47 PM2/7/18
to moose...@googlegroups.com
There is not enough information given here to troubleshoot. Do you have your application (or the moose/test application built and running ok)? Make sure the framework is working before you jump into working with peacock. When you are ready to do more, tell us about your system, and whether or not you are using our redistributable package, etc.

--
You received this message because you are subscribed to the Google Groups "moose-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to moose-users...@googlegroups.com.
Visit this group at https://groups.google.com/group/moose-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/3e735d71-589b-4b22-b8e7-19d658b5287d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Yuki Maehashi

unread,
Feb 8, 2018, 11:34:51 AM2/8/18
to moose-users
Thank you for your reply,
Yes, I have my own application, and the moose examples are correctly running.
I`m using moose on Ubuntu. I installed Ubuntu 16.04 Package version: Build 43 (Nov 30, 2017) shown in Getting Started page (http://mooseframework.org/getting-started/ubuntu-1204/).
If you need any other information, please let me know.

Thanks,
Yuki


2018年2月7日水曜日 15時23分47秒 UTC-5 Cody Permann:

Miller, Jason M

unread,
Feb 8, 2018, 12:16:16 PM2/8/18
to moose...@googlegroups.com
Can you perform the following and copy/paste the results?

  module list
  env
  which python

This will give us some additional information to go on.

Thanks!
Jason

To unsubscribe from this group and stop receiving emails from it, send an email to moose-users+unsubscribe@googlegroups.com.

Yuki Maehashi

unread,
Feb 8, 2018, 12:51:32 PM2/8/18
to moose-users
Thanks!

Attached is the obtained result.

Yuki

2018年2月8日木曜日 12時16分16秒 UTC-5 jason.miller:
Results.txt

Miller, Jason M

unread,
Feb 8, 2018, 1:06:16 PM2/8/18
to moose...@googlegroups.com
Thanks!

I am not seeing anything glaringly wrong. There may be something getting in the way with those first few entries in your PATH:

  PATH=/home/yukimaehashi/bin:/home/yukimaehashi/.local/bin:

But before we blame that, can you attempt to run peacock while in the moose/test directory (assuming you have already built moose/test... if not please do)?

  cd moose/test
  make
  peacock

If that fails, I would then like to manually import a few things using an interactive python shell:

[~]> python
Python 2.7.14 |Anaconda, Inc.| (default, Dec  7 2017, 11:07:58) 
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import vtk
>>> import PyQt5
>>> from matplotlib.backends.backend_qt5agg import FigureCanvasQTAgg
>>> import pandas
>>> 

See if you can enter those import commands, and not get an error...

Thanks!
Jason


To unsubscribe from this group and stop receiving emails from it, send an email to moose-users+unsubscribe@googlegroups.com.

Yuki Maehashi

unread,
Feb 8, 2018, 2:02:32 PM2/8/18
to moose-users
Thanks!
I entered make command on moose/test folder, and then entered peacock command.
However, "Aborted (core dumped)" was still displayed as attached...

When i entered import command as you said, there was no error.

Bests,
Yuki


2018年2月8日木曜日 13時06分16秒 UTC-5 jason.miller:
make and peacock command.txt
import.txt

Miller, Jason M

unread,
Feb 8, 2018, 2:43:43 PM2/8/18
to moose...@googlegroups.com
Looking over the results of `env` again, I just realized there is no 'DISPLAY' environment variable set. And the hostname, looks a little odd. I am thinking that this is actually a Windows machine running WSL (Windows Subsystem for Linux). We don't really officially support this yet... BUT we have gotten the older version of Peacock to work (we have yet to even attempt at launching the new version). The new version... _should_ work though!

If I am right, and this is a WSL system, can you attempt at following these posted instructions:  https://groups.google.com/forum/#!msg/moose-users/-Vwl42fZds0/aPrk5kQFDQAJ
Specifically, you need to do all the steps, except 6 and 9 (installing the moose-environment package, and build libMesh/moose)

Basically, WSL needs access to the display though the use of Xming.

Hope that is indeed the issue... If not... I am hoping someone else in our group has some ideas. Everything else looks spot on.
Jason


To unsubscribe from this group and stop receiving emails from it, send an email to moose-users+unsubscribe@googlegroups.com.

Yuki Maehashi

unread,
Feb 8, 2018, 5:53:32 PM2/8/18
to moose-users

Thank you for the many efforts.
And...yes, I`m using WSL system on Windows10.

Although I tried the procedure you proposed, I got the attached message... 
I`ll try the command suggested in the log, but I don`t know what <env_name> mean.

Bests,
Yuki
 

2018年2月8日木曜日 14時43分43秒 UTC-5 jason.miller:
Peacock.txt

Miller, Jason M

unread,
Feb 9, 2018, 9:47:45 AM2/9/18
to moose...@googlegroups.com
I'm afraid this is not going to work then... That particular error mentions a lack of OpenGL support on the system. Something we do not have much knowledge on resolving within this environment (WSL). A quick search on the internets for 'accelerated opengl wsl' does bring up some success stories. We'd love to hear back from you if you happen to get this to work! Also, there exists the Virtual Machine solution: http://mooseframework.org/getting-started/virtual-machine/.

I am sorry we just don't have a quick fix for this... Good luck with what ever path you choose to take!
Jason


To unsubscribe from this group and stop receiving emails from it, send an email to moose-users+unsubscribe@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages