November 2015 - discuss - mailman3.cels.anl.gov

MPI_Gather fails with 2048 processes and 4096 MB total
by Florian.Willich＠dlr.de 26 Nov '15

26 Nov '15

Dear mpich discussion group, the following issue appeared when running some benchmarks with MPI Gather: Gathering data (calling MPI_Gather(...) ) involing 2048 processes and 2 MB of data (4096 MB total) that each process sends fails with the following output: ____________________________ Rank 1024 [Thu Nov 26 09:43:16 2015] [c1-0c1s12n3] Fatal error in PMPI_Gather: Invalid count, error stack: PMPI_Gather(959)......: MPI_Gather(sbuf=0x2aaab826c010, scount=524288, MPI_INT, rbuf=(nil), rcount=524288, MPI_INT, root=0, MPI_COMM_WORLD) failed MPIR_Gather_impl(775).: MPIR_Gather(735)......: MPIR_Gather_intra(347): MPIC_Send(360)........: Negative count, value is -2147483648 _pmiu_daemon(SIGCHLD): [NID 00307] [c1-0c1s12n3] [Thu Nov 26 09:43:16 2015] PE RANK 1024 exit signal Aborted [NID 00307] 2015-11-26 09:43:16 Apid 949450: initiated application termination Application 949450 exit codes: 134 Application 949450 exit signals: Killed Application 949450 resources: utime ~1s, stime ~137s, Rss ~2110448, inblocks ~617782, outblocks ~1659320 ____________________________ The following are some tests that I ran to better understand the problem: 2047 processes - 2 MB (4094 MB total) -> works! 2048 processes - 2047.5 KB (~1.999512 MB) (4095 MB total) -> works! 2048 processes - 3 MB (6144 MB total) -> fails: ____________________________ Rank 1024 [Thu Nov 26 09:41:15 2015] [c1-0c1s12n3] Fatal error in PMPI_Gather: Invalid count, error stack: PMPI_Gather(959)......: MPI_Gather(sbuf=0x2aaab826c010, scount=786432, MPI_INT, rbuf=(nil), rcount=786432, MPI_INT, root=0, MPI_COMM_WORLD) failed MPIR_Gather_impl(775).: MPIR_Gather(735)......: MPIR_Gather_intra(347): MPIC_Send(360)........: Negative count, value is -1073741824 _pmiu_daemon(SIGCHLD): [NID 00307] [c1-0c1s12n3] [Thu Nov 26 09:41:15 2015] PE RANK 1024 exit signal Aborted [NID 00307] 2015-11-26 09:41:15 Apid 949448: initiated application termination Application 949448 exit codes: 134 Application 949448 exit signals: Killed Application 949448 resources: utime ~1s, stime ~139s, Rss ~3159984, inblocks ~617782, outblocks ~1659351 ____________________________ 2047 processes - 3 MB (6141 MB total) -> fails: ____________________________ Rank 1024 [Thu Nov 26 09:40:31 2015] [c1-0c1s12n3] Fatal error in PMPI_Gather: Invalid count, error stack: PMPI_Gather(959)......: MPI_Gather(sbuf=0x2aaab826c010, scount=786432, MPI_INT, rbuf=(nil), rcount=786432, MPI_INT, root=0, MPI_COMM_WORLD) failed MPIR_Gather_impl(775).: MPIR_Gather(735)......: MPIR_Gather_intra(347): MPIC_Send(360)........: Negative count, value is -1076887552 _pmiu_daemon(SIGCHLD): [NID 00307] [c1-0c1s12n3] [Thu Nov 26 09:40:32 2015] PE RANK 1024 exit signal Aborted [NID 00307] 2015-11-26 09:40:32 Apid 949446: initiated application termination Application 949446 exit codes: 134 Application 949446 exit signals: Killed Application 949446 resources: utime ~1s, stime ~134s, Rss ~3157072, inblocks ~617780, outblocks ~1659351 ____________________________ 8 processes - 625 MB (5000 MB total) -> works! I can think of some pitfalls that might cause this issue but I do not have the knowledge of the internally called routines to check them. Is someone familier with the implementation of MPI_Gather(...) and willing to help me? Best regards Florian Deutsches Zentrum für Luft- und Raumfahrt e. V. (DLR) German Aerospace Center Institute of Planetary Research | Planetary Physics | Rutherfordstraße 2 | 12489 Berlin Florian Willich| Intern - Software Developer (Parallel Applications) florian.willlich(a)dlr.de<mailto:[email protected]> DLR.de<http://www.dlr.de/> _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

a problem in build MPICH
by 蔡邹青 26 Nov '15

26 Nov '15

I can not find the problems in build MPICH.It always accur *** 没有指明目标并且找不到 makefile。停止。. _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Assist with Authorization Problem
by Balaji, Pavan 25 Nov '15

25 Nov '15

Sorry, we can't help with getting ssh to work correctly. You'll need to send your query to a more generic list that doesn't deal with MPI, such as StackOverflow or equivalent. -- Pavan > On Nov 25, 2015, at 12:49 PM, dave <dave(a)mynatt.biz> wrote: > > Hello Group, I am trying to figure out why the Authorization process fails, and enclose a copy of the CLI input: > > dave@ubuntu-desk:/home/mpiuser/cloud$ sudo ssh -v -v -v root(a)10.0.0.7 > OpenSSH_5.9p1 Debian-5ubuntu1.7, OpenSSL 1.0.1 14 Mar 2012 > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 19: Applying options for * > debug2: ssh_connect: needpriv 0 > debug1: Connecting to 10.0.0.7 [10.0.0.7] port 22. > debug1: Connection established. > debug1: permanently_set_uid: 0/0 > debug1: identity file /root/.ssh/id_rsa type -1 > debug1: identity file /root/.ssh/id_rsa-cert type -1 > debug1: identity file /root/.ssh/id_dsa type -1 > debug1: identity file /root/.ssh/id_dsa-cert type -1 > debug1: identity file /root/.ssh/id_ecdsa type -1 > debug1: identity file /root/.ssh/id_ecdsa-cert type -1 > debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1.7 > debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1.7 pat OpenSSH* > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.7 > debug2: fd 3 setting O_NONBLOCK > debug3: load_hostkeys: loading entries for host "10.0.0.7" from file "/root/.ssh/known_hosts" > debug3: load_hostkeys: found key type ECDSA in file /root/.ssh/known_hosts:3 > debug3: load_hostkeys: loaded 1 keys > debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521 > debug1: SSH2_MSG_KEXINIT sent > debug1: SSH2_MSG_KEXINIT received > debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 > debug2: kex_parse_kexinit: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],[email protected],[email protected],ssh-rsa,ssh-dss > debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc(a)lysator.liu.se > debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc(a)lysator.liu.se > debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 > debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 > debug2: kex_parse_kexinit: none,zlib(a)openssh.com,zlib > debug2: kex_parse_kexinit: none,zlib(a)openssh.com,zlib > debug2: kex_parse_kexinit: > debug2: kex_parse_kexinit: > debug2: kex_parse_kexinit: first_kex_follows 0 > debug2: kex_parse_kexinit: reserved 0 > debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 > debug2: kex_parse_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256 > debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc(a)lysator.liu.se > debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc(a)lysator.liu.se > debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 > debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 > debug2: kex_parse_kexinit: none,zlib(a)openssh.com > debug2: kex_parse_kexinit: none,zlib(a)openssh.com > debug2: kex_parse_kexinit: > debug2: kex_parse_kexinit: > debug2: kex_parse_kexinit: first_kex_follows 0 > debug2: kex_parse_kexinit: reserved 0 > debug2: mac_setup: found hmac-md5 > debug1: kex: server->client aes128-ctr hmac-md5 none > debug2: mac_setup: found hmac-md5 > debug1: kex: client->server aes128-ctr hmac-md5 none > debug1: sending SSH2_MSG_KEX_ECDH_INIT > debug1: expecting SSH2_MSG_KEX_ECDH_REPLY > debug1: Server host key: ECDSA b1:e8:45:37:94:57:19:11:32:83:6c:b5:05:c8:2d:6d > debug3: load_hostkeys: loading entries for host "10.0.0.7" from file "/root/.ssh/known_hosts" > debug3: load_hostkeys: found key type ECDSA in file /root/.ssh/known_hosts:3 > debug3: load_hostkeys: loaded 1 keys > debug1: Host '10.0.0.7' is known and matches the ECDSA host key. > debug1: Found key in /root/.ssh/known_hosts:3 > debug1: ssh_ecdsa_verify: signature correct > debug2: kex_derive_keys > debug2: set_newkeys: mode 1 > debug1: SSH2_MSG_NEWKEYS sent > debug1: expecting SSH2_MSG_NEWKEYS > debug2: set_newkeys: mode 0 > debug1: SSH2_MSG_NEWKEYS received > debug1: Roaming not allowed by server > debug1: SSH2_MSG_SERVICE_REQUEST sent > debug2: service_accept: ssh-userauth > debug1: SSH2_MSG_SERVICE_ACCEPT received > debug2: key: /root/.ssh/id_rsa ((nil)) > debug2: key: /root/.ssh/id_dsa ((nil)) > debug2: key: /root/.ssh/id_ecdsa ((nil)) > debug1: Authentications that can continue: publickey,password > debug3: start over, passed a different list publickey,password > debug3: preferred publickey,keyboard-interactive > debug3: authmethod_lookup publickey > debug3: remaining preferred: keyboard-interactive > debug3: authmethod_is_enabled publickey > debug1: Next authentication method: publickey > debug1: Trying private key: /root/.ssh/id_rsa > debug3: no such identity: /root/.ssh/id_rsa > debug1: Trying private key: /root/.ssh/id_dsa > debug3: no such identity: /root/.ssh/id_dsa > debug1: Trying private key: /root/.ssh/id_ecdsa > debug3: no such identity: /root/.ssh/id_ecdsa > debug2: we did not send a packet, disable method > debug1: No more authentication methods to try. > Permission denied (publickey,password). > > The failure is Permission Denied (as above, last line). Any help really appreciated. Thanks in advance. > > Dave > Pueblo, CO > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Assist with Authorization Problem
by dave 25 Nov '15

25 Nov '15

Hello Group, I am trying to figure out why the Authorization process fails, and enclose a copy of the CLI input: dave@ubuntu-desk:/home/mpiuser/cloud$ sudo ssh -v -v -v root(a)10.0.0.7 OpenSSH_5.9p1 Debian-5ubuntu1.7, OpenSSL 1.0.1 14 Mar 2012 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 10.0.0.7 [10.0.0.7] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1.7 debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1.7 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.7 debug2: fd 3 setting O_NONBLOCK debug3: load_hostkeys: loading entries for host "10.0.0.7" from file "/root/.ssh/known_hosts" debug3: load_hostkeys: found key type ECDSA in file /root/.ssh/known_hosts:3 debug3: load_hostkeys: loaded 1 keys debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],[email protected],[email protected],ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc(a)lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc(a)lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib(a)openssh.com,zlib debug2: kex_parse_kexinit: none,zlib(a)openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256 debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc(a)lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc(a)lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib(a)openssh.com debug2: kex_parse_kexinit: none,zlib(a)openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA b1:e8:45:37:94:57:19:11:32:83:6c:b5:05:c8:2d:6d debug3: load_hostkeys: loading entries for host "10.0.0.7" from file "/root/.ssh/known_hosts" debug3: load_hostkeys: found key type ECDSA in file /root/.ssh/known_hosts:3 debug3: load_hostkeys: loaded 1 keys debug1: Host '10.0.0.7' is known and matches the ECDSA host key. debug1: Found key in /root/.ssh/known_hosts:3 debug1: ssh_ecdsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /root/.ssh/id_rsa ((nil)) debug2: key: /root/.ssh/id_dsa ((nil)) debug2: key: /root/.ssh/id_ecdsa ((nil)) debug1: Authentications that can continue: publickey,password debug3: start over, passed a different list publickey,password debug3: preferred publickey,keyboard-interactive debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/id_rsa debug3: no such identity: /root/.ssh/id_rsa debug1: Trying private key: /root/.ssh/id_dsa debug3: no such identity: /root/.ssh/id_dsa debug1: Trying private key: /root/.ssh/id_ecdsa debug3: no such identity: /root/.ssh/id_ecdsa debug2: we did not send a packet, disable method debug1: No more authentication methods to try. Permission denied (publickey,password). The failure is Permission Denied (as above, last line). Any help really appreciated. Thanks in advance. Dave Pueblo, CO _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] MPICH 3.2 compiling error: âMPIDI_VC_tâ has no member named âpobj_mutexâ
by leicao＠andrew.cmu.edu 23 Nov '15

23 Nov '15

Got it. Thanks for the update Halim! Best, Lei > Hi Lei, > > The per-object granularity is only experimental and it is not supported. > Users are not expected to use it. > > Thanks, > --Halim > > www.mcs.anl.gov/~aamer > > On 11/23/15 8:38 PM, leicao(a)andrew.cmu.edu wrote: >> Hi, >> >> I am trying to compile mpich 3.2 but I got the following messages: >> >> CC src/mpid/ch3/src/lib_libmpi_la-ch3u_handle_connection.lo >> src/mpid/ch3/src/ch3u_handle_connection.c: In function >> 'MPIDI_CH3U_VC_SendClose': >> src/mpid/ch3/src/ch3u_handle_connection.c:225:1: error: 'MPIDI_VC_t' has >> no member named 'pobj_mutex' >> src/mpid/ch3/src/ch3u_handle_connection.c:225:1: error: 'MPIDI_VC_t' has >> no member named 'pobj_mutex' >> src/mpid/ch3/src/ch3u_handle_connection.c:225:1: error: 'MPIDI_VC_t' has >> no member named 'pobj_mutex' >> src/mpid/ch3/src/ch3u_handle_connection.c:265:1: error: 'MPIDI_VC_t' has >> no member named 'pobj_mutex' >> make[2]: *** [src/mpid/ch3/src/lib_libmpi_la-ch3u_handle_connection.lo] >> Error 1 >> make[2]: Leaving directory `/proj/plfs/mpaspvfs/mpich-3.2' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory `/proj/plfs/mpaspvfs/mpich-3.2' >> make: *** [all] Error 2 >> >> I configured mpi with the options per-object and thread multiple. >> >> Please take a look. >> >> Thanks, >> Lei Cao >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] MPICH 3.2 compiling error: ‘MPIDI_VC_t’ has no member named ‘pobj_mutex’
by Halim Amer 23 Nov '15

23 Nov '15

Hi Lei, The per-object granularity is only experimental and it is not supported. Users are not expected to use it. Thanks, --Halim www.mcs.anl.gov/~aamer On 11/23/15 8:38 PM, leicao(a)andrew.cmu.edu wrote: > Hi, > > I am trying to compile mpich 3.2 but I got the following messages: > > CC src/mpid/ch3/src/lib_libmpi_la-ch3u_handle_connection.lo > src/mpid/ch3/src/ch3u_handle_connection.c: In function > 'MPIDI_CH3U_VC_SendClose': > src/mpid/ch3/src/ch3u_handle_connection.c:225:1: error: 'MPIDI_VC_t' has > no member named 'pobj_mutex' > src/mpid/ch3/src/ch3u_handle_connection.c:225:1: error: 'MPIDI_VC_t' has > no member named 'pobj_mutex' > src/mpid/ch3/src/ch3u_handle_connection.c:225:1: error: 'MPIDI_VC_t' has > no member named 'pobj_mutex' > src/mpid/ch3/src/ch3u_handle_connection.c:265:1: error: 'MPIDI_VC_t' has > no member named 'pobj_mutex' > make[2]: *** [src/mpid/ch3/src/lib_libmpi_la-ch3u_handle_connection.lo] > Error 1 > make[2]: Leaving directory `/proj/plfs/mpaspvfs/mpich-3.2' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/proj/plfs/mpaspvfs/mpich-3.2' > make: *** [all] Error 2 > > I configured mpi with the options per-object and thread multiple. > > Please take a look. > > Thanks, > Lei Cao > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

MPICH 3.2 compiling error: MPIDI_VC_t has no member named pobj_mutex
by leicao＠andrew.cmu.edu 23 Nov '15

23 Nov '15

Hi, I am trying to compile mpich 3.2 but I got the following messages: CC src/mpid/ch3/src/lib_libmpi_la-ch3u_handle_connection.lo src/mpid/ch3/src/ch3u_handle_connection.c: In function 'MPIDI_CH3U_VC_SendClose': src/mpid/ch3/src/ch3u_handle_connection.c:225:1: error: 'MPIDI_VC_t' has no member named 'pobj_mutex' src/mpid/ch3/src/ch3u_handle_connection.c:225:1: error: 'MPIDI_VC_t' has no member named 'pobj_mutex' src/mpid/ch3/src/ch3u_handle_connection.c:225:1: error: 'MPIDI_VC_t' has no member named 'pobj_mutex' src/mpid/ch3/src/ch3u_handle_connection.c:265:1: error: 'MPIDI_VC_t' has no member named 'pobj_mutex' make[2]: *** [src/mpid/ch3/src/lib_libmpi_la-ch3u_handle_connection.lo] Error 1 make[2]: Leaving directory `/proj/plfs/mpaspvfs/mpich-3.2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/proj/plfs/mpaspvfs/mpich-3.2' make: *** [all] Error 2 I configured mpi with the options per-object and thread multiple. Please take a look. Thanks, Lei Cao _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] MPICH2 on LAN with Ubuntu 12.04
by Halim Amer 23 Nov '15

23 Nov '15

Hello Dave, The -f hostfile option works fine with newer MPICH versions. Your version of the MPICH is very old. Please try the Ubuntu packages at http://www.mpich.org/downloads/. Thanks, --Halim www.mcs.anl.gov/~aamer On 11/23/15 12:30 PM, dave wrote: > I failed to include the mpich2 version info in previous thread: > > ==================== > dave@ubuntu-desk:/home/mpiuser/cloud$ mpich2version > MPICH2 Version: 1.4.1 > MPICH2 Release date: Wed Aug 24 14:40:04 CDT 2011 > MPICH2 Device: ch3:nemesis > MPICH2 configure: --build=i686-linux-gnu --prefix=/usr > --includedir=${prefix}/include --mandir=${prefix}/share/man > --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var > --libexecdir=${prefix}/lib/mpich2 --srcdir=. --disable-maintainer-mode > --disable-dependency-tracking --disable-silent-rules --enable-shared > --prefix=/usr --enable-fc --disable-rpath --sysconfdir=/etc/mpich2 > --includedir=/usr/include/mpich2 --docdir=/usr/share/doc/mpich2 > --with-hwloc-prefix=system --enable-checkpointing > --with-hydra-ckpointlib=blcr > MPICH2 CC: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 > -Wformat -Wformat-security -g -O2 -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Wformat-security > -Werror=format-security -Wall -O2 > MPICH2 CXX: c++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 > -Wformat -Wformat-security -g -O2 -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Wformat-security > -Werror=format-security -Wall -O2 > MPICH2 F77: gfortran -g -O2 -O2 > MPICH2 FC: gfortran -O2 > dave@ubuntu-desk:/home/mpiuser/cloud$ > ========================================== > > On 11/23/2015 11:27 AM, dave wrote: >> Hello Group, >> >> Is the following statement option -F still correct? >> >> dave@ubuntu-desk:/home/mpiuser/cloud$ sudo mpiexec -f hosts.cfg -n 4 >> ./hello >> [sudo] password for dave: >> -------------------------------------------------------------------------- >> >> mpiexec was unable to launch the specified application as it could not >> find an executable: >> >> Executable: -f >> Node: ubuntu-desk >> >> while attempting to start process rank 0. >> ================================== >> >> I tried it another way too with same result: >> >> dave@ubuntu-desk:/home/mpiuser/cloud$ sudo mpiexec -n 8 machinefile >> ./hello >> -------------------------------------------------------------------------- >> >> mpiexec noticed that the job aborted, but has no info as to the process >> that caused that situation. >> -------------------------------------------------------------------------- >> >> >> Machine file, two lines, one for each machine in the network. Each >> with SSH and mpich2: >> >> ubuntu-desk-2:2 # >> ubuntu-desk # >> >> >> -------------------------------------------------------------------------- >> >> >> Any ideas about mpiexec statement or anything else to get these >> machines talking? >> >> Dave >> >> > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] MPICH2 on LAN with Ubuntu 12.04
by dave 23 Nov '15

23 Nov '15

I failed to include the mpich2 version info in previous thread: ==================== dave@ubuntu-desk:/home/mpiuser/cloud$ mpich2version MPICH2 Version: 1.4.1 MPICH2 Release date: Wed Aug 24 14:40:04 CDT 2011 MPICH2 Device: ch3:nemesis MPICH2 configure: --build=i686-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --libexecdir=${prefix}/lib/mpich2 --srcdir=. --disable-maintainer-mode --disable-dependency-tracking --disable-silent-rules --enable-shared --prefix=/usr --enable-fc --disable-rpath --sysconfdir=/etc/mpich2 --includedir=/usr/include/mpich2 --docdir=/usr/share/doc/mpich2 --with-hwloc-prefix=system --enable-checkpointing --with-hydra-ckpointlib=blcr MPICH2 CC: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -O2 MPICH2 CXX: c++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -O2 MPICH2 F77: gfortran -g -O2 -O2 MPICH2 FC: gfortran -O2 dave@ubuntu-desk:/home/mpiuser/cloud$ ========================================== On 11/23/2015 11:27 AM, dave wrote: > Hello Group, > > Is the following statement option -F still correct? > > dave@ubuntu-desk:/home/mpiuser/cloud$ sudo mpiexec -f hosts.cfg -n 4 > ./hello > [sudo] password for dave: > -------------------------------------------------------------------------- > > mpiexec was unable to launch the specified application as it could not > find an executable: > > Executable: -f > Node: ubuntu-desk > > while attempting to start process rank 0. > ================================== > > I tried it another way too with same result: > > dave@ubuntu-desk:/home/mpiuser/cloud$ sudo mpiexec -n 8 machinefile > ./hello > -------------------------------------------------------------------------- > > mpiexec noticed that the job aborted, but has no info as to the process > that caused that situation. > -------------------------------------------------------------------------- > > > Machine file, two lines, one for each machine in the network. Each > with SSH and mpich2: > > ubuntu-desk-2:2 # > ubuntu-desk # > > > -------------------------------------------------------------------------- > > > Any ideas about mpiexec statement or anything else to get these > machines talking? > > Dave > > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] MPICH2 on LAN with Ubuntu 12.04
by dave 23 Nov '15

23 Nov '15

Hello Group, Is the following statement option -F still correct? dave@ubuntu-desk:/home/mpiuser/cloud$ sudo mpiexec -f hosts.cfg -n 4 ./hello [sudo] password for dave: -------------------------------------------------------------------------- mpiexec was unable to launch the specified application as it could not find an executable: Executable: -f Node: ubuntu-desk while attempting to start process rank 0. ================================== I tried it another way too with same result: dave@ubuntu-desk:/home/mpiuser/cloud$ sudo mpiexec -n 8 machinefile ./hello -------------------------------------------------------------------------- mpiexec noticed that the job aborted, but has no info as to the process that caused that situation. -------------------------------------------------------------------------- Machine file, two lines, one for each machine in the network. Each with SSH and mpich2: ubuntu-desk-2:2 # ubuntu-desk # -------------------------------------------------------------------------- Any ideas about mpiexec statement or anything else to get these machines talking? Dave _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0