Hi,
Thanks a lot Marco for the help. Yes, I initially copied the executable,
then I built it on the cluster and now it works, almost :)
Works well until the moment I compile the program with *-x10rt mpi* option.
The program is compiled and executable is generated, but it is not running.
The error states:
* "Underlying MPI implementation does not provide
requested threading level*
* Unable to support requested level of X10
threading; exiting"*
(the whole output is attached)
I found this page: https://sourceforge.net/p/x10/mailman/message/33490796/
and started looking into X10 runtime variables (X10RT_MPI_THREAD_MULTIPLE,
X10_STATIC_THREADS) and played a bit with those but with no success..
On my linux laptop it works with -x10rt mpi option, with no errors. In both
cases, on my machine and the cluster, MPI_THREAD_MULTIPLE is set to no.
Does someone has an idea how to solve this?
Thank you,
Marina
On Tue, Jul 26, 2016 at 1:00 AM, Marco Bungart <m.bung...@gmx.net> wrote:
> Hi Maina,
>
> looks like you have not built the program on the cluster. Did you just
> copy the executable? This will in general not work. You should download
> and compile/install X10 on the cluster as well. The easiest way would be
> to build X10 from source (tutorial found here:
> http://x10-lang.org/x10-development/building-x10-from-source.html).
> After that, re-compile your program on the cluster and execute it.
>
> Cheers,
> Marco
>
> Am 25.07.2016 um 18:11 schrieb Marina Andric:
> >
> > Thanks a lot Marco, this was something I neglected :) the program is
> > compiling/executing now on my machine.
> >
> > 'Im still having a problem on the cluster. I get compilation error
> stating:
> >
> > x10.dist/stdlib/lib/libx10.so: undefined reference to 'memcpy@GLIBC_2.14
> '
> > x10.dist/stdlib/lib/libx10.so: undefined reference to
> > 'clock_gettime@GLIBC_2.17'
> >
> > Does somebody know the possible origins of this problem? Do I maybe need
> > to load some additional modules on the cluster, except gcc and mpi?
> >
> > Warm regards,
> > Marina
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Sun, Jul 24, 2016 at 11:48 PM, Marco Bungart <m.bung...@gmx.net
> > <mailto:m.bung...@gmx.net>> wrote:
> >
> > Hi,
> >
> > have you tried running "$> ./a.out" instead of "$> a.out"? Some
> systems
> > distinguish between system-wide executable (i.e. executable located
> in
> > one of the paths specified in the $PATH environment variable) and
> > executables in the current folder (i.e. ".").
> >
> > Cheers,
> > Marco
> >
> > Am 24.07.2016 um 21:22 schrieb Marina Andric:
> > > Hi all,
> > >
> > > I am trying to run an x10 program on a cluster. The cluster
> supports
> > > only MPI based communication between nodes so I built the latest
> x10
> > > source (version 2.6.0) with option -DX10RT_MPI=true and the build
> was
> > > successful.
> > >
> > > My program works when it's compiled to java (via x10c) but it
> doesn't
> > > work when it is compiled to c++ (via x10c++).
> > >
> > > For example, when
> > >
> > >> x10.dist/bin/x10c++ hello.x10 (creates a.out)
> > >> a.out
> > >
> > > the outcome is a.out: command not found.
> > >
> > > I tested a bit around, with -o option, -x10rt sockets (mpi) and
> > nothing
> > > seemed to change. I eventually built x10 without -DX10RT_MPI=true
> and
> > > the problem is the same, also with the x10 version 2.5.4.
> > >
> > > I was building and testing on my local linux machine and I checked
> all
> > > the program versions and they seem to be ok:
> > >
> > > ant 1.9.3
> > > g++ 4.8.4
> > >
> > > Can someone please say if I'm missing something?
> > >
> > > Thank you,
> > > Marina
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
> ------------------------------------------------------------------------------
> > > What NetFlow Analyzer can do for you? Monitors network bandwidth
> > and traffic
> > > patterns at an interface-level. Reveals which users, apps, and
> > protocols are
> > > consuming the most bandwidth. Provides multi-vendor support for
> > NetFlow,
> > > J-Flow, sFlow and other flows. Make informed decisions using
> > capacity planning
> > > reports.http://sdm.link/zohodev2dev
> > >
> > >
> > >
> > > _______________________________________________
> > > X10-users mailing list
> > > X10-users@lists.sourceforge.net
> > <mailto:X10-users@lists.sourceforge.net>
> > > https://lists.sourceforge.net/lists/listinfo/x10-users
> > >
> >
> > ---
> > Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> > https://www.avast.com/antivirus
> >
> >
> >
>
> ------------------------------------------------------------------------------
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> > traffic
> > patterns at an interface-level. Reveals which users, apps, and
> > protocols are
> > consuming the most bandwidth. Provides multi-vendor support for
> NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using
> > capacity planning
> > reports.http://sdm.link/zohodev2dev
> > _______________________________________________
> > X10-users mailing list
> > X10-users@lists.sourceforge.net <mailto:
> X10-users@lists.sourceforge.net>
> > https://lists.sourceforge.net/lists/listinfo/x10-users
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> > patterns at an interface-level. Reveals which users, apps, and protocols
> are
> > consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> > reports.http://sdm.link/zohodev2dev
> >
> >
> >
> > _______________________________________________
> > X10-users mailing list
> > X10-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/x10-users
> >
>
> ---
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> https://www.avast.com/antivirus
>
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> _______________________________________________
> X10-users mailing list
> X10-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/x10-users
>
[mpi/x10rt_mpi.cc:576] Underlying MPI implementation does not provide requested
threading level
Unable to support requested level of X10 threading; exiting
[n-62-14-13:05400] *** Process received signal ***
[n-62-14-13:05400] Signal: Aborted (6)
[n-62-14-13:05400] Signal code: (-6)
[n-62-14-13:05400] [ 0] /lib64/libpthread.so.0(+0xf7e0) [0x7f36bb2c47e0]
[n-62-14-13:05400] [ 1] /lib64/libc.so.6(gsignal+0x35) [0x7f36b8f6e625]
[n-62-14-13:05400] [ 2] /lib64/libc.so.6(abort+0x175) [0x7f36b8f6fe05]
[n-62-14-13:05400] [ 3]
/zhome/d8/8/110915/x10mpibuild/x10260/x10.dist/lib/libx10rt_mpi.so(x10rt_net_init+0x291)
[0x7f36bac67abd]
[n-62-14-13:05400] [ 4]
/zhome/d8/8/110915/x10mpibuild/x10260/x10.dist/lib/libx10rt_mpi.so(x10rt_lgl_init+0x40)
[0x7f36bac7c0ad]
[n-62-14-13:05400] [ 5]
/zhome/d8/8/110915/x10mpibuild/x10260/x10.dist/lib/libx10rt_mpi.so(x10rt_init+0x2a)
[0x7f36bac7a54b]
[n-62-14-13:05400] [ 6]
/zhome/d8/8/110915/x10mpibuild/x10260/x10.dist/stdlib/lib/libx10.so(_ZN6x10aux12network_initEiPPc+0x22)
[0x7f36bc3326c3]
[n-62-14-13:05400] [ 7]
/zhome/d8/8/110915/x10mpibuild/x10260/x10.dist/stdlib/lib/libx10.so(+0xaf4951)
[0x7f36bc330951]
[n-62-14-13:05400] [ 8]
/zhome/d8/8/110915/x10mpibuild/x10260/x10.dist/lib/libgc.so.1(GC_inner_start_routine+0x53)
[0x7f36bb4f20e3]
[n-62-14-13:05400] [ 9]
/zhome/d8/8/110915/x10mpibuild/x10260/x10.dist/lib/libgc.so.1(GC_call_with_stack_base+0x12)
[0x7f36bb4ed232]
[n-62-14-13:05400] [10] /lib64/libpthread.so.0(+0x7aa1) [0x7f36bb2bcaa1]
[n-62-14-13:05400] [11] /lib64/libc.so.6(clone+0x6d) [0x7f36b902493d]
[n-62-14-13:05400] *** End of error message ***
--------------------------------------------------------------------------
mpirun noticed that process rank 0 with PID 5400 on node n-62-14-13 exited on
signal 6 (Aborted).
--------------------------------------------------------------------------
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
X10-users mailing list
X10-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/x10-users
