- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
We have two users on our cluster. One can compile and run Intel cluster open MP code just fine (user A). The other can't (user B). Same source, same config file (kmp_cluster.ini). (see note below: it's something in .bashrc or .bash_profile, not surprisingly)
When user B compiles source, everything seems fine (simple "hello world" program), but trying to run executable, he gets this:
Thoughts?
When user B compiles source, everything seems fine (simple "hello world" program), but trying to run executable, he gets this:
[plain]UserB] $ ./a.out.BUser B can run user A's executable, but gets an error message that user A does not get:
Warning: cannot open configuration file /etc/man.config
./a.out: symbol lookup error: ./a.out: undefined symbol: __intel_new_proc_init
Cluster OMP Fatal: Proc#1 Thread#2 (HEARTBEAT): CAL processrsp: Can't read msg
UserB] $
[/plain]
[plain]UserB] $ ./a.out.AThe "Warning:..." is something only user B sees. If user A runs the exact same executable, he doesn't get a warning. Not sure why /etc/man.config has anything to do with anything here. Odd. Here is kmp_cluster.ini:
Warning: cannot open configuration file /etc/man.config
Hello, world!
Hello, world!
Hello, world!
Hello, world!
UserB] $
[/plain]
[plain]UserB]$ cat kmp_cluster.ini --hostlist=pleiades,n1 --process_threads=2 UserB]$ [/plain]and the source:
[cpp]#includeand the compile line:int main(int argc, char *argv[]) { #pragma omp parallel { #pragma omp critical printf("Hello, world!n"); } return 1; } [/cpp]
[plain]UserB]$ which icc /opt/intel/cce/10.1.012/bin/icc UserB]$ icc -cluster-openmp comp_hello.c -o a.out.B comp_hello.c(5): (col. 1) remark: OpenMP DEFINED REGION WAS PARALLELIZED. UserB]$ [/plain]
Thoughts?
Link kopiert
1 Antworten
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
P.S. Not surprisingly, when I copied UserA's .bashrc and .bash_profile (both users use bash) over to UserB, everything worked fine. So it's something in those two files, which is not remotely surprising of course. From here I should be able to figure it out. Apologies for taking up space with what in the end is probably something pretty trivial, but when I figure it out I'll post just for completeness anyway.

Antworten
Themen-Optionen
- RSS-Feed abonnieren
- Thema als neu kennzeichnen
- Thema als gelesen kennzeichnen
- Diesen Thema für aktuellen Benutzer floaten
- Lesezeichen
- Abonnieren
- Drucker-Anzeigeseite