Re: [OMPI users] MPI executable fails on ArchLinux on Termux

2021-02-24 Thread LINUS FERNANDES via users
Yes, I did not receive this in my inbox since I set to receive digest.


ifconfig output:

dummy0: flags=195 mtu 1500
inet6 fe80::38a0:1bff:fe81:d4f5 prefixlen 64 scopeid 0x20
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 0
(UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 210 (210.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 0
(UNSPEC)
RX packets 17247 bytes 2062939 (1.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 17247 bytes 2062939 (1.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

p2p0: flags=4099 mtu 1500
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen
1000 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

rmnet_data0: flags=65 mtu 1500
inet 10.140.58.138 netmask 255.255.255.252
inet6 fe80::93a5:ad99:4660:adc4 prefixlen 64 scopeid 0x20
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen
1000 (UNSPEC)
RX packets 416796 bytes 376287723 (358.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 318293 bytes 69933666 (66.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

rmnet_data7: flags=65 mtu 2000
inet6 fe80::a6b7:c914:44de:639 prefixlen 64 scopeid 0x20
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen
1000 (UNSPEC)
RX packets 8 bytes 620 (620.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10 bytes 752 (752.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

rmnet_ipa0: flags=65 mtu 2000
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen
1000 (UNSPEC)
RX packets 222785 bytes 381290027 (363.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 318303 bytes 69934418 (66.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099 mtu 1500
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen
1000 (UNSPEC)
RX packets 650238 bytes 739939859 (705.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 408284 bytes 63728624 (60.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


-
ip addr output:

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group
default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: dummy0:  mtu 1500 qdisc noqueue state
UNKNOWN group default
link/ether 3a:a0:1b:81:d4:f5 brd ff:ff:ff:ff:ff:ff
inet6 fe80::38a0:1bff:fe81:d4f5/64 scope link
   valid_lft forever preferred_lft forever
3: sit0@NONE:  mtu 1480 qdisc noop state DOWN group default
link/sit 0.0.0.0 brd 0.0.0.0
4: rmnet_ipa0:  mtu 2000 qdisc pfifo_fast state UNKNOWN group
default qlen 1000
link/[530]
5: rmnet_data0:  mtu 1500 qdisc htb state UNKNOWN group
default qlen 1000
link/[530]
inet 10.140.58.138/30 scope global rmnet_data0
   valid_lft forever preferred_lft forever
inet6 fe80::93a5:ad99:4660:adc4/64 scope link
   valid_lft forever preferred_lft forever
6: rmnet_data1: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
7: rmnet_data2: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
8: rmnet_data3: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
9: rmnet_data4: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
10: rmnet_data5: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
11: rmnet_data6: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
12: rmnet_data7:  mtu 2000 qdisc htb state UNKNOWN group
default qlen 1000
link/[530]
inet6 fe80::a6b7:c914:44de:639/64 scope link
   valid_lft forever preferred_lft forever
13: r_rmnet_data0: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
14: r_rmnet_data1: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
15: r_rmnet_data2: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
16: r_rmnet_data3: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
17: r_rmnet_data4: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
18: r_rmnet_data5: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/[530]
19: r_rmnet_data6: <> mtu 1500 qdisc noop state 

Re: [OMPI users] MPI executable fails on ArchLinux on Termux

2021-02-24 Thread Gilles Gouaillardet via users

Can you run


ifconfig

or

ip addr


in both Termux and ArchLinux for Termux?



On 2/25/2021 2:00 PM, LINUS FERNANDES via users wrote:


Why do I see the following error messages when executing |mpirun| on 
ArchLinux for Termux?


The same program executes on Termux without any glitches.

|@localhost:/data/data/com.termux/files/home[root@localhost home] 
mpirun --allow-run-as-root [localhost:06773] opal_ifinit: 
ioctl(SIOCGIFHWADDR) failed with errno=13 [localhost:06773] 
pmix_ifinit: ioctl(SIOCGIFHWADDR) failed with errno=13 
[localhost:06773] oob_tcp: problems getting address for index 83376 
(kernel index -1) 
-- 
No network interfaces were found for out-of-band communications. We 
require at least one available network for out-of-band messaging.|


[OMPI users] MPI executable fails on ArchLinux on Termux

2021-02-24 Thread LINUS FERNANDES via users
Why do I see the following error messages when executing mpirun on
ArchLinux for Termux?

The same program executes on Termux without any glitches.

@localhost:/data/data/com.termux/files/home[root@localhost home]
mpirun --allow-run-as-root
[localhost:06773] opal_ifinit: ioctl(SIOCGIFHWADDR) failed with errno=13
[localhost:06773] pmix_ifinit: ioctl(SIOCGIFHWADDR) failed with errno=13
[localhost:06773] oob_tcp: problems getting address for index 83376
(kernel index -1)
--
No network interfaces were found for out-of-band communications. We require
at least one available network for out-of-band messaging.