 |
 |
 |
 |
 |
 |
||
 |
 |
 |
 |
 |
| 3 | 1/1 | 返回列表 |
| 查看: 656 | 回復(fù): 2 | |||
| 當(dāng)前主題已經(jīng)存檔。 | |||
wuchenwf榮譽(yù)版主 (職業(yè)作家)
|
[交流]
安裝mpich2成功后 運(yùn)行mpdtrace 出現(xiàn)的問題 謝謝各位了
|
||
|
各位前輩，大家好。小弟我的機(jī)器是4核intel的機(jī)器 采用ifort 安裝mpich2出現(xiàn)文件夾 以及所需要的 文件如 mpd 等 運(yùn)行mpd 成功 但是運(yùn)行mpdtrace后出現(xiàn)錯(cuò)誤，以下是我的操作內(nèi)容和錯(cuò)誤內(nèi)容（其中我的機(jī)器名為wuchenwf-desktop mpich2安裝路徑為/opt/mpich2） --------------------------------------------------------------------- root@wuchenwf-desktop:~# mpd & [1] 8542 root@wuchenwf-desktop:~# mpdtrace mpdtrace (send_dict_msg 426):send_dict_msg: sock= errmsg=  32, 'Broken pipe'): mpdtb: /opt/mpich2/bin/mpdlib.py, 426, send_dict_msg /opt/mpich2/bin/mpdtrace, 51, mpdtrace /opt/mpich2/bin/mpdtrace, 83, mpdtrace: unexpected msg from mpd=:{'error_msg': 'invalid secretword to root mpd'}: -------------------------------------------------------------------------- 我看好象是兩個(gè)錯(cuò)誤，而且運(yùn)行mpdallexit也出現(xiàn)相近問題 ，請(qǐng)問這個(gè)錯(cuò)誤該如何解決，麻煩各位了 十分感謝 |
回復(fù)此樓» 猜你喜歡
2026年循環(huán)經(jīng)濟(jì)功能材料國際會(huì)議（ICFMCE 2026）
已經(jīng)有0人回復(fù)
-
2026年第五屆電氣、電子與信息工程國際會(huì)議（ISEEIE 2026）
已經(jīng)有0人回復(fù)
-
物理學(xué)I論文潤色/翻譯怎么收費(fèi)?
已經(jīng)有243人回復(fù)
-
哈爾濱理工大學(xué)物理系招收物理學(xué)考研調(diào)劑
已經(jīng)有5人回復(fù)
-
0702一志愿吉大B區(qū)求調(diào)劑
已經(jīng)有5人回復(fù)
-
求調(diào)劑
已經(jīng)有0人回復(fù)
-
0702一志愿吉大B區(qū)求調(diào)劑有論文
已經(jīng)有0人回復(fù)
-
請(qǐng)問還有沒有用Latex寫文章的小伙伴們？
已經(jīng)有0人回復(fù)
-
光學(xué)工程學(xué)碩調(diào)劑信息
已經(jīng)有29人回復(fù)
-
歡迎加入課題組
已經(jīng)有0人回復(fù)
-
散金幣，求好運(yùn)，祝面上順利！
已經(jīng)有53人回復(fù)
alwens
鐵桿木蟲 (正式寫手)
老木蟲
- 應(yīng)助: 0 (幼兒園)
- 貴賓: 0.45
- 金幣: 5208.8
- 散金: 50
- 帖子: 994
- 在線: 806.6小時(shí)
- 蟲號(hào): 8486
- 注冊(cè): 2003-04-27
- 性別: GG
- 專業(yè): 藥物設(shè)計(jì)與藥物信息
|
收藏下面這篇文章對(duì)MPICH2的用戶很有用。 附：mpich2運(yùn)行mpd錯(cuò)誤debug 1. Install mpich2, and thus mpd. 2. Make sure the mpich2 bin directory is in your path. Below, we will refer to it as MPDDIR. 3. Kill old mpd processes. If you are coming to this guide from elsewhere, e.g. a Quick Start guide for mpich2, because you encountered mpd problems, you should make sure that all mpd processes are terminated on the hosts where you have been testing. mpdallexit may assist in this, but probably not if you were having problems. You may need to use the Unix kill command to terminate the processes. 4. Run a first mpd (alone on a first node). As mentioned above, mpd uses client-server communications to perform its work. So, before running an mpd, let's run a simpler program (mpdcheck) to verify that these communications are likely to be successful. Even on hosts where communications are well supported, sometimes there are problems associated with hostname resolution, etc. So, it is worth the effort to proceed a bit slowly. Below, we assume that you have installed mpd and have it in your path. Select a test node, let's call it n1. Login to n1. First, we will run mpdcheck as a server and a client. To run it as a server, get into a window with a command-line and run this: n1 $ mpdcheck -s It will print something like this: server listening at INADDR_ANY on: n1 1234 Now, run the client side (in another window if convenient) and see if it can find the server and communicate. Be sure to use the same hostname and portnumber printed by the server (above: n1 1234): n1 $ mpdcheck -c n1 1234 If all goes well, the server will print something like: server has conn on from ('192.168.1.1', 1234) server successfully recvd msg from client: hello_from_client_to_server A TROUBLESHOOTING MPDS 29 and the client will print: client successfully recvd ack from server: ack_from_server_to_client If the experiment failed, you have some network or machine configuration problem which will also be a problem later when you try to use mpd. Even if the experiment succeeded, but the hostname printed by the server was localhost, then you will probably have problems later if you try to use mpd on n1 in conjunction with other hosts. In either case, skip to Section A.2 "Debugging host/network configuration problems." If the experiment succeeded, then you should be ready to try mpd on this one host. To start an mpd, you will use the mpd command. To run parallel programs, you will use the mpiexec program. All mpd commands accept the -h or -help arguments, e.g.: n1 $ mpd --help n1 $ mpiexec --help Try a few tests: n1 $ mpd & n1 $ mpiexec -n 1 /bin/hostname n1 $ mpiexec -l -n 4 /bin/hostname n1 $ mpiexec -n 2 PATH_TO_MPICH2_EXAMPLES/cpi where PATH TO MPICH2 EXAMPLES is the path to the mpich2-1.0.3/examples directory. To terminate the mpd: n1 $ mpdallexit 5. Run a second mpd (alone on a second node). To verify that things are fine on a second host (say n2 ), login to n2 and perform the same set of tests that you did on n1. Make sure that you use mpdallexit to terminate the mpd so you will be ready for further tests. A TROUBLESHOOTING MPDS 30 6. Run a ring of two mpds on two hosts. Before running a ring of mpds on n1 and n2, we will again use mpdcheck, but this time between the two machines. We do this because the two nodes may have trouble locating each other or communicating between them and it is easier to check this out with the smaller program. First, we will make sure that a server on n1 can service a client from n2. On n1: n1 $ mpdcheck -s which will print a hostname (hopefully n1) and a portnumber (say 3333 here). On n2: n2 $ mpdcheck -c n1 3333 If this experiment fails, skip to Section A.2 "Debugging host/network configuration problems". Second, we will make sure that a server on n2 can service a client from n1. On n2: n2 $ mpdcheck -s which will print a hostname (hopefully n2) and a portnumber (say 7777 here). On n2: n2 $ mpdcheck -c n2 7777 If this experiment fails, skip to Section A.2 "Debugging host/network configuration problems". If all went well, we are ready to try a pair of mpds on n1 and n2. First, make sure that all mpds have terminated on both n1 and n2. Use mpdallexit or simply kill them with: kill -9 PID_OF_MPD where you have obtained the PID OF MPD by some means such as the ps command. On n1: A TROUBLESHOOTING MPDS 31 n1 $ mpd & n1 $ mpdtrace -l This will print a list of machines in the ring, in this case just n1. The output will be something like: n1_6789 (192.168.1.1) The 6789 is the port that the mpd is listeneing on for connections from other mpds wishing to enter the ring. We will use that port in a moment to get an mpd from n2 into the ring. The value in parentheses should be the IP address of n1. On n2: n2 $ mpd -h n1 -p 6789 & where 6789 is the listening port on n1 (from mpdtrace above). Now try: n2 $ mpdtrace -l You should see both mpds in the ring. To run some programs in parallel: n1 $ mpiexec -n 2 /bin/hostname n1 $ mpiexec -n 4 /bin/hostname n1 $ mpiexec -l -n 4 /bin/hostname n1 $ mpiexec -l -n 4 PATH_TO_MPICH2_EXAMPLES/cpi where PATH TO MPICH2 EXAMPLES is the path to the mpich2-1.0.5/examples directory. To bring down the ring of mpds: n1 $ mpdallexit 7. Boot a ring of two mpds via mpdboot. Please be aware that mpdboot uses ssh by default to start remote mpds. It will expect that you can run ssh from n1 to n2 (and from n2 to n1) without entering a password. First, make sure that you terminate the mpd processes from any prior tests. On n1, create a file named mpd.hosts containing the name of n2: A TROUBLESHOOTING MPDS 32 n2 Then, on n1 run: n1 $ mpdboot -n 2 n1 $ mpdtrace -l n1 $ mpiexec -l -n 2 /bin/hostname The mpdboot command should read the mpd.hosts file created above and run an mpd on each of the two machines. The mpdtrace and mpiexec show the ring up and functional. Options that may be useful are: · --help use this one for extra details on all options · -v (verbose) · --chkup tries to verify that the hosts are up before starting mpds · --chkuponly only performs the verify step, then ends To bring the ring down: n1 $ mpdallexit If mpdboot works on the two machines n1 and n2, it will probably work on your others as well. But, there could be configuration problems using a new machine on which you have not yet tested mpd. An easy way to check, is to gradually add them to mpd.hosts and try an mpdboot with a -n arg that uses them all each time. Use mpdallexit after each test. [ Last edited by alwens on 2008-1-18 at 14:32 ] |
2樓2008-01-18 14:31:21
相關(guān)版塊跳轉(zhuǎn)
我要訂閱樓主 wuchenwf 的主題更新
| 3 | 1/1 | 返回列表 |
| 最具人氣熱帖推薦 [查看全部] | 作者 | 回/看 | 最后發(fā)表 | |
|---|---|---|---|---|
|
[考研]
 271材料工程求調(diào)劑
+5
|
.6lL 2026-03-18 | 5/250 |
|
|---|---|---|---|---|
|
|
[考研] 085600材料與化工調(diào)劑 324分 +8 | llllkkkhh 2026-03-18 | 8/400 |
|
|
|
[考研] 328求調(diào)劑，英語六級(jí)551，有科研經(jīng)歷 +3 | 生物工程調(diào)劑 2026-03-16 | 10/500 |
|
|
|
[考研] 328求調(diào)劑，英語六級(jí)551，有科研經(jīng)歷 +3 | 生物工程調(diào)劑 2026-03-17 | 7/350 |
|
|
[考研] 一志愿武理材料305分求調(diào)劑 +5 | 想上岸的鯉魚 2026-03-18 | 6/300 |
|
|
|
[考研] 307求調(diào)劑 +3 | 冷笙123 2026-03-17 | 3/150 |
|
|
|
[考研] 278求調(diào)劑 +5 | 煙火先于春 2026-03-17 | 5/250 |
|
|
|
[碩博家園] 湖北工業(yè)大學(xué) 生命科學(xué)與健康學(xué)院-課題組招收2026級(jí)食品/生物方向碩士 +3 | 1喜春8 2026-03-17 | 5/250 |
|
|
|
[考研] 085601求調(diào)劑 +4 | Du.11 2026-03-16 | 4/200 |
|
|
|
[考研] 26考研求調(diào)劑 +6 | 丶宏Sir 2026-03-13 | 6/300 |
|
|
|
[考研] 304求調(diào)劑 +4 | ahbd 2026-03-14 | 4/200 |
|
|
|
[考研] 085600調(diào)劑 +5 | 漾漾123sun 2026-03-12 | 6/300 |
|
|
|
[考研] 22408總分284求調(diào)劑 +3 | InAspic 2026-03-13 | 3/150 |
|
|
|
[考研] 080500，材料學(xué)碩302分求調(diào)劑學(xué)校 +4 | 初識(shí)可樂 2026-03-14 | 5/250 |
|
|
|
[考研] 中科大材料專碩319求調(diào)劑 +3 | 孟鑫材料 2026-03-13 | 3/150 |
|
|
|
[考研] 328求調(diào)劑 +3 | 5201314Lsy！ 2026-03-13 | 6/300 |
|
|
|
[考研] 266求調(diào)劑 +4 | 學(xué)員97LZgn 2026-03-13 | 4/200 |
|
|
|
[考研] 304求調(diào)劑 +6 | Mochaaaa 2026-03-12 | 7/350 |
|
|
|
[考研] 求調(diào)劑 +5 | 一定有學(xué)上- 2026-03-12 | 5/250 |
|
|
|
[考研] 333求調(diào)劑 +3 | 152697 2026-03-12 | 4/200 |
|